From: Mark Lord <lkml@rtr.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: 2.6.14-rc4-mm1: USB suspend regression
Date: Wed, 19 Oct 2005 23:21:37 -0400 [thread overview]
Message-ID: <43570D41.80505@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0510191156520.5049-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Alan Stern wrote:
>
>>None of the recent kernels can resume-from-ram reliably for me
>>if I use CONFIG_USB_SUSPEND (set). But with that option UNset,
>>suspend/resume to/from RAM works very well.
>
> Try applying this patch:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=112966405019175&w=2
I have already adopted that patch independently,
and it has done wonders for stability with 2.6.14-rc4
coming back from suspend-to-ram. Or is that just my imagination?
But I have not yet tried reenabling CONFIG_USB_SUSPEND in conjunction
with that patch -- just too much grief and wasted time every round
I try with CONFIG_USB_SUSPEND. I'll get to it again eventually though.
Cheers
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-10-20 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 10:01 2.6.14-rc1-mm1: usb breaks suspend Pavel Machek
2005-10-17 18:54 ` [linux-pm] " Alan Stern
2005-10-17 21:11 ` Rafael J. Wysocki
2005-10-18 1:01 ` Alan Stern
2005-10-19 13:13 ` 2.6.14-rc4-mm1: USB suspend regression (was: Re: 2.6.14-rc1-mm1: usb breaks suspend) Rafael J. Wysocki
2005-10-19 14:53 ` 2.6.14-rc4-mm1: USB suspend regression Mark Lord
2005-10-19 16:03 ` Alan Stern
2005-10-20 3:21 ` Mark Lord [this message]
2005-10-19 16:18 ` 2.6.14-rc4-mm1: USB suspend regression (was: Re: 2.6.14-rc1-mm1: usb breaks suspend) Alan Stern
2005-10-19 20:18 ` Rafael J. Wysocki
2005-10-19 20:46 ` Alan Stern
2005-10-19 22:16 ` Rafael J. Wysocki
2005-10-20 15:30 ` Alan Stern
2005-10-18 0:13 ` [linux-pm] 2.6.14-rc1-mm1: usb breaks suspend Pavel Machek
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=43570D41.80505@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-pm@lists.osdl.org \
--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