From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fantu Subject: Re: collecting info on platforms with VT-d BIOS problems Date: Sat, 23 Jan 2010 00:09:26 -0800 (PST) Message-ID: <27284201.post@talk.nabble.com> References: <987664A83D2D224EAE907B061CE93D530C8A3D08@orsmsx505.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <987664A83D2D224EAE907B061CE93D530C8A3D08@orsmsx505.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Motherboard Asus P6T SE with last bios (0704) on xen-unstable with kernel 2.6.31.6 pv_ops (XEN) [VT-D]dmar.c:548: Host address width 39 (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:374: dmaru->address =3D fbfff000 (XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0 (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:374: dmaru->address =3D fbffe000 (XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7 (XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0 (XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1 (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2 (XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7 (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0 (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1 (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2 (XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7 (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address bf7dbfff (XEN) Failed to parse ACPI DMAR. Disabling VT-d.=20 Kay, Allen M wrote: >=20 > We would like to collect information on platforms that have problem with > VT-d PCI device passthrough using non-IGD PCI devices. =C2=A0Note that IG= D > (integrated display device) device passthrough code is still being worked > on. >=20 > If you have encountered =C2=A0VT-d problems on a particular platform usin= g > latest xen-unstable, please provide the following information so that we > can work with OEM's to get their BIOS's fixed: >=20 > (a) Platform details (OEM, Product/Model#,=C2=A0 Other identifying in= fo) > (b) BIOS version/number > (c) Version of Xen with which failure is seen (if not the latest > xen-unstable) > (d) Specific error/failure details such as serial log >=20 > Thanks! >=20 > Allen >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20 >=20 --=20 View this message in context: http://old.nabble.com/collecting-info-on-plat= forms-with-VT-d-BIOS-problems-tp27281966p27284201.html Sent from the Xen - Dev mailing list archive at Nabble.com.