Bug 201049

Summary:	Ethernet device not starting when steam controller is connected while rebooting
Product:	Drivers	Reporter:	Jan Jurzitza (kernel.org)
Component:	Other	Assignee:	drivers_other
Status:	NEW ---
Severity:	normal
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	4.18.6	Subsystem:
Regression:	No	Bisected commit-id:

Description Jan Jurzitza 2018-09-08 16:31:16 UTC

When a steam controller is connected with the built-in driver in the kernel now and a `reboot` is done (and the steam controller stays connected until booted), the ethernet device (in this bug called enp12s0) will not go up and cannot be turned on.

The device will be listed on `ifconfig -a` and `ip link`, however trying to "up" it will fail in a "RTNETLINK answers: No such device" even though it is there.

Very rarely (so far once out of 15 boots) it can also happen that the ethernet device does actually start up while the steam controller is connected.

Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)



`dmesg` does not show any error messages and is nearly the same as a dmesg on a working boot with the steam controller not connected. The only differences in dmesg output are that with the steam controller connected the line

IPv6: ADDRCONF(NETDEV_CHANGE): enp12s0: link becomes ready

is missing, but about 4 more

IPv6: ADDRCONF(NETDEV_UP): enp12s0: link is not ready

are being printed. (Note that that line is also printed on a working boot, just only a few times)

Also a working boot additionally has this dmesg log entry which the broken one is missing:

igb 0000:0c:00.0 enp12s0: igb: enp12s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX