[Kernel-packages] [Bug 1524259] Re: igb: Detected Tx Unit Hang with stack trace
Sorry for delay. It's 4.4.0-040400rc4.201512061930 amd64. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524259 Title: igb: Detected Tx Unit Hang with stack trace Status in linux package in Ubuntu: Incomplete Bug description: Hello. For some time now we have a problem with one of our servers, that happens sporadically (once in a day or two days) and causes are not still known. We searched on lauchpad and tried many possible solutions, but nothing helped. We had tried vanilla Ubuntu 14.04.3 kernel - 3.16.x, and also 3.19.0-25-generic and linux- image-3.19.0-33-generic - the same symptoms on all of these versions. We also tried to rollback to 3.13: 3.13.0-43-generic and 3.13.0-62-generic, but the problem still persists. Our current configuration is: Ubuntu 14.04.3 with kernel 3.13.0-43.72 with Xen 4.4.2-0ubuntu0.14.04.3 (this host is used as xen hypervisor with iSCSI initiator if it is important). And here is how it's going: kernel: [135522.062941] igb :01:00.1: Detected Tx Unit Hang kernel: [135522.062941] Tx Queue <5> kernel: [135522.062941] TDH kernel: [135522.062941] TDT <21> kernel: [135522.062941] next_to_use <21> kernel: [135522.062941] next_to_clean kernel: [135522.062941] buffer_info[next_to_clean] kernel: [135522.062941] time_stamp <10203c3ca> kernel: [135522.062941] next_to_watch kernel: [135522.062941] jiffies <10203c4e6> kernel: [135522.062941] desc.status <1c8200> kernel: [135526.063054] desc.status <0> Many of messages like this. Right after that we have reports like: kernel: [135526.982825] connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4328767466, last ping 4328768718, now 4328769972 kernel: [135526.982911] connection2:0: detected conn error (1011) And finally: kernel: [135527.014836] WARNING: CPU: 8 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() kernel: [135527.014839] NETDEV WATCHDOG: eth1 (igb): transmit queue 4 timed out kernel: [135527.014841] Modules linked in: xt_physdev xen_netback xen_blkback cls_u32 sch_sfq sch_htb xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xen_gntdev xen_evtchn xenfs xen_privcmd ip6_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi gpio_ich joydev ioatdma serio_raw mac_hid shpchp lpc_ich i7core_edac intel_powerclamp coretemp edac_core lp parport hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear iptable_raw nf_nat nf_conntrack iptable_mangle iptable_filter psmouse ip_tables igb x_tables ahci libahci i2c_algo_bit dca ptp bridge pps_core 8021q garp stp llc mrp kernel: [135527.014903] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 3.13.0-43-generic #72-Ubuntu kernel: [135527.014905] Hardware name: Supermicro X8DTU/X8DTU, BIOS 2.1c 08/03/2012 kernel: [135527.014907] 0009 880268103d98 81720bf6 880268103de0 kernel: [135527.014912] 880268103dd0 810677cd 0004 880250b18000 kernel: [135527.014916] 8800030e5940 0008 0008 880268103e30 kernel: [135527.014920] Call Trace: kernel: [135527.014923][] dump_stack+0x45/0x56 kernel: [135527.014934] [] warn_slowpath_common+0x7d/0xa0 kernel: [135527.014937] [] warn_slowpath_fmt+0x4c/0x50 kernel: [135527.014943] [] dev_watchdog+0x276/0x280 kernel: [135527.014947] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014952] [] call_timer_fn+0x36/0x100 kernel: [135527.014955] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014959] [] run_timer_softirq+0x1ef/0x2f0 kernel: [135527.014964] [] __do_softirq+0xec/0x2c0 kernel: [135527.014969] [] irq_exit+0x105/0x110 kernel: [135527.014976] [] xen_evtchn_do_upcall+0x35/0x50 kernel: [135527.014981] [] xen_do_hypervisor_callback+0x1e/0x30 kernel: [135527.014982][] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014990] [] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014996] [] ? xen_safe_halt+0x10/0x20 kernel: [135527.015001] [] ? default_idle+0x1f/0xc0 kernel: [135527.015005] [] ? arch_cpu_idle+0x26/0x30 kernel: [135527.015010] [] ? cpu_startup_entry+0xc5/0x290 kernel: [135527.015015] [] ? cpu_bringup_and_idle+0x18/0x20 kernel: [135527.015018] ---[ end trace 431e88429488f9a4 ]--- kernel: [135527.015044] igb :01:00.1 eth1: Reset adapter Then the network connection to this machine is dead and it tries to reconnect continuously, but with no success. We had no problems after rollback to 3.13.0-43 kernel in about a week, but now it's cont
[Kernel-packages] [Bug 1524259] Re: igb: Detected Tx Unit Hang with stack trace
Hello. So our 4.4 servers work like a charm with 4.4 kernel for 18 days. Looks like the bug is fixed in mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524259 Title: igb: Detected Tx Unit Hang with stack trace Status in linux package in Ubuntu: Incomplete Bug description: Hello. For some time now we have a problem with one of our servers, that happens sporadically (once in a day or two days) and causes are not still known. We searched on lauchpad and tried many possible solutions, but nothing helped. We had tried vanilla Ubuntu 14.04.3 kernel - 3.16.x, and also 3.19.0-25-generic and linux- image-3.19.0-33-generic - the same symptoms on all of these versions. We also tried to rollback to 3.13: 3.13.0-43-generic and 3.13.0-62-generic, but the problem still persists. Our current configuration is: Ubuntu 14.04.3 with kernel 3.13.0-43.72 with Xen 4.4.2-0ubuntu0.14.04.3 (this host is used as xen hypervisor with iSCSI initiator if it is important). And here is how it's going: kernel: [135522.062941] igb :01:00.1: Detected Tx Unit Hang kernel: [135522.062941] Tx Queue <5> kernel: [135522.062941] TDH kernel: [135522.062941] TDT <21> kernel: [135522.062941] next_to_use <21> kernel: [135522.062941] next_to_clean kernel: [135522.062941] buffer_info[next_to_clean] kernel: [135522.062941] time_stamp <10203c3ca> kernel: [135522.062941] next_to_watch kernel: [135522.062941] jiffies <10203c4e6> kernel: [135522.062941] desc.status <1c8200> kernel: [135526.063054] desc.status <0> Many of messages like this. Right after that we have reports like: kernel: [135526.982825] connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4328767466, last ping 4328768718, now 4328769972 kernel: [135526.982911] connection2:0: detected conn error (1011) And finally: kernel: [135527.014836] WARNING: CPU: 8 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() kernel: [135527.014839] NETDEV WATCHDOG: eth1 (igb): transmit queue 4 timed out kernel: [135527.014841] Modules linked in: xt_physdev xen_netback xen_blkback cls_u32 sch_sfq sch_htb xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xen_gntdev xen_evtchn xenfs xen_privcmd ip6_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi gpio_ich joydev ioatdma serio_raw mac_hid shpchp lpc_ich i7core_edac intel_powerclamp coretemp edac_core lp parport hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear iptable_raw nf_nat nf_conntrack iptable_mangle iptable_filter psmouse ip_tables igb x_tables ahci libahci i2c_algo_bit dca ptp bridge pps_core 8021q garp stp llc mrp kernel: [135527.014903] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 3.13.0-43-generic #72-Ubuntu kernel: [135527.014905] Hardware name: Supermicro X8DTU/X8DTU, BIOS 2.1c 08/03/2012 kernel: [135527.014907] 0009 880268103d98 81720bf6 880268103de0 kernel: [135527.014912] 880268103dd0 810677cd 0004 880250b18000 kernel: [135527.014916] 8800030e5940 0008 0008 880268103e30 kernel: [135527.014920] Call Trace: kernel: [135527.014923][] dump_stack+0x45/0x56 kernel: [135527.014934] [] warn_slowpath_common+0x7d/0xa0 kernel: [135527.014937] [] warn_slowpath_fmt+0x4c/0x50 kernel: [135527.014943] [] dev_watchdog+0x276/0x280 kernel: [135527.014947] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014952] [] call_timer_fn+0x36/0x100 kernel: [135527.014955] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014959] [] run_timer_softirq+0x1ef/0x2f0 kernel: [135527.014964] [] __do_softirq+0xec/0x2c0 kernel: [135527.014969] [] irq_exit+0x105/0x110 kernel: [135527.014976] [] xen_evtchn_do_upcall+0x35/0x50 kernel: [135527.014981] [] xen_do_hypervisor_callback+0x1e/0x30 kernel: [135527.014982][] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014990] [] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014996] [] ? xen_safe_halt+0x10/0x20 kernel: [135527.015001] [] ? default_idle+0x1f/0xc0 kernel: [135527.015005] [] ? arch_cpu_idle+0x26/0x30 kernel: [135527.015010] [] ? cpu_startup_entry+0xc5/0x290 kernel: [135527.015015] [] ? cpu_bringup_and_idle+0x18/0x20 kernel: [135527.015018] ---[ end trace 431e88429488f9a4 ]--- kernel: [135527.015044] igb :01:00.1 eth1: Reset adapter Then the network connection to this machine is dead and it tries to reconnect continuously, but with no success. We had no problems after ro
[Kernel-packages] [Bug 1524259] Re: igb: Detected Tx Unit Hang with stack trace
I just booted the server into latest 4.4 kernel using packages you pointed to me. But triggering of the issue may took couple of days. Last longer uptime we had with 3.13.0-43-generic was about a week. Anyway, I'll report here the news. PS. I wasn't able to `apport-collect 1524259`. It opened lynx and when I try to type my username to login on launchpad, it redirects me to page source. Is it possible to run this command on headless machine? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524259 Title: igb: Detected Tx Unit Hang with stack trace Status in linux package in Ubuntu: Incomplete Bug description: Hello. For some time now we have a problem with one of our servers, that happens sporadically (once in a day or two days) and causes are not still known. We searched on lauchpad and tried many possible solutions, but nothing helped. We had tried vanilla Ubuntu 14.04.3 kernel - 3.16.x, and also 3.19.0-25-generic and linux- image-3.19.0-33-generic - the same symptoms on all of these versions. We also tried to rollback to 3.13: 3.13.0-43-generic and 3.13.0-62-generic, but the problem still persists. Our current configuration is: Ubuntu 14.04.3 with kernel 3.13.0-43.72 with Xen 4.4.2-0ubuntu0.14.04.3 (this host is used as xen hypervisor with iSCSI initiator if it is important). And here is how it's going: kernel: [135522.062941] igb :01:00.1: Detected Tx Unit Hang kernel: [135522.062941] Tx Queue <5> kernel: [135522.062941] TDH kernel: [135522.062941] TDT <21> kernel: [135522.062941] next_to_use <21> kernel: [135522.062941] next_to_clean kernel: [135522.062941] buffer_info[next_to_clean] kernel: [135522.062941] time_stamp <10203c3ca> kernel: [135522.062941] next_to_watch kernel: [135522.062941] jiffies <10203c4e6> kernel: [135522.062941] desc.status <1c8200> kernel: [135526.063054] desc.status <0> Many of messages like this. Right after that we have reports like: kernel: [135526.982825] connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4328767466, last ping 4328768718, now 4328769972 kernel: [135526.982911] connection2:0: detected conn error (1011) And finally: kernel: [135527.014836] WARNING: CPU: 8 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() kernel: [135527.014839] NETDEV WATCHDOG: eth1 (igb): transmit queue 4 timed out kernel: [135527.014841] Modules linked in: xt_physdev xen_netback xen_blkback cls_u32 sch_sfq sch_htb xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xen_gntdev xen_evtchn xenfs xen_privcmd ip6_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi gpio_ich joydev ioatdma serio_raw mac_hid shpchp lpc_ich i7core_edac intel_powerclamp coretemp edac_core lp parport hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear iptable_raw nf_nat nf_conntrack iptable_mangle iptable_filter psmouse ip_tables igb x_tables ahci libahci i2c_algo_bit dca ptp bridge pps_core 8021q garp stp llc mrp kernel: [135527.014903] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 3.13.0-43-generic #72-Ubuntu kernel: [135527.014905] Hardware name: Supermicro X8DTU/X8DTU, BIOS 2.1c 08/03/2012 kernel: [135527.014907] 0009 880268103d98 81720bf6 880268103de0 kernel: [135527.014912] 880268103dd0 810677cd 0004 880250b18000 kernel: [135527.014916] 8800030e5940 0008 0008 880268103e30 kernel: [135527.014920] Call Trace: kernel: [135527.014923][] dump_stack+0x45/0x56 kernel: [135527.014934] [] warn_slowpath_common+0x7d/0xa0 kernel: [135527.014937] [] warn_slowpath_fmt+0x4c/0x50 kernel: [135527.014943] [] dev_watchdog+0x276/0x280 kernel: [135527.014947] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014952] [] call_timer_fn+0x36/0x100 kernel: [135527.014955] [] ? dev_graft_qdisc+0x80/0x80 kernel: [135527.014959] [] run_timer_softirq+0x1ef/0x2f0 kernel: [135527.014964] [] __do_softirq+0xec/0x2c0 kernel: [135527.014969] [] irq_exit+0x105/0x110 kernel: [135527.014976] [] xen_evtchn_do_upcall+0x35/0x50 kernel: [135527.014981] [] xen_do_hypervisor_callback+0x1e/0x30 kernel: [135527.014982][] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014990] [] ? xen_hypercall_sched_op+0xa/0x20 kernel: [135527.014996] [] ? xen_safe_halt+0x10/0x20 kernel: [135527.015001] [] ? default_idle+0x1f/0xc0 kernel: [135527.015005] [] ? arch_cpu_idle+0x26/0x30 kernel: [135527.015010] [] ? cpu_startup_entry+0xc5/0x290 kernel: [1
[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang
The igb clash appears sporadically, once in two days or so. I can't reliably reproduce it - only by waiting for couple of days until it breaks. We seeing that in Ubuntu 14.04 with xen hypervisor 4.4.2-0ubuntu0.14.04.3 installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-utopic source package in Trusty: Fix Released Bug description: Hello! Have a: >lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty with kenel 3.16.0-46-generic. Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic version. After reboot i've got this: Sep 4 09:02:52 mail kernel: [ 310.616324] igb :02:00.0 em1: Reset adapter Sep 4 09:02:52 mail kernel: [ 310.831157] igb :02:00.1 em2: Reset adapter Sep 4 09:02:56 mail kernel: [ 315.154686] igb :02:00.0 em1: igb: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:02:56 mail kernel: [ 315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:03:02 mail kernel: [ 321.608099] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:02 mail kernel: [ 321.608099] Tx Queue <6> Sep 4 09:03:02 mail kernel: [ 321.608099] TDH <23> Sep 4 09:03:02 mail kernel: [ 321.608099] TDT <23> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_use <25> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_clean<23> Sep 4 09:03:02 mail kernel: [ 321.608099] buffer_info[next_to_clean] Sep 4 09:03:02 mail kernel: [ 321.608099] time_stamp <112af> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_watch Sep 4 09:03:02 mail kernel: [ 321.608099] jiffies <11531> Sep 4 09:03:02 mail kernel: [ 321.608099] desc.status <120200> Sep 4 09:03:04 mail kernel: [ 323.607349] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:04 mail kernel: [ 323.607349] Tx Queue <6> Sep 4 09:03:04 mail kernel: [ 323.607349] TDH <23> Sep 4 09:03:04 mail kernel: [ 323.607349] TDT <23> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_use <25> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_clean<23> Sep 4 09:03:04 mail kernel: [ 323.607349] buffer_info[next_to_clean] Sep 4 09:03:04 mail kernel: [ 323.607349] time_stamp <112af> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_watch Sep 4 09:03:04 mail kernel: [ 323.607349] jiffies <11725> Sep 4 09:03:04 mail kernel: [ 323.607349] desc.status <120200> Sep 4 09:03:06 mail kernel: [ 325.606602] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:06 mail kernel: [ 325.606602] Tx Queue <6> Sep 4 09:03:06 mail kernel: [ 325.606602] TDH <23> Sep 4 09:03:06 mail kernel: [ 325.606602] TDT <23> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_use <25> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_clean<23> Sep 4 09:03:06 mail kernel: [ 325.606602] buffer_info[next_to_clean] Sep 4 09:03:06 mail kernel: [ 325.606602] time_stamp <112af> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_watch Sep 4 09:03:06 mail kernel: [ 325.606602] jiffies <11919> Sep 4 09:03:06 mail kernel: [ 325.606602] desc.status <120200> All network connections droped after that. System still unusable. Only after boot with old linux-image-3.16.0-46-generic my production mail server can work. It's a critical bug for me, can anybody help me? ethtool -i em1 driver: igb version: 5.2.13-k firmware-version: 1.61, 0x8cd5, 1.949.0 bus-info: :02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492146] Re: igb Detected Tx Unit Hang
Hello, any news on this one? We also expecting this problem on two servers - with kernel 3.19.0-33-generic #38~14.04.1-Ubuntu. Anything we can do to make this fixed asap? I'm open to any tests. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1492146 Title: igb Detected Tx Unit Hang Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-utopic source package in Trusty: Fix Released Bug description: Hello! Have a: >lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty with kenel 3.16.0-46-generic. Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic version. After reboot i've got this: Sep 4 09:02:52 mail kernel: [ 310.616324] igb :02:00.0 em1: Reset adapter Sep 4 09:02:52 mail kernel: [ 310.831157] igb :02:00.1 em2: Reset adapter Sep 4 09:02:56 mail kernel: [ 315.154686] igb :02:00.0 em1: igb: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:02:56 mail kernel: [ 315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep 4 09:03:02 mail kernel: [ 321.608099] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:02 mail kernel: [ 321.608099] Tx Queue <6> Sep 4 09:03:02 mail kernel: [ 321.608099] TDH <23> Sep 4 09:03:02 mail kernel: [ 321.608099] TDT <23> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_use <25> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_clean<23> Sep 4 09:03:02 mail kernel: [ 321.608099] buffer_info[next_to_clean] Sep 4 09:03:02 mail kernel: [ 321.608099] time_stamp <112af> Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_watch Sep 4 09:03:02 mail kernel: [ 321.608099] jiffies <11531> Sep 4 09:03:02 mail kernel: [ 321.608099] desc.status <120200> Sep 4 09:03:04 mail kernel: [ 323.607349] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:04 mail kernel: [ 323.607349] Tx Queue <6> Sep 4 09:03:04 mail kernel: [ 323.607349] TDH <23> Sep 4 09:03:04 mail kernel: [ 323.607349] TDT <23> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_use <25> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_clean<23> Sep 4 09:03:04 mail kernel: [ 323.607349] buffer_info[next_to_clean] Sep 4 09:03:04 mail kernel: [ 323.607349] time_stamp <112af> Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_watch Sep 4 09:03:04 mail kernel: [ 323.607349] jiffies <11725> Sep 4 09:03:04 mail kernel: [ 323.607349] desc.status <120200> Sep 4 09:03:06 mail kernel: [ 325.606602] igb :02:00.0: Detected Tx Unit Hang Sep 4 09:03:06 mail kernel: [ 325.606602] Tx Queue <6> Sep 4 09:03:06 mail kernel: [ 325.606602] TDH <23> Sep 4 09:03:06 mail kernel: [ 325.606602] TDT <23> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_use <25> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_clean<23> Sep 4 09:03:06 mail kernel: [ 325.606602] buffer_info[next_to_clean] Sep 4 09:03:06 mail kernel: [ 325.606602] time_stamp <112af> Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_watch Sep 4 09:03:06 mail kernel: [ 325.606602] jiffies <11919> Sep 4 09:03:06 mail kernel: [ 325.606602] desc.status <120200> All network connections droped after that. System still unusable. Only after boot with old linux-image-3.16.0-46-generic my production mail server can work. It's a critical bug for me, can anybody help me? ethtool -i em1 driver: igb version: 5.2.13-k firmware-version: 1.61, 0x8cd5, 1.949.0 bus-info: :02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
