eth0: Detected Hardware Unit Hang

[pervin_1]

Oct 13 12:19:25 Tower kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:
Oct 13 12:19:25 Tower kernel:  TDH                  <0>
Oct 13 12:19:25 Tower kernel:  TDT                  <8>
Oct 13 12:19:25 Tower kernel:  next_to_use          <8>
Oct 13 12:19:25 Tower kernel:  next_to_clean        <0>
Oct 13 12:19:25 Tower kernel: buffer_info[next_to_clean]:
Oct 13 12:19:25 Tower kernel:  time_stamp           <127739b72>
Oct 13 12:19:25 Tower kernel:  next_to_watch        <0>
Oct 13 12:19:25 Tower kernel:  jiffies              <12773aa80>
Oct 13 12:19:25 Tower kernel:  next_to_watch.status <0>
Oct 13 12:19:25 Tower kernel: MAC Status             <80083>
Oct 13 12:19:25 Tower kernel: PHY Status             <796d>
Oct 13 12:19:25 Tower kernel: PHY 1000BASE-T Status  <3c00>
Oct 13 12:19:25 Tower kernel: PHY Extended Status    <3000>
Oct 13 12:19:25 Tower kernel: PCI Status             <10>
Oct 13 12:19:27 Tower dhcpcd[1696]: br0: probing for an IPv4LL address

 

 

 

I have been getting this error since Oct. 5th-6th and it was apparently unnoticed until today when my server became unresponsive, no GUI or SSH access, ethernet interface was down? Maybe, here is the picture of the monitor with the above message:

 

 

 

Had to use a monitor to see what's happening, so far so good, Dockers and VMs were running just fine along with other services. But the above problem caught my eyes, thinking it's related.

Diag. zip file is attached to this post down below.

 

Thanks in advance!!1 

tower-diagnostics-20181013-1219.zip

 

edit:

checked the syslog going back to July 2018 and it turns it started back then. 

Edited October 13, 2018 by pervin_1

[pervin_1]

follow up to my own post:

 

this is the most relevant information I came across today, cannot guarantee its gonna work, but gave it a try, fingers crossed, will post results shortly.

Apparently, my problem started back in July, not in Oct. as I stated in the above.

 

link

 

Also, you can try to disable the NIC flow control and NIC offload using the plugin tips and tricks to ensure persistence after reboots, otherwise use ethtool and user scripts to make it persistent.