Proxmox boot errors

yarii

Renowned Member
Mar 24, 2014
145
8
83
[ 10.984549] VFIO - User Level meta-driver version: 0.3
[ 11.469416] systemd-journald[873]: Received client request to flush runtime journal.
[ 12.249335] power_meter ACPI000D:00: Found ACPI power meter.
[ 12.269933] power_meter ACPI000D:00: Ignoring unsafe software power cap!
[ 12.278099] acpi-tad ACPI000E:00: Unsupported capabilities
[ 12.289092] power_meter ACPI000D:00: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().

[ 12.344429] IPMI message handler: version 39.2
[ 12.360471] ioatdma: Intel(R) QuickData Technology Driver 5.00
[ 12.380475] ipmi device interface
[ 12.397675] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 12.404782] ------------[ cut here ]------------
[ 12.432205] ioatdma 0000:00:04.1: failed to start channel chanerr: 0x0
[ 12.449170] WARNING: CPU: 21 PID: 948 at drivers/dma/ioat/init.c:757 ioat_alloc_chan_resources+0x1e7/0x210 [ioatdma]
[ 12.466790] Modules linked in: drm_kms_helper(+) pcspkr ipmi_devintf ioatdma(+) hpilo i2c_algo_bit fjes(-) ipmi_msghandler acpi_tad acpi_power_meter joydev input_leds mac_hid vhost_net vhost vhost_iotlb tap vfio_pci vfio_pci_core irqbypass vfio_iommu_type1 vfio iommufd efi_pstore drm dmi_sysfs ip_tables x_tables autofs4 zfs(PO) spl(O) btrfs blake2b_generic xor raid6_pq libcrc32c simplefb mlx5_ib ib_uverbs ib_core hid_generic usbkbd usbmouse usbhid hid mlx5_core ixgbe ses enclosure mlxfw xhci_pci psample xfrm_algo tls xhci_pci_renesas dca crc32_pclmul mdio pci_hyperv_intf uhci_hcd i2c_i801 ehci_pci xhci_hcd tg3 hpsa lpc_ich i2c_smbus ehci_hcd scsi_transport_sas wmi
[ 12.466827] CPU: 21 PID: 948 Comm: (udev-worker) Tainted: P O 6.5.13-1-pve #1
[ 12.466830] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 04/29/2021
[ 12.466831] RIP: 0010:ioat_alloc_chan_resources+0x1e7/0x210 [ioatdma]
[ 12.466839] Code: 75 07 4c 8b a8 d0 00 00 00 48 8d b8 d0 00 00 00 e8 ae 25 44 dd 44 89 e1 4c 89 ea 48 c7 c7 f8 28 25 c1 48 89 c6 e8 39 13 aa dc <0f> 0b 48 89 df e8 8f fa ff ff b8 f2 ff ff ff e9 3e fe ff ff b8 f4
[ 12.466841] RSP: 0018:ffffbafcb147f7f8 EFLAGS: 00010246
[ 12.466842] RAX: 0000000000000000 RBX: ffff9115cb567400 RCX: 0000000000000000
[ 12.466844] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 12.466845] RBP: ffffbafcb147f820 R08: 0000000000000000 R09: 0000000000000000
[ 12.466846] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 12.466846] R13: ffff911583b1d2e0 R14: ffff9115cb567558 R15: ffff9115aa07b000
[ 12.466847] FS: 00007a0204a2d8c0(0000) GS:ffff9153ffb40000(0000) knlGS:0000000000000000
[ 12.466849] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 12.466850] CR2: 00005cb4d7b2e028 CR3: 0000000114e58006 CR4: 00000000003706e0
[ 12.466851] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 12.466852] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 12.466852] Call Trace:
[ 12.466854] <TASK>
[ 12.466856] ? show_regs+0x6d/0x80
[ 12.466862] ? __warn+0x89/0x160
[ 12.466868] ? ioat_alloc_chan_resources+0x1e7/0x210 [ioatdma]
[ 12.466874] ? report_bug+0x17e/0x1b0
[ 12.466879] ? irq_work_queue+0x2f/0x70
[ 12.466883] ? handle_bug+0x46/0x90
[ 12.466887] ? exc_invalid_op+0x18/0x80
[ 12.466888] ? asm_exc_invalid_op+0x1b/0x20
[ 12.466893] ? ioat_alloc_chan_resources+0x1e7/0x210 [ioatdma]
[ 12.466899] ? ioat_alloc_chan_resources+0x1e7/0x210 [ioatdma]
[ 12.466904] ? kmalloc_trace+0x2a/0xb0
[ 12.466908] ioat_pci_probe+0x6cf/0xd00 [ioatdma]
[ 12.466915] local_pci_probe+0x47/0xb0
[ 12.466920] pci_device_probe+0xc5/0x260
[ 12.466925] really_probe+0x1cc/0x430
[ 12.466928] __driver_probe_device+0x8c/0x190
[ 12.466930] driver_probe_device+0x24/0xd0
[ 12.466931] __driver_attach+0x10b/0x210
[ 12.466933] ? __pfx___driver_attach+0x10/0x10
[ 12.466935] bus_for_each_dev+0x8d/0xf0
[ 12.466939] driver_attach+0x1e/0x30
[ 12.466942] bus_add_driver+0x127/0x240
[ 12.466945] driver_register+0x5e/0x130
[ 12.466947] ? __pfx_ioat_init_module+0x10/0x10 [ioatdma]
[ 12.466954] __pci_register_driver+0x62/0x70
[ 12.466956] ioat_init_module+0x90/0xff0 [ioatdma]
[ 12.466962] ? __pfx_ioat_init_module+0x10/0x10 [ioatdma]
[ 12.466967] do_one_initcall+0x5e/0x340
[ 12.466973] do_init_module+0x68/0x260
[ 12.466978] load_module+0x213a/0x22a0
[ 12.466982] ? security_kernel_post_read_file+0x75/0x90
[ 12.466986] init_module_from_file+0x96/0x100
[ 12.466989] ? init_module_from_file+0x96/0x100
[ 12.466992] idempotent_init_module+0x11c/0x2b0
[ 12.466995] __x64_sys_finit_module+0x64/0xd0
[ 12.466998] do_syscall_64+0x5b/0x90
[ 12.467001] ? ksys_mmap_pgoff+0x120/0x240
[ 12.467004] ? __secure_computing+0x89/0xf0
[ 12.467007] ? exit_to_user_mode_prepare+0x39/0x190
[ 12.467010] ? syscall_exit_to_user_mode+0x37/0x60
[ 12.467013] ? do_syscall_64+0x67/0x90
[ 12.467015] ? do_syscall_64+0x67/0x90
[ 12.467017] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 12.467019] RIP: 0033:0x7a020513a719
[ 12.467034] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 06 0d 00 f7 d8 64 89 01 48
[ 12.467035] RSP: 002b:00007ffe29c8c108 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 12.467037] RAX: ffffffffffffffda RBX: 00005cb4d7b50f80 RCX: 00007a020513a719
[ 12.467038] RDX: 0000000000000000 RSI: 00007a02052cdefd RDI: 0000000000000006
[ 12.467038] RBP: 00007a02052cdefd R08: 0000000000000000 R09: 00005cb4d7adeb80
[ 12.467039] R10: 0000000000000006 R11: 0000000000000246 R12: 0000000000020000
[ 12.467040] R13: 0000000000000000 R14: 00005cb4d7b2d560 R15: 00005cb4d5ab9ec1
[ 12.467043] </TASK>
[ 12.467043] ---[ end trace 0000000000000000 ]---
[ 12.471059] ioatdma 0000:00:04.1: selftest cannot allocate chan resource
[ 13.673526] ioatdma 0000:00:04.1: Intel(R) I/OAT DMA Engine init failed


Linux vps3 6.5.13-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-1 (2024-02-05T13:50Z) x86_64 GNU/Linux
pve-manager/8.1.4/ec5affc9e41f1d79 (running kernel: 6.5.13-1-pve)

The hardware is:
HP DL380 G9

What to do with that - is it dangerous?

Regards
JK
 
I/OAT DMA Engine init failed
Is I/OAT enabled in BIOS config. (usually under integrated devices).
There have been various bugs around with Intel QuickData Technology over the years.
I can't really add much more - you'll have to research the topic yourself. Consider any recent updates you committed - if this error/warning is new.

As to your question if its dangerous - well its not going to explode!
You may experience some latency - but I don't believe its going to cause DMA errors.

Disclaimer: I don't have/use I/OAT DMA
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!