On Fri, 4 Dec 2009, Ondrej Zary wrote: > Just found why it was sometimes hard to reproduce a problem. Sometimes the > devices are controlled by uhci_hcd and sometimes by ehci_hcd. It seems to > be random and can change on every reboot. It shouldn't change. The hub you plug into (the D-Link hub) should always be controlled by ehci-hcd. Can you post a dmesg log showing what happens on bootup for a case where the hub ends up under uhci-hcd? > With uhci_hcd, rmmod works fine. With ehci_hcd, rmmod hangs the bus - all > urbs fail with -ENOENT: > f67265e8 1428021080 S Bi:1:009:2 -115 128 < > f67265e8 1431508327 C Bi:1:009:2 -108 0 > f6726718 1458252464 S Co:1:007:0 s 40 09 0001 0000 0000 0 > f6726718 1463261404 C Co:1:007:0 -2 0 > f6726978 1463261428 S Co:1:002:0 s 23 08 0070 0001 0000 0 > f6726718 1463261509 S Co:1:007:0 s 40 00 0000 0000 0000 0 > f6726978 1464273397 C Co:1:002:0 -2 0 > f6726718 1468273397 C Co:1:007:0 -2 0 This may be a bug in ehci-hcd, a bug in your EHCI hardware, or a bug in the hub. Can you try using a different high-speed hub to see if it makes any difference? 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
