From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot Date: Tue, 15 Sep 2009 12:58:15 -0700 Message-ID: <4AAFF1D7.1060100@goop.org> References: <976E8557-F11D-416E-84C2-CD12B180CA1B@rit.edu> <20090915071730.GP31123@reaktio.net> <20090915075613.GQ31123@reaktio.net> <82B3AFF8-B4F1-4347-82F3-04F100002684@rit.edu> <20090915113914.GT31123@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090915113914.GT31123@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Charles Gruener , xen-devel@lists.xensource.com, fedora-xen@redhat.com List-Id: xen-devel@lists.xenproject.org On 09/15/09 04:39, Pasi K=E4rkk=E4inen wrote: >> (XEN) mm.c:1697:d0 Bad L1 flags 800000 >> =20 This looks like something trying to set the NX bit in a mapping, which should be fine on this processor. Could it be disabled in BIOS or something? > Jeremy: More info about the dom0 kernel crash here.. > > -- Pasi > > On Tue, Sep 15, 2009 at 01:25:35PM +0100, M A Young wrote: > =20 >> >=20 >> =20 >>> > > >>> > >gdb vmlinux >>> > >x/i ffffffff81a017f1 >>> =20 >> >=20 >> > That should of course have been >> > (gdb) x/i 0xffffffff81a017f1 >> > 0xffffffff81a017f1 : ud2a >> =20 Hm, OK. Maybe the problem is that we haven't enabled NX in EFER at that early point. I'll cook something up. J