From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Jet Chen <jet.chen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [x86, smap] general protection fault: fff2 [#1] PREEMPT DEBUG_PAGEALLOC
Date: Tue, 15 Apr 2014 19:05:22 -0700 [thread overview]
Message-ID: <534DE562.8040700@linux.intel.com> (raw)
In-Reply-To: <53477D33.8030809@intel.com>
On 04/10/2014 10:27 PM, Jet Chen wrote:
> [ 371.380921] general protection fault: fff2 [#1] PREEMPT DEBUG_PAGEALLOC
I am guessing this is an issue with DEBUG_PAGEALLOC... this message is
odd in the extreme because it is hard to see how we could #GP(0xfff2)
here -- which normally would indicate having attempted to load 0xfff2 as
a segment selector (which is going to fail spectacularly).
This happens immediately after a popfq which enables interrupts(!), so
my guess is that we're trying to deliver an interrupt but that for some
reason there is garbage in the IDT or similar.
Unfortunately the GPF message doesn't include the IDT/GDT information...
-hpa
prev parent reply other threads:[~2014-04-16 2:05 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
2014-04-16 2:05 ` H. Peter Anvin [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=534DE562.8040700@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