Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753675AbYLJTP1 (ORCPT ); Wed, 10 Dec 2008 14:15:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754630AbYLJTPQ (ORCPT ); Wed, 10 Dec 2008 14:15:16 -0500 Received: from gw.goop.org ([64.81.55.164]:34851 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753641AbYLJTPP (ORCPT ); Wed, 10 Dec 2008 14:15:15 -0500 Message-ID: <49401540.8030609@goop.org> Date: Wed, 10 Dec 2008 11:15:12 -0800 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Alan Stern CC: Linux Kernel Mailing List , linux-usb Subject: Re: Oops in UHCI when encountering "host controller process error" References: In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 878 Lines: 22 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/