From: Chris Wright <chrisw@sous-sol.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
David Woodhouse <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux-foundation.org>
Subject: Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard
Date: Tue, 9 Jul 2013 16:22:52 -0700 [thread overview]
Message-ID: <20130709232252.GB2676@sequoia2.sous-sol.org> (raw)
In-Reply-To: <20130709223106.GA16429@roeck-us.net>
* Guenter Roeck (linux@roeck-us.net) wrote:
> On Tue, Jul 09, 2013 at 03:05:39PM -0600, Bjorn Helgaas wrote:
> > [+cc Joerg, David, iommu list]
> >
> > On Tue, Jul 9, 2013 at 2:24 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > > I started seeing this problem after updating the BIOS trying fix another issue,
> > > though I may have missed it earlier.
> > >
> > > I understand this is a BIOS bug. Would be great if someone can pass this on
> > > to Intel BIOS engineers.
> >
> > Maybe. It'd be nice if Linux handled it better, though.
> >
> If anyone has an idea how to do that, I'll be happy to write a patch.
I'm not sure there's much you can do. The BIOS is saying there's a DMAR
unit, and then saying the registers are at addr 0x0. The kernel is
simply warning you about the invalid DMAR table entry.
One thing I've seen is the BIOS zeroing the base register address when
VT-d is disabled in BIOS. So, Guenter, a "fix" may be simply enabling
VT-d in the BIOS.
thanks,
-chris
next prev parent reply other threads:[~2013-07-09 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 20:24 Guenter Roeck
2013-07-09 21:05 ` Bjorn Helgaas
2013-07-09 22:31 ` Guenter Roeck
2013-07-09 23:22 ` Chris Wright [this message]
2013-07-09 23:43 ` Guenter Roeck
2013-07-10 0:05 ` Chris Wright
2013-07-10 0:18 ` Guenter Roeck
2013-07-10 0:53 ` David Woodhouse
2013-07-10 3:55 ` Guenter Roeck
2013-07-11 19:00 ` Chris Wright
2013-07-11 20:59 ` Guenter Roeck
2013-07-11 22:31 ` Chris Wright
2013-08-14 9:36 ` Joerg Roedel
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=20130709232252.GB2676@sequoia2.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=bhelgaas@google.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®