WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: BUG: unable to handle kernel paging request at ffff8

To: rush <rush1503@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: BUG: unable to handle kernel paging request at ffff8803bb6ad000
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 10 Oct 2011 12:49:20 -0400
Cc: Jonathan Nieder <jrnieder@xxxxxxxxx>, 642154@xxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ben Hutchings <ben@xxxxxxxxxxxxxxx>, Ian Campbell <ijc@xxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Oct 2011 10:04:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA+rvmvJ_i4Ta+GV5PQ0U7+2yPxT2oJXtnE_fq0j8Faa7GcUxqw@xxxxxxxxxxxxxx>
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: <1316524835.4122.8.camel@deadeye> <1316526058.3891.65.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110922190018.GA16678@xxxxxxxxxxxxxxxxx> <20111001025030.GA5198@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CA+rvmvLkBVseDCKyfbd_mGSCrRUvov5Km_2Uoo6CZPZOG7ybvA@xxxxxxxxxxxxxx> <1317460798.11991.2.camel@xxxxxxxxxxxxxxxxxxxx> <CA+rvmv+yU0=nEuvLSqkE44RFqeaQw504MkD-sxjXV3D3nkme_g@xxxxxxxxxxxxxx> <20111003184722.GB15608@xxxxxxxxxxxxxxxxx> <1317667984.11991.6.camel@xxxxxxxxxxxxxxxxxxxx> <CA+rvmvJ_i4Ta+GV5PQ0U7+2yPxT2oJXtnE_fq0j8Faa7GcUxqw@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Sat, Oct 08, 2011 at 10:13:14AM +0400, rush wrote:
> OK, I tried it again, but Oops didn't gone.
.. snip..
>         echo    'Loading Xen 4.0-amd64 ...'
>         multiboot       /boot/xen-4.0-amd64.gz placeholder xsave=0
.. snip..
> Was it right?

Yup. I think.. this is a bit embarrassing. It took a bit of time for Intel
folks to get the xsave part right and I remember seeing this error about a
year ago with xsave on a Dell Optiplex 780. Hence I wonder if the fixes that
ultimately went in 4.1.1 did not get ported over to 4.0 and you are just
hitting that.

Can I ask you to do one more thing? Can you upgrade to the xen-4.1.1 in
the testing and try with the xsave (or without) and see if it works?

<holds his fingers hoping it is the xsave feature>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel