Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752062AbaLOBHq (ORCPT ); Sun, 14 Dec 2014 20:07:46 -0500 Received: from mga09.intel.com ([134.134.136.24]:2384 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750702AbaLOBHk (ORCPT ); Sun, 14 Dec 2014 20:07:40 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,691,1406617200"; d="scan'208";a="498673512" Message-ID: <1418605658.5745.144.camel@linux.intel.com> Subject: Re: [LKP] [x86_64, vsyscall] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b From: Huang Ying To: Andy Lutomirski Cc: Thomas Gleixner , LKP ML , LKML Date: Mon, 15 Dec 2014 09:07:38 +0800 In-Reply-To: References: <1418605089.5745.139.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2014-12-14 at 17:03 -0800, Andy Lutomirski wrote: > On Sun, Dec 14, 2014 at 4:58 PM, Huang Ying 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/