[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <493DB61F.70403@goop.org>
Date: Mon, 08 Dec 2008 16:04:47 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Alan Stern <stern@...land.harvard.edu>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-usb <linux-usb@...r.kernel.org>,
Ian Jackson <Ian.Jackson@...citrix.com>
Subject: Re: Oops in UHCI when encountering "host controller process error"
Alan Stern wrote:
> On Thu, 16 Oct 2008, Jeremy Fitzhardinge wrote:
>
>
>> Looks like this is the relevent detail: "uhci->skelqh[1]->node.next is
>> NULL" for all the queues. Haven't looked into it yet.
>>
>
> Any news?
The problem went away for a while, but then came back. I still have no
idea why, but I'm back to debugging it.
The most strange thing I'm seeing is this:
uhci_hcd 0000:00:1d.0: irq 29, io base 0x0000bce0
uhci_alloc_td uhci ffff88002e1a3d58 td ffff88002e105000 dma_handle 4ce2f000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e106000 handle=4ce36000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e106080 handle=4ce36080
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e106000 handle=4ce36000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e106001 handle=4ce36001 <<<
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e107000 handle=7e546000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e107080 handle=7e546080
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e107000 handle=7e546000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e107001 handle=7e546001 <<<
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e108000 handle=7e22d000
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e108080 handle=7e22d080
uhci_alloc_qh: uhci=ffff88002e1a3d58 qh=ffff88002e108000 handle=7e22d000
usb usb1: configuration #1 chosen from 1 choice
uhci_hcd 0000:00:1d.0: host controller process error, something bad happened!
uhci_hcd 0000:00:1d.0: host controller halted, very bad!
general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC
For some reason dma_pool_alloc() is returning unaligned, overlapping
memory chunks. That that point everything else is no surprise...
So I'm trying to figure out how the dma pool stuff is malfunctioning,
and whether anything we've done is causing it.
J
--
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