From: chip@pobox.com (Chip Salzenberg)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-rc3: USB subsystem wedged when USB keyboard is re-plugged
Date: Wed, 18 Feb 2004 11:34:03 -0500 [thread overview]
Message-ID: <E1AtUeB-0000aA-Qe@tytlal> (raw)
In-Reply-To: <1qfup-7RL-7@gated-at.bofh.it>
In article <1qfup-7RL-7@gated-at.bofh.it> you write:
> usb 2-2: new full speed USB device using address 5
> usb 2-2: control timeout on ep0out
>
>And after that timeout, the USB subsystem seems totally stuck.
>Nothing I do provokes any further response. (Kind of makes me wish
>I'd built the USB drivers as modules so I could unload and reload
>them.)
It's worse: rmmod uhci_usb hung, and nothing (including kill -9) could
unhang it.
Dammit. I'd have thought that USB support would be safe on a
several-year-old IBM ThinkPad with fricking Intel chips. *sigh*
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
next parent reply other threads:[~2004-02-18 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1qfup-7RL-7@gated-at.bofh.it>
2004-02-18 16:34 ` Chip Salzenberg [this message]
2004-02-17 15:29 2.6.3-rc3: USB subsystem wedged when USB keyboard is re-plugged Chip Salzenberg
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=E1AtUeB-0000aA-Qe@tytlal \
--to=chip@pobox.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