Proxmox 6.8.12-9-pve kernel has introduced a problem with e1000e Driver and network connection lost after some hours

6.8.12-11-pve was released for both PVE and PBS, there were some changes to the ABI.
https://git.proxmox.com/?p=pve-kernel.git;a=shortlog;h=refs/heads/bookworm-6.8

ABI stands for Application Binary Interface. It defines the low-level interface between the kernel and its modules (such as device drivers), specifying how compiled code interacts with the kernel at the binary level. This includes details like register usage, memory layout, calling conventions, and symbol versions of exported kernel functions and variables
Click to expand...
 
I still have this issue also with kernel 6.8.12-11-pve. Will this be fixed in a future kernel or do I have to apply the ethtool workaround?
 
For what it's worth (and may help in the debug process): I have 3 Systems in my Home Lab with Intel 217/219 NICs.

Only the 217-LM (Rev04) is affected by freezes. The other systems with 219-V (Rev 21) and 219-V (Rev 31) are working fine with all kernels up
to 6.8.12-10-pve (did not test -11 so far).

Main production Servers with Intel X710 and X550 are also working fine with kernels -8, -9 and -10.
 
  • Like
Reactions: sammyke007 and leandrosgf
PwrBank said:
We have a few machines with `Intel Corporation Ethernet Connection (17) I219-LM (rev 11)` that are having this issue on the 6.8.12-11-pve kernel.
Click to expand...
Thanks for letting us know. We should wait for a fix in a future kernel. We hope to have someone from Proxmox looking into this soon.
Meanwhile, still running the pinned 6.8.12-8
 
I also have this issue, all my LXCs lose connection on sporadic intervals but always many hours apart, I have uptimekuma set up on a different server to monitor this for me and it shows.

Network card:

07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

PVE:

proxmox-ve: 8.4.0 (running kernel: 6.8.12-10-pve)
 
Last edited:
I've upgraded my system on Tuesday from 6.8.12-10-pve to 6.8.12-11-pve and it is still online, so yesterday I updated another system, which is technically identical. That one froze just few hours after the upgrade. The main difference is that the second one is also running PBS in a PVE VM.
 
Last edited:
Is it possible that on a network card so common in millions of PCs this very serious bug is still present? absurd
 
I forgot tomention that I had implemented the offloading config in /etc/network/interfaces on my system. So that did help here.

1748803866098.png
 
You must log in or register to reply here.
Top Bottom