linux-kernel - Re: next-20130709 DMAR issues

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <51E35F31.1040709@hp.com>
Date:	Mon, 15 Jul 2013 10:32:17 +0800
From:	"Li, Zhen-Hua" <zhen-hual@...com>
To:	Joerg Roedel <joro@...tes.org>
CC:	Ingo Molnar <mingo@...nel.org>,
	Valdis Kletnieks <Valdis.Kletnieks@...edu>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: next-20130709 DMAR issues

I have met a bug with the same error message, its cause was that the bios
did not allocate RMRR/DRHD(can't remember which one) for the device.

Thanks
ZhenHua

On 07/12/2013 10:31 PM, Joerg Roedel wrote:
> Thanks for the heads-up, Ingo.
>
> On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
>>> Jul 10 12:20:19 turing-police kernel: [    0.021583] DMAR:[fault reason 06] PTE Read access is not set
>>>
>>> Now I have 3 extra messages talking about handling a fault status.  lspci says 00:1f.2 is:
>>>
>>> 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
> This could be caused by some change in the SATA driver stack. Maybe a
> DMA buffer is used after unmap or something.
>
>
>>> If this doesn't ring any bells, I'l go do the bisect thing...
> Yes, a bisection would help here, thanks for doing this.
>
>
> 	Joerg
>
>
> .
>

--
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/