I have tried both the 2.6.17 and 2.6.18 linux kernels and both give the message:
"reset low speed USB device using ohci_hcd and address X" every few minutes in the system logs. The "X" is, of course, a numeral and corresponds to my USB keyboard. The device resets are accompanied by a delayed keyboard response and then the key pressed is repeated several (25, maybe) times. Inbetween device resets, the keyboard operates completely normally. The keyboard is the only device on the USB bus. I found someone else who noticed this problem with the 2.6.19 linux kernel and posted to the linux-kernel mailing list. The thread can be found here: http://www.gossamer-threads.com/lists/linux/kernel/709839#709839 . The poster does not seem to have achieved resolution of the issue. Following the suggestions at the end of the linux-kernel thread, I turned on CONFIG_USB_DEBUG. No additional information is emitted by the kernel during a reset event. In addition, I used usbmon to capture bus activity during a reset event. usbmon gave the following trace: ffff81015cabd200 3741485036 C Ii:007:01 0 8 = 00000000 00000000 ffff81015cabd200 3741485053 S Ii:007:01 -115 8 < ffff81015cabda40 3838186011 C Ii:007:02 -110 0 ffff81015cabd200 3838187009 C Ii:007:01 -2 0 ffff81015cabd500 3838187021 S Co:001:00 s 23 03 0004 0001 0000 0 ffff81015cabd500 3838250569 C Co:001:00 0 0 ffff81007f499740 3838306573 C Ii:001:01 0 2 = 0200 ffff81007f499740 3838306577 S Ii:001:01 -115 2 < ffff81015cabd8c0 3838454569 S Ci:001:00 s a3 00 0000 0001 0004 4 < ffff81015cabd8c0 3838454573 C Ci:001:00 0 4 = 03031000 ffff81015cabd980 3838510567 S Co:001:00 s 23 01 0014 0001 0000 0 ffff81015cabd980 3838510571 C Co:001:00 0 0 ffff810033f3a9c0 3838510584 S Ci:000:00 s 80 06 0100 0000 0040 64 < ffff810033f3a9c0 3838513004 C Ci:000:00 0 18 = 12011001 00000008 6d040fc3 00230102 0001 ffff810033f3a9c0 3838513011 S Co:001:00 s 23 03 0004 0001 0000 0 ffff81007f499740 3838558570 C Ii:001:01 0 2 = 0200 ffff81007f499740 3838558574 S Ii:001:01 -115 2 < ffff810033f3a9c0 3838578565 C Co:001:00 0 0 ffff810033f3a9c0 3838782566 S Ci:001:00 s a3 00 0000 0001 0004 4 < ffff810033f3a9c0 3838782571 C Ci:001:00 0 4 = 03031000 ffff81007f499740 3838810567 C Ii:001:01 0 2 = 0200 ffff81007f499740 3838810571 S Ii:001:01 -115 2 < ffff810033f3a9c0 3838838563 S Co:001:00 s 23 01 0014 0001 0000 0 ffff810033f3a9c0 3838838567 C Co:001:00 0 0 ffff810033f3a9c0 3838838571 S Co:000:00 s 00 05 0007 0000 0000 0 ffff810033f3a9c0 3838839997 C Co:000:00 0 0 ffff81015cabd2c0 3838858565 S Ci:007:00 s 80 06 0100 0000 0012 18 < ffff81015cabd2c0 3838860996 C Ci:007:00 0 18 = 12011001 00000008 6d040fc3 00230102 0001 ffff810033f3a9c0 3838861004 S Ci:007:00 s 80 06 0200 0000 003b 59 < ffff810033f3a9c0 3838865996 C Ci:007:00 0 59 = 09023b00 020100a0 32090400 00010301 01000921 10010001 22400007 05810308 ffff810033f3a9c0 3838866002 S Co:007:00 s 00 09 0001 0000 0000 0 ffff810033f3a9c0 3838868995 C Co:007:00 0 0 ffff810033f3a9c0 3838869001 S Co:007:00 s 01 0b 0000 0000 0000 0 ffff810033f3a9c0 3838871994 C Co:007:00 0 0 ffff810033f3a9c0 3838872100 S Co:007:00 s 01 0b 0000 0001 0000 0 ffff810033f3a9c0 3838874996 C Co:007:00 0 0 ffff810033f3a9c0 3838875084 S Co:007:00 s 21 0a 0000 0001 0000 0 ffff810033f3a9c0 3838877995 C Co:007:00 0 0 ffff81015cabda40 3838878003 S Ii:007:02 -115 3 < ffff810033f3a9c0 3838878009 S Co:007:00 s 21 0a 0000 0000 0000 0 ffff810033f3a9c0 3838880995 C Co:007:00 0 0 ffff81015cabd200 3838881001 S Ii:007:01 -115 8 < ffff81015cabd200 3843130907 C Ii:007:01 0 8 = 01000000 00000000 ffff81015cabd200 3843130921 S Ii:007:01 -115 8 < Note that in this trace the keyboard is device 7. Also, this trace was captured by allowing the machine to sit idle, waiting for a device reset (i.e. no keys were pressed, nothing was touched). Hardware details are as follows: Both the linux-kernel poster and I have nVidia chipsets: $lspci -nn 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3) The linux-kernel poster and I have different keyboards. Mine is a Logitech Media Elite: $lsusb Bus 001 Device 007: ID 046d:c30f Logitech, Inc. I have tried a different, non-Logitech USB keyboard (one with fewer extra buttons) and did not experience any device resets. Both the linux-kernel poster and I are using our keyboards on a USB 1.0 bus controlled by the ohci_hcd driver. Can anyone provide any insight? What is happening in the usbmon trace? I'm just about at the end of my technical ability troubleshooting this, but I'm happy to provide additional information to more capable individuals. Thanks. --Ethan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
