From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: collecting info on platforms with VT-d BIOS problems
Date: Sat, 23 Jan 2010 00:09:26 -0800 (PST) [thread overview]
Message-ID: <27284201.post@talk.nabble.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D530C8A3D08@orsmsx505.amr.corp.intel.com>
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 = 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 = 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.
Kay, Allen M wrote:
>
> We would like to collect information on platforms that have problem with
> VT-d PCI device passthrough using non-IGD PCI devices. Note that IGD
> (integrated display device) device passthrough code is still being worked
> on.
>
> If you have encountered VT-d problems on a particular platform using
> latest xen-unstable, please provide the following information so that we
> can work with OEM's to get their BIOS's fixed:
>
> (a) Platform details (OEM, Product/Model#, Other identifying info)
> (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
>
> Thanks!
>
> Allen
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
--
View this message in context: http://old.nabble.com/collecting-info-on-platforms-with-VT-d-BIOS-problems-tp27281966p27284201.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-01-23 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 0:22 collecting info on platforms with VT-d BIOS problems Kay, Allen M
2010-01-23 8:09 ` Fantu [this message]
2010-01-23 13:11 ` Pasi Kärkkäinen
2010-01-25 15:25 ` Andrew Oakley
2010-01-25 16:35 ` Sander Eikelenboom
2010-02-01 13:04 ` Andrew Oakley
2010-01-25 15:59 ` Christian Tramnitz
2010-01-25 16:26 ` Sander Eikelenboom
2010-03-29 7:20 ` collecting info on platforms with VT-d BIOS problems / Supermicro X7SB4 Pasi Kärkkäinen
-- strict thread matches above, loose matches on Subject: below --
2010-01-29 1:26 collecting info on platforms with VT-d BIOS problems Mark Hurenkamp
2010-01-29 21:56 Mark Hurenkamp
2010-01-30 21:57 Mark Hurenkamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27284201.post@talk.nabble.com \
--to=fantonifabio@tiscali.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.