From: Dirk Hohndel <hohndel@infradead.org>
To: Ingo Molnar <mingo@elte.hu>,
iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: git-latest: kernel oops in IOMMU setup
Date: Thu, 8 Jan 2009 12:05:38 -0800 [thread overview]
Message-ID: <20090108120538.0176d348@infradead.org> (raw)
latest git from Linus. On a Thinkpad x200s with VT-d enabled (if I
disable VT-d, this of course goes away).
The oops happens very early during boot in device_to_iommu (called
from domain_context_mapping_one).
Looking at the code dump and the disassembled function here's where
the error happens:
static struct intel_iommu *device_to_iommu(u8 bus, u8 devfn)
{
struct dmar_drhd_unit *drhd = NULL;
int i;
for_each_drhd_unit(drhd) {
if (drhd->ignored)
continue;
for (i = 0; i < drhd->devices_cnt; i++)
if (drhd->devices[i]->bus->number == bus &&
--> drhd->devices[0] is NULL
drhd->devices[i]->devfn == devfn)
return drhd->iommu;
Given how early this happens it's a little hard to provide logs, etc. I
literally used delay_boot=100 and wrote things down by hand (forgot my
digital camera) and then added printk's to verify).
please let me know what other data I should collect.
The system ran fine with the 2.6.28 release kernel.
/D
--
Dirk Hohndel
Intel Open Source Technology Center
next reply other threads:[~2009-01-08 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 20:05 Dirk Hohndel [this message]
2009-01-08 21:41 ` Grant Grundler
2009-01-08 21:56 ` Dirk Hohndel
2009-01-09 0:58 ` Han, Weidong
2009-01-09 2:05 ` Dirk Hohndel
2009-01-09 4:52 ` Dirk Hohndel
2009-01-09 6:53 ` Han, Weidong
2009-01-09 15:08 ` Dirk Hohndel
2009-01-09 16:16 ` Zhao, Yu
2009-01-09 16:34 ` Dirk Hohndel
2009-01-09 16:45 ` Zhao, Yu
2009-01-09 16:55 ` Dirk Hohndel
2009-01-09 16:58 ` [PATCH] Prevent oops at boot with VT-d Dirk Hohndel
2009-01-11 15:25 ` [Resend][PATCH] " Dirk Hohndel
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=20090108120538.0176d348@infradead.org \
--to=hohndel@infradead.org \
--cc=arjan@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
/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