From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Wes Janzen <superchkn@sbcglobal.net>, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] USB trouble since 2.6.8-rc1...
Date: Tue, 27 Jul 2004 13:17:39 -0700 [thread overview]
Message-ID: <200407271317.39470.david-b@pacbell.net> (raw)
In-Reply-To: <41004A8C.1000906@sbcglobal.net>
On Thursday 22 July 2004 16:15, Wes Janzen wrote:
> I've been having trouble with USB since 2.6.8-rc1; khubd ends up
> blocking on something which makes USB hotplugging stop working (and only
> half my devices even get initialized). I did get 2.6.8-rc1 to work once
> though it seemed to help inserting modules before calling hotplug.
> However I haven't been able to repeat that during my last 5 attempts
> with no changes besides a reboot. I'm running 2.6.7-ck5 right now with
> no apparent problems.
>
> I haven't done extensive testing, but things seemed to work OK until I
> plugged in my Belkin F5U231 4-port multi-tt hub. My other hub is a
> 4-port single-tt Belkin F5U224.
The log messages you sent didn't show a multi-tt hub ... just a
single-TT one from NEC.
One of the boot problems you had was because you didn't start
EHCI first. That meant that when you started EHCI, it grabbed
that hub, which had already been enumerated (and the devices
on the hub) ... it's possible some of the recent changes to the
hub code made that misbehave. Basically it's like pulling out
a hub with three devices attached, and I think I recently saw
that misbehave too.
If that's really what's up, then the workaround is to do what you
should have been doing all along: initialize EHCI first, so it
grabs all high speed devices before the other controllers grab
on to them.
- Dave
prev parent reply other threads:[~2004-07-29 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 23:15 Wes Janzen
2004-07-27 20:17 ` David Brownell [this message]
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=200407271317.39470.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=superchkn@sbcglobal.net \
/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
all inboxes | Powered by JetHome®