From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752664Ab1KOG3e (ORCPT ); Tue, 15 Nov 2011 01:29:34 -0500 Received: from mail2.unitix.de ([176.9.2.175]:60337 "EHLO mail2.unitix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751993Ab1KOG3d (ORCPT ); Tue, 15 Nov 2011 01:29:33 -0500 Message-ID: <4EC206C9.10909@arndnet.de> Date: Tue, 15 Nov 2011 07:29:29 +0100 From: Arnd Hannemann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Robert Hancock CC: linux-kernel@vger.kernel.org, dwmw2@infradead.org, iommu@lists.linux-foundation.org Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2 References: <4EC19738.8050007@arndnet.de> <4EC1B80D.5000102@arndnet.de> <4EC1EB39.1080705@gmail.com> In-Reply-To: <4EC1EB39.1080705@gmail.com> X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 15.11.2011 05:31, schrieb Robert Hancock: > 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. Looks lite a "Ricoh Co Ltd MMC/SD Host Controller" is the culprit: 0d:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 01) Subsystem: Lenovo Device 2133 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-