Bug 90188

Summary:	systemd-networkd regression failing to configure connected device
Product:	systemd	Reporter:	Kai Hendry <hendry>
Component:	general	Assignee:	Tom Gundersen <teg>
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium	CC:	jckeerthan
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Kai Hendry 2015-04-27 04:12:36 UTC

On my X1 Carbon Gen 3 with my network dongle, systemd-networkd is failing to notice the connection is UP and get an IP address

http://s.natalian.org/2015-04-27/1430107323_1912x1036.png

My workaround is to now use `dhclient`.

I say this is a regression as I'm confident it used to work before <218. I'm using 219-6 on Archlinux.

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03)
        Subsystem: Lenovo Device 2227
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 43
        Region 0: Memory at f1100000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at f113e000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at 3080 [size=32]
        Capabilities: <access denied>
        Kernel driver in use: e1000e
        Kernel modules: e1000e

Comment 1 Lennart Poettering 2016-06-07 11:02:17 UTC

I am pretty sure this works these days. If this still an issue, please file a new bug on github systemd!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.