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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 15 Nov 2011 07:34:45 +0100
From:	Arnd Hannemann <arnd@...dnet.de>
To:	Chris Wright <chrisw@...s-sol.org>
CC:	linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
	dwmw2@...radead.org
Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2

Am 15.11.2011 05:36, schrieb Chris Wright:
> * Arnd Hannemann (arnd@...dnet.de) wrote:
>> 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?
> 
> With CONFIG_INTEL_IOMMU_DEFAULT_ON=n, you have to manually enabled the
> IOMMU on the kernel commandline.  So, yes, disabling that and having
> your laptop boot is not surprising.  The Kconfig item changed names,
> and the default is yes, so you may have had CONFIG_DMAR_DEFAULT_ON=n,
> but this would not have propagated forward.
> 
> As for the endless loop of DMAR faults...sounds like the Ricoh
> cardbus/firewire issue where the firewire fucntion does DMA from
> function 0.  I thought this was quirked and fixed though.

In this case it seems to be
0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01)
(using sdhci-pci)
The Fireware function seems to be at a different address:
0d:00.3 FireWire (IEEE 1394): Ricoh Co Ltd FireWire Host Controller (rev 01) (prog-if 10 [OHCI])

Maybe another quirk is needed? Where does this need to be fixed?
I suppose sdhci-pci.ko is loaded much later on bootup.

Best regards
Arnd
--
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/