On Fri, 12 Feb 2010, Winslow Dalpe wrote: > Sorry it took me so long, but I have done as you said and attached ( > http://bugzilla.kernel.org/attachment.cgi?id=25009 ) the dmesg output to > the bug report. > > Some notes about this attachment: > > 1. You might see a second instance of the USB headset trying to be > recognized. This is because I plugged it back in to make sure that the > same error was occurring; it was. The headset apparently was unplugged at time 212.009448, which is long after a whole bunch of error messages about audio output timing out. They may or may not be related to what you hear. Then at time 319.524108 the headset was plugged back in. Is that what you mean? > 2. The last messages from about 544.069838 to the end of the log are the > result of me disconnecting my mouse and reconnecting it in order to > speed up the mouse crash. > > Hopefully this is of assistance, and please let me know if there's > anything else I need to do. It gives me the overall picture. Now you need to repeat the test. This time, when the audio stops, unplug & replug the mouse. Then a few seconds later, unplug the headset. When that is done, mount a debugfs filesystem on /sys/kernel/debug, go to /sys/kernel/debug/usb/ohci/0000:00:04.0/ and attach the files you find there to the bug report. You can omit files that are empty -- the ones that matter most are "registers" and "async". Don't forget to attach the dmesg log as well. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
