From: Dirk Hohndel <hohndel@infradead.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: 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: Re: git-latest: kernel oops in IOMMU setup
Date: Thu, 8 Jan 2009 13:56:25 -0800 [thread overview]
Message-ID: <20090108135625.7e8dc1b4@infradead.org> (raw)
In-Reply-To: <20090108214116.GB20506@colo.lackof.org>
On Thu, 8 Jan 2009 14:41:16 -0700
Grant Grundler <grundler@parisc-linux.org> wrote:
> On Thu, Jan 08, 2009 at 12:05:38PM -0800, Dirk Hohndel wrote:
> >
> > 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).
Look here, that's where it's called from.
Do you want me to note down the complete backtrace?
> If you can, a back trace. Basically just need to know which caller
> is tripping over this. But there can't be that many callers and they
> are all in this file:
> ...
> so it should be possible to figure out which one is called
> before the dev is setup. It's unlikely to be anything with
> "remove" in the name. :)
correct - it's context_mapping_one
--
Dirk Hohndel
Intel Open Source Technology Center
next prev parent reply other threads:[~2009-01-08 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 20:05 Dirk Hohndel
2009-01-08 21:41 ` Grant Grundler
2009-01-08 21:56 ` Dirk Hohndel [this message]
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=20090108135625.7e8dc1b4@infradead.org \
--to=hohndel@infradead.org \
--cc=arjan@infradead.org \
--cc=grundler@parisc-linux.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