Bug#572858: initramfs-tools: Doesn't resume from hibernation, restarts fresh
On Sun, Mar 07, 2010 at 04:17:55PM +0100, Julien Valroff wrote:
> Le dimanche 07 mars 2010 à 16:14 +0100, maximilian attems a écrit :
> > On Sun, 07 Mar 2010, Julien Valroff wrote:
> >
> > > Package: initramfs-tools
> > > Version: 0.93.4
> > > Severity: normal
> > >
> > > Hi,
> > >
> > > If I do not specify my resume partition in the kernel command line, my computer doesn't resume from hibernation, but starts fresh instead.
> > >
> > > This wasn't the case until recently.
> > >
> > > I have found a similar issue in Ubuntu, which has a patch attached and which is now tagged as fixed. Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/499940 for all the details.
> > >
> > > I haven't tried adapting the patch to the currernt Debian package as it doesn't apply cleanly and I fear I make some errors and break my complete boot process.
> > > I would be glad testing anyway if needed.
> > >
> > > Cheers,
> > > Julien
> >
> > please post the content of those 2 files on relevant box:
> > /etc/initramfs-tools/conf.d/resume
>
> RESUME=UUID=aa748dde-93f1-4e7f-887a-71fa58db6140
>
>
> > /etc/fstab
>
> proc /proc proc defaults 0 0
> /dev/mapper/gaia-root / ext3 errors=remount-ro 0 1
> # /boot was on /dev/sda1 during installation
> UUID=08ff5fb8-82dd-4968-a05f-b7cd323e052f /boot ext2 defaults 0 2
> /dev/mapper/gaia-swap_1 none swap sw 0 0
>
>
> $ ls -l /dev/disk/by-uuid/
> total 0
> lrwxrwxrwx 1 root root 10 7 mars 08:24 08ff5fb8-82dd-4968-a05f-b7cd323e052f -> ../../sda1
> lrwxrwxrwx 1 root root 24 7 mars 08:24 aa748dde-93f1-4e7f-887a-71fa58db6140 -> ../../mapper/gaia-swap_1
> lrwxrwxrwx 1 root root 22 7 mars 08:24 e91cb78c-f290-4059-8d5c-8183e2adc177 -> ../../mapper/gaia-root
>
> It is worth noting this box was installed on Sunday last week (from the
> testing daily CD image and immedately upgraded to sid after the base
> installation)
oh i can see the bug the conversion to UUID happens to late,
so lvm wouldn't activate your UUID swap.
will fix later today and ask you to test latest git, thanks.
Reply to: