From: Faidon Liambotis <paravoid@debian.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
"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 11:40:28 +0300 [thread overview]
Message-ID: <4A8D0BFC.7030101@debian.org> (raw)
In-Reply-To: <1250754748.8974.17.camel@macbook.infradead.org>
David Woodhouse wrote:
> 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.
Matt may be wondering why he was addressed, since the bugzilla entry
mentions only a bug in HP's BIOS.
I'm experiencing the same bug on a newly bought Dell Optiplex 760 with
BIOS version A03, as explained in my mail in lkml,
<4A89CB52.4030008@debian.org>, subject "[regression, bisected] fails to
boot on Dell Optiplex 760 with VT-d enabled".
Thanks,
Faidon
prev parent reply other threads:[~2009-08-20 8:44 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 ` [Bugme-new] [Bug 14003] New: Infinite loop on bootup while handling DMAR Andrew Morton
2009-08-20 1:15 ` Suresh Siddha
2009-08-20 7:52 ` David Woodhouse
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 ` Faidon Liambotis [this message]
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=4A8D0BFC.7030101@debian.org \
--to=paravoid@debian.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=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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 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.