Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261998AbTEMViI (ORCPT ); Tue, 13 May 2003 17:38:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262001AbTEMViI (ORCPT ); Tue, 13 May 2003 17:38:08 -0400 Received: from hermine.idb.hist.no ([158.38.50.15]:56845 "HELO hermine.idb.hist.no") by vger.kernel.org with SMTP id S261998AbTEMVhU (ORCPT ); Tue, 13 May 2003 17:37:20 -0400 Date: Tue, 13 May 2003 23:48:30 +0200 To: Alan Stern Cc: Greg KH , Paul Fulghum , Andrew Morton , "linux-kernel@vger.kernel.org" , Arnd Bergmann , johannes@erdfelt.com Subject: Re: 2.5.69 Interrupt Latency Message-ID: <20030513214830.GA685@hh.idb.hist.no> References: <20030513181120.GA10790@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i From: Helge Hafting Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 843 Lines: 17 On Tue, May 13, 2003 at 05:35:47PM -0400, Alan Stern wrote: > My take is that wakeup_hc() is getting called whenever some stray signal > causes the device to generate an interrupt, and then a little while later > the stall timer routine calls suspend_hc() since nothing is active. The > interrupts are probably indistinguishable from what you would get if a new > device really had just been attached to the bus. > Could this also happen if the USB interrupt is shared? The other device interrupts, and the kernel calls into usb interrupt routine just in case USB has some data too? Helge Hafting - 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/