From: Guenter Roeck Subject: Re: WARNING: at drivers/iommu/dmar.c:484 warn_invalid_dmar with Intel Motherboard Date: Tue, 9 Jul 2013 20:55:23 -0700 Message-ID: <20130710035523.GB13149@roeck-us.net> References: <20130709202406.GA11867@roeck-us.net> <20130709223106.GA16429@roeck-us.net> <20130709232252.GB2676@sequoia2.sous-sol.org> <20130709234331.GA10833@roeck-us.net> <20130710000511.GC2676@sequoia2.sous-sol.org> <20130710001828.GA32072@roeck-us.net> <1373417595.26127.27.camel@dwoodhou-mobl5.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1373417595.26127.27.camel-NkH8fLdbH5RE2VDN4QcBkG7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: David Woodhouse Cc: Chris Wright , Bjorn Helgaas , "open list:INTEL IOMMU (VT-d)" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: iommu@lists.linux-foundation.org On Wed, Jul 10, 2013 at 01:53:15AM +0100, David Woodhouse wrote: > On Tue, 2013-07-09 at 17:18 -0700, Guenter Roeck wrote: > > > > I meant warning as in pr_warn or dev_warn, not WARNING as in traceback. > > Keep in mind that a casual user doesn't expect to see a traceback and will tend > > to get alarmed. Several bugs have been filed against this "issue" in various > > distributions, which is not surprising given the alarmist message. > > What is the point of that ? > > It is warning you that your hardware is broken. Take it back to the > place from which you purchased it, and ask for your money back if it > isn't fixed. > > (Slightly) more seriously, this level of warning *does* get things > fixed, and when kerneloops was running it made it very easy to track > this kind of issue and apply pressure where it was needed to improve > quality. > > Any user who has taken the trouble to file bugs has *also* taken it up > with their firmware vendor, I hope? > No idea ... but have you ever tried that as a private entity ? If there is a secret list of people to contact at vendor X to get things like this one fixed, please let me know ;). Thanks, Guenter