Re: [x86] a75a3f6fc9 Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
From: Andy Lutomirski
Date: Sat Feb 18 2017 - 01:13:03 EST
On Fri, Feb 17, 2017 at 9:42 PM, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote:
> FYI here is an old bug, however is still active in mainline kernel.
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> [ 3.185986] init vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffe878ff8b8 ax:ffffffffff600400 si:7f2c3de62a4c di:7ffe878ff978
I don't know what's up with the bisection, but I think this is a
configuration problem in your test setup. You've configured with:
which is not valid when you're running binaries that are compiled with
as old a glibc as you're using. *Dynamic* glibc binaries have been
fine for a long time, but static glibc binaried (e.g. your init, I
presume) need a glibc that's only a couple years old.
You could fix it by either disallowing that particular configuration
or by updating your distro.