From: Faidon Liambotis <paravoid@debian.org>
To: linux-kernel@vger.kernel.org
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
Weidong Han <weidong.han@intel.com>,
David Woodhouse <David.Woodhouse@intel.com>,
iommu@lists.linux-foundation.org, allen.m.kay@intel.com,
fenghua.yu@intel.com
Subject: [regression, bisected] fails to boot on Dell Optiplex 760 with VT-d enabled
Date: Tue, 18 Aug 2009 00:27:46 +0300 [thread overview]
Message-ID: <4A89CB52.4030008@debian.org> (raw)
I am experiencin a bug on an Dell Optiplex 760 with a configuration that
has an Intel Core2 Q9550 CPU and with an up-to-date BIOS, version A03.
When "VT for Direct I/O" is enabled in the BIOS, v2.6.30 boots and works
perfectly, while v2.6.31-rc1..rc6 fail (both of them x86-64).
More specifically, I get an endless loop of printing the following
messages in
the screen:
DMAR: [DMA Read] Request device [ff:1f.7] fault addr
fffffffffffff000
DMAR: [fault reason 255] Unknown
and the boot process doesn't move on from there.
I ran git bisect good v2.6.30/bad v2.6.31-rc1 and I was pointed to the
following commit:
937582382c71b75b29fbb92615629494e1a05ac0
x86, intr-remap: enable interrupt remapping early
I have no idea if VT-d is functioning on v2.6.30; I just had the option
enabled in the BIOS and noticed the problem when I tried to upgrade to
2.6.31-rcX.
I've read a similar bug report against a Mandriva kernel and another
VT-d related bug for the same hardware against Xen and in both threads
they were finger-pointing the BIOS.
I'm not sure if that's the case but, even if it is, I'd expect the
system to boot, like previous versions did, perhaps printing a warning
about VT-d functionality.
Thanks,
Faidon
next reply other threads:[~2009-08-17 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 21:27 Faidon Liambotis [this message]
2009-08-17 22:17 ` [regression, bisected] fails to boot on Dell Optiplex 760 with VT-d enabled David Woodhouse
2009-08-17 22:59 ` Faidon Liambotis
2009-08-17 23:11 ` Chris Wright
2009-08-17 23:22 ` Faidon Liambotis
2009-08-17 23:29 ` Chris Wright
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=4A89CB52.4030008@debian.org \
--to=paravoid@debian.org \
--cc=David.Woodhouse@intel.com \
--cc=allen.m.kay@intel.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=weidong.han@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