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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home