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 11:17:06 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 20 Sep 2010 11:17:38 -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=L08xHbiUK5p8UP0OjNUU2K4VYuBMtMoko6N1iWp0UHo=; b=nrfkjqijUNbxujKzLK4TSX0421S3E7XUfVOHVKwWEO6L29hh+cNjucQWAmZOFyZHyA 46NT5+Bi9m/+VVXx70bKuqPzfS3YwRZ1k8RmTmtNz/fLkRY5e8fO8Kh0dePdROhQA1Hq cLhdTSzkUaBiLl+rlp1ZuDOb+TMluJJW8Rp2g=
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=lf0RcuPpZe4NPTwkFL2hIOHbOKhB789gfmtnCDLyXZAKeeyDMDgnju5zgDP9kGVOdu M+7PmWezVNX35X0J9LrM5gIRr28HVjUvQ/qAHazhuCP9cUPUXyGbugphxsTBD9TEvbfL MKvYNgfjI27cLL0bceyJOcBLuBxnXweH+0pFY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100920164017.GF15129@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

-Bruce

>
>> I thought perhaps it looked like a problem with the pciback driver.
>
> Doubtfull. The pciback/pcifront only do the initial part of relaying pci conf
> read/writes.
>>
>> -Bruce
>>
>> _______________________________________________
>> 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