From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT Date: Mon, 20 Sep 2010 12:40:17 -0400 Message-ID: <20100920164017.GF15129@dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bruce Edge Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Thu, Sep 16, 2010 at 07:13:35AM -0700, Bruce Edge wrote: > On Thu, Sep 16, 2010 at 12:53 AM, Keir Fraser wrote: > > On 16/09/2010 00:49, "Bruce Edge" wrote: > > > >> (XEN) > >> (XEN) > >> (XEN) NMI - MEMORY ERROR > > > > PCI parity errors, possibly? It looks rather like you are getting an = NMI > > with fatal consequuences. > > > > =A0-- Keir > > >=20 > 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? > 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. >=20 > -Bruce >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel