Re: swsusp logic error?

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > > > > 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?

No, it has not changed for mainline.

SuSE has patch to allow resume from modular IDE.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!