From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Re: BUG: unable to handle kernel paging request at
	ffff8803bb6ad000
Date: Mon, 10 Oct 2011 12:49:20 -0400
Message-ID: <20111010164920.GA30351@phenom.oracle.com>
References: <1316524835.4122.8.camel@deadeye>
	<1316526058.3891.65.camel@zakaz.uk.xensource.com>
	<20110922190018.GA16678@phenom.oracle.com>
	<20111001025030.GA5198@elie.sbx02827.chicail.wayport.net>
	<CA+rvmvLkBVseDCKyfbd_mGSCrRUvov5Km_2Uoo6CZPZOG7ybvA@mail.gmail.com>
	<1317460798.11991.2.camel@dagon.hellion.org.uk>
	<CA+rvmv+yU0=nEuvLSqkE44RFqeaQw504MkD-sxjXV3D3nkme_g@mail.gmail.com>
	<20111003184722.GB15608@phenom.oracle.com>
	<1317667984.11991.6.camel@dagon.hellion.org.uk>
	<CA+rvmvJ_i4Ta+GV5PQ0U7+2yPxT2oJXtnE_fq0j8Faa7GcUxqw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <CA+rvmvJ_i4Ta+GV5PQ0U7+2yPxT2oJXtnE_fq0j8Faa7GcUxqw@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: rush <rush1503@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, 642154@bugs.debian.org, xen-devel <xen-devel@lists.xensource.com>, Ben Hutchings <ben@decadent.org.uk>, Ian Campbell <ijc@hellion.org.uk>
List-Id: xen-devel@lists.xenproject.org

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>