mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Faidon Liambotis <paravoid@debian.org>,
	Matt Domsch <Matt_Domsch@dell.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, bero@arklinux.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 14003] New: Infinite loop on bootup while handling DMAR
Date: Thu, 20 Aug 2009 08:52:28 +0100	[thread overview]
Message-ID: <1250754748.8974.17.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090819142634.0fc550d1.akpm@linux-foundation.org>

On Wed, 2009-08-19 at 14:26 -0700, Andrew Morton wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=14003
> >            Summary: Infinite loop on bootup while handling DMAR
> 
> That's a box-killing post-2.6.30 regression.

It's a BIOS bug -- the user's BIOS is written by idiots who obviously
shipped it without any QA whatsoever.

As far as I can tell, 2.6.30 aborted early because of a _different_ BIOS
bug, but now we cope with that particular bug and we fall over the next
bug. Or just come across them in a different order.

The IOMMU on this board can _never_ have worked. Just disable it.

Or use a board with open source firmware available, and this kind of
crap won't happen. (At least if it does, you'll be able to fix it).

-- 
dwmw2


  parent reply	other threads:[~2009-08-20  7:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14003-10286@http.bugzilla.kernel.org/>
2009-08-19 21:26 ` Andrew Morton
2009-08-20  1:15   ` Suresh Siddha
2009-08-20  7:52   ` David Woodhouse [this message]
2009-08-20  8:01     ` [PATCH] intel-iommu: Work around yet another BIOS bug David Woodhouse
2009-08-20  9:44       ` Andrew Morton
2009-08-20 11:14         ` David Woodhouse
2009-08-20 18:48           ` Andrew Morton
2009-08-20 12:36         ` Matthew Wilcox
2009-08-20 19:29       ` Ray Lee
2009-08-20 19:32         ` David Woodhouse
2009-08-20 21:47           ` Grant Grundler
2009-08-20 21:54             ` David Woodhouse
2009-08-31 13:15               ` Carl-Daniel Hailfinger
2009-08-20  8:40     ` [Bugme-new] [Bug 14003] New: Infinite loop on bootup while handling DMAR Faidon Liambotis

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=1250754748.8974.17.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=Matt_Domsch@dell.com \
    --cc=akpm@linux-foundation.org \
    --cc=bero@arklinux.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=paravoid@debian.org \
    --cc=suresh.b.siddha@intel.com \
    /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

Powered by JetHome