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

[Bruce Edge <bruce.edge@xxxxxxxxx>]

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