linux-kernel - Re: 3.6.8: dmar: DRHD: handling fault status reg 602

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <50B5663D.2020003@gmail.com>
Date:	Tue, 27 Nov 2012 19:17:49 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 3.6.8: dmar: DRHD: handling fault status reg 602

On 11/27/2012 09:16 AM, Justin Piszcz wrote:
> Hello,
>
> Any idea why this is happening (e.g. why is PTE Read Access not set?)
>
> [   13.204560] dmar: DRHD: handling fault status reg 602
> [   13.208078] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
> [   13.208078] DMAR:[fault reason 06] PTE Read access is not set
> [   15.777874] dmar: DRHD: handling fault status reg 702
> [   15.777879] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
> [   15.777879] DMAR:[fault reason 06] PTE Read access is not set
> [   16.100453] dmar: DRHD: handling fault status reg 2
> [   16.100458] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
> [   16.100458] DMAR:[fault reason 06] PTE Read access is not set
> [   16.141058] dmar: DRHD: handling fault status reg 102
> [   16.141062] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
> [   16.141062] DMAR:[fault reason 06] PTE Read access is not set
> [   16.210102] dmar: DRHD: handling fault status reg 202
> [   16.210111] dmar: DMAR:[DMA Read] Request device [04:00.0] fault addr 0
> [   16.210111] DMAR:[fault reason 06] PTE Read access is not set
> [   16.918149] ixgbe 0000:86:00.0: eth2: NIC Link is Up 10 Gbps, Flow
> Control: RX/TX
>
> This is from:
> http://lkml.org/lkml/2012/11/27/263
>
> Justin.
>

 From the dmesg you posted (and some comments on that thread) it might 
have something to do with CONFIG_PCI_MMCONFIG being disabled. If so, try 
enabling that.

Of course the DMAR stuff should be recovering from that more gracefully 
if that's the problem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/