From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Giridhar Pemmasani <giri@lmc.cs.sunysb.edu>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
swsusp-devel@lists.sourceforge.net
Subject: Re: pmdisk suspend patch
Date: Mon, 15 Mar 2004 17:35:07 +1100 [thread overview]
Message-ID: <1079332506.1966.152.camel@gaston> (raw)
In-Reply-To: <c31t68$f99$1@sea.gmane.org>
On Mon, 2004-03-15 at 02:19, Giridhar Pemmasani wrote:
> Hello
>
> I have been trying to get a reliable way to suspend-to-disk. For me
> swsusp was taking more than a few minutes and swsusp2 was not
> reliable. So I decided to give pmdisk a chance. Since my laptop
> supported S4bios, pmdisk wouldn't let me change it to S4 platform
> based suspend. Even after fixing it, I didn't have much luck. I dug
> deeper and found another problem. pmdisk resumes all devices while
> suspending. So I patched the pmdisk to resume only the device on which
> suspend image is to be stored. With these patches, I have been able to
> use pmdisk reliably (tested with two laptops over 100 times).
>
> I am not subscribed to the mailing list, so if you have problems or
> feedback, CC to me.
That's broken. You cannot call resume_device for a single device
like that. You must properly (and in order) resume the parents of
this device first. Your patch, on some controllers, will cause the
IDE layer to try to wake up the drive without waking up the IDE
controller itself.
I agree that it would be nice to be able to resume only one "branch"
of the PM tree like that, it's just not possible at this point.
Ben
next prev parent reply other threads:[~2004-03-15 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 15:19 pmdisk suspend patch Giridhar Pemmasani
2004-03-15 6:35 ` Benjamin Herrenschmidt [this message]
2004-03-15 8:13 ` Giridhar Pemmasani
2004-03-15 9:36 ` Benjamin Herrenschmidt
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=1079332506.1966.152.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=giri@lmc.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=swsusp-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