[Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Andreas Olsowski]

[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]

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

at the bottom line of the screen.

Here is a screenshot:
http://imageshack.us/photo/my-images/10/crashtm.png/



System is:
Dell PE2950 (Xeon L5335, Intel 5000 chipset)
Debian 6.0.2 squeeze(stable)
grub 1.98+20100804-14

Kernel .config:
http://pastebin.com/bQAyC30i

It has been derived from the example configurations on 
"http://wiki.xensource.com/xenwiki/XenParavirtOps".


The kernel boots loads fine as dom0 under Xen 4.1.1


Though i know this kernel tree is intended to be a dom0 kernel, it 
should still be bootable bare-metal or am i mistaken?

It worked previously, allthough i am unable to tell what the latest 
working version was.


with best regards
-- 
Andreas Olsowski


[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 5144 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Eric Camachat]

On Thu, Aug 18, 2011 at 4:04 PM, Andreas Olsowski
<andreas.olsowski@leuphana.de> 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
>
-- snip --

I have this problem too.
Not only occurs on bare metal but also on HVM and QEMU.

I faced some mmap() issues (see previous discuss in this list), and
try to use xen.git's kernel instead of generic one.
Right now, the xen.git's cannot boot even on bare metal! I have to
find out the other way to put our servers into XEN.

/Eric

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Jeremy Fitzhardinge]

On 08/18/2011 04:04 PM, 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
>
> at the bottom line of the screen.
>
> Here is a screenshot:
> http://imageshack.us/photo/my-images/10/crashtm.png/
>
>
>
> System is:
> Dell PE2950 (Xeon L5335, Intel 5000 chipset)
> Debian 6.0.2 squeeze(stable)
> grub 1.98+20100804-14
>
> Kernel .config:
> http://pastebin.com/bQAyC30i
>
> It has been derived from the example configurations on
> "http://wiki.xensource.com/xenwiki/XenParavirtOps".
>
>
> The kernel boots loads fine as dom0 under Xen 4.1.1
>
>
> Though i know this kernel tree is intended to be a dom0 kernel, it
> should still be bootable bare-metal or am i mistaken?

It is supposed to still work as a native/hvm guest.

What was the last kernel version which worked?

    J

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Konrad Rzeszutek Wilk]

On Fri, Aug 19, 2011 at 01:04:48AM +0200, 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
> 
> at the bottom line of the screen.
> 
> Here is a screenshot:
> http://imageshack.us/photo/my-images/10/crashtm.png/
> 
> 
> 
> System is:
> Dell PE2950 (Xeon L5335, Intel 5000 chipset)
> Debian 6.0.2 squeeze(stable)
> grub 1.98+20100804-14
> 
> Kernel .config:
> http://pastebin.com/bQAyC30i
> 
> It has been derived from the example configurations on
> "http://wiki.xensource.com/xenwiki/XenParavirtOps".
> 
> 
> The kernel boots loads fine as dom0 under Xen 4.1.1
> 
> 
> Though i know this kernel tree is intended to be a dom0 kernel, it
> should still be bootable bare-metal or am i mistaken?

It should have been. Not sure what is happening - however the 3.0.x
kernel boots for you as Dom0 and baremetal, right?

> 
> It worked previously, allthough i am unable to tell what the latest
> working version was.

OK. I don't think we are going to look at this in much detail unless
you have some bisection numbers.

The upstream 3.x kernels are our main focus - to make sure they work
properly and we haven't really focused much on the 2.6.32.

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[M A Young]

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.

 	Michael Young

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Andreas Olsowski]

[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]


> 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.
Sounds realistic, i did test 42-45.
I will try to find the time to narrow it down to one exact version this 
weekend.



-- 
Andreas Olsowski
Leuphana Universität Lüneburg
Rechen- und Medienzentrum
Scharnhorststraße 1, C7.015
21335 Lüneburg

Tel: ++49 4131 677 1309


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[M A Young]

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.

 	Michael Young

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Jeremy Fitzhardinge]

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

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[M A Young]

On Thu, 1 Sep 2011, Jeremy Fitzhardinge wrote:

> 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.

Yes, xen-2.6.32.40 with c3dd7941354fa96a71f2613e2c7a1b215fa175dc reverted 
will boot on bare metal.

 	Michael Young

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Konrad Rzeszutek Wilk]

On Fri, Sep 02, 2011 at 12:44:31AM +0100, M A Young wrote:
> 
> 
> On Thu, 1 Sep 2011, Jeremy Fitzhardinge wrote:
> 
> >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.
> 
> Yes, xen-2.6.32.40 with c3dd7941354fa96a71f2613e2c7a1b215fa175dc
> reverted will boot on bare metal.

<smacks his head> bare metal. Yes, it won't work under that - at least
not in that state.

Jeremy, can you revert that patch please - it was fixing one instance
of machines - and it looks to be breaking many more.

Grrrrrr

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Jeremy Fitzhardinge]

On 09/02/2011 06:37 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 02, 2011 at 12:44:31AM +0100, M A Young wrote:
>>
>> On Thu, 1 Sep 2011, Jeremy Fitzhardinge wrote:
>>
>>> 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.
>> Yes, xen-2.6.32.40 with c3dd7941354fa96a71f2613e2c7a1b215fa175dc
>> reverted will boot on bare metal.
> <smacks his head> bare metal. Yes, it won't work under that - at least
> not in that state.
>
> Jeremy, can you revert that patch please - it was fixing one instance
> of machines - and it looks to be breaking many more.

Done.  Unfortunately I can't push it because kernel.org is still out.

    J

Re: [Xen-deve] xen/stable-2.6.32.x bare-metal: panic early exception 0e rip 10:0 error 10 cr2 0

[Konrad Rzeszutek Wilk]

On Thu, Sep 01, 2011 at 03:42:31PM -0700, Jeremy Fitzhardinge wrote:
> 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.

There was a patch on top of it - that made it work under PV.
<sigh>