On Wed, 25 Jul 2007 08:13:45 -0500, <[EMAIL PROTECTED]> wrote:
> [...] and maybe the inactivate bit was set early enough that
> actual_length never got initialized to anything and the -4 was just
> leftover in that memory space...? I suggest this without looking at the
> code--I don't know if that's actually possible.
No, Stuart, this won't do. I need you to look at the code, because:
a) I have explored the obvious avenues already, and
b) We know that unsetting CONFIG_CPU_FREQ clears the issue.
The initialization of actual_length is done unconditionally in
usb_submit_urb, it was the first thing I checked!
I have two vague hypotheses (-sii?) currently:
#1 Somehow your patch conflicts with the insertion code which
moves dummy qTD around.
#2 The length in QH gets desynched from length in QTD, and we
have a pice of code which takes the qh->hw_token and uses it
for length calculation against qtd->length.
-- Pete
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
