From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@osdl.org
Subject: 2.6.20 regression: suspend to disk no more works
Date: Mon, 1 Jan 2007 22:44:42 +0300 [thread overview]
Message-ID: <200701012244.42781.arvidjaar@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In *the same* configuration STD now fails with "Cannot find swap device". The
reason is changes in kernel/power/swap.c. In 2.6.19 it did not require valid
swsusp_resume_device at all - it took first available swap device and saved
image. Later during resume swsusp_resume_device was set either by command
line or sysfs and everything worked nicely.
Now swsusp_swap_check() unfortunately checks for swsusp_resume_device at
*suspend* time:
res = swap_type_of(swsusp_resume_device, swsusp_resume_block);
if (res < 0)
return res;
root_swap = res;
resume_bdev = open_by_devnum(swsusp_resume_device, FMODE_WRITE);
if (IS_ERR(resume_bdev))
return PTR_ERR(resume_bdev);
but in case of modular driver for swap device this is likely to be undefined.
This is as of 2.6.20-rc3.
I already have seen these reports. While 'echo a:b > /sys/power/resume' before
suspend is a workaround, this still breaks perfectly valid setup that worked
before. Also 'echo a:b > /sys/power/resume' is actually wrong - we are not
going to resume at this point; but there is no way to just tell kernel "use
this device for next STD" ... also the error message is misleading, it should
complaint "no resume device found". Swap is there all right.
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFmWSqR6LMutpd94wRAu61AJ9mdbF4W6RNQ848PU0e4n/3MKtNnwCgzwOh
HkZ9e8lHPMH1tRNzCw/2O58=
=HlW4
-----END PGP SIGNATURE-----
next reply other threads:[~2007-01-01 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 19:44 Andrey Borzenkov [this message]
2007-01-01 23:28 ` 2.6.20 regression: suspend to disk no more works Rafael J. Wysocki
2007-01-02 8:38 ` Andrey Borzenkov
2007-01-02 10:32 ` 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=200701012244.42781.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.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