Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 32 replies
  • Subscribers 2 subscribers
  • Views 10635 views
  • Users 0 members are here
Options
Suggested
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

UTM 9.204 Intel E1000e NIC crash

ECKEROTH
Just upgraded to 9.204 and I still have Intel E1000e NIC crashs. PLEAZE SOPHOS - fix this now asap...

After manuel set "ethtool -K eth1 gso off gro off" normal operation can be obtained, but this it gone when rebooting [:@] 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] next_to_watch 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] jiffies 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] next_to_watch.status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] MAC Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY 1000BASE-T Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PHY Extended Status 

2014:07:11-20:28:20 fw kernel: [ 6621.930212] PCI Status 

2014:07:11-20:28:20 fw kernel: [ 6621.937388] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:28:23 fw kernel: [ 6625.762700] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

2014:07:11-20:32:06 fw kernel: [ 6847.695940] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:32:06 fw kernel: [ 6847.695940] TDH 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] TDT 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_use 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_clean 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] buffer_info[next_to_clean]:

2014:07:11-20:32:06 fw kernel: [ 6847.695940] time_stamp 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_watch 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] jiffies 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] next_to_watch.status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] MAC Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY 1000BASE-T Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PHY Extended Status 

2014:07:11-20:32:06 fw kernel: [ 6847.695940] PCI Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:32:08 fw kernel: [ 6849.693885] TDH 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] TDT 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_use 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_clean 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] buffer_info[next_to_clean]:

2014:07:11-20:32:08 fw kernel: [ 6849.693885] time_stamp 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_watch 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] jiffies 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] next_to_watch.status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] MAC Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY 1000BASE-T Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PHY Extended Status 

2014:07:11-20:32:08 fw kernel: [ 6849.693885] PCI Status 

2014:07:11-20:32:09 fw kernel: [ 6850.691975] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:32:12 fw kernel: [ 6854.449265] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

2014:07:11-20:33:27 fw kernel: [ 6928.600113] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:27 fw kernel: [ 6928.600113] TDH 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] TDT 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_use 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_clean 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] buffer_info[next_to_clean]:

2014:07:11-20:33:27 fw kernel: [ 6928.600113] time_stamp 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_watch 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] jiffies 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] next_to_watch.status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] MAC Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY 1000BASE-T Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PHY Extended Status 

2014:07:11-20:33:27 fw kernel: [ 6928.600113] PCI Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:29 fw kernel: [ 6930.598052] TDH 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] TDT 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_use 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_clean 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] buffer_info[next_to_clean]:

2014:07:11-20:33:29 fw kernel: [ 6930.598052] time_stamp 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_watch 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] jiffies 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] next_to_watch.status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] MAC Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY 1000BASE-T Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PHY Extended Status 

2014:07:11-20:33:29 fw kernel: [ 6930.598052] PCI Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:31 fw kernel: [ 6932.595992] TDH 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] TDT 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_use 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_clean 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] buffer_info[next_to_clean]:

2014:07:11-20:33:31 fw kernel: [ 6932.595992] time_stamp 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_watch 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] jiffies 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] next_to_watch.status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] MAC Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY 1000BASE-T Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PHY Extended Status 

2014:07:11-20:33:31 fw kernel: [ 6932.595992] PCI Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:07:11-20:33:33 fw kernel: [ 6934.593959] TDH 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] TDT 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_use 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_clean 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] buffer_info[next_to_clean]:

2014:07:11-20:33:33 fw kernel: [ 6934.593959] time_stamp 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_watch 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] jiffies 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] next_to_watch.status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] MAC Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY 1000BASE-T Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PHY Extended Status 

2014:07:11-20:33:33 fw kernel: [ 6934.593959] PCI Status 

2014:07:11-20:33:33 fw kernel: [ 6934.604903] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly

2014:07:11-20:33:36 fw kernel: [ 6938.414254] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx


This thread was automatically locked due to age.
  • 0
    @jeffshead:  Correct Jeff.  Only those with a paid support contract can contact support.
    @martinta:  Again, open up (another?) support ticket to query the status of a fix.  If you get runaround, request escalation.
  • 0
    There is usually a Known Issue List for each version; if this isn't in there it certainly should be.

    Barry
  • 0 in reply to BarryG
    There is usually a Known Issue List for each version; if this isn't in there it certainly should be.

    Barry


    This BUG is not on the KIL anymore!
    Bianca removed it long time ago, without any fix... [:S]

    // Martin
  • 0
    I keep getting these: 

    e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang

    Bad network card or bug?


    e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   TDH                  
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   TDT                  
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   next_to_use          
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   next_to_clean        
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] buffer_info[next_to_clean]:
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   time_stamp           
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   next_to_watch        
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   jiffies              
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239]   next_to_watch.status 
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] MAC Status             
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] PHY Status             
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] PHY 1000BASE-T Status  
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] PHY Extended Status    
    2014:10:01-18:41:00 WallofFire kernel: [ 1471.820239] PCI Status             
    2014:10:01-18:41:01 WallofFire kernel: [ 1472.832027] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
    2014:10:01-18:41:04 WallofFire kernel: [ 1475.636860] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  • 0 in reply to tlamming
    I keep getting these: 

    e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang

    Bad network card or bug?


    bug.. when you look in the log it should be listing something like 

    1000e 0000:00:19.0 eth1: Reset adapter unexpectedly
    e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx


    prior to that line.. there is a workaround mentioned several places on this forum

    Edit: For the record, the latest details from his reply wasen't there when i posted the above :-)
  • 0
    I keep getting these: 

     e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang

     Bad network card or bug?



    Are you using an Intel NIC? 


    Perform a forum search using the keyword "e1000" and you will see there is a bug affecting certain Intel NIC's.
  • 0 in reply to Jeff x
    Are you using an Intel NIC? 


    Perform a forum search using the keyword "e1000" and you will see there is a bug affecting certain Intel NIC's.


    the log does state "e1000", so my guess is that he is using intel e1000 chip.. :-)
  • 0
    Yep, thanks guys. Ok I'll check out the work around [:)]
  • 0
    The workaround (switching off gso + gro) did not work. I was able to switch to a nic with broadcom chipsets. No problems thus far, no errors, marginal loss of packets, no hang ups or resets. Pretty annoying for everyone be it commercial or home user. If they keep it to one situation like this per year I can live with it. no one is perfect. ;-)
  • 0 in reply to tekuton
    The workaround (switching off gso + gro) did not work. I was able to switch to a nic with broadcom chipsets. No problems thus far, no errors, marginal loss of packets, no hang ups or resets. Pretty annoying for everyone be it commercial or home user. If they keep it to one situation like this per year I can live with it. no one is perfect. ;-)


    I've the same problem on two UTM that use the same intel interface, the problem is that I don't have any alternative and the (gso + gro off) commands didn't fix this issue, I'm constantly have my lan down and have to restart the UTM 3 or 4 times a day, its very annoying and I don't understand why this issue has been reported some months ago a Sophos was not able to solve it!!! [:@]