This bug should be a top priority because people will suffer from it as soon as
they reboot
their 14.04 LTS with an Intel Gigabit NIC and the "current" Utopic kernel
(3.16.0-48-generic).
I had the same problem with HP ProLiant DL380e Gen8 which an Intel I350 Gigabit
NIC
(Hewlett-Packard Company Ethernet 1Gb 4-port 366i Adapter)
It was hard to get a shell with 30-50% packets drop and igb driver resetting
ALL NICs...
"blind-typing" on the shell and wait 1-2 minutes to get the output... of dmesg
;-)
I updated the kernel of 14.04 LTS from Utopic to Vivid and everything is
working again.
Workaround is:
screen -S kernel
apt-get -y purge linux-{headers,image,image-extra}-3.16.0-48-generic
apt-get -y install linux-image-generic-lts-vivid linux-headers-generic-lts-vivid
reboot
Output of dmesg:
igb 0000:02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
igb 0000:02:00.1: Detected Tx Unit Hang
Tx Queue <3>
TDH <0>
TDT <0>
next_to_use <4>
next_to_clean <0>
buffer_info[next_to_clean]
time_stamp <100039540>
next_to_watch <ffff880230b0e030>
jiffies <1000397b6>
desc.status <0>
igb 0000:02:00.1 em2: Reset adapter
igb 0000:02:00.2 em3: Reset adapter
igb 0000:02:00.0 em1: Reset adapter
igb 0000:02:00.0 em1: igb: em1 NIC Link is Up 100 Mbps Full Duplex, Flow
Control: RX
igb 0000:02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
igb 0000:02:00.1: Detected Tx Unit Hang
--
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
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 0000:02:00.0 em1: Reset
adapter Sep 4 09:02:52 mail kernel: [ 310.831157] igb 0000:02:00.1 em2: Reset
adapter Sep 4 09:02:56 mail kernel: [ 315.154686] igb 0000: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 0000: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
0000: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 <1000012af>
Sep 4 09:03:02 mail kernel: [ 321.608099] next_to_watch
<ffff880272571240>
Sep 4 09:03:02 mail kernel: [ 321.608099] jiffies <100001531>
Sep 4 09:03:02 mail kernel: [ 321.608099] desc.status <120200>
Sep 4 09:03:04 mail kernel: [ 323.607349] igb 0000: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 <1000012af>
Sep 4 09:03:04 mail kernel: [ 323.607349] next_to_watch
<ffff880272571240>
Sep 4 09:03:04 mail kernel: [ 323.607349] jiffies <100001725>
Sep 4 09:03:04 mail kernel: [ 323.607349] desc.status <120200>
Sep 4 09:03:06 mail kernel: [ 325.606602] igb 0000: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 <1000012af>
Sep 4 09:03:06 mail kernel: [ 325.606602] next_to_watch
<ffff880272571240>
Sep 4 09:03:06 mail kernel: [ 325.606602] jiffies <100001919>
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, 0x80000cd5, 1.949.0
bus-info: 0000: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
