From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.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 23:02:54 +0200 [thread overview]
Message-ID: <19f34abd0809251402v13b926a1o2236ddb9e7517a65@mail.gmail.com> (raw)
In-Reply-To: <48DBF964.7070106@zytor.com>
On Thu, Sep 25, 2008 at 10:49 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> 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?
I have no computer that can do KVM, sorry :-(
Stack trace contains IO_APIC functions, so it seems that maybe the
emulated IOAPIC is trying to (erroneously) deliver an int 0 (for some
reason)? But I don't know, that's just speculation which can be done
better by others, so I will stop now :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-09-25 21:03 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
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 [this message]
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=19f34abd0809251402v13b926a1o2236ddb9e7517a65@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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®