Hello you lovely people,
I'm on debian with linux 3.11.4 and want to try the hibernation feature on my laptop.
I've had problems with supending - the power led didn't come on after resuming - but those are out of the way.
My biggest problem is, that concurrent hibernations don't work. After resuming any way of hibernating again - echoing disk, pm-hibernate or via Kickoff - will lock the screen and do nothing else, no log entries in pm-logs in /var/log and when shutting down i see the pm-hibernate process hanging there until terminated.
Also, resuming wont work if the resume paramter is specified as UUID.
That means passing
resume=UUID=3dda5c70-e1b4-4084-bbf6-f190687d7060 or
resume=/dev/disk/by-uuid/3dda5c70-e1b4-4084-bbf6-f190687d7060 wont resume whereas
resume=/dev/sda5 does
This is from blkid:
Code:
/dev/sda5: UUID="3dda5c70-e1b4-4084-bbf6-f190687d7060" TYPE="ext4
Code:
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root 99a50daf-5d8e-4b83-ba83-d5e02060e456
echo 'Loading Linux 3.11.4 ...'
linux /vmlinuz-3.11.4 root=/dev/sda6 ro acpi_osi=Linux iommu=noaperture rootflags=data=journal resume=UUID=3dda5c70-e1b4-4084-bbf6-f190687d7060 resume_offset=17397760 quiet
This is output by
update-grub and for some reason the root-parameter is a device instead of a UUID.
On the side:
Could my kernel have problems with UUID's?
Edit:
init/do_mounts.c states that UUID's should be passed as
PARTUUID. I've tried that also.
Taken from /var/log/kern.log :
Code:
Oct 15 12:43:44 rivendell kernel: [ 2.050450] PM: Checking hibernation image partition PARTUUID=3dda5c70-e1b4-4084-bbf6-f190687d7060
...
Oct 15 12:43:44 rivendell kernel: [ 3.171408] PM: Hibernation image not present or could not be loaded.
kind regards, yogo1212