Alan Stern said: > If you haven't done that, try running the test again with USB debugging > on. Or if you already have, look through the system log for messages from > the uhci driver.
Attached is the log with debugging enabled (first with firmware loaded, then after rebooting, without firmware). usbtest is currently wedged in test_ctrl_queue (according to /proc/<pid>/wchan). 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. -- Charles Lepple <[EMAIL PROTECTED]> http://www.ghz.cc/charles/
usbtest+fw+debug.gz
Description: Unix tar archive
oops+no-fw+debug
Description: Binary data
