Alan Stern <[EMAIL PROTECTED]> wrote: > > What about those scheduler changes you found through the bisection search? > Any word on that?
Ingo's gone over them pretty closely. The current theory is that the CPU scheduler change alters timing sufficiently for the bug to bite. The machine passes memtest86. Ingo's suspecting stack corruption. Do you know whether USB anywhere does DMA into automatically-allocated storage (ie: kernel stacks)? Am about to reboot into a stack-corruption-detector patch from Ingo. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
