From: Kevin Fenzi <kevin-kernel@scrye.com>
To: linux-kernel@vger.kernel.org
Subject: pmdisk/swsusp 2.6.8-rc2-mm1 success
Date: Wed, 28 Jul 2004 15:16:13 -0600 [thread overview]
Message-ID: <20040728211616.A6C36894D7@voldemort.scrye.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ok. Compiling without preempt and no highmem support and using the
echo 'shutdown' > /sys/power/disk
I managed to do some suspend/resume cycles.
Some impressions:
The status display is very ugly. It prints cryptic items and lots of
random .... and | that don't mean much to me. ;)
It would be nice if it could just give a % age complete or a spinning
cursor to indicate its doing something.
It's a good deal slower than software suspend2. Is there any plans to
add in the LZO compression that software suspend2 uses?
With software suspend 2 I usually can do an entire suspend/resume
cycle in about 30 seconds. Thats from prompt to prompt.
With swsup1/pmdisk (should I just call it swsusp1 now?) It looks like
it takes about 2.5 minutes to do a cycle from prompt to prompt.
On resume there is a inital part where the display just sits there. I
wasn't sure if it was hung or not, but it was just calculating. It
would be nice if it could provide a 'this might take a while' or a
spinning cursor or status bar to let you know it's not dead.
There aren't any bootup messages to indicate that it's
available. Would it be possible to add something like:
swsusp1: will use /dev/hda2 to resume.
swsusp1: /dev/hda2 is regular swap space. Continuing to boot.
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFBCBeg3imCezTjY0ERAm5oAJ9xzR1Pd6z8xH/VlS4LU9QNKLy7fgCfY7SR
27v7FeEaFch662gB73jEZuk=
=E4nz
-----END PGP SIGNATURE-----
next reply other threads:[~2004-07-28 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 21:16 Kevin Fenzi [this message]
2004-08-10 11:00 ` 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=20040728211616.A6C36894D7@voldemort.scrye.com \
--to=kevin-kernel@scrye.com \
--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
all inboxes | Powered by JetHome®