[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Bruce Edge <bruce.edge@xxxxxxxxx>
  • Date: Thu, 16 Sep 2010 07:13:35 -0700
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 16 Sep 2010 07:14:30 -0700
  • 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=lBKlD2xHFu8V7ayMJn5OeIURNqibeEvHFgJ/rqQ8V0IwFfmdg07HRPYUt+puF0N+0n gP51y1AaGgfwFXixmWP9qcSCwNbpbe5rELwgNga4buHzKWHcEfW6PZm/48ar3xNmb1ge AijuTfCxRpZ+REYmE22go06rWtsQHluE7ANjc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.
I thought perhaps it looked like a problem with the pciback driver.

-Bruce

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.