[lkml]   [2005]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Disc driver is module, software suspend fails

> > You insmod driver for your swap device, then you echo device numbers
> > to /sys... then initiate resume.
> So you're saying, let the machine come all the way up, log in as root,
> "echo 8:5 > /sys/power/resume" (I think that was the name), then "echo
> resume > /sys/power/state"? Hmm, you would have to bypass "swapon -a",
> e.g. boot with the -b kernel parameter.

Well, basically yes, but do that without any writing to filesystem, or
it is "bye bye data".

> Or I'll bet one could do something equivalent in the initrd -- much more
> user friendly. But the friendliest of all would be if the swsusp resume
> call were not a late_initcall but rather were called just before the root
> was mounted, after the initrd (if any) had loaded whatever modules. I
> think you're confirming that that approach would not blow up the kernel --
> if it will work with the root mounted and user space in full roar (well,
> skimpy roar with the -b switch), then it's got to be OK at the earlier
> time.

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.
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-04-06 13:31    [W:0.034 / U:9.868 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site