Regarding Kernel 4.2.0-30-lowlatency, system-udevd is now giving me the outputs on boot: seq 1106 '/devices/pci0000:00/0000:00:1a.0/usb5 killed (same for usb6) reason being ; a timeout Then I start to get usb 5-1: device not accepting address 5, error -110 usb usb5-port1; unable to enumerate USB device and the same for usb6. There is also: system-udevd: worker terminated by signal 9, and then the system waits for 2-5 minutes, finishing with a kernel hang and a stack trace "not tainted, blocked for more than 120 seconds" On Fri, Mar 4, 2016 at 2:34 PM, Devon Ash <noobaca2@xxxxxxxxx> wrote: > If they are completely unresponsive, why do you get the -110 errors? I > would expect you wouldn't get anything at all. > > They become unresponsive after the -110 errors. Dmesg will show > nothing after those errors come up during boot. > > Failing that, can you at least provide a usbmon trace showing what > happens when you plug a device into one of the bad ports? > > usbmon trace: > > I'm unable to get anything from doing "cat 0u && cat 5u && cat 6u" > (which are all of the offending devices locations) > > > And also a > dmesg log with USB debugging enabled? > > dmesg shows nothing. I htink I'm missing something - to enable USB > debugging all that needs to be done is mount the debugfs right? > > > What type of motherboard or system is this? > > Mini ITX from ASRock. > > Can you try using a more up-to-date kernel, such as 4.4? > > I'll try, and get back to you. > > On Fri, Mar 4, 2016 at 1:59 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: >> On Fri, 4 Mar 2016, Devon Ash wrote: >> >>> I'm unable to use 8 of the 10 USB devices I have on a motherboard. Two >>> USB 3.0 ports work, and all of the devices, if plugged into a hub, can >>> be recognized and used if plugged through those 2 ports. However, the >>> other ports are completely unresponsive. >> >> If they are completely unresponsive, why do you get the -110 errors? I >> would expect you wouldn't get anything at all. >> >>> Thoughts/Ideas? The broken drivers are ehci-pci. xhci-hcd works on the >>> usb 3.0 ports, but for 2 other usb 3.0 ports it does not work. >>> >>> The machine is being netbooted and running kernel 3.19-49-lowlatency >>> (i've tried with generic as well). This same identical setup running >>> off of a hard disk boot does not have this problem for any USB ports. >>> Im lead to believe there may be a bug in the ehci-pci driver while >>> using netboot. >> >> What type of motherboard or system is this? >> >> Can you try using a more up-to-date kernel, such as 4.4? >> >> Failing that, can you at least provide a usbmon trace showing what >> happens when you plug a device into one of the bad ports? And also a >> dmesg log with USB debugging enabled? >> >> Alan Stern >> > > > > -- > > Devon Ash > <a href="http://ca.linkedin.com/pub/devon-ash/48/478/981"; > style="text-decoration:none;"><span style="font: 80% Arial,sans-serif; > color:#0783B6;"><img > src="https://static.licdn.com/scds/common/u/img/webpromo/btn_in_20x15.png"; > width="20" height="15" alt="View Devon Ash's LinkedIn profile" > style="vertical-align:middle" border="0">View Devon Ash's > profile</span></a> -- Devon Ash <a href="http://ca.linkedin.com/pub/devon-ash/48/478/981"; style="text-decoration:none;"><span style="font: 80% Arial,sans-serif; color:#0783B6;"><img src="https://static.licdn.com/scds/common/u/img/webpromo/btn_in_20x15.png"; width="20" height="15" alt="View Devon Ash's LinkedIn profile" style="vertical-align:middle" border="0">View Devon Ash's profile</span></a> -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![https://static.licdn.com/scds/common/u/img/webpromo/btn_in_20x15.png"](https://static.licdn.com/scds/common/u/img/webpromo/btn_in_20x15.png"){kind=link}
