From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: david-b@pacbell.net, linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: OHCI root_port_reset() deadly loop...
Date: Tue, 09 Oct 2007 16:37:08 +1000 [thread overview]
Message-ID: <1191911828.6355.64.camel@pasglop> (raw)
In-Reply-To: <20071008.222622.22041332.davem@davemloft.net>
On Mon, 2007-10-08 at 22:26 -0700, David Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Tue, 09 Oct 2007 15:13:36 +1000
>
> > I'm not even sure module load order is 100% fault proof here since
> > khubd spawns as a thread...
>
> I'm concerned about that as well, thanks for bringing it up.
>
> My understanding, however, is that the critical thing is that the EHCI
> device reset being done by the EHCI driver probe occurs and completes
> first. If that is true, then just making sure EHCI loads initially is
> a sufficient constraint to fix this problem.
Yup, that would be, though I hate that sort of load order
dependencies...
Ben.
next prev parent reply other threads:[~2007-10-09 6:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 6:53 OHCI root_port_reset() deadly loop David Miller
2007-10-07 7:31 ` David Brownell
2007-10-07 7:51 ` David Miller
2007-10-08 23:54 ` David Miller
2007-10-09 3:10 ` Greg KH
2007-10-09 3:16 ` David Miller
2007-10-09 3:34 ` David Brownell
2007-10-09 3:42 ` David Miller
2007-10-09 4:39 ` Greg KH
2007-10-09 4:47 ` David Miller
2007-10-09 5:11 ` Benjamin Herrenschmidt
2007-10-09 6:06 ` Greg KH
2007-10-09 19:22 ` [linux-usb-devel] " David Brownell
2007-10-10 15:32 ` Alan Stern
2007-10-09 5:00 ` David Brownell
2007-10-09 5:23 ` David Miller
2007-10-09 6:43 ` Benjamin Herrenschmidt
2007-10-09 18:48 ` David Brownell
2007-10-09 16:01 ` [Linux-usb-users] " Alan Stern
2007-10-09 17:39 ` Greg KH
2007-10-09 18:42 ` Alan Stern
2007-10-09 18:59 ` David Brownell
2007-10-09 21:27 ` David Miller
2007-10-09 21:43 ` David Brownell
2007-10-09 22:00 ` David Miller
2007-10-10 4:35 ` David Miller
2007-10-15 22:01 ` David Miller
2007-10-15 23:39 ` David Brownell
2007-10-15 23:58 ` David Miller
2007-10-16 15:23 ` Alan Stern
2007-10-16 22:06 ` David Miller
2007-10-16 22:20 ` Greg KH
2007-10-17 15:56 ` Alan Stern
2007-10-16 22:08 ` David Miller
2007-10-17 15:51 ` Alan Stern
2007-10-17 23:03 ` David Miller
2007-10-18 14:28 ` Alan Stern
2007-10-16 18:26 ` David Brownell
2007-10-09 4:09 ` David Brownell
2007-10-09 5:13 ` Benjamin Herrenschmidt
2007-10-09 5:26 ` David Miller
2007-10-09 6:37 ` Benjamin Herrenschmidt [this message]
2007-10-09 4:36 ` David Brownell
2007-10-09 4:44 ` David Miller
2007-10-09 16:38 ` David Brownell
2007-10-09 20:41 ` David Miller
2007-10-09 20:46 ` Greg KH
2007-10-09 21:05 ` David Brownell
2007-10-09 21:09 ` David Brownell
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=1191911828.6355.64.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.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