I was mistaken before when I said that usbtest would respond to signals when the firmware was loaded; the only way I could see to terminate it was to unplug the USB device.
Yes, that's a minor annoyance. Or sometimes not-so-minor, when khubd can't un-block. It'd be a Good Deed to fix that.
By the way, since you seem to have found the "fun" failure modes using "testusb -t10 -g7 -c 5000" ... have you tried using "-g6"?
The reason is that the seventh queued control request must stall, which means the HCD is executing code it likely doesn't run very often: recovering from the stall (which probably works) while there's another request queued (kablooie!). "-g6" will skip that request (and several others, including more faults and a short-read).
That one test (test10) seems particularly good at finding problems. It's the only one (so far) that tests fault recovery when processing the I/O queues.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
