From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xen-unstable: [error_code=0000] , IN INTERRUPT CONTEXT
Date: Mon, 20 Sep 2010 17:26:42 -0400
Message-ID: <20100920212642.GF26201@dumpdata.com>
References: <AANLkTikr8CMb=g6EHvoVm=j=iEPJ4OoObUTvZ2=K0QUX@mail.gmail.com>
	<C8B78B6E.23224%keir.fraser@eu.citrix.com>
	<AANLkTimwOYomsjmvps_V2Vbvn0SZ-dQ97zvxhHv+kgHR@mail.gmail.com>
	<20100920164017.GF15129@dumpdata.com>
	<AANLkTims1LL-3PL2F7ONUiDiTqhtuqEs2tw_jxmzOtOr@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <AANLkTims1LL-3PL2F7ONUiDiTqhtuqEs2tw_jxmzOtOr@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Bruce Edge <bruce.edge@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Keir Fraser <keir.fraser@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

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@oracle.com> 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@eu.citrix=
.com> wrote:
> >> > On 16/09/2010 00:49, "Bruce Edge" <bruce.edge@gmail.com> 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
> >> >
> >>
> >> 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?
>=20
> 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 Dom=
U'?