Bug 205357
Summary: | e1000e: Link not detected after resume | ||
---|---|---|---|
Product: | Drivers | Reporter: | dzp (dietz.lkml) |
Component: | Network | Assignee: | drivers_network (drivers_network) |
Status: | RESOLVED UNREPRODUCIBLE | ||
Severity: | normal | CC: | patdung100 |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 5.3.5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: | lspci output |
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. Hi, with version 5.5 I can not reproduce the above anymore. Therefore I'll close this one. |
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!