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 3.2.1-rc5: FATAL PAGE FAULT

To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.2.1-rc5: FATAL PAGE FAULT
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 22 Apr 2008 19:46:34 +0100
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 Apr 2008 11:46:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <480E2C2C.303@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcikqS/kbo44ExCcEd2wrgAWy6hiGQ==
Thread-topic: [Xen-devel] Xen 3.2.1-rc5: FATAL PAGE FAULT
User-agent: Microsoft-Entourage/
On 22/4/08 19:19, "Christopher S. Aker" <caker@xxxxxxxxxxxx> wrote:

> Here are two more Xen traces with this problem.  These always appear to
> occur after we're forced to destroy a domain.  The first trace is a
> DoubleDump<tm> and has something new in the second dump...
> http://www.theshore.net/~caker/xen/build-1.11/
> I still don't have a method to reproduce, but since we're hitting this
> with some frequency, would it be worth it to stick in some extra
> debugging now?

The second crash is just some overzealous asserting. Easily fixed but also
not very interesting, unfortunately.

The two main backtraces are exactly the same bug as you saw last time.
Except in this case you have bogus nonsense in a pair of L2 pagetable
entries, whereas last time the garbage was in an L3 entry.

My best guess just now, seeing as noone else has reported ever seeing this,
is that maybe you have a bad driver or hardware corrupting memory? Obviously
that's a bit of a stab in the dark though.

Have you seen this particular type of crash on multiple different machines?
If so, are they different types of machine?

 -- Keir

Xen-devel mailing list