[SOLVED] [Proxmox 8] [Kernel 6.2.16-4-pve]: ixgbe driver fails to load due to PCI device probing failure

I updated to PVE 8.2.2, which updates the kernel to version 6.8, removed my custom kernel parameters, and all is working correctly.
Which controller are you using? The X550 is not working for me with 6.8.8-2-pve. 6.1.10-1-pve is the last functioning version. :/
 
Which controller are you using? The X550 is not working for me with 6.8.8-2-pve. 6.1.10-1-pve is the last functioning version. :/
Whoops. Sorry for never getting back to you on this. My device is a SAS2308 card built into the motherboard.
 
  • Like
Reactions: dff
Another HP Proliant ML30 g9 with X520 here.
Same OP ixgbe dmesg errors with kernel 6.8.12-2-pve on pbs server. Rollback to 6.8.8-3-pve recovered nic.
 
Another HP Proliant ML30 g9 with X520 here.
Same OP ixgbe dmesg errors with kernel 6.8.12-2-pve on pbs server. Rollback to 6.8.8-3-pve recovered nic.
Would you please send the complete dmesg logs from 6.8.8-3-pve and 6.8.12-2-pve to bjorn@helgaas.com? I assume those are Proxmox kernels; are the sources available anywhere so I could compare them?
 
I have Supermicro X9DRi-LN4+/X9DR3-LN4+, integrated Ethernet Intel I350 network card.
After updating and rebooting to kernel 6.8.12-5, I saw that my network adapter is not visible in the system
In dmesg I found an error:
Code:
[    3.018745] igb 0000:06:00.0: BAR 0: can't reserve [mem 0x80000000-0x8001ffff]
[    3.022349] igb: probe of 0000:06:00.0 failed with error -16
I have an update for anyone who comes across this thread in the future. Shortly after my last post, I came across this thread.

It has exactly the solution I needed! Here is the important part:

Personally, I used the "pci=realloc=off" kernel boot parameter and it's been solid. I also tested the "pci=nommconf" parameter and it worked, as well. I couldn't get the "reserve" parameter to work, but I'm pretty sure that's because I wasn't doing it right.

From what I've read, this problem will be fixed in kernel 6.8, and the Proxmox devs may even be working on backporting it to an earlier pve-kernel. At that point, you would be able to remove whichever kernel boot parameter you decided on.

I hope this helps!

Thank you very much for your work! Setting the kernel parameter "pci=realloc=off" helped me.
I also came across this topic while searching for a solution to my problem.
I have dmesg dumps without the parameter "pci=realloc=off" and with this parameter. I assume that this can be useful for solving the kernel problem. I will attach this data.
 

Attachments

  • Like
Reactions: GraceAboundz