Bug 56621 - Intel 82579LM Gigabit Network adapter deactivated on boot, has to be activated separately
Summary: Intel 82579LM Gigabit Network adapter deactivated on boot, has to be activate...
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-15 06:56 UTC by Harvey
Modified: 2013-11-13 21:08 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.8.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Harvey 2013-04-15 06:56:50 UTC
I have a Fujitsu Laptop E751 vPro. According to lspci the network adapter is:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
The kernel uses e1000e as the kernel driver.
When I boot my latop with kernel 3.8.7 and a network cable plugged in, the Adaper is down. 'Ip addr show' says:
4: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 5c:9a:d8:e7:c1:c8 brd ff:ff:ff:ff:ff:ff
I googled around a bit and found that e1000e had some bugs in the past, but all should be fixed now.
Issuing 'echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control' on a shell gets the adapter up and working without problems. All other mentioned things do not work. Unplugging and replugging, sending system to standby and waking it again a.s.o.
Comment 1 Christophe Morvan 2013-04-29 11:03:24 UTC
I am experiencing a similar bug on my lenovo x230.
(I did since 3.8.3, and in 3.8.6 -- from kernel.org)

It happen *after* resuming *and* when AC is not plugged in.

Plugging the AC in or performing the line 'echo on > /sys/bus/pci/devices/0000\:00\:19.0/power/control' resume to nominal performance.
Comment 2 Christophe Morvan 2013-04-29 11:06:17 UTC
It is most probably related to bug 56611:

https://bugzilla.kernel.org/show_bug.cgi?id=56611
Comment 3 Christophe Morvan 2013-05-01 09:37:03 UTC
This bug is corrected in kernel 3.9.0
(Maybe earlier)
Comment 4 Harvey 2013-05-01 11:17:48 UTC
For me its corrected with 3.9.0

Note You need to log in before you can comment on or make changes to this bug.