From: Avi Kivity <avi@qumranet.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22-rc1-mm1: strange GPF when panicing under kvm
Date: Thu, 17 May 2007 16:23:24 +0300 [thread overview]
Message-ID: <464C574C.5020201@qumranet.com> (raw)
In-Reply-To: <464B9E19.6050902@goop.org>
Jeremy Fitzhardinge wrote:
> When I boot 2.6.22-rc1-mm1 under kvm, but forget to specify a root
> filesystem, it panics as expected. However, when panicing, it gets a
> GPF in delay_tsc, and then starts recursively panicing.
>
> I don't really understand what's going on; the instruction it's faulting
> on seems to be "pause" (ie, rep;nop), which seems like it shouldn't
> fault at all. It looks like some kvm artifact to me, but I'm not sure.
>
> Hm, given the error code, maybe it's a segment register problem.
>
>
Strange. What does your msr 0x482 look like? If you have
/dev/cpu/0/msr, the following will spit it out:
-------------
#!/usr/bin/python
import struct
msrs = file('/dev/cpu/0/msr')
msrs.seek(0x482)
msr = msrs.read(8)
msr = struct.unpack('Q', msr)[0]
print '%x' % (msr,)
----------------
(that msr can force trapping of the pause instruction, even though
there's no good reason to do it, and kvm wouldn't inject a gp if it did
anyway).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-05-17 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 0:13 2.6.22-rc1-mm1: strange GPF when panicing under kvm Jeremy Fitzhardinge
2007-05-17 13:23 ` Avi Kivity [this message]
2007-05-17 17:15 ` Jeremy Fitzhardinge
2007-05-17 17:30 ` Avi Kivity
2007-05-17 18:10 ` Jeremy Fitzhardinge
2007-05-17 18:17 ` Avi Kivity
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=464C574C.5020201@qumranet.com \
--to=avi@qumranet.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--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