[SOLVED] Intel NIC e1000e hardware unit hang

[sloppyjoe]

that seems to have fixed it for me.
I have no performance problems and no more problems are visible in the log since then:

ethtool -K eth0 gso off gro off tso off tx off rx off rxvlan off txvlan off

Really appreciate the help with this as the constant disconnects were driving me crazy!

This fixed my issues with the Intel i219 adapter in my Lenovo M920q.

It seems that this fix needs to be applied every time you restart. So remember to set it up in systemctl or however you run your startup scripts.

lspci | grep -i ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)

 

[RedNano]

Hi all!! I just moved from ESXi yesterday and I'm noticing this same error on my NUC10FNH.

Does applying "ethtool -K eth0 gso off gro off tso off tx off rx off rxvlan off txvlan off" solve the issue?
Should all vms be powered off to apply this?

 

[Sunrise]

I have the same problem. Proxmox runs on an old laptop.
The error appears every 1,5 - 6 weeks. Only restarting helps.
Ideas?

 

[RedNano]

Hi!!!
has this been solved in recent proxmox patches?

 

[parallax]

I have the same issue on one of my Proxmox servers.
BUT i have exactly the same server running Proxmox without any issues.
Both newly installed, Proxmox up to date, same BIOS version, same offloading settings,...

If someone can point me in the right direction to debug this, it seems a very good usecase as i have 2 servers with identical hardware.

 

[TErxleben]

I have the same issue on one of my Proxmox servers.
BUT i have exactly the same server running Proxmox without any issues.
Both newly installed, Proxmox up to date, same BIOS version, same offloading settings,...

If someone can point me in the right direction to debug this, it seems a very good usecase as i have 2 servers with identical hardware.

I have the exact same problem here. I have now made the modification

ethtool -K vmbr0 gso off gro off tso off tx off rx off rxvlan off txvlan of
ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan of

on the Proxmoxhost and will report further.

 

[chris8837]

Really appreciate the help with this as the constant disconnects were driving me crazy!

This fixed my issues with the Intel i219 adapter in my Lenovo M920q.

It seems that this fix needs to be applied every time you restart. So remember to set it up in systemctl or however you run your startup scripts.

lspci | grep -i ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)

Do you have a turorial on how to run this everytime it reboots? New to all this

 

[rocha.best]

Same issue here,

Starts with 8.3.0 PVE version, only on heavy-load (abobe 60/70% throughput of 1GbE onboard interface (Intel I219-LM).

On 8.3.4 PVE version, few days after update, we completely lost connection at night.
Host rebooted, connectivity ok.
Next day, same issue.
Update to 8.3.5 - no changes at all.

Since yesterday (2025-04-01), after few hours working, it is dead again.
{ PVE current Version - pve-manager/8.3.5/dac3aa88bac3f300 (running kernel: 6.8.12-9-pve) }

Syslog shows the same error message over and over again.


kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:


Today, from 8:00AM to 10:30AM, more than 4300 records from message above.

Server rebooted again, 2,5 hours working, same issue again.

After this last reboot, used this command to check flags...

/sbin/ethtool -k enp0s31f6

And this to set flags...
(run at 2025-04-02@17:03 (UTC))

/sbin/ethtool -K enp0s31f6 tx off rx off



I have tried to edit the /etc/network/if-up.d/ethtool2 file, adding "/sbin/ethtool -K enp0s31f6 tx off rx off" on it, NO SUCCESS.

So, I have edited the /etc/network/interfaces file, add some parameters on file, as follows.

iface enp0s31f6 inet manual
post-up /sbin/ethtool -K enp0s31f6 tx off rx off


Finally, I have checked the "results"

"
root@hostname:~# /sbin/ethtool -k enp0s31f6
Features for enp0s31f6:
rx-checksumming: off
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
tx-tcp-segmentation: off [requested on]
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: off [requested on]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-gre-csum-segmentation: off [fixed]
tx-ipxip4-segmentation: off [fixed]
tx-ipxip6-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-udp_tnl-csum-segmentation: off [fixed]
tx-gso-partial: off [fixed]
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: off [fixed]
tx-gso-list: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off
macsec-hw-offload: off [fixed]
rx-udp-gro-forwarding: off
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]
"

It is under monitoring for at least two weeks.


If anyone has more thoughts about it, feel free to share