All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: collecting info on platforms with VT-d BIOS problems
Date: Mon, 25 Jan 2010 16:59:11 +0100	[thread overview]
Message-ID: <hjkf4p$3ph$4@ger.gmane.org> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D530C8A3D08@orsmsx505.amr.corp.intel.com>

Hi Allen,

thanks for taking care of this!
You may already know those two (we have been in contact regarding the 
P6T before, you provided me a beta bios that worked around this):


1)
(a) Asus P6T Deluxe
(b) all (except you provided beta BIOS) including latest 1904
(c) all (even with iommu_include_reserved)
(d) xm dmesg shows:
(XEN) Command line: dom0_mem=1024M iommu=1 iommu_include_reserved=1
...
(XEN) [VT-D]dmar.c:473: Host address width 39
(XEN) [VT-D]dmar.c:482: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:337: dmaru->address = fbfff000
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:482: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:337: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:294: found IOAPIC: bdf = f0:1f.7
(XEN) [VT-D]dmar.c:294: found IOAPIC: bdf = 0:13.0
(XEN) [VT-D]dmar.c:346: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:486: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.0
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.1
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.2
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1d.7
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:288: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:486: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:376: RMRR error: base_addr bf7dc000 end_address bf7dbfff
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.



2)
(a) Asus P5E-VM DO
(b) 0702 (latest)
(c) all (even with iommu_include_reserved)
(d) as soon as the IGD is disabled in the BIOS "xm dmesg" shows:
(XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000
(XEN) [VT-D]dmar.c:485: Host address width 36
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed90000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1b.0
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:3.3
(XEN) [VT-D]dmar.c:494: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:349: dmaru->address = fed93000
(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:300: found endpoint: bdf = 0:1a.0
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.1
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.2
(XEN) [VT-D]dmar.c:300: found endpoint: bdf = 0:1a.7
(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:388: RMRR error: base_addr d0000000 end_address cfffffff
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.

  parent reply	other threads:[~2010-01-25 15:59 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
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 [this message]
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='hjkf4p$3ph$4@ger.gmane.org' \
    --to=chris.ace@gmx.net \
    --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.