This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT

To: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 30 Aug 2010 10:02:05 +0100
Delivery-date: Mon, 30 Aug 2010 02:03:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY121-W47C2F18C8C8A31F98554B0DA890@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActIIBeD3ivBxorCQdW93ALtV+NA9AAAezhx
Thread-topic: [Xen-devel] Xen-unstable panic: FATAL PAGE FAULT
User-agent: Microsoft-Entourage/
On 30/08/2010 09:47, "MaoXiaoyun" <tinnycloud@xxxxxxxxxxx> wrote:

>        3) Every panic pointer to the same address:  ffff8315ffffffe4, which is
> not a valid page address.
> I printted pages of the domain in assign_pages, which all looks like
> ffff82f60bd64000,  at least
> ffff82f60 is the same.

Yes, well you may not be crashing on a supposed page address. Certainly the
page pointer that relinquish_memory() is working on, and passed to
put_page->free_domheap_pages is valid enough to not cause any of those
functions to crash when dereferencing it. At the moment you really have no
idea what is causing free_heap_pages() to crash.

>        A bit of lost direction to go further.  Thanks.

You need to find out which line of code in free_heap_pages() is crashing,
and what variable it is trying to dereference when it crashes. You have a
nice backtrace with an EIP value, so you can 'objdump -d xen-syms' and
search for the EIP in the disassembly. If you have a debug build of Xen you
can even do 'objdump -S xen-syms' and have the disassembly annotated with
corresponding source lines.

Have you seen this on more than one physical machine? If not, have you run
memtest on the offending machine?

 -- Keir

Xen-devel mailing list