I am getting the following error in proxmox, I have noticed the server hangs at times. I have tried different cables but now I am thinking its the network interface. I am using a ASROCK z790 Taichi Lite and only using the 1g Intel^® I219V port. I have uptime kuma installed in a few locations that keep have basically narrowed the problem down to the port of the ethernet cable in the port(already changed but I ran a test on the cable with my klein cable tester and it passed). It seems completely random as most of the times I works fine.

May 29 06:03:09 pve kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <7a>
TDT <8d>
next_to_use <8d>
next_to_clean <79>
buffer_info[next_to_clean]:
time_stamp <149f43bf1>
next_to_watch <7a>
jiffies <149f44300>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
May 29 06:03:11 pve corosync[2125]: [TOTEM ] Token has not been received in 3225 ms
May 29 06:03:12 pve kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <7a>
TDT <8d>
next_to_use <8d>
next_to_clean <79>
buffer_info[next_to_clean]:
time_stamp <149f43bf1>
next_to_watch <7a>
jiffies <149f44b00>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>

Hi r/Proxmox,

I'm having a tough time with my Proxmox server. It keeps losing its network connection, and I can't figure out why. I'm using an Intel i219-lm network card. Here's what's happening:

Connection is Hit or Miss: Sometimes my server connects to the internet, and sometimes it just doesn't.
DHCP vs. Static IP: When I set it to get an IP automatically (DHCP), it's a bit better but still drops out in the middle of things. When I try to give it a fixed IP (static), it's worse, especially when I try to set up VLANs.
VLAN Problems: Every time I try to set up VLANs with a static IP, the server doesn't respond, even if I get it to work in the first place.
CLI Works Fine: The weird thing is, I can always use the command line directly on the server. So, it seems like only the network part is messing up.
Network Setup: My server connects to an Aruba switch. This switch has a normal VLAN for management and other special VLANs. I also have an OPNsense firewall.
It's Just This Server: No other device in my network has this problem.

I've tried using both automatic and fixed IP settings, and I've tried setting up VLANs, but no luck. Has anyone else had trouble like this, especially with the Intel i219-lm card in a Proxmox setup? I'd really appreciate any tips or ideas to fix this.

*Would installing Debian and Proxmox on top of it help? Above installation was always done via Proxmox iso. Yes, I have reinstalled it at least 5 times.

Thanks!

I have a HP Elitedesk 800 G6 DM running PVE9. When a Win10 VM heavily stresses the i219-LM, PVE crashes with a kernel log message indicating that the NIC is hanging.

Sep 11 23:09:54 pve5 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
  TDH                  <4c>
  TDT                  <74>
  next_to_use          <74>
  next_to_clean        <4b>
buffer_info[next_to_clean]:
  time_stamp           <100522f40>
  next_to_watch        <4c>
  jiffies              <100525cc0>
  next_to_watch.status <0>
MAC Status             <80483>
PHY Status             <796d>
PHY 1000BASE-T Status  <3800>
PHY Extended Status    <3000>
PCI Status             <10>

One of the suggestions is to try and update the firmware which is at 0.4-4

How do I find out if there is a newer version and how would I install it? I can boot from a Windows disk if needed.

Hey everyone, I’m troubleshooting a weird stability issue on my Proxmox node and could use some guidance.

Setup

- Proxmox VE (latest kernel)

- Intel onboard NIC: I219-LM (e1000e driver)

- NVMe storage (SK hynix)

- Multiple VMs + LXC containers

- Linux bridge (vmbr0)

- Gigabit switch (recently added)

Issue

The node randomly reboots, especially when:

- Starting multiple VMs

- Bulk starting containers

- High network activity

- Bridge/tap interfaces coming up

Before reboot, the UI shows:

«Connection refused (595)

No network information»

Logs (last lines before crash)

I consistently see this spammed:

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

TDH <…> TDT <…>

next_to_use <…>

next_to_clean <…>

MAC Status <80083>

PHY Status <796d>

watchdog: watchdog0: watchdog did not stop!

Then the node reboots.

Additional observations

- Started happening after moving from Fast Ethernet switch → Gigabit switch

- Happens more often during VM start / bridge churn

- SSD tested fine (no errors)

- No ECC or RAM errors

- Offloading already disabled:

ethtool -K eno1 tso off gso off gro off

- No packet errors in "ethtool -S"

- Firewall disabled for testing

Questions

1. Is this a known e1000e / I219-LM firmware bug under virtualization load?

2. Could bridge + promiscuous + tap traffic trigger NIC DMA hangs?

3. Any kernel params / driver tweaks that actually help?

4. Would adding a PCIe NIC and moving vmbr0 off Intel fully resolve it?

5. Anyone seen watchdog reboots tied to e1000e hangs?

Trying to confirm whether this is:

- Driver bug

- Firmware issue

- Hardware degradation

- Switch compatibility problem

Any insight appreciated 🙏