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 dom0 crash: "d0:v0: unhandled page fault (ec=0000)"

To: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
From: Andreas Kinzler <ml-xen-devel@xxxxxx>
Date: Wed, 20 Oct 2010 01:31:15 +0200
Cc: "Alan J. Wylie" <NDA5OWUy@xxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, sven <ml@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 19 Oct 2010 16:32:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1287503143.12843.2191.camel@xxxxxxxxxxxxxxxxxxxxxx>
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>
References: <19629.39326.337589.71778@xxxxxxxxxxx> <1287498599.12843.2111.camel@xxxxxxxxxxxxxxxxxxxxxx> <4CBDB229.3030501@xxxxxxxxxxxxx> <1287503143.12843.2191.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100915 Thunderbird/3.1.4
On 19.10.2010 17:45, Gianni Tedesco wrote:
ditto, I suspected a known bug in my gcc version which broke xchg
because when I compiled with -O2 instead of -Os... the problem went away
but then something else bad happened later (I forget the details, and it
was too many config tweaks ago to get back to last time I had it working
that well)

Jeremy, one user earlier reported that he found out that for him there seems to be a relation between kernel size and crash status. He just added/removed some options that could never influence the "crash status" (like adding/removing netfilter modules). With all the experiences here, is may be useful to check for code paths related to kernel size.

Regards Andreas

Xen-devel mailing list