linux-kernel - Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4EC1EB39.1080705@gmail.com>
Date:	Mon, 14 Nov 2011 22:31:53 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Arnd Hannemann <arnd@...dnet.de>
CC:	linux-kernel@...r.kernel.org, dwmw2@...radead.org,
	iommu@...ts.linux-foundation.org
Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2

On 11/14/2011 06:53 PM, Arnd Hannemann wrote:
> Hi,
>
> Am 14.11.2011 23:33, schrieb Arnd Hannemann:
>
>> when trying to boot kernel 3.2rc1 on my thinkpad t510 I get an endless loop of errors:
>>
>>   DRHD: handling fault status reg 2
>>   DMAR: [DMA Read] Request device [0d:00.0] fault addr fffff000
>>   DMAR: [fault reason 02] Present bit in context entry is clear
>>
>> screenshot can be found here:
>> http://arndnet.de/lkml/screenshot3.2rc1.jpg
>>
>> kernel 3.1.1 is booting up flawlessly.
>
> I must have inadvertently enabled CONFIG_INTEL_IOMMU_DEFAULT_ON in my config
> for 3.2-rc1.
>
> With disabled CONFIG_INTEL_IOMMU_DEFAULT_ON my thinkpad boots up again.
> Not sure if this is expected?

No, that's not supposed to happen. Can you post the output of "lspci 
-vv"? Apparently that device 0d:00.0 is generating unexpected DMA 
accesses for some reason.
--
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/