public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>, LKP ML <lkp@01.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [x86_64, vsyscall] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Date: Mon, 15 Dec 2014 09:07:38 +0800	[thread overview]
Message-ID: <1418605658.5745.144.camel@linux.intel.com> (raw)
In-Reply-To: <CALCETrUYd3obWmBRWooA+J1fpxvsjvLEyReZ=2weMUQHhgykrg@mail.gmail.com>

On Sun, 2014-12-14 at 17:03 -0800, Andy Lutomirski wrote:
> On Sun, Dec 14, 2014 at 4:58 PM, Huang Ying <ying.huang@linux.intel.com> wrote:
> > FYI, we noticed the below changes on
> >
> > commit 1ad83c858c7d4ea210429142c99a1548e6715a35 ("x86_64,vsyscall: Make vsyscall emulation configurable")
> >
> 
> This is expected.  You turned off an expert option, disabling
> emulation of a deprecated feature that your init needs. :)  If you
> enable that option but boot with vsyscall=none, you'll get the same
> OOPS, but you'll get a helpful error message, too.
> 
> Either force CONFIG_X86_VSYSCALL_EMULATION=y or upgrade to a modern
> gilbc and make sure you rebuild all your static binaries.

Thanks a lot for your information!  That is helpful for our testing!

Best Regards,
Huang, Ying



      reply	other threads:[~2014-12-15  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  0:58 [LKP] [x86_64, vsyscall] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Huang Ying
2014-12-15  1:03 ` Andy Lutomirski
2014-12-15  1:07   ` Huang Ying [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1418605658.5745.144.camel@linux.intel.com \
    --to=ying.huang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=luto@amacapital.net \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox