https://bugzilla.kernel.org/show_bug.cgi?id=207219 --- Comment #18 from Alan Stern (stern@xxxxxxxxxxxxxxxxxxx) --- Okay. You need to start the usbmon data collection _before_ you do the insmod, so that the trace can capture _all_ of the USB traffic. And since the usbmon/4u file doesn't exist before you do the insmod, you will have to capture the trace from the usbmon/0u file instead (that file reports all the USB traffic on all the buses). Also, it wouldn't hurt to get a copy of the system log showing what happens when you run the test. Before running insmod, do: dmesg -C >/dev/null After you run insmod, wait a little while (something like 10 seconds), then stop the usbmon trace, and do: dmesg >logfile.txt You don't even need to do the writes to the bConfigurationValue file. Let's see what the usbmon trace and the logfile show. -- You are receiving this mail because: You are watching the assignee of the bug.
