On Mon, 7 Dec 2009, Ondrej Zary wrote: > > > diff between ehci and uhci logs: > > > There seems to be some problem with timing. > > > Also order of ehci_usb vs uhci_usb loading changes. > > > > That order doesn't matter much. But this... > > Looks like it does matter. I compiled ehci_hcd in kernel and left uhci_hcd as > module - and the hub was always attached to ehci. Compiled uhci_hcd in kernel > and ehci_hcd as module - and it was always attached to uhci. So the HW is > probably OK. As a matter of fact, it probably isn't. The hub should have switched over to EHCI when the module was loaded. The question remains whether the problem is in the hub or in the EHCI controller. You don't have to compile either driver into the kernel. Try doing this: rmmod ehci-hcd dmesg -c >/dev/null (clear the log buffer) Start up usbmon on the 0u file Plug in the hub, which attaches to UHCI modprobe ehci-hcd At this point the hub should switch over to EHCI It will make things easier to understand if you unplug all other USB devices first. Let's see what that shows, both in usbmon and in dmesg. It would be nice if the EHCI controller turned out to be at fault. Then we could blame this entire problem on the controller hardware. :-) Alan Stern -- 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
