From: Dirk Hohndel <hohndel@infradead.org>
To: Dirk Hohndel <hohndel@infradead.org>
Cc: "Han, Weidong" <weidong.han@intel.com>,
"'Grant Grundler'" <grundler@parisc-linux.org>,
"'linux-pci@vger.kernel.org'" <linux-pci@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'Jesse Barnes'" <jbarnes@virtuousgeek.org>,
"'iommu@lists.linux-foundation.org'"
<iommu@lists.linux-foundation.org>,
"'Ingo Molnar'" <mingo@elte.hu>,
"'Arjan van de Ven'" <arjan@infradead.org>
Subject: Re: git-latest: kernel oops in IOMMU setup
Date: Thu, 8 Jan 2009 20:52:22 -0800 [thread overview]
Message-ID: <20090108205222.2c89dcde@infradead.org> (raw)
In-Reply-To: <20090108180515.2f279671@infradead.org>
On Thu, 8 Jan 2009 18:05:15 -0800
Dirk Hohndel <hohndel@infradead.org> wrote:
> On Fri, 9 Jan 2009 08:58:46 +0800 "Han, Weidong"
>
> I updated to Linus' latest git (as your description made me wonder if
> the async stuff might play a role here). I still get an oops - but at
> a different spot and the system no longer hangs - it partly recovers
> (but things aren't too well - for example my USB keyboard / mouse
> don't work anymore).
Spoke too soon. Rebooted and had the same hard lockup again. This time
I had my camera within reach, so here's the trace:
device_to_iommu+0x33/0x73
domain_context_mapping_one+0x37/0x335
domain_context_mapping+0x25/0xa7
iommu_prepare_identity+0xd7/0xf3
intel_iommu_init+0x4e4/0x8f3
? mutex_lock
? sysctl_net_init
? pci_iommu_init
pci_iommu_init
I also have stack, code and register values. Let me know if you need
them. Or I can just post the picture :-)
Again, very latest git tree, VT-d enabled.
/D
--
Dirk Hohndel
Intel Open Source Technology Center
next prev parent reply other threads:[~2009-01-09 4:52 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
2009-01-09 0:58 ` Han, Weidong
2009-01-09 2:05 ` Dirk Hohndel
2009-01-09 4:52 ` Dirk Hohndel [this message]
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=20090108205222.2c89dcde@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 \
--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
Powered by JetHome