4.14.0 final crashed hard after running 17 hours. Not only was the
ethernet not-responsive, neither was the console, not even the magic
sys-req key. I had to power cycle the machine to get it unhung. Then
I booted 4.14.0rc1 and it immediately exploded however I had set a 20 second
time out and the machine self booted back into 4.15.0-21 and I turned hardware
offloading back off.
I can not continue testing this on production machines and the one Intel
machine I have with that interface chip is currently broken. I'll work on
getting that working and setup a web server on it and use some test software
to put a load on it.
One thing I found digging in github is that there has been only one
commit against the E1000 driver in the last three years and that was on
February 13th, so might be worth looking at.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Fri, 11 May 2018, Joseph Salisbury wrote:
> Date: Fri, 11 May 2018 12:31:14 -0000
> From: Joseph Salisbury <joseph.salisb...@canonical.com>
> Reply-To: Bug 1766377 <1766...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1766377] Re: Ethernet E1000 Controller Hangs
>
> Thanks for testing. We should work backwards towards 4.13 now. Can you
> test the following:
>
> 4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
> 4.14-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4/
> 4.14-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/
>
>
> You don't have to test every kernel, just up until the kernel that first has
> this bug.
>
> Thanks in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1766377
>
> Title:
> Ethernet E1000 Controller Hangs
>
> Status in linux package in Ubuntu:
> Incomplete
> Status in linux source package in Bionic:
> Incomplete
>
> Bug description:
> With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic
> hanging of the LAN connection. This is happening on an Asus X99-DELUX
> motherboard, controller specifications:
> Intel® I218V, 1 x Gigabit LAN Controller(s)
> Intel® I211-AT, 1 x Gigabit LAN
> Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE)
> appliance
> Support Teaming Technology
> ASUS Turbo LAN Utility
> The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
> This machine has a number of Qemu/KVM virtual guests and is using a software
> bridge to share the interface.
> This did not happen with 17.10 and 4.13.0 kernel. It is happening on
> multiple machines here.
> Here are the messages from dmesg:
> 1016198.957850] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
> TDH <ea>
> TDT <2d>
> next_to_use <2d>
> next_to_clean <e9>
> buffer_info[next_to_clean]:
> time_stamp <13c8d0008>
> next_to_watch <ea>
> jiffies <13c8d0880>
> next_to_watch.status <0>
> MAC Status <80083>
> PHY Status <796d>
> PHY 1000BASE-T Status <3c00>
> PHY Extended Status <3000>
> PCI Status <10>
> [1016200.942072] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
> TDH <ea>
> TDT <2d>
> next_to_use <2d>
> next_to_clean <e9>
> buffer_info[next_to_clean]:
> time_stamp <13c8d0008>
> next_to_watch <ea>
> jiffies <13c8d1040>
> next_to_watch.status <0>
> MAC Status <80083>
> PHY Status <796d>
> PHY 1000BASE-T Status <3c00>
> PHY Extended Status <3000>
> PCI Status <10>
> [1016202.413607] e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly
> [1016202.413701] bridge0: port 1(eno1) entered disabled state
> [1016202.413732] bridge0: topology change detected, propagating
> [1016206.666676] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: Rx/Tx
> [1016206.666708] bridge0: port 1(eno1) entered blocking state
> [1016206.666712] bridge0: port 1(eno1) entered listening state
> [1016216.750911] bridge0: port 1(eno1) entered learning state
> [1016232.110291] bridge0: port 1(eno1) entered forwarding state
> [1016232.110294] bridge0: topology change detected, sending tcn bpdu
> [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for
> regulatory database
> [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> [1017834.414792] platform regulatory.0: Direct firmware load for
> regulatory.db failed with error -2
> [1017834.414794] cfg80211: failed to load regulatory.db
> If there is any other information I can provide to aid in resolution, please
> contact me, nan...@eskimo.com. Thank you!
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
> ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
> Uname: Linux 4.15.0-15-lowlatency x86_64
> ApportVersion: 2.20.9-0ubuntu6
> Architecture: amd64
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3',
> '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p',
> '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p',
> '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0',
> '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer']
> failed with exit code 1:
> CurrentDesktop: MATE
> Date: Mon Apr 23 16:45:30 2018
> HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
> InstallationDate: Installed on 2017-05-05 (353 days ago)
> InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
> MachineType: ASUS All Series
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency
> root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1
> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
> RelatedPackageVersions:
> linux-restricted-modules-4.15.0-15-lowlatency N/A
> linux-backports-modules-4.15.0-15-lowlatency N/A
> linux-firmware 1.173
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: Upgraded to bionic on 2018-04-12 (11 days ago)
> dmi.bios.date: 08/11/2017
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1801
> dmi.board.asset.tag: Default string
> dmi.board.name: X99-E
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Default string
> dmi.chassis.type: 3
> dmi.chassis.vendor: Default string
> dmi.chassis.version: Default string
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1801:bd08/11/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
> dmi.product.family: ASUS MB
> dmi.product.name: All Series
> dmi.product.version: System Version
> dmi.sys.vendor: ASUS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766377
Title:
Ethernet E1000 Controller Hangs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
