On Mon, Feb 7, 2011 at 10:04 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > Jiri, do you have any suggestions for further debugging? > > That's also normal. Obviously the patch helped; you never got this > much information before. > Yup. your patch is helped. I never got this information before. >> Feb 7 10:06:40 kalau kernel: [ 974.480087] generic-usb: probe of >> 0003:0926:3333.0005 failed with error -32 > > This is clearly different from A, and it is not normal. > >> Everytime I plugged and unplugged keyboard it always produce "Message >> A" and "Message B" randomly. > > It would help to see a usbmon trace for Message B. The trace you > collected before appears to be for A. > Usbmon trace in not normal mode (Message B) produce no information about keyboard bus. Event if I trace all bus with # cat /sys/kernel/debug/usb/usbmon/0u > /tmp/1.mon.out Here is the output trace. http://pastebin.com/x2BhMA6k . Keyboard is on Bus 002 Device 015. kholis@kalau:~$ lsusb Bus 002 Device 015: ID 0926:3333 Bus 002 Device 014: ID 04cc:1521 ST-Ericsson USB 2.0 Hub Bus 002 Device 005: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 002 Device 003: ID 04f2:b1c1 Chicony Electronics Co., Ltd Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > The trace seems to show everything working correctly. It shows key > presses and releases, just as one would expect. When you say the > keyboard doesn't work, what do you mean? > Keyboard produce nothing when I typed it in text editor, in web browser, in shell, etc. Indeed, no character appear on screen at all. -- 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
