Resume from encrypted swap fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pm-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm using (K)ubuntu 8.04.1 Hardy, freshly installed from the alternate iso.
lsb_release -rd:
Description: Ubuntu 8.04.1
Release: 8.04
I can't resume after hibernation. Hibernate itself seems to work fine (at least mounting the encrypted swap complains about a suspend signature on the device, see below). However on restart it doesn't seem to actually do a resume, but a normal startup.
I created two encrypted partitions with the alternate installer:
/dev/mapper/
/dev/mapper/
I don't use LVM. Booting and mounting both partitions works fine as long as I don't hibernate. However if I do, on startup I get:
[...]
[successfully unlocking root]
Done.
Begin: Running /scripts/
Begin: Waiting for resume device... ...
Done.
Done.
[successfully mounting root]
[...]
* Starting early crypto disks...
Enter LUKS passphrase:
key slot 0 unlocked.
Command successful.
* sda9_crypt: the check for '/dev/mapper/
* Starting remaining crypto disks...
[another try for sda9_crypt, fails same as above]
I don't know how the boot process for resume should look like, but to me it seems as if it's just the normal boot procedure, and that unsuprisingly fails i.e. as if it's not performing a resume at all! The resume device seems to be ignored. I tried specifying different resume parameters in grub, but couldn't find one that worked. (I couldn't find out what exactly it should look like for encrypted swap partitions, though.)
affects: | acpi (Ubuntu) → pm-utils (Ubuntu) |
Coonfirming with a fresh Ubuntu Karmic install (using the encrypted home directory option in the installer).