e1000e eno1: Detected Hardware Unit Hang:

I just started looking into this issue and found here...testing the tso workaround.

I have three Dell Precision 3431s that use the Q246 C246 chipset. The first one I updated from PVE 8 to 9 started exhibiting this issue...more often when under network load like doing file transfers, but sometimes when it wasn't significant. The other two have not shown the problem...yet.

All are BIOS 1.32.0 (the latest when first deployed). 1.36.0 is out now, but details on fixes are pretty terse.
 
Last edited:
There is no "Q246" chipset, but only a "C246". And as mentioned, the original bug only should still affect older chipsets/systems (list see in my previous comment). So, if the issue persists and was not fixed with a BIOS update, then contact Dell. They should also be aware of this i219 Erratum.
 
celemine1gig said:
There is no "Q246" chipset, but only a "C246". And as mentioned, the original bug only should still affect older chipsets/systems (list see in my previous comment). So, if the issue persists and was not fixed with a BIOS update, then contact Dell. They should also be aware of this i219 Erratum.
Click to expand...

Oops, yes, that was a typo.
 
I have a few NUCs showing this behaviour, on 2 of them I have blacklisted the e1000e driver and use a different NIC which seems to work fine.

What I have noticed though, this only seems to happen on servers hosting VMs, I got one that only hosts LXCs which seems to be running forever and did migrate a VM across as I needed to perform some upgrades, as soon as the VM migrated across and started, the server crashed a few seconds/minutes later with the notorious log entry in the logs when I looked for a reason. When the server came back the upgrades had already completed and I migrated the VM away from the server back to the original hosting LCXs and VMs with the module being blacklisted, no issues whatsoever since.
 
You must log in or register to reply here.
Top Bottom