From: David Ford <david+powerix@blue-labs.org>
To: John Mock <kd6pag@qsl.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: test9 suspend problems
Date: Mon, 27 Oct 2003 16:00:14 -0500 [thread overview]
Message-ID: <3F9D875E.8020302@blue-labs.org> (raw)
In-Reply-To: <E1AEEKl-0000yc-00@penngrove.fdns.net>
Unfortunately I use USB mostly for my digital camera. Losing sound is
pretty annoying too because everything that tries to play sound then
gets into D state as well.
John Mock wrote:
>Software suspend failing with 'uhci-hcd' is a known problem under 2.6.0
>(see Bug #1373):
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0308.0/1805.html
> http://www.ussg.iu.edu/hypermail/linux/kernel/0308.0/1867.html
> http://bugzilla.kernel.org/show_bug.cgi?id=1373
>
>It was reported a while ago (in 2.5.73-mm1):
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0306.3/1093.html
>
>According to current release critera, it seems that most software-suspend
>related issues will have to wait until after 2.6.0 is released in terms
>of the regular kernel. (Maybe a private patch might be available sooner.)
>
>If your only USB devices are mice and/or keyboards, then you can probably
>put a 'rmmod uhci-hcd'/'modprobe uhci-hcd' pair in your hiberation script.
>
>That fix is unlikely to work for things like file-oriented devices (such
>as digital cameras).
> -- JM
>
>
next prev parent reply other threads:[~2003-10-27 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 20:51 test9 suspend problems John Mock
2003-10-27 21:00 ` David Ford [this message]
2003-10-27 21:53 ` Patrick Mochel
2003-10-27 21:56 ` David Ford
2003-10-27 22:17 ` Patrick Mochel
2003-10-27 23:19 ` Felipe Alfaro Solana
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 19:53 David Ford
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=3F9D875E.8020302@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=kd6pag@qsl.net \
--cc=linux-kernel@vger.kernel.org \
/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