From: David Woodhouse <dwmw2@infradead.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current git fails to boot with VT-D enabled due to flood of DMAR errors
Date: Sat, 19 Sep 2009 21:41:08 -0700 [thread overview]
Message-ID: <1253421668.6317.83.camel@macbook.infradead.org> (raw)
In-Reply-To: <4AB5B07B.5090506@gmail.com>
On Sat, 2009-09-19 at 22:32 -0600, Robert Hancock wrote:
> On an Asus P7P55D Pro-based system (Lynnfield CPU), with Intel VT-d
> enabled in the BIOS, on 2.6.30.5 (the previous version I tested) I get
> these lines in dmesg:
>
> DMAR:Host address width 36
> DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed90000
> DMAR:RMRR base: 0x00000000000e4000 end: 0x00000000000e7fff
> DMAR:RMRR base: 0x00000000bf7ec000 end: 0x00000000bf7fffff
> Not all IO-APIC's listed under remapping hardware
>
> In current -git, I get these lines as well, but then I get this:
>
> DRHD: handling fault status reg ffffffff
> DMAR:[DMA Read] Request device [ff:1f.7] fault addr fffffffffffff000
> DMAR:[fault reason 255] Unknown
>
> The last two lines repeat in a continuous flood and the system doesn't
> boot. This happens even if I pass "intel_iommu=off" (which seems like
> it's already the default).
>
> Could be a kernel bug or a BIOS bug, but in the latter case we should
> probably deal with it better. The registers all reading FF seems like
> maybe the registers are disabled or something..
This ought to be 'fixed' in linux-next by this commit:
http://git.infradead.org/iommu-2.6.git/commitdiff/0815565ad
Please try linux-next or the iommu tree from
git://git.infradead.org/iommu-2.6.git
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-09-20 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 4:32 Current git fails to boot with VT-D enabled due to flood of DMAR errors Robert Hancock
2009-09-20 4:41 ` David Woodhouse [this message]
2009-09-20 4:46 ` Robert Hancock
2009-09-20 5:09 ` David Woodhouse
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=1253421668.6317.83.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=hancockrwd@gmail.com \
--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.