From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: New DMAR errors in Xen 4.1
Date: Tue, 06 Apr 2010 15:38:17 -0700 [thread overview]
Message-ID: <4BBBB7D9.20709@goop.org> (raw)
I'm seeing DMAR errors with current Xen-unstable, which weren't there in
-rc8 (-rc9?):
type=1403 audit(1270593095.214:3): policy loaded auid=4294967295 ses=4294967295
(XEN) [VT-D]iommu.c:821: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:796: DMAR:[DMA Write] Request device [00:1f.2] fault addr bf57b000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83013fff3e80 bdf = 0:1f.2 gmfn = bf57b
(XEN) root_entry = ffff83013ff36000
(XEN) root_entry[0] = 13c6bb001
(XEN) context = ffff83013c6bb000
(XEN) context[fa] = 2_13fec4001
(XEN) l4 = ffff83013fec4000
(XEN) l4_index = 0
(XEN) l4[0] = 13fec1003
(XEN) l3 = ffff83013fec1000
(XEN) l3_index = 2
(XEN) l3[2] = 13ccbe003
(XEN) l2 = ffff83013ccbe000
(XEN) l2_index = 1fa
(XEN) l2[1fa] = 13cac3003
(XEN) l1 = ffff83013cac3000
(XEN) l1_index = 17b
(XEN) l1[17b] = 0
(XEN) l1[17b] not present
(XEN) [VT-D]iommu.c:796: DMAR:[DMA Write] Request device [00:1f.2] fault addr bf57a000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83013fff3e80 bdf = 0:1f.2 gmfn = bf57a
(XEN) root_entry = ffff83013ff36000
(XEN) root_entry[0] = 13c6bb001
(XEN) context = ffff83013c6bb000
(XEN) context[fa] = 2_13fec4001
(XEN) l4 = ffff83013fec4000
(XEN) l4_index = 0
(XEN) l4[0] = 13fec1003
(XEN) l3 = ffff83013fec1000
(XEN) l3_index = 2
(XEN) l3[2] = 13ccbe003
(XEN) l2 = ffff83013ccbe000
(XEN) l2_index = 1fa
(XEN) l2[1fa] = 13cac3003
(XEN) l1 = ffff83013cac3000
(XEN) l1_index = 17a
(XEN) l1[17a] = 0
(XEN) l1[17a] not present
Device 0:1f.2 is my SATA controller. I haven't tried bisecting it or
anything yet; I don't see any recent changes which are obviously
relevant though.
J
next reply other threads:[~2010-04-06 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:38 Jeremy Fitzhardinge [this message]
2010-04-07 0:00 ` New DMAR errors in Xen 4.1 Jeremy Fitzhardinge
2010-04-07 2:50 ` Weidong Han
2010-04-07 8:31 ` Cui, Dexuan
2010-04-07 16:55 ` Jeremy Fitzhardinge
2010-04-08 2:32 ` Weidong Han
2010-04-08 16:58 ` Jeremy Fitzhardinge
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=4BBBB7D9.20709@goop.org \
--to=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--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.