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

Re: [Xen-devel] Xen panic on guest shutdown with PCI Passthrough


  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
  • Date: Mon, 7 Feb 2011 15:06:17 +0000
  • Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 07 Feb 2011 07:07:55 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=eP5wK/zhm8VQQrvTtRtPuQ7xPZJSyOhW5w+ri/CjP30r8xE2qpVt/lVL+Ov4O3WrKG JGkbVU881ctt7aebHFvF9LfK0gMkhuCVmuz2/Ct8ppKP9EukfsS0HdnfPjGruv1N365a 6HfOQfN7FJMm37lyC3BPawcpuow2c7SbgE7n0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Mon, Feb 7, 2011 at 09:27, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:
>>>> On 04.02.11 at 17:34, Anthony PERARD <anthony.perard@xxxxxxxxxx> wrote:
>> Hi,
>>
>> Each time I shutdown a guest with a passthrough pci device, Xen panic
>> on a NMI - MEMORY ERROR.
>
> And this happening in msi_set_mask_bit() is consistent? Always at
> the same RIP, or (slightly) varying? If always at the same address,
> could you disassemble the respective instruction so we know what
> address is being read/written?

Unfortunately, this error happened in many place, even in default_idle.

Maybe this can help:
(XEN) irq.c:1585: dom1: forcing unbind of pirq 16
(XEN) irq.c:1585: dom1: forcing unbind of pirq 54
the error happened just after these debug print.

> And quite certainly only on one (type of) machine?

Yes, only one machine, I didn't try on other machine.

-- 
Anthony

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


 


Rackspace

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