From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes
Date: Tue, 13 Dec 2005 23:39:24 +0100 [thread overview]
Message-ID: <200512132339.25078.rjw@sisk.pl> (raw)
In-Reply-To: <200512131422.26224.david-b@pacbell.net>
On Tuesday, 13 December 2005 23:22, David Brownell wrote:
> On Tuesday 13 December 2005 2:10 pm, Rafael J. Wysocki wrote:
> > On Tuesday, 13 December 2005 07:52, David Brownell wrote:
> > > >
> > > > if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
> > >
> > > What happens if you make that line read
> > >
> > > if ((status & STS_PCD) != 0) {
> > >
> > > and ignore the root hub thing?
> >
> > So far, so good. It works and hasn't triggered the oops yet. I'll report if there's
> > anything wrong with it.
>
> I suspect that should be safe to merge for 2.6.15, and it might be
> worth considering that. You were using kexec() right?
No, I was not. Why would that be important?
Rafael
next prev parent reply other threads:[~2005-12-13 22:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 12:13 2.6.15-rc5-mm2 Andrew Morton
2005-12-11 12:39 ` 2.6.15-rc5-mm2 Benoit Boissinot
2005-12-11 15:17 ` 2.6.15-rc5-mm2 Benoit Boissinot
2005-12-11 15:47 ` 2.6.15-rc5-mm2 Rafael J. Wysocki
2005-12-11 15:52 ` 2.6.15-rc5-mm2: broken resume from disk on x86-64 Rafael J. Wysocki
2005-12-11 16:02 ` 2.6.15-rc5-mm2: evdev problem Rafael J. Wysocki
2005-12-11 18:22 ` Dmitry Torokhov
2005-12-11 16:06 ` 2.6.15-rc5-mm2: ehci_hcd crashes on load sometimes Rafael J. Wysocki
2005-12-11 20:38 ` Andrew Morton
2005-12-12 19:53 ` Rafael J. Wysocki
2005-12-12 20:29 ` Andrew Morton
2005-12-12 20:55 ` Rafael J. Wysocki
2005-12-12 21:09 ` Andrew Morton
2005-12-12 21:39 ` Rafael J. Wysocki
2005-12-12 21:47 ` Andrew Morton
2005-12-12 21:56 ` Ben Pfaff
2005-12-13 6:52 ` [linux-usb-devel] " David Brownell
2005-12-13 22:10 ` Rafael J. Wysocki
2005-12-13 22:22 ` David Brownell
2005-12-13 22:39 ` Rafael J. Wysocki [this message]
2005-12-13 23:31 ` David Brownell
2005-12-11 16:08 ` 2.6.15-rc5-mm2 Jesper Juhl
2005-12-11 21:13 ` [PATCH] Fix vesafb display panning regression Antonino A. Daplas
2005-12-11 21:30 ` Jesper Juhl
2005-12-11 16:12 ` 2.6.15-rc5-mm2 :-) Maciej Soltysiak
2005-12-13 5:52 ` Con Kolivas
[not found] ` <1916802326.20051213121330@dns.toxicfilms.tv>
2005-12-13 12:16 ` Con Kolivas
2005-12-13 23:30 ` Peter Williams
2005-12-11 17:56 ` 2.6.15-rc5-mm2: two cs5535 modules Adrian Bunk
2005-12-12 18:29 ` Ben Gardner
2005-12-12 22:49 ` Alan Cox
2005-12-12 0:53 ` 2.6.15-rc5-mm2 Grant Coady
2005-12-12 14:05 ` 2.6.15-rc5-mm2 Cornelia Huck
2005-12-14 8:54 ` SMP+nosmp=hang [was: Re: 2.6.15-rc5-mm2] J.A. Magallon
[not found] ` <20060120192259.4460af42.akpm@osdl.org>
2006-01-21 23:46 ` J.A. Magallon
2006-01-22 0:22 ` Randy.Dunlap
2005-12-15 13:41 ` 2.6.15-rc5-mm2 Reuben Farrelly
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=200512132339.25078.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@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;
as well as URLs for NNTP newsgroup(s).