Hi,
> Sometime I often trigger this:
>
> Badness in isp116x_send_queue at drivers/usb/host/ohci-isp116x-emu.c:417
>
> with Line 417 being
>
> WARN_ON((!(__isp1362_read_reg16(dev, HCuPINT) & HCuPINT_ISP116x_AIIEOT)));
>
> How do I avoid the occurence of this? I remember havin read here about AIIEOT
> Interrupt but excuse me, I don't find it anymore.
>
ALLEOT is set when the amount of data programmed in the XFERCOUNT
register has been transferred to/from the chip buffer. If it's not set
at the end of the the read/write_buffer it means that the chip is
waiting for more data. Could be a hardware timing problem.
> When I plug a pcm2702 in and try to play a sound file (alsamixer works fine
> :))
> I get an endless loop of
>
> process_ed_list: Processing ED @ 08c3b040 #9795
> process_ed_list: Processing TD ffc03000
> process_ed_list: Processing ISO TD 08d53000
> Badness in retire_td at drivers/usb/host/ohci-isp116x-emu.c:781
>
> with line 781 being
>
> if (TD_CC_GET(td_flags) != TD_BUSY) {
> ohci_dump_td(ohci, __FUNCTION__, td);
> WARN_ON(1);
> return;
> }
>
> Why is the warning/error generated and how to avoid this?
>
TD_BUSY is set, when the driver starts processing a TD and reset after
it has been released to the OHCI HCD. So if it's not set in
retire_td() it means that the same TD has already been retired earlier.
Lothar Wassmann
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
