Guest User!

You are not Sophos Staff.

[9.192-8][BUG] Detected Hardware e1000e Unit Hang

Have this in my kernel.log today

2014:01:30-07:22:39 fw kernel: [1069893.170006] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:

2014:01:30-07:22:39 fw kernel: [1069893.170006]   TDH                  
2014:01:30-07:22:39 fw kernel: [1069893.170006]   TDT                  
2014:01:30-07:22:39 fw kernel: [1069893.170006]   next_to_use          
2014:01:30-07:22:39 fw kernel: [1069893.170006]   next_to_clean        
2014:01:30-07:22:39 fw kernel: [1069893.170006] buffer_info[next_to_clean]:
2014:01:30-07:22:39 fw kernel: [1069893.170006]   time_stamp           
2014:01:30-07:22:39 fw kernel: [1069893.170006]   next_to_watch        
2014:01:30-07:22:39 fw kernel: [1069893.170006]   jiffies              
2014:01:30-07:22:39 fw kernel: [1069893.170006]   next_to_watch.status 
2014:01:30-07:22:39 fw kernel: [1069893.170006] MAC Status             
2014:01:30-07:22:39 fw kernel: [1069893.170006] PHY Status             
2014:01:30-07:22:39 fw kernel: [1069893.170006] PHY 1000BASE-T Status  
2014:01:30-07:22:39 fw kernel: [1069893.170006] PHY Extended Status    
2014:01:30-07:22:39 fw kernel: [1069893.170006] PCI Status             
2014:01:30-07:22:41 fw kernel: [1069895.168953] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:
2014:01:30-07:22:41 fw kernel: [1069895.168953]   TDH                  
2014:01:30-07:22:41 fw kernel: [1069895.168953]   TDT                  
2014:01:30-07:22:41 fw kernel: [1069895.168953]   next_to_use          
2014:01:30-07:22:41 fw kernel: [1069895.168953]   next_to_clean        
2014:01:30-07:22:41 fw kernel: [1069895.168953] buffer_info[next_to_clean]:
2014:01:30-07:22:41 fw kernel: [1069895.168953]   time_stamp           
2014:01:30-07:22:41 fw kernel: [1069895.168953]   next_to_watch        
2014:01:30-07:22:41 fw kernel: [1069895.168953]   jiffies              
2014:01:30-07:22:41 fw kernel: [1069895.168953]   next_to_watch.status 
2014:01:30-07:22:41 fw kernel: [1069895.168953] MAC Status             
2014:01:30-07:22:41 fw kernel: [1069895.168953] PHY Status             
2014:01:30-07:22:41 fw kernel: [1069895.168953] PHY 1000BASE-T Status  
2014:01:30-07:22:41 fw kernel: [1069895.168953] PHY Extended Status    
2014:01:30-07:22:41 fw kernel: [1069895.168953] PCI Status             
2014:01:30-07:22:43 fw kernel: [1069897.166586] e1000e 0000:00:19.0 eth1: Detected Hardware Unit Hang:
2014:01:30-07:22:43 fw kernel: [1069897.166586]   TDH                  
2014:01:30-07:22:43 fw kernel: [1069897.166586]   TDT                  
2014:01:30-07:22:43 fw kernel: [1069897.166586]   next_to_use          
2014:01:30-07:22:43 fw kernel: [1069897.166586]   next_to_clean        
2014:01:30-07:22:43 fw kernel: [1069897.166586] buffer_info[next_to_clean]:
2014:01:30-07:22:43 fw kernel: [1069897.166586]   time_stamp           
2014:01:30-07:22:43 fw kernel: [1069897.166586]   next_to_watch        
2014:01:30-07:22:43 fw kernel: [1069897.166586]   jiffies              
2014:01:30-07:22:43 fw kernel: [1069897.166586]   next_to_watch.status 
2014:01:30-07:22:43 fw kernel: [1069897.166586] MAC Status             
2014:01:30-07:22:43 fw kernel: [1069897.166586] PHY Status             
2014:01:30-07:22:43 fw kernel: [1069897.166586] PHY 1000BASE-T Status  
2014:01:30-07:22:43 fw kernel: [1069897.166586] PHY Extended Status    
2014:01:30-07:22:43 fw kernel: [1069897.166586] PCI Status             
2014:01:30-07:22:44 fw kernel: [1069898.172025] e1000e 0000:00:19.0 eth1: Reset adapter unexpectedly
2014:01:30-07:22:48 fw kernel: [1069902.045783] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  • Closed... Will 9.202 have a new Intel driver??

    Barry
  • Yeah what's th plan to fix this issue?
    I got this now daily....

    2014:05:24-10:10:05 fw kernel: [317881.156267] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:

    Only a reboot of the FW helps.

    Sophos UTM Version: 9.201-23

    NIC Hardware: Intel Corporation 82579LM Gigabit Network Connection

    Kernel log:

    2014:05:24-10:10:05 fw kernel: [317881.156267] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:05:24-10:10:05 fw kernel: [317881.156267]   TDH                  
    2014:05:24-10:10:05 fw kernel: [317881.156267]   TDT                  
    2014:05:24-10:10:05 fw kernel: [317881.156267]   next_to_use          
    2014:05:24-10:10:05 fw kernel: [317881.156267]   next_to_clean        
    2014:05:24-10:10:05 fw kernel: [317881.156267] buffer_info[next_to_clean]:
    2014:05:24-10:10:05 fw kernel: [317881.156267]   time_stamp           
    2014:05:24-10:10:05 fw kernel: [317881.156267]   next_to_watch        
    2014:05:24-10:10:05 fw kernel: [317881.156267]   jiffies              
    2014:05:24-10:10:05 fw kernel: [317881.156267]   next_to_watch.status 
    2014:05:24-10:10:05 fw kernel: [317881.156267] MAC Status             
    2014:05:24-10:10:05 fw kernel: [317881.156267] PHY Status             
    2014:05:24-10:10:05 fw kernel: [317881.156267] PHY 1000BASE-T Status  
    2014:05:24-10:10:05 fw kernel: [317881.156267] PHY Extended Status    
    2014:05:24-10:10:05 fw kernel: [317881.156267] PCI Status             
    2014:05:24-10:10:07 fw kernel: [317883.154542] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:05:24-10:10:07 fw kernel: [317883.154542]   TDH                  
    2014:05:24-10:10:07 fw kernel: [317883.154542]   TDT                  
    2014:05:24-10:10:07 fw kernel: [317883.154542]   next_to_use          
    2014:05:24-10:10:07 fw kernel: [317883.154542]   next_to_clean        
    2014:05:24-10:10:07 fw kernel: [317883.154542] buffer_info[next_to_clean]:
    2014:05:24-10:10:07 fw kernel: [317883.154542]   time_stamp           
    2014:05:24-10:10:07 fw kernel: [317883.154542]   next_to_watch        
    2014:05:24-10:10:07 fw kernel: [317883.154542]   jiffies              
    2014:05:24-10:10:07 fw kernel: [317883.154542]   next_to_watch.status 
    2014:05:24-10:10:07 fw kernel: [317883.154542] MAC Status             
    2014:05:24-10:10:07 fw kernel: [317883.154542] PHY Status             
    2014:05:24-10:10:07 fw kernel: [317883.154542] PHY 1000BASE-T Status  
    2014:05:24-10:10:07 fw kernel: [317883.154542] PHY Extended Status    
    2014:05:24-10:10:07 fw kernel: [317883.154542] PCI Status             
    2014:05:24-10:10:09 fw kernel: [317885.152815] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:05:24-10:10:09 fw kernel: [317885.152815]   TDH                  
    2014:05:24-10:10:09 fw kernel: [317885.152815]   TDT                  
    2014:05:24-10:10:09 fw kernel: [317885.152815]   next_to_use          
    2014:05:24-10:10:09 fw kernel: [317885.152815]   next_to_clean        
    2014:05:24-10:10:09 fw kernel: [317885.152815] buffer_info[next_to_clean]:
    2014:05:24-10:10:09 fw kernel: [317885.152815]   time_stamp           
    2014:05:24-10:10:09 fw kernel: [317885.152815]   next_to_watch        
    2014:05:24-10:10:09 fw kernel: [317885.152815]   jiffies              
    2014:05:24-10:10:09 fw kernel: [317885.152815]   next_to_watch.status 
    2014:05:24-10:10:09 fw kernel: [317885.152815] MAC Status             
    2014:05:24-10:10:09 fw kernel: [317885.152815] PHY Status             
    2014:05:24-10:10:09 fw kernel: [317885.152815] PHY 1000BASE-T Status  
    2014:05:24-10:10:09 fw kernel: [317885.152815] PHY Extended Status    
    2014:05:24-10:10:09 fw kernel: [317885.152815] PCI Status             
    2014:05:24-10:10:11 fw kernel: [317887.151336] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:05:24-10:10:11 fw kernel: [317887.151336]   TDH                  
    2014:05:24-10:10:11 fw kernel: [317887.151336]   TDT                  
    2014:05:24-10:10:11 fw kernel: [317887.151336]   next_to_use          
    2014:05:24-10:10:11 fw kernel: [317887.151336]   next_to_clean        
    2014:05:24-10:10:11 fw kernel: [317887.151336] buffer_info[next_to_clean]:
    2014:05:24-10:10:11 fw kernel: [317887.151336]   time_stamp           
    2014:05:24-10:10:11 fw kernel: [317887.151336]   next_to_watch        
    2014:05:24-10:10:11 fw kernel: [317887.151336]   jiffies              
    2014:05:24-10:10:11 fw kernel: [317887.151336]   next_to_watch.status 
    2014:05:24-10:10:11 fw kernel: [317887.151336] MAC Status             
    2014:05:24-10:10:11 fw kernel: [317887.151336] PHY Status             
    2014:05:24-10:10:11 fw kernel: [317887.151336] PHY 1000BASE-T Status  
    2014:05:24-10:10:11 fw kernel: [317887.151336] PHY Extended Status    
    2014:05:24-10:10:11 fw kernel: [317887.151336] PCI Status             
    2014:05:24-10:10:13 fw kernel: [317889.149612] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:05:24-10:10:13 fw kernel: [317889.149612]   TDH                  
    2014:05:24-10:10:13 fw kernel: [317889.149612]   TDT                  
    2014:05:24-10:10:13 fw kernel: [317889.149612]   next_to_use          
    2014:05:24-10:10:13 fw kernel: [317889.149612]   next_to_clean        
    2014:05:24-10:10:13 fw kernel: [317889.149612] buffer_info[next_to_clean]:
    2014:05:24-10:10:13 fw kernel: [317889.149612]   time_stamp           
    2014:05:24-10:10:13 fw kernel: [317889.149612]   next_to_watch        
    2014:05:24-10:10:13 fw kernel: [317889.149612]   jiffies              
    2014:05:24-10:10:13 fw kernel: [317889.149612]   next_to_watch.status 
    2014:05:24-10:10:13 fw kernel: [317889.149612] MAC Status             
    2014:05:24-10:10:13 fw kernel: [317889.149612] PHY Status             
    2014:05:24-10:10:13 fw kernel: [317889.149612] PHY 1000BASE-T Status  
    2014:05:24-10:10:13 fw kernel: [317889.149612] PHY Extended Status    
    2014:05:24-10:10:13 fw kernel: [317889.149612] PCI Status             
    2014:05:24-10:10:13 fw kernel: [317889.160739] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
    2014:05:24-10:10:16 fw kernel: [317892.706974] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
  • Is there a fix or workaround to get rid of this bug?
  • I had this issue with two UTM 120's.  An engineer at Sophos uploaded a patch to temporarily fix them until it's fixed with an Up2Date patch.  The fix is not persistent so a reboot requires that it be applied again.

    I was told by support that the fix was going to be in 9.2, but I haven't gotten confirmation on this.  The UTMs have not gotten the update yet - in fact, I can't make any sense of how 9.2 is being rolled out.  We manage 20 UTMs of different hardware types and there seems to be no rhyme or reason to which have gotten the update.

    Add to this the whole "erroneous" download of the update and it all has been very confusing.
  • I encountered this issue as well (https://community.sophos.com/products/unified-threat-management/astaroorg/f/51/t/22278). I would loose connectivity as if that NIC did not exist or was unplugged. Luckily, I had another port (different model NIC) so I switched to it as a workaround.

    --------------------------------------------------------------------
    Sophos UTM 9.714-4 - Home User
    Currently testing VM on i3-9100 @ 3.60 GHz
    16 GB RAM
    Dell Optiplex XE
    Intel Core 2 Duo CPU E8600 @ 3.33GHz
    8GB RAM
    --------------------------------------------------------------------

  • i hope for a fix. a firewall with crashing lan ports is a no-go.
  • Still getting same entries in the kernel log albeit fewer in number. This bug is affecting other Intel NICs as well. Never lost connectivity (as far as I can tell) since switching to the different Intel NIC but encountered other issues with 9.2 so I reinstalled 9.1.
     
    How can this issue be closed? Can't believe they rolled out 9.2 with this bug. I read on here that others experienced this issue with 9.1 but I went through all of my archived Kernel logs and I never encountered this issue with 9.1. Guess I'm not updating for a while.

    --------------------------------------------------------------------
    Sophos UTM 9.714-4 - Home User
    Currently testing VM on i3-9100 @ 3.60 GHz
    16 GB RAM
    Dell Optiplex XE
    Intel Core 2 Duo CPU E8600 @ 3.33GHz
    8GB RAM
    --------------------------------------------------------------------