From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Xen 3.2.1-rc1: FATAL PAGE FAULT
Date: Thu, 03 Apr 2008 16:55:29 +0100
Message-ID: <C41ABC81.1EC6A%keir.fraser@eu.citrix.com>
References: <47F4E401.2080703@theshore.net>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <47F4E401.2080703@theshore.net>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Christopher S. Aker" <caker@theshore.net>, xen devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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