public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Arnd Hannemann <arnd@arndnet.de>
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
Date: Mon, 14 Nov 2011 22:31:53 -0600	[thread overview]
Message-ID: <4EC1EB39.1080705@gmail.com> (raw)
In-Reply-To: <4EC1B80D.5000102@arndnet.de>

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.

  reply	other threads:[~2011-11-15  4:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 22:33 3.2rc1: bootup fails: DRHD: handling fault status reg 2 Arnd Hannemann
2011-11-15  0:53 ` Arnd Hannemann
2011-11-15  4:31   ` Robert Hancock [this message]
2011-11-15  6:29     ` Arnd Hannemann
2011-11-15  4:36   ` Chris Wright
2011-11-15  6:34     ` Arnd Hannemann
2011-11-15  8:55     ` David Woodhouse
2011-11-16  4:01       ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EC1EB39.1080705@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=arnd@arndnet.de \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox