mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.27-rc7: x86: #GP on panic?
Date: Thu, 25 Sep 2008 10:04:17 +0200	[thread overview]
Message-ID: <20080925080417.GB27048@elte.hu> (raw)
In-Reply-To: <19f34abd0809241209l3a69d607v153549ee43e085e9@mail.gmail.com>


* Vegard Nossum <vegard.nossum@gmail.com> wrote:

> Hi,
> 
> With 2.6.27-rc7 on qemu-x86_64, it seems that panic will trigger a 
> General Protection Fault. I haven't seen it before.

> [    4.523641] Code: eb fd 55 48 89 e5 53 51 83 3d 25 e8 78 00 00 75
> 1a 31 d2 31 f6 48 c7 c7 e1 9c 01 81 e8 f7 a4 03 00 9c 5b fa e8 94 09
> 00 00 53 9d <5a> 5b c9 c3 55 31 c0 48 89 e5 89 04 25 b0 c0 5f ff 65 83
> 04 25

hm, 0x5a is a simple pop %rdx. A #GP there means the stack segment is 
bust?

hm:

> ffffffff8101a6b9 <disable_local_APIC>
> ffffffff81019d25:       53                      push   %rbx
> ffffffff81019d26:       9d                      popfq
> ffffffff81019d27:       5a                      pop    %rdx

so it's preceded by a popfq and on the next instruction we #GP.

but the stack and flags state looks good:

  [    4.523641] RSP: 0018:ffff880007867d70  EFLAGS: 00000286

weird.

	Ingo

  reply	other threads:[~2008-09-25  8:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 19:09 Vegard Nossum
2008-09-25  8:04 ` Ingo Molnar [this message]
2008-09-25  8:53   ` H. Peter Anvin
2008-09-25 14:07     ` Vegard Nossum
2008-09-25 15:20       ` Vegard Nossum
2008-09-25 20:46         ` Vegard Nossum
2008-09-25 20:49           ` H. Peter Anvin
2008-09-25 21:02             ` Vegard Nossum
2008-09-25 21:53               ` H. Peter Anvin
2008-09-27 18:43                 ` Ingo Molnar

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=20080925080417.GB27048@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@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
all inboxes | Powered by JetHome®