On Mon, Dec 10, 2018 at 03:02:26PM +0000, Richard van der Hoff wrote: > On 10/12/2018 14:53, Mika Westerberg wrote: > > On Mon, Dec 10, 2018 at 01:33:45PM +0000, Richard van der Hoff wrote: > > > > > > On 10/12/2018 13:30, Mathias Nyman wrote: > > > > Do you have the beginning part of the dmesg? It could show why the USB > > > > devices all get disconnected. > > > > The whole xhci usb host will be hotplug removed from the PCI bus when > > > > last device is disconnected, this > > > > is roughly where your current dmesg starts. > > > > > > There's nothing in the dmesg for many minutes before what I sent. > > > > It still might reveal something useful, like PCI resource allocation > > etc. So it is always good idea to provide a full dmesg. > > > My bad. Here you go. Thanks for the log. Unfortunately I can't immediately spot anything that could explain this. > [ 541.184315] IPv6: ADDRCONF(NETDEV_UP): enx00249b194c4f: link is not ready > [ 1943.745174] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 2: -110 (exp. 1). > [ 1987.411132] usb 3-1: USB disconnect, device number 2 > [ 1987.411135] usb 3-1.1: USB disconnect, device number 3 > [ 1987.411137] usb 3-1.1.3: USB disconnect, device number 5 > [ 1987.411553] usb 3-1.1.3: cannot submit urb (err = -19) > [ 1987.412833] usb 3-1.1.3: cannot submit urb (err = -19) > [ 1987.470866] xhci_hcd 0000:39:00.0: remove, state 1 To me this looks pretty much like the USB link goes down for unknown reasons and that triggers the ACPI PCI hot-remove followed by hot-add again (these systems the xHCI controller is removed if there is nothing connected). Maybe Mathias and other USB developers are able to figure out more.
