WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.1 rc5 outstanding bugs
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 21 Feb 2011 11:05:13 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 21 Feb 2011 03:08:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D6231130200007800032E18@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.DEB.2.00.1102181836520.2826@kaball-desktop> <4D6231130200007800032E18@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
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.

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