WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 20 Sep 2010 14:44:30 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 20 Sep 2010 14:45:04 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VOz3ddpCkljsabJh/aui8nDpQ50stiZIXrMC+BsDP94=; b=Xo5izlp3G8ziqI0y1TlbhNTX0yZycfe0onHR+bZdA6IDQHd8GjLxoDFtgBOfLRdPtM j468sO9dHBoZBByM8hJF+s7koXOhKZ5waDOvQ/mUFHMoAp1WvYWaJulDPkDBIqU2UVDa gnwtTYluA/yY5mS7xJq499oDPlf92+u4TaUNM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vctOJinq8zDtrMjfUjZ4eLftHAUpXiSh1TaYXxjlhV23gCdE8/C1IE6WTmoqBIJcy4 UJjsmhQBJ7PPGRfYc6pQZz0v36sbRpmgLVYtrZB1hKKCAwBuwOKxAtwSqbWyp7ElJMgV cD4pnNQ0MRr0rJJIW4dMuIv5TovMrdbeqiD5c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100920212642.GF26201@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTikr8CMb=g6EHvoVm=j=iEPJ4OoObUTvZ2=K0QUX@xxxxxxxxxxxxxx> <C8B78B6E.23224%keir.fraser@xxxxxxxxxxxxx> <AANLkTimwOYomsjmvps_V2Vbvn0SZ-dQ97zvxhHv+kgHR@xxxxxxxxxxxxxx> <20100920164017.GF15129@xxxxxxxxxxxx> <AANLkTims1LL-3PL2F7ONUiDiTqhtuqEs2tw_jxmzOtOr@xxxxxxxxxxxxxx> <20100920212642.GF26201@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Sep 20, 2010 at 2:26 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> On Mon, Sep 20, 2010 at 11:17:06AM -0700, Bruce Edge wrote:
>> On Mon, Sep 20, 2010 at 9:40 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@xxxxxxxxxx> wrote:
>> > On Thu, Sep 16, 2010 at 07:13:35AM -0700, Bruce Edge wrote:
>> >> On Thu, Sep 16, 2010 at 12:53 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 
>> >> wrote:
>> >> > On 16/09/2010 00:49, "Bruce Edge" <bruce.edge@xxxxxxxxx> wrote:
>> >> >
>> >> >> (XEN)
>> >> >> (XEN)
>> >> >> (XEN) NMI - MEMORY ERROR
>> >> >
>> >> > PCI parity errors, possibly? It looks rather like you are getting an NMI
>> >> > with fatal consequuences.
>> >> >
>> >> >  -- Keir
>> >> >
>> >>
>> >> It seems very odd that a parity error would be so reliably
>> >> recreatable. This also doesn't happen with xen-testing.
>> >
>> > This is irregardless of the PVOPS kernel, right?
>>
>> This does not happen running hvm domU. Only pvops domU kernels have
>> this problem.
>
> Huh? PVOPS DomU kernel can run as HVM or PV. What do you mean by 'HVM DomU'?
>

Sorry, I forget there are so many ways one can run the pvops kernel.

I meant that it didn't happen when I was running an HVM domU using a
different bare-metal kernel. IOW, a non-pvops HVM kernel.

It does happen when I use the pvops kernel in PV mode for the domU.

I have not tried the pvops kernel in hvm mode. I'll try that next.

-Bruce

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