Xen project Mailing List

Re: [Xen-devel] Xen 4.0 crashes with pvops kernel

To: Cris Daniluk <cris.daniluk@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>

Date: Tue, 15 Jun 2010 09:18:32 -0700 (PDT)

Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Tue, 15 Jun 2010 09:19:22 -0700

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=sCIHfJ84RGGAWQEAvI74EjNGBwQJzVHP6uvEkv6PXsViSRvyX13Jzk/ofzHTHwtdatvERs1obsj4kwHYkRhVXNenkZHxnVc8zUtIL9V4zpazJusFx3nb/bkFsKdd9jZg4Qmath8FvT9ctQruSVHRNcP4MkiCDOclkpLf6G3/azs=;

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

There was an old issue with 2.6.32.10 pvops under Xen 4.0 on ASUS P5Q-E board
ACPI dumped SSDT and DSDT tables ( as requested today), serial log were submitted by myself to Yu Ke and Jeremy was aware of this issue.
I still don't activate acpi_processor (Yu Ke) for 2.6.32.15 under Xen 4.0.1-rc3-pre
for any pvops 2.6.32.X gets loaded on this board. Very simple solution. But issue stays
unresolved at least to my knowledge. Same software works fine on ASUS P5Q3 with
acpi_processor hard linked to pvops kernel 2.6.32.X (10 - 15 )

Boris.

--- On Tue, 6/15/10, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:

From: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0 crashes with pvops kernel
To: "Cris Daniluk" <cris.daniluk@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, June 15, 2010, 11:21 AM

>>> On 15.06.10 at 17:01, Cris Daniluk <cris.daniluk@xxxxxxxxx> wrote:
> On Tue, Jun 15, 2010 at 10:58 AM, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>>> On 15.06.10 at 16:35, Cris Daniluk <cris.daniluk@xxxxxxxxx> wrote:
>>> Hmm, so could there be a Xen-based workaround in the interim, such as
>>> bypassing the code page that is triggering this? It seems like that
>>> may not provide too much relief given the nature of the issue.
>>
>> Unfortunately I can't think of anything.
>>
>> Jan
>>
>
> Fair enough. I will see if I can get some other hardware to test with.
> What would the path toward resolution be here? It still seems like Xen
> shouldn't be writing into that page, let alone reading..

I can't think of anything but getting the BIOS fixed, plus getting
handling in proper shape in the kernel.

Jan

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

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