All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	dwmw2@infradead.org
Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2
Date: Mon, 14 Nov 2011 20:36:34 -0800	[thread overview]
Message-ID: <20111115043634.GA30247@sequoia.sous-sol.org> (raw)
In-Reply-To: <4EC1B80D.5000102@arndnet.de>

* Arnd Hannemann (arnd@arndnet.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.

thanks,
-chris

  parent reply	other threads:[~2011-11-15  4:36 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
2011-11-15  6:29     ` Arnd Hannemann
2011-11-15  4:36   ` Chris Wright [this message]
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=20111115043634.GA30247@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.