From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Jody Belka <lists-lkml@pimb.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Ian Campbell <ijc@hellion.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <andi@firstfloor.org>,
Mika Penttila <mika.penttila@kolumbus.fi>
Subject: Re: 2.6.25-rc1 xen pvops regression
Date: Sat, 16 Feb 2008 22:46:23 +1100 [thread overview]
Message-ID: <47B6CD0F.4020202@goop.org> (raw)
In-Reply-To: <20080216085454.GA24570@ca-server1.us.oracle.com>
Joel Becker wrote:
> On Sat, Feb 16, 2008 at 01:44:26PM +1100, Jeremy Fitzhardinge wrote:
>
>> Joel Becker wrote:
>>
>>
>>> (XEN) mm.c:1825:d109 Bad type (saw 0000000028000001 != exp
>>> 00000000e0000000) for mfn 3a2f0f (pfn f0)
>>> (XEN) mm.c:649:d109 Error getting mfn 3a2f0f (pfn f0) from L1 entry
>>> 00000003a2f0f063 for dom109
>>> (XEN) mm.c:1825:d109 Bad type (saw 0000000028000001 != exp
>>> 00000000e0000000) for mfn 3a2f0f (pfn f0)
>>> (XEN) mm.c:649:d109 Error getting mfn 3a2f0f (pfn f0) from L1 entry
>>> 00000003a2f0f063 for dom109
>>> (XEN) mm.c:3331:d109 ptwr_emulate: could not get_page_from_l1e()
>>>
>>>
>> Hm, I have a suspicion about what this might be. I'll haven't tried
>> reproducing it yet though.
>>
>>
>>> (XEN) Unhandled page fault in domain 109 on VCPU 0 (ec=0003)
>>> (XEN) Pagetable walk from 00000000c01687f0:
>>> (XEN) L4[0x000] = 00000003a2933027 00000000000006cc
>>> (XEN) L3[0x003] = 000000039afea027 0000000000000005
>>> (XEN) L2[0x000] = 000000039bfb7067 0000000000001048 (XEN) L1[0x168] =
>>> 00000003a2e97061 0000000000000168
>>> (XEN) domain_crash_sync called from entry.S
>>> (XEN) Domain 109 (vcpu#0) crashed on cpu#2:
>>> (XEN) ----[ Xen-3.1.3-rc3 x86_64 debug=n Not tainted ]----
>>> (XEN) CPU: 2
>>> (XEN) RIP: e019:[<00000000c04040bd>]
>>>
>>>
>> What does this EIP correspond to in your kernel? Also:
>>
>> c01687f0 c0417ab6 c040288f c040299a c0403270
>>
>> (as guesses of potential callers to try and work out a stack trace).
>>
>
> ksymoops is no help at all, but I got these from objdump of
> vmlinux:
>
> c04040bd xen_set_pte
> c0417ab6 set_pte_present
> c040288f set_bit
> c040299a __raw_spin_unlock
> c0403270 __set_64bit
(My usual technique is use "gdb vmlinux" and "x/i 0x...." to do the
lookup.)
Unfortunately that doesn't narrow down what the kernel was actually
trying to do at the time. Clearly a set_pte; looks like someone is
trying to create a writable mapping of an existing pte page.
Does "console=hvc0 earlyprintk=xen" on the kernel command line give any
clue about how far it gets before crashing?
J
next prev parent reply other threads:[~2008-02-16 11:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 23:54 2.6.25-rc1 xen pvops regression Jody Belka
2008-02-13 11:59 ` Jeremy Fitzhardinge
2008-02-13 12:13 ` Jody Belka
2008-02-13 12:23 ` Ingo Molnar
2008-02-14 2:27 ` Joel Becker
2008-02-14 7:50 ` Jeremy Fitzhardinge
2008-02-15 20:23 ` Joel Becker
2008-02-16 2:44 ` Jeremy Fitzhardinge
2008-02-16 8:54 ` Joel Becker
2008-02-16 11:46 ` Jeremy Fitzhardinge [this message]
2008-02-17 6:29 ` Joel Becker
2008-02-17 12:09 ` Jeremy Fitzhardinge
2008-02-17 6:39 ` Joel Becker
2008-02-17 18:49 ` Ian Campbell
2008-02-18 10:40 ` Joel Becker
2008-02-19 21:50 ` Ian Campbell
2008-02-19 21:59 ` Ian Campbell
2008-02-20 7:43 ` H. Peter Anvin
2008-02-20 8:51 ` Ian Campbell
2008-02-20 21:42 ` Joel Becker
2008-02-20 22:30 ` Ian Campbell
2008-02-20 21:58 ` Jeremy Fitzhardinge
2008-02-20 22:29 ` Ian Campbell
2008-02-21 21:16 ` Jeremy Fitzhardinge
2008-02-21 21:21 ` H. Peter Anvin
2008-02-21 21:37 ` Jeremy Fitzhardinge
2008-02-21 21:44 ` H. Peter Anvin
2008-02-21 22:12 ` Ian Campbell
2008-02-21 22:23 ` H. Peter Anvin
2008-02-21 22:49 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` H. Peter Anvin
2008-02-22 7:25 ` Ian Campbell
2008-02-22 9:28 ` Alan Cox
2008-02-22 9:55 ` Andi Kleen
2008-02-22 10:00 ` Alan Cox
2008-02-22 10:15 ` Andi Kleen
2008-02-22 16:27 ` H. Peter Anvin
2008-02-22 19:25 ` Pavel Machek
2008-02-26 17:06 ` Mark McLoughlin
2008-02-26 20:05 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` Joel Becker
2008-02-21 22:04 ` Eric W. Biederman
2008-02-21 23:14 ` Jeremy Fitzhardinge
2008-02-21 23:26 ` H. Peter Anvin
2008-02-21 23:46 ` Jeremy Fitzhardinge
2008-02-21 23:57 ` H. Peter Anvin
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=47B6CD0F.4020202@goop.org \
--to=jeremy@goop.org \
--cc=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lists-lkml@pimb.org \
--cc=mika.penttila@kolumbus.fi \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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