From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>, Jet Chen <jet.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [x86, smap] general protection fault: fff2 [#1] PREEMPT DEBUG_PAGEALLOC
Date: Tue, 15 Apr 2014 19:06:01 -0700 [thread overview]
Message-ID: <534DE589.5020408@linux.intel.com> (raw)
In-Reply-To: <20140411141727.GA14997@localhost>
On 04/11/2014 07:17 AM, Fengguang Wu wrote:
> Sorry, but I suspect this commit may well be innocent and merely
> _discloses_ an existing bug.
>
> Because dmesgs for the parent commit all(*) stop here, long before being able
> to emit the "reboot: machine restart" and the general protection fault.
>
> (*) "all" means all the machines that run qemu "-cpu Haswell,+smep,+smap".
>
> [ 562.353714] Failed to execute /init (error -14)
> [ 562.400008] Starting init: /sbin/init exists but couldn't execute it (error -14)
> [ 562.400008] Starting init: /etc/init exists but couldn't execute it (error -13)
> [ 562.422116] Starting init: /bin/sh exists but couldn't execute it (error -14)
> [ 562.450049] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
> [ 562.450049] CPU: 0 PID: 1 Comm: init Not tainted 3.14.0-rc1-00171-g03bbd59 #1
> [ 562.450049] 0000000000000000 ffff880012035ec0 ffffffff81380af6 ffff880012035f38
> [ 562.450049] ffffffff8137e608 ffffffff00000008 ffff880012035f48 ffff880012035ee8
> [ 562.450049] 0000000000000000 ffffffff81067fcf 0000000000000001 0000000000000000
> [ 562.450049] Call Trace:
> [ 562.450049] [<ffffffff81380af6>] dump_stack+0x19/0x1b
> [ 562.450049] [<ffffffff8137e608>] panic+0xcb/0x1ca
> [ 562.450049] [<ffffffff81067fcf>] ? console_unlock+0x319/0x336
> [ 562.450049] [<ffffffff8137778d>] ? rest_init+0xc1/0xc1
> [ 562.450049] [<ffffffff8137785e>] kernel_init+0xd1/0xd5
> [ 562.450049] [<ffffffff81386d3a>] ret_from_fork+0x7a/0xb0
> [ 562.450049] [<ffffffff8137778d>] ? rest_init+0xc1/0xc1
> [ 562.450049] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
>
That makes sense, because without that patch any SMAP-based machine
would be known broken.
-hpa
next prev parent reply other threads:[~2014-04-16 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 5:27 [x86, smap] general protection fault: fff2 [#1] PREEMPT DEBUG_PAGEALLOC Jet Chen
2014-04-11 14:17 ` Fengguang Wu
2014-04-16 2:06 ` H. Peter Anvin [this message]
2014-04-16 2:05 ` H. Peter Anvin
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=534DE589.5020408@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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