Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19481 - Hibernate (suspend to disk) does resume from swap volumes on LVM2

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Sunday, 16 May 2010, 13:59 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 16 May 2010, 23:21 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

My machine never resumes from hibernation. It boots normally intead. I tried both the in-kernel implementation and TuxOnIce. None of them works with my swap volume on LVM2. It suspends, but never resumes.

I have already described the problem here http://bbs.archlinux.org/viewtopic.php?id=97124, but the bug tracker could probably get more attention. :-)

The 'resume' hook is already on my list of hooks in mkinitcpio.conf. (Didn't know about it when writing the BB post.) Unfortunately, the system still boots as usual, never resuming.

Additional info:
* package version(s)
mkinitcpio 0.6.3-1

Steps to reproduce:
Try to resume from a swap volume on LVM2.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Sunday, 16 May 2010, 23:21 GMT
Reason for closing:  Not a bug
Comment by Andrej Podzimek (andrej) - Sunday, 16 May 2010, 13:59 GMT
Sorry, 'not' is missing in my title. s/does resume/does not resume/
My stupidity, as usual. :-D
Comment by Andrej Podzimek (andrej) - Sunday, 16 May 2010, 14:11 GMT
Based on a piece of advice from a mailing list, I have just got this working. You need *two* things:

1) The 'resume' hook in your mkinitcpio.conf, so that the resume operation can start *after* the LVM2 group is ready.
2) The 'resume=/dev/mapper/octopus-swap' (in my case) on the kernel command line.

In all the kernels I tried, at least one of these two things was missing, so that's why it didn't resume. I thought the 'resume=' parameter should not be needed, since I have this in my (vanilla) kernel configuration:

CONFIG_PM_STD_PARTITION="/dev/mapper/octopus-swap"

That was a wrong assumption. Someone (probably the 'resume' hook) just takes a look at the kernel command line and expects 'resume=' to be there.

Loading...