From: Robert Hancock <hancockrwd@gmail.com>
To: Don Dutile <ddutile@redhat.com>
Cc: Jason Gao <pkill.2012@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, kvm <kvm@vger.kernel.org>
Subject: Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
Date: Sat, 15 Dec 2012 16:16:59 -0600 [thread overview]
Message-ID: <50CCF6DB.7080204@gmail.com> (raw)
In-Reply-To: <50CB9ADC.2020103@redhat.com>
On 12/14/2012 03:32 PM, Don Dutile wrote:
> On 12/13/2012 04:50 AM, Jason Gao wrote:
>> Dear List:
>>
>> Description of problem:
>> After installed Centos 6.3(RHEL6.3) on my Dell R710(lastest
>> bios:Version: 6.3.0,Release Date: 07/24/2012) server,and updated
>> lastest kernel "2.6.32-279.14.1.el6.x86_64",I want to use the Intel
>> 82576 ET Dual Port nic's SR-IOV feature,assigning VFs to kvm guest
>>
>> appended kernel boot parameter: intel_iommu=on,after boot with the
>> following messages:
>>
>> Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 2
>> Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0]
>> fault addr ffe65000
>> Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is
>> not set
>> Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 102
>> Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0]
>> fault addr ffe8a000
>> Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is
>> not set
>> Dec 13 16:58:15 2 kernel: scsi 0:0:32:0: Enclosure DP
>> BACKPLANE 1.07 PQ: 0 ANSI: 5
>> Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 202
>> Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0]
>> fault addr ffe89000
>> Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is
>> not set
>>
>> full dmesg detail:
>> http://pastebin.com/BzFQV0jU
>> lspci -vvv full detail:
>> http://pastebin.com/9rP2d1br
>>
>>
>> it's a production server,and I'm not sure if this is a critical
>> problem,how to fix it,any help would be greatly appreciated.
>
> DMAR table does not have an entry for this device to this region.
> Once the driver reconfigs/resets the device to stop polling bios-boot
> cmd rings and use (new) OS (dma-mapped) rings, there's a period of time
> during this transition that the hw is babbling away to an area that is no
> longer mapped.
Maybe some kind of boot PCI quirk is needed to stop the device DMA
activity before enabling the IOMMU?
next prev parent reply other threads:[~2012-12-15 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 9:50 DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu Jason Gao
2012-12-13 16:23 ` Alex Williamson
2012-12-14 2:01 ` Jason Gao
2012-12-14 4:45 ` Alex Williamson
2012-12-14 6:56 ` Jason Gao
2012-12-14 7:00 ` Jason Gao
2012-12-14 21:54 ` Don Dutile
2012-12-15 8:18 ` Jason Gao
2012-12-14 21:55 ` Don Dutile
2012-12-15 8:25 ` Jason Gao
2012-12-14 21:32 ` Don Dutile
2012-12-15 22:16 ` Robert Hancock [this message]
2012-12-17 16:27 ` Don Dutile
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=50CCF6DB.7080204@gmail.com \
--to=hancockrwd@gmail.com \
--cc=ddutile@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pkill.2012@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).