New: e1000 network driver doesn't recognize (and load on) its hardware
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]/
Quoted 29 lines · On Mon, 28 Jan 2008 05:32:00 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9836
Summary: e1000 network driver doesn't recognize (and load on) its hardware Product: Drivers Version: 2.5 KernelVersion: 2.6.24 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Network AssignedTo: [email protected] ReportedBy: [email protected]Latest working kernel version: not known
Earliest failing kernel version: every
Distribution: Fedora Core 7
Hardware Environment: lspci output and dmesg information are attached Software Environment: doesn't matter
Problem Description: recently e1000 network drivers stopped working when right after switching on or rebooting our Intel server. While trying to 'modprobe e1000; ifconfig eth0IP_address' I've got a failure and e1000 says hardware is not detected. After about a *hundred* attempts to modprobe and rmmod it, the e1000 network driver finally loads and allows to set up networking.
Quoted 3 lines
Steps to reproduce: reboot or power on your server. Try to up the network which is attached to your Intel PCI-X Pro 1000 NIC.
Odd.
Quoted 10 lines · Andrew Morton
Quoted 7 lines · On Mon, 28 Jan 2008 05:32:00 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9836
Problem Description: recently e1000 network drivers stopped working when right after switching on or rebooting our Intel server. While trying to 'modprobe e1000; ifconfig eth0IP_address' I've got a failure and e1000 says hardware is not detected. After about a *hundred* attempts to modprobe and rmmod it, the e1000 network driver finally loads and allows to set up networking.
I'm not sure how you figured out rmmod/insmoding the driver gets you working, but I don't see any failure messages in the dmesg log you sent, I just see:
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:07:04.0[A] -> GSI 16 (level, low) -> IRQ 16
e1000: 0000:07:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:04:23:cc:82:5e
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI interrupt for device 0000:07:04.0 disabled Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:07:04.0[A] -> GSI 16 (level, low) -> IRQ 16
e1000: 0000:07:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:04:23:cc:82:5e
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI interrupt for device 0000:07:04.0 disabled Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:07:04.0[A] -> GSI 16 (level, low) -> IRQ 16
e1000: 0000:07:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:04:23:cc:82:5e
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow
Control: RX/TX
I believe the PCI interrupt for device 7:4.0 disabled is you unloading the driver again each time, and I don't see any messages at all that indicate the driver knows anything is wrong.
can you run 'ethtool -t eth0 offline' after rebooting, loading the module, ifconfig eth0 up, and waiting 4 seconds?
what does ethtool eth0 say after loading the driver (before you ifconfig up it?) are you sure you're not having some udev problem? Can you send the console output or attach it to the bug?
Quoted 2 lines
Quoted 2 lines
Steps to reproduce: reboot or power on your server. Try to up the network which is attached to your Intel PCI-X Pro 1000 NIC.
This is a PCI only adapter, FYI.
Quoted 3 lines
Quoted 1 line
Odd.
agreed, something doesn't add up here, yet.