Control: severity -1 import Control: tag -1 moreinfo On Tue, 2014-09-09 at 19:43 +0200, C. Dominik Bodi wrote: > Package: src:linux > Version: 3.16.2-2 > Severity: critical > Justification: breaks the whole system > > I've got a debian unstable system running in a ganeti/kvm vm that runs > with lvm. The physical volume the root file system resides on is > encrypted with luks. I've installed dropbear to unlock the luks volume > via ssh, using a kernel cmdline ip=... in /etc/grub/default > > Up and including linux-image-3.14-2-amd64 this worked flawlessly. > > However, having installed and booted from 3.16-1, the kernel panics > after unlocking the luks volume. There were some error messages about > /dev/pts and/or /dev not being mounted successfully, but as the kernel > panicked, the busybox console (accessed via spice) was frozen and I had to ask the admin > admin to hard-reset the machine for me. > > The 3.14-2 kernel continues to boot normally, > > I'm a bit at loss what might cause 3.16 to panic but 3.14 to boot > successfully. Unfortunately I cannot hard-reset the machine myself > (spice remote-viewer does not to support hard-reset signals to the vm) > and I wasn't able to deduce anything from the few kernel panic lines > on the console. [...] But we might be able to. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports.
Attachment:
signature.asc
Description: This is a digitally signed message part