[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090108205222.2c89dcde@infradead.org>
Date: Thu, 8 Jan 2009 20:52:22 -0800
From: Dirk Hohndel <hohndel@...radead.org>
To: Dirk Hohndel <hohndel@...radead.org>
Cc: "Han, Weidong" <weidong.han@...el.com>,
'Grant Grundler' <grundler@...isc-linux.org>,
"'linux-pci@...r.kernel.org'" <linux-pci@...r.kernel.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
'Jesse Barnes' <jbarnes@...tuousgeek.org>,
"'iommu@...ts.linux-foundation.org'"
<iommu@...ts.linux-foundation.org>, 'Ingo Molnar' <mingo@...e.hu>,
'Arjan van de Ven' <arjan@...radead.org>
Subject: Re: git-latest: kernel oops in IOMMU setup
On Thu, 8 Jan 2009 18:05:15 -0800
Dirk Hohndel <hohndel@...radead.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists