iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Chris Wright <chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org>
Cc: Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	"open list:INTEL IOMMU (VT-d)"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard
Date: Tue, 9 Jul 2013 16:43:31 -0700	[thread overview]
Message-ID: <20130709234331.GA10833@roeck-us.net> (raw)
In-Reply-To: <20130709232252.GB2676-k0AF34rgNAQdGiBX8rKX95cPDiHTxzko@public.gmane.org>

On Tue, Jul 09, 2013 at 04:22:52PM -0700, Chris Wright wrote:
> * Guenter Roeck (linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org) 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-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org> 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.
> 
Ah, yes, I think I may have that disabled. I'll check it tonight.

Does that really warrant a traceback, or would a warning message be more
appropriate (possibly telling the user to enable VT-d) ?

Thanks,
Guenter

  parent reply	other threads:[~2013-07-09 23:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130709202406.GA11867@roeck-us.net>
     [not found] ` <20130709202406.GA11867-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-09 21:05   ` WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard Bjorn Helgaas
2013-07-09 22:31     ` Guenter Roeck
     [not found]       ` <20130709223106.GA16429-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-09 23:22         ` Chris Wright
     [not found]           ` <20130709232252.GB2676-k0AF34rgNAQdGiBX8rKX95cPDiHTxzko@public.gmane.org>
2013-07-09 23:43             ` Guenter Roeck [this message]
     [not found]               ` <20130709234331.GA10833-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-10  0:05                 ` Chris Wright
     [not found]                   ` <20130710000511.GC2676-k0AF34rgNAQdGiBX8rKX95cPDiHTxzko@public.gmane.org>
2013-07-10  0:18                     ` Guenter Roeck
     [not found]                       ` <20130710001828.GA32072-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-10  0:53                         ` David Woodhouse
     [not found]                           ` <1373417595.26127.27.camel-NkH8fLdbH5RE2VDN4QcBkG7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-07-10  3:55                             ` Guenter Roeck
2013-07-11 19:00                 ` Chris Wright
     [not found]                   ` <20130711190054.GC24833-k0AF34rgNAQdGiBX8rKX95cPDiHTxzko@public.gmane.org>
2013-07-11 20:59                     ` Guenter Roeck
     [not found]                       ` <20130711205902.GB22605-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
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=20130709234331.GA10833@roeck-us.net \
    --to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
    --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).