Bug 203769 - Regression: Valid network link no longer detected
Summary: Regression: Valid network link no longer detected
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
: 204099 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-06-01 09:53 UTC by Greg White
Modified: 2019-07-15 00:05 UTC (History)
8 users (show)

See Also:
Kernel Version: 5.2.0-rc2
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Greg White 2019-06-01 09:53:51 UTC
Commit 7dc2bccab0ee37ac28096b8fcdc390a679a15841 has broken wired networking on two of my machines.  Drivers e1000e, igb and r8169 all fail to detect link with this commit applied.  The drivers load and appear to initialize correctly, but no link is ever detected.

With this commit reverted, they work perfectly.

This is on a fully updated Arch.  Happy to provide any other information that is of use.
Comment 1 kyle.d.pelton 2019-06-05 21:10:32 UTC
I've also noticed this. 

The commit breaks systemd-networkd with the following error:

/usr/lib/systemd/systemd-networkd
Enumeration completed
ens2: Could not bring up interface: Invalid argument

I am running systemd v241
Comment 2 Yanko Kaneti 2019-06-09 01:40:16 UTC
I can confirm the same on Fedora rawhide.

Again a systemd-networkd setup. 
If I manually ip link set up   the device it comes up and works.
Comment 3 Nicolas Mailhot 2019-06-09 08:43:40 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1718192 has another breakage example, with e1000, alx and bond
Comment 5 Stephen Hemminger 2019-07-09 15:26:26 UTC
*** Bug 204099 has been marked as a duplicate of this bug. ***
Comment 6 Ian Kumlien 2019-07-09 17:31:01 UTC
I don't know if this is only systemd:s fault - 5.1.16 works just fine with the same binaries.

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