[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
Hello, we have the very same problem after upgrading to ubuntu 18.04 . Server is not booting anymore, hanging on: aacraid: Host Adapter abort request. aacraid: Outstanding commands on (1,1,241,0): aacraid: Host Adapter abort request. aacraid: Outstanding commands on (1,1,242,0): aacraid: Host Adapter abort request. aacraid: Outstanding commands on (1,1,243,0): etc etc. # uname -a Linux 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 RAID bus controller: Adaptec Series 6 - 6G SAS/PCIe 2 (rev 01) -- 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/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
Adaptec/Microsemi support recommends to replace the RAID card for ubuntu 18.04.. Answer from support: Unfortunately, this card has no drivers for Ubunto 18. See it's product page here https://storage.microsemi.com/en-us/support/raid/sas_raid/sas-6405e/ Replacement card is https://storage.microsemi.com/en-us/support/raid/sas_raid/asr-8405e/ which contains driver availability for Ubuntu 18. -- 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/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello, same issue here on Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX331UN with kernel: Linux shadow 5.0.0-16-generic #17~18.04.1-Ubuntu SMP Mon May 20 14:00:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Occasionally, the touchpad freezes. Following message is printed in dmesg: Jun 12 17:35:32 shadow kernel: [ 522.384692] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: IRQ triggered but there's no data The touchpad then needs to be disabled/reenabled using feature key on keyboard. -- 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/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1348832] Re: e1000e Detected Hardware Unit Hang
Hello all, this happened right now on my server using 3.13.0-39-generic . The NIC was under I/O due to concurring backups. In my syslog i found many lines of: Nov 10 23:21:17 server kernel: [759261.907344] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 10 23:21:17 server kernel: [759261.907344] TDH Nov 10 23:21:17 server kernel: [759261.907344] TDT Nov 10 23:21:17 server kernel: [759261.907344] next_to_use Nov 10 23:21:17 server kernel: [759261.907344] next_to_clean Nov 10 23:21:17 server kernel: [759261.907344] buffer_info[next_to_clean]: Nov 10 23:21:17 server kernel: [759261.907344] time_stamp <10b4f2f76> Nov 10 23:21:17 server kernel: [759261.907344] next_to_watch Nov 10 23:21:17 server kernel: [759261.907344] jiffies <10b4f30c5> Nov 10 23:21:17 server kernel: [759261.907344] next_to_watch.status <0> Nov 10 23:21:17 server kernel: [759261.907344] MAC Status <40080183> Nov 10 23:21:17 server kernel: [759261.907344] PHY Status <796d> Nov 10 23:21:17 server kernel: [759261.907344] PHY 1000BASE-T Status <3800> Nov 10 23:21:17 server kernel: [759261.907344] PHY Extended Status<3000> Nov 10 23:21:17 server kernel: [759261.907344] PCI Status <10> # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller (rev 09) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C204 Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 RAID bus controller: Adaptec Series 6 - 6G SAS/PCIe 2 (rev 01) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) any help appreciated. -- 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/1348832 Title: e1000e Detected Hardware Unit Hang Status in “linux” package in Ubuntu: Expired Bug description: e1000e device on a trusty router/server/etc, up for a few weeks, stopped responding and went into a "Detected Hardware Unit Hang" loop. At the time, the interface was under moderate load, about 60mbps inbound. [1871400.121801] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871400.121801] TDH <92> [1871400.121801] TDT [1871400.121801] next_to_use [1871400.121801] next_to_clean<90> [1871400.121801] buffer_info[next_to_clean]: [1871400.121801] time_stamp <11be7959f> [1871400.121801] next_to_watch<92> [1871400.121801] jiffies <11be79797> [1871400.121801] next_to_watch.status <0> [1871400.121801] MAC Status <80083> [1871400.121801] PHY Status <796d> [1871400.121801] PHY 1000BASE-T Status <7800> [1871400.121801] PHY Extended Status<3000> [1871400.121801] PCI Status <10> [1871402.120130] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871402.120130] TDH <92> [1871402.120130] TDT [1871402.120130] next_to_use [1871402.120130] next_to_clean<90> [1871402.120130] buffer_info[next_to_clean]: [1871402.120130] time_stamp <11be7959f> [1871402.120130] next_to_watch<92> [1871402.120130] jiffies <11be7998b> [1871402.120130] next_to_watch.status <0> [1871402.120130] MAC Status <80083> [1871402.120130] PHY Status <796d> [1871402.120130] PHY 1000BASE-T Status <7800> [1871402.120130] PHY Extended Status<3000> [1871402.120130] PCI Status <10> [1871404.118513] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [1871404.118513] TDH <92> [1871404.118513] TDT [1871404.118513] next_to_use [1871404.118513] next_to_clean<90> [1871404.118513] buffer_info[next_to_clean]: [1871404.118513] time_stamp <11be7959f> [1871404.118513] next_to_watch<92> [1871404.1185
[Kernel-packages] [Bug 1391674] [NEW] "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
Public bug reported: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <40080183> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status <3800> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status<3000> Nov 11 23:29:10 argeste kernel: [846173.956722] PCI Status <10> Nov 11 23:29:12 argeste kernel: [846175.956759] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:12 argeste kernel: [846175.956759] TDH <0> Nov 11 23:29:12 argeste kernel: [846175.956759] TDT <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_use <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_clean<0> Nov 11 23:29:12 argeste kernel: [846175.956759] buffer_info[next_to_clean]: Nov 11 23:29:12 argeste kernel: [846175.956759] time_stamp <10c9ab819> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch<0> Nov 11 23:29:12 argeste kernel: [846175.956759] jiffies <10c9abdb9> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch.status <0> Nov 11 23:29:12 argeste kernel: [846175.956759] MAC Status <40080183> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Status <796d> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY 1000BASE-T Status <3800> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Extended Status<3000> Nov 11 23:29:12 argeste kernel: [846175.956759] PCI Status <10> Nov 11 23:29:14 argeste kernel: [846177.956686] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:14 argeste kernel: [846177.956686] TDH <0> Nov 11 23:29:14 argeste kernel: [846177.956686] TDT <1> Nov 11 23:29:14 argeste kernel: [846177.956686] next_to_use <1> Nov 11 23:29:14 argeste kernel: [846177.956686] next_to_clean<0> Nov 11 23:29:14 argeste kernel: [846177.956686] buffer_info[next_to_clean]: Nov 11 23:29:14 argeste kernel: [846177.956686] time_stamp <10c9ab819> Nov 11 23:29:14 argeste kernel: [846177.956686] next_to_watch<0> Nov 11 23:29:14 argeste kernel: [846177.956686] jiffies <10c9abfad> Nov 11 23:2
[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
Hello Cristopher, I have managed to update the firmware of all the servers. The issue is still happening: # dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2.10 01/09/2014 # uname -a Linux 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux After starting an high bandwidth load (backups): [95407.726267] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [95407.726267] TDH <0> [95407.726267] TDT <1> [95407.726267] next_to_use <1> [95407.726267] next_to_clean<0> [95407.726267] buffer_info[next_to_clean]: [95407.726267] time_stamp <1016abfd3> [95407.726267] next_to_watch<0> [95407.726267] jiffies <1016ac6eb> [95407.726267] next_to_watch.status <0> [95407.726267] MAC Status <40080183> [95407.726267] PHY Status <796d> [95407.726267] PHY 1000BASE-T Status <3800> [95407.726267] PHY Extended Status<3000> [95407.726267] PCI Status <10> [95409.726297] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: [95409.726297] TDH <0> [95409.726297] TDT <1> [95409.726297] next_to_use <1> [95409.726297] next_to_clean<0> [95409.726297] buffer_info[next_to_clean]: [95409.726297] time_stamp <1016abfd3> [95409.726297] next_to_watch<0> [95409.726297] jiffies <1016ac8df> [95409.726297] next_to_watch.status <0> [95409.726297] MAC Status <40080183> [95409.726297] PHY Status <796d> [95409.726297] PHY 1000BASE-T Status <3800> [95409.726297] PHY Extended Status<3000> [95409.726297] PCI Status <10> [95409.729969] e1000e :00:19.0 eth1: Reset adapter unexpectedly ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- 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/1391674 Title: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O Status in linux package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <
[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
On a side note: the issue doesn't happen using old kernel version linux- image-3.5.0-45-generic_3.5.0-45.68~precise1 -- 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/1391674 Title: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O Status in linux package in Ubuntu: Incomplete Bug description: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <40080183> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status <3800> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status<3000> Nov 11 23:29:10 argeste kernel: [846173.956722] PCI Status <10> Nov 11 23:29:12 argeste kernel: [846175.956759] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:12 argeste kernel: [846175.956759] TDH <0> Nov 11 23:29:12 argeste kernel: [846175.956759] TDT <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_use <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_clean<0> Nov 11 23:29:12 argeste kernel: [846175.956759] buffer_info[next_to_clean]: Nov 11 23:29:12 argeste kernel: [846175.956759] time_stamp <10c9ab819> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch<0> Nov 11 23:29:12 argeste kernel: [846175.956759] jiffies <10c9abdb9> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch.status <0> Nov 11 23:29:12 argeste kernel: [846175.956759] MAC Status <40080183> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Status <796d> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY 1000BASE-T Status <3800> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Extended Status<3000> Nov 11 23:29:12 argeste kernel: [846175.956759] PCI Status <10> Nov 11 23:29:14 argeste kernel: [846177.956686] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:14 argeste kernel: [846177.956686] TDH <0> Nov 11 23:29:14 argeste
[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
I switched my 3 Supermicro X9SCL/X9SCM servers to 3.19.0-031900rc6-generic and the issue is repeating again under heavy I/O (during backups on DRBD-backed xen guests). The issue happens on all the servers. Feb 1 00:47:55 hostname kernel: [179433.583173] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Feb 1 00:47:55 hostname kernel: [179433.583173] TDH <7c> Feb 1 00:47:55 hostname kernel: [179433.583173] TDT <89> Feb 1 00:47:55 hostname kernel: [179433.583173] next_to_use <89> Feb 1 00:47:55 hostname kernel: [179433.583173] next_to_clean<7a> Feb 1 00:47:55 hostname kernel: [179433.583173] buffer_info[next_to_clean]: Feb 1 00:47:55 hostname kernel: [179433.583173] time_stamp <102ab4e95> Feb 1 00:47:55 hostname kernel: [179433.583173] next_to_watch<7c> Feb 1 00:47:55 hostname kernel: [179433.583173] jiffies <102ab5089> Feb 1 00:47:55 hostname kernel: [179433.583173] next_to_watch.status <0> Feb 1 00:47:55 hostname kernel: [179433.583173] MAC Status <40080183> Feb 1 00:47:55 hostname kernel: [179433.583173] PHY Status <796d> Feb 1 00:47:55 hostname kernel: [179433.583173] PHY 1000BASE-T Status <3800> Feb 1 00:47:55 hostname kernel: [179433.583173] PHY Extended Status<3000> Feb 1 00:47:55 hostname kernel: [179433.583173] PCI Status <10> >> uname -a Linux hostname 3.19.0-031900rc6-generic #201501261152 SMP Mon Jan 26 16:53:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.19-rc6 -- 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/1391674 Title: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O Status in linux package in Ubuntu: Incomplete Bug description: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <40080183> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status <3800> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status
[Kernel-packages] [Bug 1391674] Re: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1391674 Title: "Reset adapter unexpectedly" - NIC hangs using e1000e driver under average I/O Status in linux package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 LTS > uname -a Linux argeste 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux /var/log/syslog: Nov 11 23:29:00 argeste kernel: [846163.967778] e1000e :00:19.0 eth1: Reset adapter unexpectedly Nov 11 23:29:01 argeste kernel: [846163.982417] xen-br1: port 1(eth1) entered disabled state Nov 11 23:29:05 argeste kernel: [846168.028959] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Nov 11 23:29:05 argeste kernel: [846168.029085] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:05 argeste kernel: [846168.029094] xen-br1: port 1(eth1) entered forwarding state Nov 11 23:29:08 argeste kernel: [846171.956810] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:08 argeste kernel: [846171.956810] TDH <0> Nov 11 23:29:08 argeste kernel: [846171.956810] TDT <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_use <1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_clean<0> Nov 11 23:29:08 argeste kernel: [846171.956810] buffer_info[next_to_clean]: Nov 11 23:29:08 argeste kernel: [846171.956810] time_stamp <10c9ab819> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch<0> Nov 11 23:29:08 argeste kernel: [846171.956810] jiffies <10c9ab9d1> Nov 11 23:29:08 argeste kernel: [846171.956810] next_to_watch.status <0> Nov 11 23:29:08 argeste kernel: [846171.956810] MAC Status <40080183> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Status <796d> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY 1000BASE-T Status <3800> Nov 11 23:29:08 argeste kernel: [846171.956810] PHY Extended Status<3000> Nov 11 23:29:08 argeste kernel: [846171.956810] PCI Status <10> Nov 11 23:29:10 argeste kernel: [846173.956722] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:10 argeste kernel: [846173.956722] TDH <0> Nov 11 23:29:10 argeste kernel: [846173.956722] TDT <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_use <1> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_clean<0> Nov 11 23:29:10 argeste kernel: [846173.956722] buffer_info[next_to_clean]: Nov 11 23:29:10 argeste kernel: [846173.956722] time_stamp <10c9ab819> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch<0> Nov 11 23:29:10 argeste kernel: [846173.956722] jiffies <10c9abbc5> Nov 11 23:29:10 argeste kernel: [846173.956722] next_to_watch.status <0> Nov 11 23:29:10 argeste kernel: [846173.956722] MAC Status <40080183> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Status <796d> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY 1000BASE-T Status <3800> Nov 11 23:29:10 argeste kernel: [846173.956722] PHY Extended Status<3000> Nov 11 23:29:10 argeste kernel: [846173.956722] PCI Status <10> Nov 11 23:29:12 argeste kernel: [846175.956759] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:12 argeste kernel: [846175.956759] TDH <0> Nov 11 23:29:12 argeste kernel: [846175.956759] TDT <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_use <1> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_clean<0> Nov 11 23:29:12 argeste kernel: [846175.956759] buffer_info[next_to_clean]: Nov 11 23:29:12 argeste kernel: [846175.956759] time_stamp <10c9ab819> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch<0> Nov 11 23:29:12 argeste kernel: [846175.956759] jiffies <10c9abdb9> Nov 11 23:29:12 argeste kernel: [846175.956759] next_to_watch.status <0> Nov 11 23:29:12 argeste kernel: [846175.956759] MAC Status <40080183> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Status <796d> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY 1000BASE-T Status <3800> Nov 11 23:29:12 argeste kernel: [846175.956759] PHY Extended Status<3000> Nov 11 23:29:12 argeste kernel: [846175.956759] PCI Status <10> Nov 11 23:29:14 argeste kernel: [846177.956686] e1000e :00:19.0 eth1: Detected Hardware Unit Hang: Nov 11 23:29:14 argeste kernel: [846177.956686] TDH <0> Nov 11 23:29:14 argeste kernel: [846177.956686] TDT <