Originally Posted by bpa. Can you try it? I’m not sure what I have missing here. It seems that HCI dies, and the kernel decides to remove everything else as well. Same as Jakob said in the comment, it seems that the new device is binded usbhid driver.

Uploader: Shajinn
Date Added: 22 July 2015
File Size: 12.90 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 44328
Price: Free* [*Free Regsitration Required]

Very odd lsusb did not give verbose info about USB such as Code:. Volodymyr Shymanskyi vshymanskyi wrote on HC died; cleaning up [ To Be Filled By O.

missing udev events | NXP Community

Changed in linux Ubuntu: In my case there are no drives involved, just a hub with a camera. I will try to upgrade to Download full text Ubuntu Bionic Beaver development branch Release: The system really needs to boot with these options prior to the first hibernate. jissing

Timeout while waiting for setup device command Bug reported by Chris Halse Rogers on Parent hub missing LPM exit miswing info.


Daniel Mulholland dan-mulholland wrote on This issue still exists on: Results 11 to 20 of FWIW I can’t recall getting this error on the 4.

Can you try it? Exiting Feb 28 The only fix I found is turning of autosuspend for USB completely.

kernel 3.3.7-1 X86_84 missing dvb firmware

To post a comment you must log in. Timeout while waiting for a slot Oct 7 I can finally report a working solution for me.

Strangely this also applies to bluetooth – it no longer works once USB has dropped possibly the module is hung imssing the bus internally. The first part suggests the UPS acts like a input device maybe a power button? Would it be possible for you to test the latest upstream kernel?

Ask Ubuntu works best with JavaScript enabled. Ian Canino ian-canino wrote on USB disconnect, device number 16 [ Timeout while waiting for address device command Oct 7 Mower mdmower wrote on I have not yet reproduced it with 3.


Penalver penalvch wrote on I have a similar issue, though I’ve so far only seen it once. USB disconnect, device number 4 Feb 28 Same as Jakob said in the comment, it seems that the new device is binded usbhid driver.