Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
On Mon, 7 Mar 2016, Devon Ash wrote: > Attached is dmesg.txt and usbmon.txt. For what kernel version? And what's with all those netconsole error messages popping up every 5 minutes? > This is the only usbmon I could > capture, from 0u, 5u and 6u don't give anything, I've tried to plug > them in and out of every usb port. It looks like you traced 2u. That's not going to help much if the error messages are for bus 5 or 6. Tried to plug _what_ in and out of every USB port? > Yes, the filepath from above is the current filepath I'm using for usbmon. What filepath above? > Note, I had enabled dynamic debugging for this. > > On Mon, Mar 7, 2016 at 3:29 PM, Devon Ash wrote: > > Running kernel 4.4.4 is no good.. with the same setup as above but > > only changing out vmlinuz and initrd.img, I run into a kernel panic. > > > > "Kernel panic - not syncing: attempted to kill init!" > > > > There was an error that I hadn't seen before about > > > > "systemd-udevd: could not open builtin file > > /lib/modules/4.4.4/modules.builtin.bin". It sounds like you didn't install the new kernel properly. > > Before the kernel panic, I got the same "device not accepting address, > > error -110" as I did on 3.19. There wasn't anything about a -110 error in the dmesg log you attached. Or in the usbmon trace. > > To focus on the problem at hand, should I be using kernel 3.19 source > > configured with the options above? What options above? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
Running kernel 4.4.4 is no good.. with the same setup as above but only changing out vmlinuz and initrd.img, I run into a kernel panic. "Kernel panic - not syncing: attempted to kill init!" There was an error that I hadn't seen before about "systemd-udevd: could not open builtin file /lib/modules/4.4.4/modules.builtin.bin". Before the kernel panic, I got the same "device not accepting address, error -110" as I did on 3.19. To focus on the problem at hand, should I be using kernel 3.19 source configured with the options above? On Fri, Mar 4, 2016 at 4:47 PM, Alan Stern wrote: > On Fri, 4 Mar 2016, Devon Ash wrote: > >> 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) > > Is CONFIG_USB_MON set? If it is set to M, have you loaded the usbmon > module? > >> 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? > > No, that's not enough. I don't remember how 3.19 does it, but with > more modern kernels you have to enable dynamic debugging by doing: > > echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control > > That's assuming CONFIG_DYNAMIC_DEBUG is set, which it should be in a > typical distribution kernel. > >> Regarding Kernel 4.2.0-30-lowlatency, >> >> system-udevd is now giving me the outputs on boot: >> >> seq 1106 '/devices/pci:00/: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" > > Can you post the actual dmesg log? > >> here is the output of: >> >> sudo mount -t usbfs none /proc/bus/usb >> >> mount: mounting none on /proc/bus/usb failed: no such file or directory > > There no longer is any such thing as a usbfs filesystem. Instead > there are USB device nodes under /dev/bus/usb. > >> cat /proc/bus/usb/devices: no such file or directory >> >> sudo mount -t debugfs none /sys/kernel/debug >> >> mount: muonting none on /sys/kernel/debug failed: Device or resource busy > > Probably because it's already mounted there. > >> As well, all usbmon outputs are returning me nothing when plugging >> in/out the broken USB ports that are in question > > What is the full path of the files you are watching for usbmon? They > should be things like /sys/kernel/debug/usb/usbmon/5u -- which of > course won't exist unless debugfs is properly mounted and usbmon is > properly loaded. > > Alan Stern > -- Devon Ash http://ca.linkedin.com/pub/devon-ash/48/478/981"; style="text-decoration:none;">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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
On Fri, 4 Mar 2016, Devon Ash wrote: > 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) Is CONFIG_USB_MON set? If it is set to M, have you loaded the usbmon module? > 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? No, that's not enough. I don't remember how 3.19 does it, but with more modern kernels you have to enable dynamic debugging by doing: echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control That's assuming CONFIG_DYNAMIC_DEBUG is set, which it should be in a typical distribution kernel. > Regarding Kernel 4.2.0-30-lowlatency, > > system-udevd is now giving me the outputs on boot: > > seq 1106 '/devices/pci:00/: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" Can you post the actual dmesg log? > here is the output of: > > sudo mount -t usbfs none /proc/bus/usb > > mount: mounting none on /proc/bus/usb failed: no such file or directory There no longer is any such thing as a usbfs filesystem. Instead there are USB device nodes under /dev/bus/usb. > cat /proc/bus/usb/devices: no such file or directory > > sudo mount -t debugfs none /sys/kernel/debug > > mount: muonting none on /sys/kernel/debug failed: Device or resource busy Probably because it's already mounted there. > As well, all usbmon outputs are returning me nothing when plugging > in/out the broken USB ports that are in question What is the full path of the files you are watching for usbmon? They should be things like /sys/kernel/debug/usb/usbmon/5u -- which of course won't exist unless debugfs is properly mounted and usbmon is properly loaded. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
On 03/04/2016 12:24 PM, Greg KH wrote: > On Fri, Mar 04, 2016 at 02:53:59PM -0500, Devon Ash wrote: >> Regarding Kernel 4.2.0-30-lowlatency, > > What is "lowlatency"? -lowlatency is Ubuntu's optional kernel config. A stock Ubuntu kernel is CONFIG_PREEMPT_VOLUNTARY=y && CONFIG_HZ=250 The -lowlatency kernel is CONFIG_PREEMPT=y && CONFIG_HZ=1000 That is the only difference. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
My deepest apologies.. I ran those commands on another computer (I'm ssh tunnelling)... here is the output of: sudo mount -t usbfs none /proc/bus/usb mount: mounting none on /proc/bus/usb failed: no such file or directory cat /proc/bus/usb/devices: no such file or directory sudo mount -t debugfs none /sys/kernel/debug mount: muonting none on /sys/kernel/debug failed: Device or resource busy As well, all usbmon outputs are returning me nothing when plugging in/out the broken USB ports that are in question On Fri, Mar 4, 2016 at 2:53 PM, Devon Ash wrote: > Regarding Kernel 4.2.0-30-lowlatency, > > system-udevd is now giving me the outputs on boot: > > seq 1106 '/devices/pci:00/: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 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 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 >> http://ca.linkedin.com/pub/devon-ash/48/478/981"; >> style="text-decoration:none;">> 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 > > > > -- > > Devon Ash > http://ca.linkedin.com/pub/devon-ash/48/478/981"; > style="text-decoration:none;"> 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 -- Devon Ash http://ca.linkedin.com/pub/devon-ash/48/478/981"; style="text-decoration:none;">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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
On Fri, Mar 04, 2016 at 02:53:59PM -0500, Devon Ash wrote: > Regarding Kernel 4.2.0-30-lowlatency, What is "lowlatency"? Try 4.4.4 please, 4.2 is now old and obsolete :( And can you test this without any -rt patches, we have no idea how those interact with the USB subsystem, sorry. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
Regarding Kernel 4.2.0-30-lowlatency, system-udevd is now giving me the outputs on boot: seq 1106 '/devices/pci:00/: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 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 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 > http://ca.linkedin.com/pub/devon-ash/48/478/981"; > style="text-decoration:none;"> 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 -- Devon Ash http://ca.linkedin.com/pub/devon-ash/48/478/981"; style="text-decoration:none;">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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
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 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 http://ca.linkedin.com/pub/devon-ash/48/478/981"; style="text-decoration:none;">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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Unable to enumerate USB Device, error -110 Kernel 3.19-0.49-lowlatency netboot
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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html