From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>,
David Brownell <david-b@pacbell.net>
Cc: "Cédric Boutillier" <cedric.boutillier@gmail.com>,
"pm list" <linux-pm@lists.linux-foundation.org>,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Fwd: Re: [Suspend-devel] s2both on powerpc
Date: Sun, 1 Apr 2007 18:37:15 +0200 [thread overview]
Message-ID: <200704011837.16014.rjw@sisk.pl> (raw)
Alan, Dave, could you please have a look at this?
Rafael
---------- Forwarded Message ----------
Subject: Re: [Suspend-devel] s2both on powerpc
Date: Sunday, 1 April 2007 18:18
From: "Cédric Boutillier" <cedric.boutillier@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, "Tim Dijkstra" <newsuser@famdijkstra.org>, suspend-devel@lists.sourceforge.net
Hi !
On 4/1/07, Johannes Berg <johannes@sipsolutions.net> wrote:
> Have you gotten it to resume?
> I'd test s2both but I haven't gotten s2disk to resume yet... Need to
> test that patch.
Yes it resumes, but I am stuck at some point because after the image
is reloaded from swap, the system freezes when (usb) modules are
reloaded. That is a problem I got with suspend-to-disk with recent
kernels : 2.6.18 leads to oops, and 2.6.20 / 2.6.21-rc5 lead to
lockup.
If I unload usb modules before suspending, the system resumes and I
get a prompt, but I get also some errors from usb (root hub lost power
or was reset). (see
http://marc.info/?l=linux-usb-devel&m=117528005511118&w=2)
I would appreciate If you had an idea on that .
Cedric
next reply other threads:[~2007-04-01 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 16:37 Rafael J. Wysocki [this message]
2007-04-05 21:38 ` Fwd: Re: [Suspend-devel] s2both on powerpc David Brownell
2007-04-05 23:32 ` Rafael J. Wysocki
2007-04-06 14:24 ` Alan Stern
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=200704011837.16014.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cedric.boutillier@gmail.com \
--cc=david-b@pacbell.net \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.linux-foundation.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