On Fri, Dec 27, 2013 at 10:56:06PM +0100, Rodolfo García Peñas wrote: > > I am trying to solve this bug, but I need more info.
Thanks, I'll do what I can. > > Please, could you try the latest initramfs-tools package (version 0.115)? The > initramfs-tools package had a problem with blkid, and this problem affected > uswsusp. This problem is solved now, but I need that you test this new > version. I am using initramfs-tools 0.115 to generate the initramfs I examined. > OTOH, if you are using lvm2, this package has a problem because doesn't > initialize the swap device if is in a LVM device. You can see the bug number > #544641 I use the workaround suggested in this bug report: I give resume=/dev/mapper/cryptvg-swap as kernel commandline parameter To my reading of the initscripts, this variant should work. (See end of scripts/local-top/lvm2) Practical test with debugging and breakpoints confirms it. IMHO the meaning of the resume variable varies a bit across all involved initscripts. I have not yet looked up if there is a debian policy about it, as said, I had a bad surprise with the change in behaviour. Bye, Joerg
signature.asc
Description: Digital signature
