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] [BUG] double fault for sale ;)

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [BUG] double fault for sale ;)
From: Gerd Hoffmann <kraxel@xxxxxxx>
Date: Tue, 30 May 2006 18:49:45 +0200
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 30 May 2006 09:50:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <E1Fl5UV-00021i-00@xxxxxxxxxxxxxxxxx>
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>
References: <E1Fl5UV-00021i-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20060411)
> Gerd,
> Can you please let me know whether the attached patch fixes the
> crash for you? I suspect a bug in your modified builder triggered a
> broken error path in Xen -- so this patch will hopefully turn the Xen
> crash into a failure of your modified builder. :-)

Yep, its fixed, now the newly created domain crashes, probably during
kernels initial page table setup (pfn 0 looks like that), which likely
is a builder bug.

I get this now:

(XEN) DOM1: (file=mm.c, line=1528) Bad type (saw 33030001 != exp
e0000000) for mfn c72 (pfn 0)
(XEN) DOM1: (file=mm.c, line=505) Error getting mfn c72 (pfn 0) from L1
entry 00c72063 for dom1
(XEN) DOM1: (file=mm.c, line=3054) ptwr: Could not revalidate l1 page
(XEN) domain_crash called from mm.c:3055
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    1
(XEN) EIP:    e019:[<c0101347>]
(XEN) EFLAGS: 00000286   CONTEXT: guest
[ ... ]



Gerd Hoffmann <kraxel@xxxxxxx>

Xen-devel mailing list