From: Pavel Machek <pavel@ucw.cz>
To: Jim Carter <jimc@math.ucla.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disc driver is module, software suspend fails
Date: Wed, 13 Apr 2005 12:07:57 +0200 [thread overview]
Message-ID: <20050413100756.GK1361@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0504101612240.10130@xena.cft.ca.us>
Hi!
On Ne 10-04-05 16:14:52, Jim Carter wrote:
> On Wed, 30 Mar 2005, Pavel Machek wrote:
> > You do not want to mount journaling filesystems; they tend to write to
> > disks even during read-only mounts... But doing it from initrd should
> > be okay. ext2 and init=/bin/bash should do the trick, too.
>
> I did give it a try -- successfully.
>
> For reference I recite the original issue: the driver for my primary
> disc is in the initrd, not hardwired. (It's ata_piix and friends, but
> the same issue happens if you boot from RAID or other weird devices. As
> modern systems tend to have a SATA disc, more and more people are
> complaining on the web that software suspend has stopped working after
> they upgraded their machines.) software_suspend would suspend all the
> way, then immediately wake up having accomplished nothing (but broken
> nothing either). In kernel 2.6.12-rc1 but not 2.6.8 it complains "can't
> find swap device". If this safety check is unwisely overriden so a
> suspend image is written, and you then resume (providing the device by
> number), it fails to read the image using the driver which it hasn't
> loaded yet.
Yep.
> This patch makes software_resume not a late_initcall but rather an
> external subroutine similar to software_suspend, and calls it at the
> beginning of mount_root (in init/do_mounts.c), just _after_ the initrd
> (if any) and its driver have been seen. This buried placement is needed
> because there are several flow paths that call mount_root, and otherwise
> each path would need to be monkeyed with.
But the patch is very dangerous. Unsuspecting users will see their
systems resumed after unsafe initrd is ran. It is okay for you,
through..
What you want to do si to audit your initrd, then add echo to
/sys/power/resume at the end...
> So, what do you think? Can we bring the benefit of software suspend to
> systems with SATA or RAID boot discs?
Yes, but not this way. -rc2 already contains
/sys/power/resume... (Better documentation would be needed, through).
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
next prev parent reply other threads:[~2005-04-13 10:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 23:14 Jim Carter
2005-04-13 10:07 ` Pavel Machek [this message]
2005-04-14 17:53 ` Jim Carter
2005-04-14 20:42 ` Pavel Machek
2005-05-04 1:11 ` Jim Carter
2005-05-04 9:14 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 6:54 Jim Carter
2005-03-25 8:14 ` Pavel Machek
2005-03-25 10:54 ` Stefan Seyfried
2005-03-28 0:27 ` Jim Carter
2005-03-28 22:19 ` Pavel Machek
2005-03-30 1:38 ` Jim Carter
2005-03-30 9:06 ` Pavel Machek
2005-03-23 6:19 Jim Carter
2005-03-23 10:17 ` Pavel Machek
2005-03-23 22:34 ` Jim Carter
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=20050413100756.GK1361@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=jimc@math.ucla.edu \
--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®