Re: [Xen-devel] Xen 4.1 rc5 outstanding bugs

["Jan Beulich" <JBeulich@xxxxxxxxxx>]

>>> On 21.02.11 at 12:05, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
wrote:
> On Mon, 21 Feb 2011, Jan Beulich wrote:
>> >>> On 18.02.11 at 19:59, Stefano Stabellini 
>> >>> <stefano.stabellini@xxxxxxxxxxxxx> 
> wrote:
>> >  *  Xen panic on guest shutdown with PCI Passthrough
>> > 
> http://xen.1045712.n5.nabble.com/Xen-panic-on-guest-shutdown-with-PCI-Passthrough-tt
>  
> 
>> > 3371337.html#none
>> > When the guest with a passthrough pci device is shut down, Xen panic
>> > on a NMI - MEMORY ERROR.
>> > (XEN) Xen call trace:
>> > (XEN)    [<ffff82c48015f032>] msi_set_mask_bit+0xea/0x121
>> > (XEN)    [<ffff82c48015f087>] mask_msi_irq+0xe/0x10
>> > (XEN)    [<ffff82c480162fb1>] __pirq_guest_unbind+0x298/0x2aa
>> > (XEN)    [<ffff82c48016315c>] unmap_domain_pirq+0x199/0x307
>> > (XEN)    [<ffff82c480163321>] free_domain_pirqs+0x57/0x83
>> > (XEN)    [<ffff82c48015642a>] arch_domain_destroy+0x30/0x2e3
>> > (XEN)    [<ffff82c480104c59>] complete_domain_destroy+0x6e/0x12a
>> > (XEN)    [<ffff82c48012adfd>] rcu_process_callbacks+0x173/0x1e1
>> > (XEN)    [<ffff82c480123327>] __do_softirq+0x88/0x99
>> > (XEN)    [<ffff82c4801233a2>] do_softirq+0x6a/0x7a
>> 
>> Are you sure you want to consider this one severe? Xen by itself
>> can't cause NMIs (unless sending IPIs as such, which certainly isn't
>> the case here), and iirc from the mailing list post corresponding to
>> this it's being observed only on a single (with the above presumably
>> buggy) system.
>  
> Good point. We should have another identical machine, we'll try to
> reproduce it there.

Another identical machine may have the same problem (if its a
design flaw rather than broken hardware) - reproducing on a
different machine would be of much more interest.

Jan


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