WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] New DMAR errors in Xen 4.1

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] New DMAR errors in Xen 4.1
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: 2010年4月06日 17:00:13 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: 2010年4月06日 17:01:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BBBB7D9.20709@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BBBB7D9.20709@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] pvgrub boot problems , Jeremy Fitzhardinge
Next by Date: Re: [Xen-devel] Xen 4.0.0-rc7 problem/hang with vt-d DMAR parsing , Weidong Han
Previous by Thread: [Xen-devel] New DMAR errors in Xen 4.1 , Jeremy Fitzhardinge
Next by Thread: Re: [Xen-devel] New DMAR errors in Xen 4.1 , Weidong Han
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /