Intel e1000e Regression Causing Proxmox Host Freezes — Resolved by Removing Onboard NIC

WDT

New Member
Mar 28, 2026
1
0
1

Problem Summary:

Two Proxmox nodes with Intel onboard NICs (I217/I219 family) suddenly began experiencing intermittent freezes, SSH drops, and bridge instability. Both nodes had been stable for years. The failures began simultaneously after recent kernel updates.

Symptoms Observed:

  • SSH sessions dropping
  • VPN VM losing connectivity
  • vmbr0 flapping or freezing
  • Host temporarily unreachable
  • No logs indicating a clean shutdown
  • Both nodes affected identically
  • Only the onboard NIC (e1000e driver) showed issues
  • PCIe NICs remained stable

Root Cause:

A regression in the Intel e1000e driver introduced instability in the onboard NICs. Even when not actively carrying traffic, the NIC could hang internally and lock the kernel’s network stack.

Both nodes shared the same NIC family and kernel version, so both were affected at the same time.

Solution:

  1. Migrated vmbr0 off the onboard NIC to a stable PCIe NIC
  2. Removed the failing NIC from the bridge
  3. Blacklisted the e1000e driver:

    Code

    echo "blacklist e1000e" &gt; /etc/modprobe.d/blacklist-eno1.conf<br>update-initramfs -u<br>
  4. Rebooted the host
  5. Verified the driver was no longer loaded
  6. (Planned) Disable the onboard NIC in BIOS for permanent removal

Outcome:

  • System stability fully restored
  • No further freezes or network drops
  • VPN VM autostarted correctly
  • vmbr0 now runs exclusively on the healthy PCIe NIC
  • Environment stable for 24+ hours post‑fix

Why This Matters:

Intel’s e1000e driver has a long history of regressions across kernel versions. A kernel update can destabilize previously reliable hardware. Removing the NIC from service is often safer than attempting to tune or patch around the issue.

Word smithed by AI, verified results WDT
 
I had the same problem on one host yesterday.
Thought this was solved over a year ago.

modify /etc/network/interfaces with a post-up command helped.

Code:
iface eno1 inet manual
        post-up ethtool -K eno1 tso off gso off
 
  • Like
Reactions: Kingneutron
Also, no poweroff or restarts (console dissapears, but that's it);
if I219 is in a bridge, last two lines in console are:
Code:
e1000e: EEE TX LPI TIMER: 00000000
ACPI: Preparing to enter sleep state S5
sometime followed by a dump trace
e1000e blacklist won't work (prpbably because of AMT/ME)
 
Last edited:
I am seeing the same instability with the latest 6.17 kernel. I am going to upgrade to the 7.0 kernel that was released today.
 
added
Code:
rmmod e1000e
in a 3-seconds delayed cron job, using the interface cony for AMT purposes
 
Was running fine for the last week on the 7.0 kernel but I had the e1000e crash this morning. Updated to Kernel 7.0.2-2 today.
 
used op's solution, e1000e is successfully blacklisted (first time i was writing wrong command)
still getting (at restart) "Preparing to enter sleep state S5" and dump trace after a timeout of 120 seconds, repeated.
maybe it;s also another thing implied.