e1000e driver failed with error -3

Bug #984404 reported by P. S.
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

When I switch on my system, 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. The system board is a EVGA P55V with onboard Intel 82578DC controller.

I found the difference between the "good" (reboot) and "bad" (power-on) is the last line of this syslog snippet:

[ 1.016930] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[ 1.016932] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 1.016970] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 1.016976] e1000e 0000:00:19.0: setting latency timer to 64
[ 1.017042] e1000e 0000:00:19.0: irq 32 for MSI/MSI-X
[ 2.013270] e1000e 0000:00:19.0: PCI INT A disabled
[ 2.013283] e1000e: probe of 0000:00:19.0 failed with error -3

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-40-generic 2.6.32-40.87
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stevie 1448 F.... kmix
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ef4000 irq 22'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,38420075,00100202'
   Controls : 35
   Simple ctrls : 20
Date: Tue Apr 17 23:43:37 2012
HibernationDevice: RESUME=UUID=9583944a-2835-4185-b4a1-9c50c635e53f
InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-40-generic root=UUID=869a5efd-f9e2-465d-9f6c-66584e353e4e ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:

SourcePackage: linux
dmi.bios.date: 12/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 120-LF-E650
dmi.board.vendor: EVGA
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd12/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrRev1.xx:rvnEVGA:rn120-LF-E650:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: Rev 1.xx
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
P. S. (sadowsky46) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Luis Henriques (henrix) wrote :

I did a quick search for this problem, and it looks like it could be a BIOS issue, not setting up interrupts correctly. Could you please check for any BIOS upgrades for your system?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
P. S. (sadowsky46) wrote :

Ok, after two years there is a BIOS update with small changes. But they don't refer to interrupt settings. Will try it later this week.

BTW, I just tried Knoppix v7 with Kernel 3.2.4 and e1000e driver version 1.5.1-k. This does not show the issue. It seems newer driver versions have a solution built-in. Maybe 10.04 deserves a back-port of that fix, because other systems seem to suffer from the same issue. There are similar bug reports related to e1000e failures.

Revision history for this message
P. S. (sadowsky46) wrote :

I updated to the latest BIOS version (0407) today. The problem stays the same. No change.

Revision history for this message
laloi (laloi666) wrote :

I think I have the same bug with Linux version 3.2.0-24-generic (buildd@yellow) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 (Ubuntu 3.2.0-24.37-generic 3.2.14).

When I switch on my system (bad):
[ 2.323029] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
[ 2.323032] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 2.323125] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 2.323135] e1000e 0000:00:19.0: setting latency timer to 64
[ 2.323399] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 3.373701] e1000e 0000:00:19.0: PCI INT A disabled
[ 3.373707] e1000e: probe of 0000:00:19.0 failed with error -3

when I reboot (good):
[ 2.296107] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
[ 2.296109] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[ 2.296143] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 2.296152] e1000e 0000:00:19.0: setting latency timer to 64
[ 2.296250] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 2.570111] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:01:29:00:ee:b3
[ 2.570114] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[ 2.570166] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: FFFFFF-0FF
[ 17.574732] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 17.630464] e1000e 0000:00:19.0: irq 40 for MSI/MSI-X
[ 19.097427] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx
[ 19.097431] e1000e 0000:00:19.0: eth0: 10/100 speed: disabling TSO

Revision history for this message
penalvch (penalvch) wrote :

P. S., this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
P. S. (sadowsky46) wrote :

This is funny: if there is no activity the bug report simply vanishes? Ok, all problems go away finally if we throw the affected HW away ...

Changed in linux (Ubuntu):
status: Expired → New
Revision history for this message
P. S. (sadowsky46) wrote :

I mean - is there any additional information we can provide in order to hunt down the bug?

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Diego (gran-diego) wrote :

bug still present in ubuntu 16.04 (kernel 4.4.0-21)

Revision history for this message
penalvch (penalvch) wrote :

Diego, 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.

Revision history for this message
Diego (gran-diego) wrote :

New bug filed, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576953

Christopher, I've subscribed you to it.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.