On Fri, 8 Dec 2006, Dominik Brodowski wrote:

> Hi,
> 
> On Fri, Dec 08, 2006 at 11:00:15AM -0500, Alan Stern wrote:
> > Okay.  Here's a patch that will print out some information for each of the 
> > first 100 interrupts received by ehci-hcd.  Block yenta-socket from being 
> > loaded, so as to reduce the number of extraneous interrupts, and see what 
> > you get.
> 
> Now I did not only block yenta-socket (which does not cause any interrupts
> during initialization) but also ohci1394 (which is on the other IRQ line,
> but anyways) and snd-intel8x0;

Good.

>  but that did not help:
> 
> http://userweb.kernel.org/~brodo/dmesg-autosuspend.txt
> 
> The "offending" IRQ status seems to be 2008; as INTR_MASK does neither
> include STS_FLR nor STS_RECL (if I got the math correctly), IRQ_NONE is
> returned.

Yes, that's right.  In fact the controller isn't supposed to send an IRQ
when only those two bits are on.  I suspect the STS_FLR bit is somehow
getting set in the intr_enable register (don't ask me how -- there doesn't
seem to be any code that could do it).  Can you modify the patch to print
out the value of that register as well as the value of the status 
register?

Also, does the problem occur if you block uhci-hcd from loading at startup
too?  Then ehci-hcd would be the only remaining user of IRQ 10.

Alan Stern


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to