From: Pavel Machek <pavel@suse.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
seife@suse.de
Subject: Suspend to RAM and disk
Date: Mon, 16 Jan 2006 12:40:37 +0100 [thread overview]
Message-ID: <20060116114037.GA26986@elf.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Hi!
In good old days of Pentium MMX, when ACPI was not yet born and APM
ruled the world, I had and thinkpad 560X notebook. And that beast
supported suspend-to-both: It stored image on disk, but then suspended
to RAM, anyway. I think I want that feature back.
[Advantage was, that suspend/resume was reasonably fast for common
case, yet you did not loose your opened applications if your battery
ran flat. Speed advantage will be even greater these days -- boot of
"resume" kernel takes most of time.]
Unfortunately, suspend-to-RAM is not in quite good state these
days. It tends to work -- after you setup your video drivers according
to video.txt, with some scripting needed. Unfortunately, after we
suspended to disk, system is frozen -- we may not run scripts.
I guess the solution is to create userland application that will parse
the DMI, look into table, and if it is neccessary do the vbe
saving/restoring itself. (We may not run external binaries on frozen
system; everything has to be pagelocked.) I guess that will include
quite a lot of cut-copy-and-paste from various project, but I see no
other way :-(.
OTOH this should get us to state where suspend-to-RAM "just works", so
I guess it is worth it.
Pavel
--
Thanks, Sharp!
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2006-01-16 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 11:40 Pavel Machek [this message]
2006-01-16 20:06 ` Suspend to RAM and disk Rafael J. Wysocki
2006-01-16 20:11 ` 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=20060116114037.GA26986@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=seife@suse.de \
/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