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
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
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
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
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
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,
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
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
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.
