This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[9.206] Intel E1000E adapter hung

Just upgraded to 9.206 without any problems BUT...

I still have nic's hang's on my Intel E1000E adapter [:@]
After set [PHP]/sbin/ethtool -K eth1 gso off gro off[/PHP] normal traffic worked again, until next reboot...

2014:09:04-20:32:59 fw kernel: [ 505.279629] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:09:04-20:32:59 fw kernel: [ 505.279629] TDH 
2014:09:04-20:32:59 fw kernel: [ 505.279629] TDT 
2014:09:04-20:32:59 fw kernel: [ 505.279629] next_to_use 
2014:09:04-20:32:59 fw kernel: [ 505.279629] next_to_clean 
2014:09:04-20:32:59 fw kernel: [ 505.279629] buffer_info[next_to_clean]:
2014:09:04-20:32:59 fw kernel: [ 505.279629] time_stamp 
2014:09:04-20:32:59 fw kernel: [ 505.279629] next_to_watch 
2014:09:04-20:32:59 fw kernel: [ 505.279629] jiffies 
2014:09:04-20:32:59 fw kernel: [ 505.279629] next_to_watch.status 
2014:09:04-20:32:59 fw kernel: [ 505.279629] MAC Status 
2014:09:04-20:32:59 fw kernel: [ 505.279629] PHY Status 
2014:09:04-20:32:59 fw kernel: [ 505.279629] PHY 1000BASE-T Status 
2014:09:04-20:32:59 fw kernel: [ 505.279629] PHY Extended Status 
2014:09:04-20:32:59 fw kernel: [ 505.279629] PCI Status 
2014:09:04-20:33:00 fw kernel: [ 506.285760] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly
2014:09:04-20:33:01 fw kernel: [ 506.778527] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None


This thread was automatically locked due to age.
Parents Reply
  • Don't bother if you are a home user or using the Essentials license; this email address will kick back any request that is not from a customer who has purchased Standard or Premium Support.


    I've sent them an email and they had forwarded the email to the development team and its in their interest to solve the issue!!
Children
  • It definitely is in their interest to solve the problem, but, typically, they do not respond to emails from non-commercially-licensed users -- I guess in this case, they must have made an exception, given it's an issue they've been fighting with for a while (probably because of all the different device IDs an Intel NIC can have)... that or you got lucky.