Re: Kernel panic - Attempted to kill init!
On 17/05/15 11:49 PM, Marc F. Clemente wrote:
> On 05/16/2015 05:03 AM, Ben Armstrong wrote:
>>
> That's fine. We'll stick with stretch/amd64.
>
OK. I tried using 5.0~a7-1 (with patch: see below) to build a default
stretch/i386 image. It booted fine in qemu with the following options:
qemu -enable-kvm -m 1G -nographic -display vnc=:2 live-image-i386.hybrid.iso
> I will look at build logs to see if any messages or errors come up.
> What's the preferred way to get build logs? Something like "lb build
> > logfile.txt" or is there something better?
As per live-manual which gives the same advice:
lb build 2>&1 | tee build.log
>
>> And finally, you did not indicate the exact version of live-build you
>> are using. Since you said you're using up-to-date packages on unstable,
>> I assume it's 5.0~a7-1, but you should always include versions of live-*
>> components when reporting issues.
>
> I had 5.0~a6-1, but I upgraded to 5.0~a7-1. It was even worse; I
> couldn't even get an image created. Commands:
> su ; mkdir /root/live ; cd /root/live ; lb clean ; lb config ; lb build
>
> lb build exited with an error:
>
> no such script: binary_grub
Yes, I noticed that too, so I had to patch it as follows:
(sid)root@lear:/usr/lib/live/build# diff -u binary.old binary
--- binary.old 2015-05-14 11:16:57.000000000 +0000
+++ binary 2015-05-18 10:11:21.365709058 +0000
@@ -60,7 +60,7 @@
lb binary_package-lists ${@}
lb binary_linux-image ${@}
lb binary_memtest ${@}
-lb binary_grub ${@}
+lb binary_grub-legacy ${@}
lb binary_grub-pc ${@}
lb binary_syslinux ${@}
lb binary_disk ${@}
>
> So I just downgraded back to 5.0-a6-1. Same commands as above, I can
> get an image built. The build logs do not seem to indicate any
> anomaly. If I run that image on qemu, I still get a kernel panic,
> with the following nugget right before the panic:
>
> [ 2.908847] Freeing unused kernel memory: 216K (ffff8800017ca000 -
> ffff880001800000)
> /bin/sh: error while loading shared libraries:
> /lib/x86_64-linux-gnu/libc.so.6: invalid ELF header
> [ 2.977436] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00007f00
Interesting. Maybe an amd64-specific issue? Try again with an i386 image.
>
> If I move the image to a USB drive and boot on "real" hardware, I get...
> a bootable system. This leaves a few unanswered questions. What's
> wrong with 5.0~a7-1?
See patch above.
> What's wrong with qemu and/or the binary image that they won't run
> together?
No idea (but could be arch-specific as I hint above).
> N.B. The Debian installer (--debian-installer netboot) will run just
> fine under qemu.
But doesn't, as you indicated later ... ;) I'm not at all shocked this
early in the testing development cycle the installer isn't ready yet.
Until the debian-installer team provides one, leave off the installer
from your test images.
Ben
Reply to: