[Top] [All Lists]

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

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

To: Bruce Edge <bruce.edge@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 16 Sep 2010 08:53:02 +0100
Cc:
Delivery-date: Thu, 16 Sep 2010 00:53:58 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: ActVMMRW7faNzSqfTEOymXyvt2E0cgAQ2urR
Thread-topic: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT

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

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

Follow-Ups:
- Re: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
  - From: Bruce Edge

References:
- [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
  - From: Bruce Edge

Prev by Date: Re: [Xen-devel] Re: [PATCH] linux/netback: save interrupt state in add_to_net_schedule_list_tail
Next by Date: [Xen-devel] how to keep time of windows pvhvm synchronized with host after resuming
Previous by thread: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
Next by thread: Re: [Xen-devel] xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
Index(es):
- Date
- Thread

Rackspace

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