Obviously running low on caffeine, I neglected to load the firmware. If I invoked testusb from the command line, it produced a kernel panic.
Before I round up the ksymoops log (it requires setting up a serial console), should I try testing with a later version of usbtest? Is this a known issue?
Caffeine shortages cause lots of trouble ... :)
New issue, I've never seen it. I seem to recall the "no firmware" case just being a "driver waits forever on bulk i/o", though.
Also, what is the recommended way of enabling debug output for usbtest?
I usually just enable CONFIG_USB_DEBUG, and hack the source if more details are needed.
- 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
