Here is the Oops log dumped to the display right before the system locks up:
It's not very useful unless you include "ksymoops" output... can you get that, and resend along with kernel information (like the version etc). It'd also be good to have "objdump -dr" output for the relevant module, to help track down the problem.
Does the 2.5 OHCI code have the same failure?
Other points to note: When a write to the device succeeds, the write_callback gets called, but when the device locks up like it did here, the write_callback never comes back. It only tends to lock up when there are characters in the queue.
This doesn't necessarily mean that it's OHCI code causing the problem, of course...
Thanks, and I apologize if this the wrong place for this. (I'm new at filing kernel bug reports)
Right place, but not enough information. There's information in various places (including the www.linux-usb.org FAQ) saying what else to do.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
