8086:153a e1000e driver failed with error -3

Bug #1576953 reported by Diego on 2016-04-30
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

When I switch on my laptop, running Ubuntu 16.04 LTS amd64, it will boot and load e1000e, but no eth* interface is present. Even repeated rmmod and modprobe don't bring up the interface. After a reboot (i.e. no fresh power-up) it works just fine. After the next power-cycle the problem is there again. Laptop is a Clevo W130SV, network card is Intel I217-LM (rev 05).

Upstream report:
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005431.html

 dmesg | grep e1000e
[ 0.985539] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 0.985541] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 0.985710] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1.979369] e1000e: probe of 0000:00:19.0 failed with error -3

On warm reboot, last line is gone.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: diego 2235 F.... pulseaudio
 /dev/snd/controlC1: diego 2235 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sat Apr 30 11:24:15 2016
HibernationDevice: RESUME=UUID=1c631208-0b9d-4ea8-b00c-42463325399c
MachineType: TEKNO SERVICE SL W130SV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=011e1a79-9a2b-47d7-a20c-c1b362ffd636 ro splash quiet vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W130SV
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/21/2014:svnTEKNOSERVICESL:pnW130SV:pvrNotApplicable:rvnNotebook:rnW130SV:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W130SV
dmi.product.version: Not Applicable
dmi.sys.vendor: TEKNO SERVICE SL

Diego (gran-diego) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed

Diego, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Diego (gran-diego) wrote :

Test done using v4.6-rc5-willy, Bug still present.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6-rc5
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Diego, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO: Jeff Kirsher, Jesse Brandeburg, Shannon Nelson, Carolyn Wyborny, Don Skidmore, Bruce Allan, John Ronciak, and Mitch Williams CC: intel-wired-lan)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
summary: - e1000e driver failed with error -3
+ 8086:153a e1000e driver failed with error -3
Joerg Albert (jal2) wrote :

Same problem here with a Lenovo T520 and this NIC

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
(8086:1502)

with the official kernel 4.4.0-22-generic #39-Ubuntu

No interface after coldboot, error -3. Everything is fine after a reboot.

Joerg Albert (jal2) wrote :

As I couldn't see any posting from Diego in the intel-wired-lan mailing list during the last two weeks, I've sent a bug report both to Jeff Kirsher and the mailing list:

http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005381.html

(I couldn't find any nicer online archive of the ml, the archive linked above is week-based. So any reply later than one week will go into another URL :-(

Diego (gran-diego) wrote :

I just got home. I've been working abroad without internet access since the bug report.

Joerg, thanks for sending the bug report on my behalf.

I'll be here for several weeks, so anything I could do about this, just let me know.

Joerg Albert, given you have different hardware, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Diego, in order to keep your report relevant to upstream, it is helpful if you continue to test the latest mainline kernel at your convenience (now 4.6).

Diego (gran-diego) wrote :

I've just tested 4.6.0 and bug is still present. Will file the bug upstream

Joerg Albert (jal2) wrote :

@Christopher
I'm pretty sure both Diego's and my bug have the same root cause, but here is my report
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1583750

@Diego
If you are willing to compile the 4.6.0 kernel from the sources, you might try my patch

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1583750/+attachment/4666376/+files/0001-e1000e-added-more-error-output-during-probe.patch

which adds some error output to the e1000e driver. I wonder if you'd get the same line

[ 7900.183212] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): Failed to acquire the semaphore, FW or HW has it: FWSM=0x60000040 EXTCNF_CTRL=0x002800c9)

tags: added: kernel-bug-exists-upstream-4.6
removed: kernel-bug-exists-upstream-4.6-rc5
Diego (gran-diego) wrote :

reported upstream

http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005431.html

@jal2
I'll test it, for sure. I think it'll be done by next tuesday.

description: updated
Diego (gran-diego) wrote :

Finally got it. Long time since last kernel I compiled back in Debian Potato days.

~$ dmesg | grep e1000e
[ 1.273616] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.273619] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.273784] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2.270530] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): Failed to acquire the semaphore, FW or HW has it: FWSM=0x60000040 EXTCNF_CTRL=0x002800c9)
[ 2.272412] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): Failed to initialize PHY flow (-3)
[ 2.273634] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): e1000_init_phy_params_pchlan: e1000_init_phy_workarounds_pchlan returned -3
[ 2.275351] e1000e 0000:00:19.0: e1000_init_phy_params-* failed with -3 (mac.type 11)
[ 2.276444] e1000e 0000:00:19.0: ei->get_variants failed with -3
[ 2.286596] e1000e: probe of 0000:00:19.0 failed with error -3

Diego (gran-diego) wrote :

And this is the log after a warm reboot

~$ dmesg | grep e1000e
[ 1.308156] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.308158] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.308326] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1.481950] e1000e 0000:00:19.0 eth0: registered PHC clock
[ 1.481954] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 80:fa:5b:13:9f:02
[ 1.481956] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.482015] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 32.693226] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 32.693232] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO

Diego (gran-diego) wrote :

Joerg Albert, you were right. We are suffering the same bug.

I've updated bug report upstream

http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160523/005468.html

You-Sheng Yang (vicamo) wrote :

https://bbs.archlinux.org/viewtopic.php?id=185765
Some reports said an update to BIOS would fix this issue, so please definitely have a try.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers