From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Christopher S. Aker" <caker@theshore.net>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.2.1-rc1: FATAL PAGE FAULT
Date: Thu, 03 Apr 2008 16:55:29 +0100 [thread overview]
Message-ID: <C41ABC81.1EC6A%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <47F4E401.2080703@theshore.net>
On 3/4/08 15:04, "Christopher S. Aker" <caker@theshore.net> wrote:
>>> Maybe the symbols would help just a little bit? In any case, here are
>>> the files:
>>>
>>> http://theshore.net/~caker/xen/BUGfatal_page_fault/
>>
>> I will take a look. It might help narrow down the possibilities a bit.
>>
My analysis is that the hypervisor crashed because one of the entries in a
dying guest's third-level page directory has the present bit (bit 0) set,
yet the physical address mapped by that entry is 0xb72dedde51000. That is a
rather large and obviously bogus number! It causes us to access way off the
end of an array indexed by physical address, resulting in a fatal page
fault.
Obviously the question is: Where did the bogus address come from?
That's going to be rather hard to answer without finding a more reliable
repro of the bug, and then adding some hypervisor tracing.
-- Keir
next prev parent reply other threads:[~2008-04-03 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 4:34 Xen 3.2.1-rc1: FATAL PAGE FAULT Christopher S. Aker
2008-04-03 14:04 ` Christopher S. Aker
2008-04-03 15:55 ` Keir Fraser [this message]
2008-04-22 18:19 ` Xen 3.2.1-rc5: " Christopher S. Aker
2008-04-22 18:46 ` Keir Fraser
2008-04-22 19:39 ` Christopher S. Aker
2008-04-22 20:21 ` Keir Fraser
2008-04-28 14:02 ` Christopher S. Aker
2008-04-28 14:44 ` Keir Fraser
2008-04-28 15:00 ` Christopher S. Aker
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=C41ABC81.1EC6A%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=caker@theshore.net \
--cc=xen-devel@lists.xensource.com \
/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.