I am running a custom 2.6.29-rc2 on a crypted-root machine, and as kenzo pointed out, it doesn't boot at all.
The machine was upgraded to jaunty from intrepid without any warnings or errors.
update-initramfs on a (old) working kernel/initrd causes this bug to appear, too.
I am running a custom 2.6.29-rc2 on a crypted-root machine, and as kenzo pointed out, it doesn't boot at all.
The machine was upgraded to jaunty from intrepid without any warnings or errors.
update-initramfs on a (old) working kernel/initrd causes this bug to appear, too.
Afer some time, the machine reboots.