![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=1028966 Bug ID: 1028966 Summary: Kernel oops when connecting ethernet cable to USB-C ethernet card Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: oneukum@suse.com Reporter: rbrown@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 717094 --> http://bugzilla.suse.com/attachment.cgi?id=717094&action=edit picture of the oops System: Dell Precision Workstation 5510 (SUSE Corporate Laptop) Operating System: Tumbleweed 20170308 Kernel: 4.10.1 This laptop does not have a wired ethernet port on the chassis, instead is supplied with a USB-C Ethernet card. This card appears to use the r8152 module. This Ethernet card works perfectly fine as long as it is present during system boot. Detaching and reattaching the card has no negative effect to the system. The Ethernet cable can be connected and disconnected from the card with no negative effect to the system. The problem comes ONLY in when the system is booted WITHOUT the USB-C device connected at boot. In this case, the card can be connected and disconnected from the system without problems, but as soon as an ethernet cable is also connected to the card, the Kernel panics. Photo of the panic is attached - no kdump sadly as kdump is broken on Tumbleweed it seems. In the followup comments I will attach two logs from dmesg on the system. dmesg.log shows the full output of the system, from boot to panic at timecode 369.0 onwards I connected the USB-C Ethernet card. You can see an ACPI Error followed by what seems to me to be the expected PCI, USB, and r8152 messages related to the device being connected at timecode 406.0 onwards I then connected an ethernet cable to the USB-C Ethernet card. You can see what looks to me like an error disconnecting usb 4-1 (the r8152 device) followed immediately by what looks like a successful attempt to disconnect usb 3-1 (the hub which seems to be internal to the USB-C dongle), releasing it's psi_bus's just as the kernel explodes -- You are receiving this mail because: You are on the CC list for the bug.