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

Interface eth0 hangs

Hi,

I'm not sure if this is a coincidence or not but since last update to 9.205-12 I'm having some problems with the eth0 interface that keeps resetting and I loose all lan connections including the two AP30 that are connected to this interface. I will attach the kernel log to help checking the error messages and I would like to have some support from you guys.

My UTM version 9.205-12
Motherboard Intel DQ77KB 

Thanks.[:@]


This thread was automatically locked due to age.
Parents
  • Cannot believe on this!!!
    Just upgraded to 9.206 and the adapter e1000 stills reseting!!! [:@]

    Kernel Log:

    2014:09:03-21:03:38 utm9-lan kernel: [   24.011742] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
    
    2014:09:03-21:03:38 utm9-lan kernel: [   24.011745] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
    2014:09:03-21:03:46 utm9-lan kernel: [   32.375641] hwinfo: vm86 mode not supported on 64 bit kernel
    2014:09:03-21:12:58 utm9-lan kernel: [  582.130872] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   TDH                  
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   TDT                  
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   next_to_use          
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   next_to_clean        
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] buffer_info[next_to_clean]:
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   time_stamp           
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   next_to_watch        
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   jiffies              
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031]   next_to_watch.status 
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] MAC Status             
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] PHY Status             
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] PHY 1000BASE-T Status  
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] PHY Extended Status    
    2014:09:03-21:31:29 utm9-lan kernel: [ 1690.454031] PCI Status             
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   TDH                  
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   TDT                  
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   next_to_use          
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   next_to_clean        
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] buffer_info[next_to_clean]:
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   time_stamp           
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   next_to_watch        
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   jiffies              
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904]   next_to_watch.status 
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] MAC Status             
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] PHY Status             
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] PHY 1000BASE-T Status  
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] PHY Extended Status    
    2014:09:03-21:31:31 utm9-lan kernel: [ 1692.448904] PCI Status             
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   TDH                  
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   TDT                  
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   next_to_use          
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   next_to_clean        
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] buffer_info[next_to_clean]:
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   time_stamp           
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   next_to_watch        
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   jiffies              
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764]   next_to_watch.status 
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] MAC Status             
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] PHY Status             
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] PHY 1000BASE-T Status  
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] PHY Extended Status    
    2014:09:03-21:31:33 utm9-lan kernel: [ 1694.443764] PCI Status             
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   TDH                  
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   TDT                  
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   next_to_use          
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   next_to_clean        
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] buffer_info[next_to_clean]:
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   time_stamp           
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   next_to_watch        
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   jiffies              
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547]   next_to_watch.status 
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] MAC Status             
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] PHY Status             
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] PHY 1000BASE-T Status  
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] PHY Extended Status    
    2014:09:03-21:31:35 utm9-lan kernel: [ 1696.438547] PCI Status             
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439263] ------------[ cut here ]------------
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439275] WARNING: at net/sched/sch_generic.c:254 dev_watchdog+0xe7/0x182()
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439277] Hardware name:         
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439279] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439281] Modules linked in: sr_mod cdrom ipt_MASQUERADE xt_policy xt_hashlimit xt_connlabel xt_TPROXY nf_tproxy_core xt_socket xt_NFQUEUE xt_connmark xt_REDIRECT xt_mark xt_addrtype xt_tcpudp xt_multiport xt_set nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_ftp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_ftp nfnetlink_queue ip_set_hash_ip 8021q ebt_arp bridge stp llc ebtable_filter ebtables redv2_netlink af_packet ip6table_ips ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_ips iptable_mangle iptable_nat nf_nat_ipv4 nf_nat xt_NFLOG xt_condition(O) xt_logmark xt_confirmed xt_owner ip6t_REJECT ipt_REJECT xt_state ip_set red2 ip_scheduler red nfnetlink_log nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6table_raw nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter iptable_raw xt_CT nf_conntrack_netlink nfnetlink nf_conntrack ip6_tables ip_tables x_tables ipv6 loop hid_generic usbhid evdev acpi_cpufreq mperf crc32c_intel rtc_cmos aesni_intel ablk_helper cryptd lrw aes_x86_64 aes_generic xts gf128mul coretemp button i2c_i801 pcspkr sg microcode e1000e(O) ptp pps_core ehci_pci ehci_hcd sd_mod fan thermal xhci_hcd processor thermal_sys hwmon edd ahci libahci libata scsi_mod
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439361] Pid: 0, comm: swapper/0 Tainted: G           O 3.8.13.27-0.173454012.g3d22934-smp64 #1
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439362] Call Trace:
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439364]    [] ? dev_watchdog+0xe7/0x182
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439374]  [] ? warn_slowpath_common+0x78/0x8d
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439378]  [] ? netif_tx_lock+0x7e/0x7e
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439381]  [] ? warn_slowpath_fmt+0x45/0x4a
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439385]  [] ? netif_tx_lock+0x43/0x7e
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439392]  [] ? dev_watchdog+0xe7/0x182
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439396]  [] ? call_timer_fn+0x1b/0x6e
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439399]  [] ? run_timer_softirq+0x16c/0x1b3
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439404]  [] ? timekeeping_get_ns+0x12/0x35
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439409]  [] ? __do_softirq+0x9d/0x15f
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439413]  [] ? clockevents_program_event+0x9a/0xb9
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439418]  [] ? disable_cpuidle+0xb/0xb
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439422]  [] ? call_softirq+0x1c/0x30
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439426]  [] ? do_softirq+0x3f/0x79
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439430]  [] ? irq_exit+0x43/0xb1
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439435]  [] ? smp_apic_timer_interrupt+0x85/0x93
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439438]  [] ? apic_timer_interrupt+0x6d/0x80
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439439]    [] ? __setup_broadcast_timer+0x2d/0x2d
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439447]  [] ? cpuidle_wrap_enter+0x3c/0x71
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439451]  [] ? cpuidle_wrap_enter+0x32/0x71
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439455]  [] ? cpuidle_enter_state+0xa/0x33
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439458]  [] ? cpuidle_idle_call+0x9e/0xcc
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439461]  [] ? cpu_idle+0x61/0xa9
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439465]  [] ? early_idt_handlers+0x120/0x120
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439469]  [] ? start_kernel+0x372/0x37e
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439472]  [] ? repair_env_string+0x5d/0x5d
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439476]  [] ? x86_64_start_kernel+0x102/0x10f
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439478] ---[ end trace d9eaa99e7b2dcdff ]---
    2014:09:03-21:31:36 utm9-lan kernel: [ 1697.439497] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
    2014:09:03-21:31:40 utm9-lan kernel: [ 1701.178749] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  • Cannot believe on this!!!
    Just upgraded to 9.206 and the adapter e1000 stills reseting!!! [:@]




    Ahhhh... CRAP!


    I was hoping it was fixed in this version.


    This has been a known issue for quite sometime. I'm surprised it's still not fixed [:(]

    --------------------------------------------------------------------
    Sophos UTM 9.719-3 - Home User
    Virtual machine on Dell Optiplex 3070
    i3-9100 @ 3.60 GHz, 16 GB RAM
    --------------------------------------------------------------------

  • Ahhhh... CRAP!


    I was hoping it was fixed in this version.


    This has been a known issue for quite sometime. I'm surprised it's still not fixed [:(]


    I'm also surprised, Sophos list as fixed on 9.206 "ID32378 9.204 Reset Adapter and Hardware unit hang after update to v9.204 for intel ethernet controller 82579LM Gigabit Network Connection" but unfortunately the issue remains and I'm not the only guy complaining about this!!
  • I'm also surprised, Sophos list as fixed on 9.206 "ID32378 9.204 Reset Adapter and Hardware unit hang after update to v9.204 for intel ethernet controller 82579LM Gigabit Network Connection" but unfortunately the issue remains and I'm not the only guy complaining about this!!


    For the record.. I can confirm that this issue is still very much allive.

    was really dissapointed after installing the update when i noticed that the adapter still hang.
  • For the record.. I can confirm that this issue is still very much allive.

    was really dissapointed after installing the update when i noticed that the adapter still hang.


    Does someone knows if Sophos will deliver a fix soon for this?
    I can browse the web fine but if I try to make some heavy downloads the adapter starts resetting and almost my downloaded files become corrupt.

    SOPHOS PLEASE FIX THIS ASAP!!!!

    Note: I would recommend everyone who has this problem send and email to support@sophos.com to report this issue!!!
  • My guess is that some of the fixes they implement in udev to fix this issue are not set to work for your particular device IDs.  While your NICs may use the same chipsets, etc. they may be reporting different PCI IDs to Linux, and thus the fixes are not being applied for your particular NIC variant.  I will find the thread where I listed a way to look these up, and you can try posting them here, or, if you have a commercial license, you can report them to Sophos Support.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • My guess is that some of the fixes they implement in udev to fix this issue are not set to work for your particular device IDs.  While your NICs may use the same chipsets, etc. they may be reporting different PCI IDs to Linux, and thus the fixes are not being applied for your particular NIC variant.  I will find the thread where I listed a way to look these up, and you can try posting them here, or, if you have a commercial license, you can report them to Sophos Support.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
No Data