From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>,
cijoml@volny.cz, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [linux-pm] potential pitfall? changing configuration while PC in hibernate (fwd)
Date: Thu, 26 May 2005 10:34:27 -0700 [thread overview]
Message-ID: <200505261034.28186.david-b@pacbell.net> (raw)
In-Reply-To: <20050525164701.52a45680.akpm@osdl.org>
On Wednesday 25 May 2005 4:47 pm, Andrew Morton wrote:
> Michal Semler <cijoml@volny.cz> wrote:
> >
> > It is real stupid, that Linux kernel freezes when simply during hibernate I
> > change Bluetooth dongle to USB mouse in my USB port.
That is, you unplug the dongle -- breaking the USB power session -- and then
plug in a mouse? And the kernel does something other than disconnecting the
dongle, and then enumerate a new mouse? That'd be a bug. Somewhere. It'd
probably help a lot if the bluetooth USB driver had a suspend() method.
It's not clear to me what you mean by "hibernate". If that's an "everything
powered off" pseudo-suspend state, then the dongle should always be getting
disconnected, and USB always re-enumerated by Linux. Only "real suspend"
states, like suspend-to-RAM, can normally maintain USB power sessions. And
even then, the device drivers need to be prepared to maintain them ... and
do things like stop active I/O requests, and resume them later.
You said this was an all-Intel system. So which host controller driver is
in use here ... UHCI? EHCI? With RC5 and CONFIG_USB_DEBUG, what do the
USB debug messages say is happening? Does CONFIG_USB_SUSPEND change things?
Try this with purely modular USB for now.
- Dave
prev parent reply other threads:[~2005-05-26 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050321184512.GA1390@elf.ucw.cz>
2005-03-21 22:10 ` [linux-pm] potential pitfall? changing configuration while PC in hibernate (fwd) Michal Semler
2005-05-25 23:47 ` Andrew Morton
2005-05-26 17:34 ` 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=200505261034.28186.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=cijoml@volny.cz \
--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