From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ncunningham@cyclades.com
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] Fix USB suspend/resume crasher
Date: Wed, 23 Nov 2005 16:13:16 +1100 [thread overview]
Message-ID: <1132722797.26560.279.camel@gaston> (raw)
In-Reply-To: <1132715647.4707.8.camel@localhost>
> Sounds great. Maybe I'll finally be able to change my first question to
> people with suspend problems from: "Do you have USB built as modules and
> unloaded while suspending."
Heh, I don't know :) I haven't done anything to UHCI at this point, and
there are still other possible issues.
For example, we should probably do the "handoff" trick on resume as well
as on boot. In fact, I suspect that most PCI quirks should be re-run on
resume, with IRQs off if possible, so that stuffs can be put back into
some sane state when coming back from the BIOS before they get a chance
to spam the kernel with bogus IRQs left enabled by that same BIOS (does
this happen ?) or other niceties of that sort... I don't have any of
these problems on powermacs, but x86 might not be yet at the end of the
tunnel...
Ben.
next prev parent reply other threads:[~2005-11-23 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 3:08 [PATCH] Fix USB suspend/resume crasher Benjamin Herrenschmidt
2005-11-23 3:09 ` Benjamin Herrenschmidt
2005-11-23 3:14 ` Nigel Cunningham
2005-11-23 5:13 ` Benjamin Herrenschmidt [this message]
2005-11-23 17:10 ` Greg KH
2005-11-23 18:58 ` David Brownell
2005-11-24 0:22 ` Rafael J. Wysocki
2005-11-24 1:23 ` Benjamin Herrenschmidt
2005-11-24 20:50 ` Rafael J. Wysocki
2005-11-24 21:01 ` Benjamin Herrenschmidt
2005-11-24 21:14 ` Rafael J. Wysocki
2005-11-24 21:22 ` Benjamin Herrenschmidt
2005-11-24 16:52 ` Arkadiusz Miskiewicz
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=1132722797.26560.279.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ncunningham@cyclades.com \
--cc=stern@rowland.harvard.edu \
/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).