Control: tag -1 moreinfo On Sun, 01 Nov 2015 15:18:46 +0100 Stefano Zacchiroli <zack@debian.org> wrote: > Package: src:linux > Version: 4.2.3-2 Can you test whether this is fixed in 4.2.6-1 or 4.3-1~exp1? > Severity: serious > > [ note I'm not reporting this bug from the affected kernel version, before I > can't boot with it ] > > My laptop (Debian testing) fails to boot with linux-image-4.2.0-1-amd64 , but > boots fine with linux-image-4.1.0-2-amd64 . The boot hangs after grub, with > only "Loading, please wait..." shown on the screen (see attached picture > 1-boot-hang.jpg). My hard disk is fully encrypted, so what is supposed to > happen at that point is prompting the user for a cryptsetup passphrase. In > attached picture 3-boot-regular.jpg you have a regular boot with 4.1.0, > prompting for the passphrase (with some warnings which I've always seen, but > that might be relevant here). I see those warnings as well; it's a bug in lvm2. > I've tried to get a systemd debug shell, but that didn't work either. That won't work as systemd isn't used in the initramfs. You can use 'break=top' or similar to get a shell in the initramfs. > I've also > tried to remove quiet from the kernel command line to see what happens. You can > see the result in attached picture 2-boot-hang-details.jpg . The last visible > message in there is "Begin: Running /scripts/init-premount ...". > > To make sure this is not some sort of timeout issue (that anyhow doesn't happen > with 4.1.0), I've waited up to 30 minutes, without any visible change. > > Let me know how I can help debugging this further, This is very strange - that's much longer than the initramfs device timeout and the kernel lockup-detector timeouts. Can you try this: - Boot with the added parameter: break=top - In the shell, run: echo 1 >/proc/sys/kernel/sysrq openvt exit - Once the system has hung, press Alt-SysRq, Alt-W, Alt-SysRq, Alt-L - Switch to VT 2 then show the kernel log with: dmesg | less - Send photos of all the call traces Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code.
Attachment:
signature.asc
Description: This is a digitally signed message part