All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.27-rc7: x86: #GP on panic?
Date: Thu, 25 Sep 2008 13:49:40 -0700	[thread overview]
Message-ID: <48DBF964.7070106@zytor.com> (raw)
In-Reply-To: <19f34abd0809251346r62cff1ck4730260f17e643b3@mail.gmail.com>

Vegard Nossum wrote:
> 
> But I don't see how the divide error could occur here:
> 
> ffffffff8103918b:       fb                      sti
> ffffffff8103918c:       49 c7 c4 80 c0 6e 81    mov    $0xffffffff816ec080,%r12
> ffffffff81039193:       f6 c3 01                test   $0x1,%bl
> ffffffff81039196:       74 27                   je     ffffffff810391bf <__do_so
> ffffffff81039198:       4c 89 e7                mov    %r12,%rdi
> ffffffff8103919b:       41 ff 14 24             callq  *(%r12)
> 
> Seems like an external interrupt happened and was delivered after the sti?
> 
> Hm. I guess it smells like a qemu bug since it's rather easily
> reproducible here and sounds strange that nobody else saw it. Is qemu
> 0.9.1.
> 

Yes, but there shouldn't be any external interrupts that could turn into 
  a divide error.  It really smells like a Qemu problem -- possibly even 
a Qemu miscompile -- to me.

Does it reproduce in KVM?

	-hpa

  reply	other threads:[~2008-09-25 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 19:09 v2.6.27-rc7: x86: #GP on panic? Vegard Nossum
2008-09-25  8:04 ` Ingo Molnar
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 [this message]
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=48DBF964.7070106@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.