I have hand write this: Call Trace: dump_stack+0x45/0x56 panic+0xc6/0x1fa do_exit+0xaa1/0xab0 do_group_exit+0x43/0xc0 SyS_exit_group+0x14/0x20 system_call_fastpath+0x1a/0x1f kernel offset:0x00 from 0xffffffff81000000 (relocation range: 0xffffffff80000000 - 0xffffffffbfffffff Kernel panic - not syncing: Attempted to kill init! exit code = 0x00000b00 and this is my istro and packages: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1402957
Created attachment 166691 [details] panic screenshot of virtualbox I get the same panic with kernel 3.19.0 (no rc ) in Gentoo guest inside VirtualBox, whilst trying to boot from a btrfs root device which is on the same LVM volume group as the btrfs boot device, and that LVM is inside a LUKS partition; using grub(git version) to boot from a disk that has BIOS boot partition(for grub) and 1 LUKS partition(within it it's the LVM with the 2 lvs: boot and root, both btrfs) Used grub with these 2 patches: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1420584 for me: Kernel panic - not syncing: Attempted to kill init! exit code=0x00000100 well here's a screenshot:
I tried adding kernel parameter boot_delay= but it has no effect whatsoever tried: boot_delay=500 boot_delay=1000 boot_delay=9999 the doc(Documentation/kernel-parameters.txt) says: boot_delay= Milliseconds to delay each printk during boot. Values larger than 10 seconds (10000) are changed to no delay (0). Format: integer
Created attachment 166721 [details] dmesg serial output Ok, since I am on VirtualBox, I used a serial port file and by passing this to kernel cmdline: console=ttyS0,9600n8 earlyprintk=serial,ttyS0,9600,keep I was able to see why this issue happens for me: !! The ramdisk does not support LUKS [ 33.995717] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 33.995717] [ 34.004751] CPU: 2 PID: 1 Comm: init Not tainted 3.19.0-gentoo #1 [ 34.004751] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 34.004751] ffffffff81563ee0 ffff88021d8c3e38 ffffffff813d0ddc 00000000000000a6 [ 34.004751] ffffffff814b9afa ffff88021d8c3eb8 ffffffff813cef30 ffff88021d89a760 [ 34.004751] 0000000000000010 ffff88021d8c3ec8 ffff88021d8c3e68 ffff88021d8c3ef8 [ 34.004751] Call Trace: [ 34.004751] [<ffffffff813d0ddc>] dump_stack+0x45/0x57 [ 34.004751] [<ffffffff813cef30>] panic+0xb9/0x1dc [ 34.004751] [<ffffffff81039188>] do_exit+0x48c/0x896 [ 34.004751] [<ffffffff8103a2e8>] ? SyS_wait4+0x9b/0xb4 [ 34.004751] [<ffffffff8103a07f>] do_group_exit+0x3f/0x93 [ 34.004751] [<ffffffff8103a0e2>] SyS_exit_group+0xf/0xf [ 34.004751] [<ffffffff813d5e92>] system_call_fastpath+0x12/0x17 [ 34.004751] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) [ 34.004751] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 34.004751] So I'm going back to booting from livecd and making sure initramfs has support for LUKS :)
I fixed that(I had passed --no-luks before, to genkernel, but should've been --luks), but OP likely has a different issue, not to mention on a different OS. Cheers.
This is RAM issue I have mixed 2x4GB Hynix CL 11-11-11-28 and Geil 8GB CL 10-10-10-28. After remove Geil RAM this problem disappear.