Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access isnot set] Vt-d & intel_iommu
From: Alex Williamson
Date: Thu Dec 13 2012 - 11:23:02 EST
On Thu, 2012-12-13 at 17:50 +0800, 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.
Device 03:00.0 is your raid controller:
03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
For some reason it's trying to read from ffe65000, ffe8a000, ffe89000,
ffe86000, ffe87000, ffe84000. Those are in reserved memory regions, so
it's not reading an OS allocated buffer, which probably means it's some
kind of side-band communication with a management controller. I'd guess
it's a BIOS bug and there should be an RMRR covering those accesses.
Thanks,
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/