On Sat, Nov 18, 2000, David Ford <david@linux.com> wrote:
> Here's another one for the books. In the recent test11 series, timing
> appears to be partially broken for dev addr assignments. If I'm lucky a
> new usb device will answer back and get all the numbers set up
> properly. Regularly however a new device gets plugged in and I get
> several of the below without the success at the end. I usually need to
> reboot to get my USB stuff alive again. The below is test7.
>
> # dmesg
> hub.c: USB new device connect on bus1/1, assigned device number 6
> usb-uhci.c: interrupt, status 2, frame# 121
> usb.c: USB device not accepting new address=6 (error=-110)
> hub.c: USB new device connect on bus1/1, assigned device number 7
Status 2 means there was an error with the transfer. This doesn't look
like a hub.c bug at all.
What kind of device is this?
Does this problem still happen with the other UHCI driver?
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 23 2000 - 21:00:16 EST