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

[Xen-devel] XEN Panic with VT-d support enabled on Xeon E55xx platform

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] XEN Panic with VT-d support enabled on Xeon E55xx platform
From: "Isabelle, Francois" <Francois.Isabelle@xxxxxxxxxxxxxx>
Date: Mon, 6 Apr 2009 11:52:15 -0400
Delivery-date: Mon, 06 Apr 2009 08:52:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acm2z6gztVOOcs5kTD+lkXTqdNsV0w==
Thread-topic: XEN Panic with VT-d support enabled on Xeon E55xx platform
Hi all,

I'm working with a board on which XEN panics with the following message (see 
below). From what I can see on the lists, most of the problems on these 
platforms seem to be related to broken DMAR tables and RMRR, but this platform 
passes the VT-d firmware toolkit (http://edc.intel.com/Platforms/Xeon-5500/) 
successfully so I'm tented to blame XEN for it... should I file a bug entry?

>From what I can see in the 'queue invalidation' code, a timeout is reached. As 
>anyone seen this on a similar platform? 


(XEN) Xen version 3.4-unstable (root@localdomain) (gcc version 4.1.2 20080704 
(Red Hat 4.1.2-44)) Fri Apr  3 14:20:00 EDT 2009
(XEN) Latest ChangeSet: Mon Mar 30 16:48:26 2009 +0100 19433:d5ddc782bc49
(XEN) Command line: console=com1 com1=115200,8n1  iommu=1 loglvl=all 
loglvl_guest=all ro

..
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000
(XEN) [VT-D]dmar.c:485: Host address width 39
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:306: found IOAPIC: bdf = f0:1f.7
(XEN) [VT-D]dmar.c:358: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:502: found ACPI_DMAR_ATSR
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:3.0  sec = 5  sub = 5
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:4.0  sec = 6  sub = e
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:5.0  sec = 3  sub = 3
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:7.0  sec = 18  sub = 18
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:8.0  sec = f  sub = 17
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:9.0  sec = 4  sub = 4
(XEN) [VT-D]dmar.c:287: found bridge: bdf = 0:a.0  sec = 2  sub = 2
..
(XEN) Intel VT-d Snoop Control supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation supported.
(XEN) Intel VT-d Interrupt Remapping supported.
(XEN) DMAR_IQA_REG = 7f79d000
(XEN) DMAR_IQH_REG = 0
(XEN) DMAR_IQT_REG = 20
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) queue invalidate wait descriptor was not executed
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...

François Isabelle

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