e1000e eno1: Detected Hardware Unit Hang:

Anyone tried Proxmox v9 with the new kernel and see if they get any hangs ?
I have a Realtek usb 2.5gbe and experience similar network issues with newer kernels than 6.8.12-8-pve.

With 6.8.12-8-pve all is very stable.
 
Is-This-Heaven said:
Anyone tried Proxmox v9 with the new kernel and see if they get any hangs ?
I have a Realtek usb 2.5gbe and experience similar network issues with newer kernels than 6.8.12-8-pve.

With 6.8.12-8-pve all is very stable.
Click to expand...
In another thread, it was mentioned that the issue persists with Proxmox V9 and the corresponding kernel. > https://forum.proxmox.com/threads/e1000-driver-hang.58284/page-17#post-789226

The solution that currently works for me:

Code: 
uname -r
6.8.12-8-pve
+
Code: 
ethtool -K eno1 gso off gro off tso off
+
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"

=

No Problems since yesterday.

Code: 
date && journalctl | grep "Detected Hardware Unit Hang" | cut -c1-6 | uniq -c
Sun Aug 10 01:27:11 PM CEST 2025
    344 Aug 08
    753 Aug 09
 
Last edited:
Just a small pointer: my e1000 card went offline while I'm on vacation so unfortunately, I cannot currently fix it. Shortly before, I updated my Proxmox 8 using apt upgrade. So the pinning suggestions here seem to work only as long as you're not doing apt updates. I'll be switching the network card now. I highly suggest looking into the self-healing scripts posted here if you guys are staying with the e1000 network adapter.
 
c0by said:
In another thread, it was mentioned that the issue persists with Proxmox V9 and the corresponding kernel. > https://forum.proxmox.com/threads/e1000-driver-hang.58284/page-17#post-789226

The solution that currently works for me:

Code: 
uname -r
6.8.12-8-pve
+
Code: 
ethtool -K eno1 gso off gro off tso off
+
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"

=

No Problems since yesterday.

Code: 
date && journalctl | grep "Detected Hardware Unit Hang" | cut -c1-6 | uniq -c
Sun Aug 10 01:27:11 PM CEST 2025
    344 Aug 08
    753 Aug 09
Click to expand...
still stable...

Code: 
uname -r
6.8.12-8-pve

uptime
 20:03:05 up 2 days, 21:44,  1 user,  load average: 0.52, 0.63, 0.60

date && journalctl | grep "Detected Hardware Unit Hang" | cut -c1-6 | uniq -c
Tue Aug 12 08:03:09 PM CEST 2025
    344 Aug 08
    753 Aug 09
 
Just a few minutes ago, no fixes applied yet as it's a new server which ran for several weeks without any issues so far:

Code: 
Aug 19 14:02:41 theia kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                                TDH                  <64>
                                TDT                  <75>
                                next_to_use          <75>
                                next_to_clean        <63>
                              buffer_info[next_to_clean]:
                                time_stamp           <1869482ba>
                                next_to_watch        <64>
                                jiffies              <186948a80>
                                next_to_watch.status <0>
                              MAC Status             <80083>
                              PHY Status             <796d>
                              PHY 1000BASE-T Status  <3800>
                              PHY Extended Status    <3000>
                              PCI Status             <10>

Version:
Code: 
root@theia:~# uname -r
6.8.12-13-pve

Will try the workarounds mentioned above.
 
I have 2 identical machines both running Proxmox (more than a year), I accidentally update one of the machine to latest version and it starting having this issue. I've read a countless thread of this issue but I'm still confused is this a problem on Intel side (driver bug) or is it from Proxmox side? If it's from Intel side, why is the older version of Proxmox doesn't have this issue?

Can this be fixed from Proxmox side and if there's any plan/ETA for the fix? (not workaround like hardware offloading solution).

Thank you
 
warheat1990 said:
I have 2 identical machines both running Proxmox (more than a year), I accidentally update one of the machine to latest version and it starting having this issue. I've read a countless thread of this issue but I'm still confused is this a problem on Intel side (driver bug) or is it from Proxmox side? If it's from Intel side, why is the older version of Proxmox doesn't have this issue?

Can this be fixed from Proxmox side and if there's any plan/ETA for the fix? (not workaround like hardware offloading solution).

Thank you
Click to expand...
I very much would like to know the answer to this as well. If it is a Proxmox side issue, why has it not been corrected in the updates. This seems to be a very prevalent issue. If it is a Intel side issue, what would cause it to only have started since the updates.

I have the issue as well on only one of my nodes and it keeps causing my entire smart home to go down each time. Please PROXMOX or INTEL figure this out. The workaround doesn't seem to do it for me though.
 
To add my voice to the list of folks with issues, I updated my system mid-July and started having issues shortly after. Just updated to the latest 8x Proxmox and problem still exists. Tried the fix of `ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg off` and that worked for about 12 hours, but issue has arisen again. Next step is rolling back the kernel to see if that fixes it.
 
pkkrusty said:
To add my voice to the list of folks with issues, I updated my system mid-July and started having issues shortly after. Just updated to the latest 8x Proxmox and problem still exists. Tried the fix of `ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg off` and that worked for about 12 hours, but issue has arisen again. Next step is rolling back the kernel to see if that fixes it.
Click to expand...
Kernel rollback worked for a while, but still seeing the problem.
 
Kernel rollback definitely does not solve the issue completely. Rolled back to 6.8.12-8 and it eventually hung. Updated to newest kernel and created a linux bond for automatic backup with a usb to lan conn. Im kind of confused if this is a network card problem or Proxmoxs.
 
Same here apparently.

As a noob, I first thought the computer (Esprimo E520 E85+) froze totally and I suspected a hardware problem. So I replaced the hardware with an HP ProDesk 600 G4 SFF. Currently Running PVE 8.4.12.

The problem occurs mainly when a remote backup system (Windows) copies files from an Openmediavault QEMU.
 
Hi everybody. Just want to let you know that in my previous post I had mentioned that on my system I had rolled back to Proxmox VE kernel 6.8.12-8 and it eventually hung. I didn't notice at the time of the post that PVE had updated to kernel 6.8.12-13 and that was the reason for the hanging. I eventually rolled back again to 6.8.12-8, disabled other kernels and updates and my system has had no hangings since then (almost a week). I will keep watching it closely, but if this helps anyone then great.
 
glcarlos said:
Hi everybody. Just want to let you know that in my previous post I had mentioned that on my system I had rolled back to Proxmox VE kernel 6.8.12-8 and it eventually hung. I didn't notice at the time of the post that PVE had updated to kernel 6.8.12-13 and that was the reason for the hanging. I eventually rolled back again to 6.8.12-8, disabled other kernels and updates and my system has had no hangings since then (almost a week). I will keep watching it closely, but if this helps anyone then great.
Click to expand...

For future reference, as I presume users will keep on visiting this thread:

Code: 
dpkg -l |grep proxmox-kernel
proxmox-boot-tool kernel pin 6.8.12-8-pve

And reboot.

P.S. Not sure if I already posted this before... :D
 
  • Like
Reactions: glcarlos
You must log in or register to reply here.
Top Bottom