Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 9148 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

Issue with "Detected Tx Unit Hang"

Harald Moun

Hi all!

We are running Sophos UTM9.5 (9.510-5) on ESXi 6.0.0, 9239799 (Hardware Lenovo System x3650 M5, Broadcom NetXtreme BCM5719 gigabit ethernet).

Within the last two months the virtual appliance drops the network connection.

Networking is completely down, the web administration interface is not accessable any more (Terminal window is alive, but not tried to logon).

Only rebooting the machine brings back network connection.

Today I checked the logfiles and found the following:

 

2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620] e1000 0000:02:00.0 eth0: Detected Tx Unit Hang
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   Tx Queue             
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   TDH                  
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   TDT                  
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   next_to_use          
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   next_to_clean        
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620] buffer_info[next_to_clean]
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   time_stamp           
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   next_to_watch        
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   jiffies              
2018:10:25-11:23:19 xyzfirewall kernel: [70712.066620]   next_to_watch.status 
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171] e1000 0000:02:00.0 eth0: Detected Tx Unit Hang
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   Tx Queue             
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   TDH                  
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   TDT                  
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   next_to_use          
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   next_to_clean        
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171] buffer_info[next_to_clean]
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   time_stamp           
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   next_to_watch        
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   jiffies              
2018:10:25-11:23:21 xyzfirewall kernel: [70714.308171]   next_to_watch.status 
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973581] ------------[ cut here ]------------
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973592] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0xe6/0x181()
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973594] NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973595] Modules linked in: nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE tun xt_hashlimit xt_connlabel xt_TPROXY xt_socket xt_NFQUEUE xt_connmark xt_nat xt_mark xt_psd(O) xt_limit xt_addrtype xt_geoip(O) xt_set xt_policy xt_multiport ip_set_hash_net nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_irc ip_set_hash_ip nfnetlink_queue xfrm_user xfrm_algo ebtable_filter ebtables redv2_netlink(O) ip6table_ips ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_ips iptable_mangle iptable_nat nf_nat_ipv4 xt_NFLOG xt_condition(O) xt_tcpudp xt_logmark xt_confirmed xt_owner ip6t_REJECT ipt_REJECT xt_state ip_set red2(O) ip_scheduler red af_packet 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_dns nf_nat nf_conntrack_netlink nfnetlink nf_conntrack ip6_tables ip_tables x_tables ipv6 loop rtc_cmos crc32c_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper sg sr_mod aes_x86_64 aes_generic microcode cdrom vmw_vmci pcspkr vmw_balloon evdev i2c_piix4 button ac sd_mod processor thermal_sys hwmon pata_acpi ata_generic edd ata_piix libata mptspi mptscsih mptbase scsi_transport_spi scsi_mod vmxnet3 vmxnet(O) e1000e(O) ptp pps_core e1000 hid_generic usbhid ehci_pci ehci_hcd [last unloaded: nf_conntrack_ftp]
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973736] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O 3.12.74-0.292688430.ga5ef2ae.rb5-smp64 #1
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973738] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/21/2015
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973740]  0000000000000000 ffffffff8136bf91 ffffffff813073c6 ffffffff813073c6
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973742]  ffff88013fc03dd0 ffffffff81046a60 ffff880139a90000 0000000000000000
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973744]  ffff880139a90000 ffff880139a90348 ffffffff813072e0 ffffffff81046b11
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973746] Call Trace:
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973747]    [] ? dump_stack+0x61/0x80
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973755]  [] ? dev_watchdog+0xe6/0x181
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973757]  [] ? dev_watchdog+0xe6/0x181
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973763]  [] ? warn_slowpath_common+0x74/0x8b
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973765]  [] ? netif_tx_lock+0x7e/0x7e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973768]  [] ? warn_slowpath_fmt+0x45/0x4a
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973772]  [] ? update_curr+0x4e/0x131
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973774]  [] ? netif_tx_lock+0x43/0x7e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973779]  [] ? netif_tx_lock+0x7e/0x7e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973781]  [] ? dev_watchdog+0xe6/0x181
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973784]  [] ? raise_softirq_irqoff+0x9/0x3e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973792]  [] ? call_timer_fn+0x6a/0x10e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973795]  [] ? netif_tx_lock+0x7e/0x7e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973797]  [] ? run_timer_softirq+0x176/0x1bd
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973801]  [] ? timerqueue_add+0x79/0x94
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973803]  [] ? __do_softirq+0x128/0x24c
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973805]  [] ? call_softirq+0x1c/0x30
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973811]  [] ? do_softirq+0x3f/0x79
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973813]  [] ? irq_exit+0x46/0xa1
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973819]  [] ? smp_apic_timer_interrupt+0x22/0x2d
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973822]  [] ? apic_timer_interrupt+0x6d/0x80
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973823]    [] ? native_sched_clock+0x27/0x2e
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973828]  [] ? mwait_idle+0xb1/0xb1
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973831]  [] ? native_safe_halt+0x2/0x3
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973833]  [] ? default_idle+0x1b/0x2f
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973837]  [] ? cpu_startup_entry+0xdd/0x13c
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973840]  [] ? start_kernel+0x3d1/0x3dd
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973842]  [] ? repair_env_string+0x5c/0x5c
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973844]  [] ? early_idt_handler_array+0x120/0x120
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973846]  [] ? early_idt_handler_array+0x120/0x120
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973848]  [] ? x86_64_start_kernel+0x15a/0x169
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973850] ---[ end trace 42997df934a6f31f ]---
2018:10:25-11:23:23 xyzfirewall kernel: [70715.973859] e1000 0000:02:00.0 eth0: Reset adapter

I was looking for a solution for this problem but I couldn't find anything helpful hints except old forum-threads on different websites concerning different Linux distributions, but nothing seemed to be useful for me.

The Sophos UTM worked fine until we upgraded our internet connection from 12 mbit/s to 80 mbit/s. It occurs about 2 or 3 times a week at normal business hours. Unfortunately I  have no idea what the actual load on the line is but I assume that there is medium or higher load on the wire when the failure occurs)

 

Any idea what we could do?

(First I moved the Virtual Machine to an other host which has the same hardware and software configuration - let us see if it changes anything)

 

regards

Harald

 



This thread was automatically locked due to age.
Parents
  • 0

    Hey Harald,

     

    i run the same config with the same IBM Server. I had some similar issues some time ago. Things that migh help

    Upgrade Modem Firmware to the latest Version alot of the times they do not support higher speeds with old firmware. (had this for example with vigor modem).

     

    Run the Lenovo Update Manager maybe there are some new Network drivers as well. (Updating those isnt bad anyway :P )

     

    Regards

    Jason

    Regards

    Jason

    Sophos Certified Architect - UTM

Reply
  • 0

    Hey Harald,

     

    i run the same config with the same IBM Server. I had some similar issues some time ago. Things that migh help

    Upgrade Modem Firmware to the latest Version alot of the times they do not support higher speeds with old firmware. (had this for example with vigor modem).

     

    Run the Lenovo Update Manager maybe there are some new Network drivers as well. (Updating those isnt bad anyway :P )

     

    Regards

    Jason

    Regards

    Jason

    Sophos Certified Architect - UTM

Children
Unfiltered HTML