From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>
Subject: Re: Oops in UHCI when encountering "host controller process error"
Date: Wed, 10 Dec 2008 11:15:12 -0800 [thread overview]
Message-ID: <49401540.8030609@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0812101006540.2175-100000@iolanthe.rowland.org>
Alan Stern wrote:
> The entry point is uhci_urb_enqueue(). You can do whatever you like
> there, but bear in mind that it may be called in interrupt context.
> uhci_sprint_schedule() should be fine.
>
> However I don't really see the point. If the DMA pool allocations are
> so badly messed up that the initial setup is wrong, why bother to
> search any further?
I was trying to use it as a way of gauging where the damage was coming from.
But its moot now; Ian Campbell tracked it down to a missing TLB flush
which explained all the weird non-deterministic symptoms we were
seeing. It all looks pretty good now.
J
prev parent reply other threads:[~2008-12-10 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 23:42 Oops in UHCI when encountering "host controller process error" Jeremy Fitzhardinge
2008-10-16 14:03 ` Alan Stern
2008-10-16 22:02 ` Jeremy Fitzhardinge
2008-10-16 23:34 ` Alan Stern
2008-10-17 1:00 ` Jeremy Fitzhardinge
2008-10-17 14:58 ` Alan Stern
2008-10-17 15:20 ` Jeremy Fitzhardinge
2008-10-21 20:02 ` Alan Stern
2008-10-21 20:41 ` Jeremy Fitzhardinge
2008-12-09 0:04 ` Jeremy Fitzhardinge
2008-12-09 1:04 ` Jeremy Fitzhardinge
2008-12-09 2:13 ` Alan Stern
2008-12-09 18:24 ` Jeremy Fitzhardinge
2008-12-09 18:43 ` Alan Stern
2008-12-09 22:49 ` Jeremy Fitzhardinge
2008-12-10 15:10 ` Alan Stern
2008-12-10 19:15 ` Jeremy Fitzhardinge [this message]
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=49401540.8030609@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.