Bug 205357 - e1000e: Link not detected after resume
Summary: e1000e: Link not detected after resume
Status: RESOLVED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-30 08:05 UTC by dzp
Modified: 2020-01-30 17:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.3.5
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
lspci output (2.48 KB, text/plain)
2019-10-30 08:05 UTC, dzp
Details

Description dzp 2019-10-30 08:05:37 UTC
Created attachment 285715 [details]
lspci output

Hi,

(this is my first bug report here, plz be gentle if I screwed it up ;-) )

there might be a regression in the e1000e ethernet driver:

After upgrade from 5.2.13 to 5.3.5 (both not from distribution but self-built), the ethernet interface does sometimes (3 out of 5 times I think) not detect the cable connected after a resume.
There are no anormalities in the system log (apart from "e1000e: eth0 NIC Link is Down" of course ;-) ). Unloading and loading the e1000e module does not help, if I put the system to sleep and resume several times, the link eventually works again.

Reverting to 5.2.13 resolves the problem. I assume, that this is also present in 5.3, but did not test.

The system in question is a Lenovo T580 laptop running Debian/unstable. I added the lspci output

Feel free to ask for additional information!
Comment 1 dzp 2019-11-10 11:15:02 UTC
After playing around a little, it seems that Energy-Efficient Ethernet (IEEE 802.3az) might be the culprit.

If I switch EEE off for the interface in question (i.e. by ethtool --set-eee eth0 eee off) then the link gets detected reliably. Switching it on again, once the link got detected works, too.
Comment 2 dzp 2020-01-30 17:12:45 UTC
Hi,

with version 5.5 I can not reproduce the above anymore.

Therefore I'll close this one.

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