From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Zhao, Yu" Subject: Re: XEN Panic with VT-d support enabled on Xeon E55xx platform Date: Tue, 07 Apr 2009 10:31:25 +0800 Message-ID: <49DABAFD.4070301@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Isabelle, Francois" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Hi Francois, Do you have this problem all the times? Can you please grab some logs=20 and send them to me? The dmesg from a native kernel if you can't boot up=20 any version of Xen, and the whole Xen hypervisor log would help us to=20 figure out the problem. Thanks, Yu Isabelle, Francois wrote: > Hi all, >=20 > 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 t= hese platforms seem to be related to broken DMAR tables and RMRR, but thi= s platform passes the VT-d firmware toolkit (http://edc.intel.com/Platfor= ms/Xeon-5500/) successfully so I'm tented to blame XEN for it... should I= file a bug entry? >=20 >>>From what I can see in the 'queue invalidation' code, a timeout is reac= hed. As anyone seen this on a similar platform?=20 >=20 >=20 > (XEN) Xen version 3.4-unstable (root@localdomain) (gcc version 4.1.2 20= 080704 (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:d5ddc782bc= 49 > (XEN) Command line: console=3Dcom1 com1=3D115200,8n1 iommu=3D1 loglvl=3D= all loglvl_guest=3Dall ro >=20 > .. > (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 =3D fbffe000 > (XEN) [VT-D]dmar.c:306: found IOAPIC: bdf =3D 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 =3D 0:1d.0 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.1 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.2 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.7 > (XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.0 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.1 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.2 > (XEN) [VT-D]dmar.c:300: found endpoint: bdf =3D 0:1d.7 > (XEN) [VT-D]dmar.c:502: found ACPI_DMAR_ATSR > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:3.0 sec =3D 5 sub =3D= 5 > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:4.0 sec =3D 6 sub =3D= e > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:5.0 sec =3D 3 sub =3D= 3 > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:7.0 sec =3D 18 sub =3D= 18 > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:8.0 sec =3D f sub =3D= 17 > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:9.0 sec =3D 4 sub =3D= 4 > (XEN) [VT-D]dmar.c:287: found bridge: bdf =3D 0:a.0 sec =3D 2 sub =3D= 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 =3D 7f79d000 > (XEN) DMAR_IQH_REG =3D 0 > (XEN) DMAR_IQT_REG =3D 20 > (XEN)=20 > (XEN) **************************************** > (XEN) Panic on CPU 0: > (XEN) queue invalidate wait descriptor was not executed > (XEN) **************************************** > (XEN)=20 > (XEN) Reboot in five seconds... >=20 > Fran=E7ois Isabelle >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel