David Brownell wrote:
On Wednesday 09 February 2005 11:39 am, Brian Murphy wrote:I used start_async() (no arguments) instead when I tested at work (this is the problem
David Brownell wrote:
Did you mean something like this?But, rather than just logging a KERN_CRIT error, the better fix would be to just do what ehci-hcd.c::unlink_async() does and stick that QH at the end of the reclaim queue, in QH_STATE_UNLINK_WAIT. In fact, can you try just calling unlink_async() there, to see if that behaves? Instead of start_unlink_async(). If that works, I'd like to see if this could still get into 2.6.11 ...
Yes, does that work OK for you?
of having a real job that pays money and hacking the linux kernel at the same time)
and this seemed to work!!
Is it possible that the argument list from qh_completions was passed to start_async()?
In any case I will test with the correct patch tomorrow and post my verdict.
/Brian
------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
