From: David Miller <davem@davemloft.net>
To: david-b@pacbell.net
Cc: linux-usb-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: OHCI root_port_reset() deadly loop...
Date: Sun, 07 Oct 2007 00:51:56 -0700 (PDT) [thread overview]
Message-ID: <20071007.005156.85395415.davem@davemloft.net> (raw)
In-Reply-To: <20071007073141.A88DD2393E2@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
From: David Brownell <david-b@pacbell.net>
Date: Sun, 07 Oct 2007 00:31:41 -0700
> Is this SPARC, or is ACPI potentially in play? PCI, or non-PCI?
It's sparc64 on PCI.
> Are the other ports still behaving? Is EHCI maybe trying to switch
> ownership of that port? Is maybe the (newish) autosuspend stuff
> kicking in?
I wouldn't know, the machine hangs and doesn't get any further.
> Patches accepted. :)
I'm 700 patches deep with an additionally large backlog of
patches to apply for the networking and sparc64 tree.
I don't have the time, which is why I reported the problem
to the OHCI maintainer instead of letting it slip through
the cracks.
> Since the PRS bit is specified as "write one", with writing zero
> as no-effect (since the rest is hardware-timed), the only recovery
> procedure might involve resetting the whole controller. Messy,
> and not something the usb core has historically handled very well.
At a minimum you should exit the loop and print out a warning
messages and try to continue even without trying to reset the
whole controller if that will take some developer effort.
Anything is better than just hanging there forever. Not every
user knows to hit ALT-SYSRQ then 'P' to get a register dump to
figure out why their computer stopped booting.
Every register polling loops, without exception, should have a limit
and exit with an error indication when that limit is reached. It
will never hang someones machine, because although not this time, in
many cases these kinds of hangs are absolutely impossible to debug
(interrupts disabled, critical lock held, etc.)
next prev parent reply other threads:[~2007-10-07 7:52 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 [this message]
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
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=20071007.005156.85395415.davem@davemloft.net \
--to=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