From: Nigel Cunningham <ncunningham@cyclades.com>
To: martin f krafft <madduck@madduck.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp logic error?
Date: Tue, 01 Mar 2005 20:00:21 +1100 [thread overview]
Message-ID: <1109667621.4229.40.camel@desktop.cunningham.myip.net.au> (raw)
In-Reply-To: <20050301082254.GA4402@piper.madduck.net>
Hi Martin.
On Tue, 2005-03-01 at 19:22, martin f krafft wrote:
> also sprach Pavel Machek <pavel () ucw ! cz>
> > > > Could you, please, verify that you don't need to load any
> > > > modules from initrd for your swap partition to work? It won't
> > > > work if you do.
> > >
> > > this makes perfect sense to me when you talk about resuming.
> > > does it also apply to suspending?
> >
> > As kernel is the same for suspend and resume... Yes, it seems it
> > makes sense.
>
> But before the suspend, the IDE modules are loaded, so the swap
> drive is accessible, no? Or are IDE modules (yes, they are modules
> here) unloaded just before writing to swap?
I think Pavel got a bit confused somewhere here! The IDE modules will
always be loaded when you're doing the suspend, right to the very end.
At resume time, they need to be loaded the swsusp attempts to parse the
resume= parameter, so that it can actually succeed in doing that.
Suspend2 works with IDE made as modules because it allows you to delay
that parsing until after the modules are loaded (you put echo >
/proc/software_suspend/do_resume in your initrd after modules are loaded
but before you mount filesystems). Last time I looked, swsusp didn't
have that capability and thus required IDE to be built in. Pavel, has
that changed?
Regards,
Nigel
--
Nigel Cunningham
Software Engineer, Canberra, Australia
http://www.cyclades.com
Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574
Maintainer of Suspend2 Kernel Patches http://softwaresuspend.berlios.de
next prev parent reply other threads:[~2005-03-01 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 20:39 martin f krafft
2005-02-09 22:07 ` Pavel Machek
2005-02-26 15:39 ` martin f krafft
2005-02-27 17:04 ` Pavel Machek
2005-02-27 17:43 ` martin f krafft
2005-02-27 17:50 ` Pavel Machek
2005-02-27 18:27 ` Rafael J. Wysocki
2005-02-28 1:58 ` Barry K. Nathan
2005-02-28 13:56 ` martin f krafft
2005-02-28 14:17 ` Pavel Machek
2005-02-28 14:33 ` Rafael J. Wysocki
2005-02-28 14:45 ` martin f krafft
2005-02-28 14:47 ` Pavel Machek
[not found] ` <<20050228144723.GA3384@elf.ucw.cz>
2005-03-01 8:22 ` martin f krafft
2005-03-01 9:00 ` Nigel Cunningham [this message]
2005-03-01 10:30 ` Pavel Machek
2005-03-01 10:30 ` 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=1109667621.4229.40.camel@desktop.cunningham.myip.net.au \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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®