From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0 Date: Thu, 01 Sep 2011 15:42:31 -0700 Message-ID: <4E600A57.9040208@goop.org> References: <4E4D9A90.30800@leuphana.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: M A Young Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 09/01/2011 02:29 PM, M A Young wrote: > On Wed, 31 Aug 2011, M A Young wrote: > >> On Fri, 19 Aug 2011, Andreas Olsowski wrote: >> >>> Source: >>> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git >>> >>> Tested branches: >>> xen/stable-2.6.32.x >>> xen/next-2.6.32.x >>> >>> When trying to boot the current kernel bare-metal it will not load >>> properly, instead i am prompted with: >>> >>> panic early exception 0e rip 10:0 error 10 cr2 0 >> >> I am seeing this as well. I have been trying to narrow it down a bit, >> and it seems to me that the bug was introduced somewhere between >> xen-2.6.32.39 and xen-2.6.32.42. > > xen-2.6.32.40 also crashes. I think that means that it is either > commits c3dd7941354fa96a71f2613e2c7a1b215fa175dc or > 280802657fb95c52bb5a35d43fea60351883b2af (or something in the stable > kernel or else compile differences though both are unlikely). I am > still working on this to confirm which patch it is. 280802657fb95c5 is unlikely - that's just a blkback change. c3dd7941354fa96 looks plausible. J