Re: [Swsusp-devel] [PATCH 2.6]: suspend to disk only available if non-modular IDE

[Andreas Jellinghaus <aj@dungeon.inka.de>]

[currently no scsi support]
ah, ok. 

> > btw: would it be somehow possible to resume after initrd phase?
> > or some other idea how a generic kernel with modules in the initrd
> > could use suspend to disk? or a laptop where the initrd is needed
> > to setup a dm-crypt volume with the right decrypton key?
> 
> That should be doable, provided that the initrd doesn't mount anything.
> Decryption is 'interesting'. The key needs to be set up in the resumed
> kernel too. (Shouldn't be a problem, if you manage to suspend to it!).

I don't know if loading modules can be done without, but the usual way
is to mount /sys and /proc so you can see what hardware is available.

I do that too for my dm-crypt setup, even mount a tmpfs at /dev,
create devices, start usb hotplugging, etc. but after getting the
decryption key, all filesystems are unmounted again, all processes
killed, there is nothing visible to me left. would that still create
some problems in the kernel internals preventing resume (or making it
too hard to do)?

Regards, Andras