From: Johannes Erdfelt <johannes@erdfelt.com>
To: David Ford <david@linux.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: speaking of USB...(bug/hub.c)
Date: Sat, 18 Nov 2000 15:40:42 -0500 [thread overview]
Message-ID: <20001118154042.A15356@sventech.com> (raw)
In-Reply-To: <3A165556.FFA4FCB6@linux.com>
In-Reply-To: <3A165556.FFA4FCB6@linux.com>; from David Ford on Sat, Nov 18, 2000 at 02:09:26AM -0800
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/
next prev parent reply other threads:[~2000-11-18 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 10:09 speaking of USB...(bug/hub.c) David Ford
2000-11-18 20:40 ` Johannes Erdfelt [this message]
2000-11-19 5:24 ` David Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001118154042.A15356@sventech.com \
--to=johannes@erdfelt.com \
--cc=david@linux.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox