|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] New DMAR errors in Xen 4.1
Jeremy Fitzhardinge wrote:
On 04/06/2010 03:38 PM, Jeremy Fitzhardinge wrote:
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.
It turns out its... "Enable debug=y by default in the build." So I
guess these errors have been happening silently thus far?
J
I don't encounter this issue. These DMAR fault messages will be printed
even when debug=n. what platform are you using? could you post complete
booting log with "iommu=verbose"?
Regards,
Weidong
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|