The USB RF keyboard and mouse frequently become non-responsive. > dmesg | grep -i mouse -B5 -A5 Root mount waiting for: usbus3 usbus2 usbus0 uhub5: 8 ports with 8 removable, self powered ugen0.3: <vendor 0x050d> at usbus0 uhub6: <vendor 0x050d product 0x0237, class 9/0, rev 2.00/0.00, addr 3> on usbus0 ugen3.3: <Chicony> at usbus3 ukbd0: <Chicony HP 2.4Ghz Wireless Keyboard and Mouse, class 0/0, rev 2.00/1.11, addr 3> on usbus3 kbd2 at ukbd0 ums0: <Chicony HP 2.4Ghz Wireless Keyboard and Mouse, class 0/0, rev 2.00/1.11, addr 3> on usbus3 ums0: 3 buttons and [XYZ] coordinates ID=4 Root mount waiting for: usbus3 usbus2 usbus0 ugen3.4: <vendor 0x0cf3> at usbus3 uhub6: 7 ports with 7 removable, self powered ugen0.4: <Prolific Technology Inc.> at usbus0 Moving the mouse or repeatedly pressing the key seems to free things for some time. How-To-Repeat: Connect RF keyboard and mouse. Use the system normally. At some point, pressing a key 20 times will not cause the system to respond to the key. I pressed the R key 9 times before the R in RF appeared.
Responsible Changed From-To: gnats-admin->freebsd-usb rescue from email mangling and assign.
----- Forwarded message from Hans Petter Selasky <hselasky@c2i.net> ----- Date: Sat, 18 Feb 2012 12:49:42 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-usb@freebsd.org Cc: linimon@freebsd.org, gnats-admin@freebsd.org Subject: Re: usb/165163: [keyboard] The USB RF keyboard and mouse become non-responsive User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) You can use "usbdump" to figure out what is going on. Look for USB error codes. usbdump -i usbus3 -vvvv -s 65536 --HPS ----- End forwarded message -----
I did not see any error messages. I do not understand usb status codes. I started a script and then started usbdump. During the time script was running, I moved the mouse from side to side on the screen. The mouse pointer would 'hang' and then jump to the proper (?) location. > script usbdump.log ... > usbdump -i usbus3 -vvvv -s 65536 ... 11:23:54.903238 usbus3.3 SUBM-INTR-EP=00000082,SPD=LOW,NFR=1,SLEN=0,IVAL=10 frame[0] READ 8 bytes flags 0xa <SHORT_XFER_OK|PIPE_BOF|0> status 0xeb023 <OPEN|TRANSFERRING|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0> ... 11:23:54.911238 usbus3.3 SUBM-INTR-EP=00000082,SPD=LOW,NFR=1,SLEN=0,IVAL=10 frame[0] READ 8 bytes flags 0xa <SHORT_XFER_OK|PIPE_BOF|0> status 0xcb023 <OPEN|TRANSFERRING|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0> ... Just repeats of these two types of entries. > grep status usbdump.log | sort | uniq status 0xca1a1 <OPEN|STARTED|CONTROL_XFR|CONTROL_HDR|BDMA_ENABLE|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xca1a3 <OPEN|TRANSFERRING|STARTED|CONTROL_XFR|CONTROL_HDR|BDMA_ENABLE|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xcb021 <OPEN|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xcb023 <OPEN|TRANSFERRING|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xea1a1 <OPEN|STARTED|CONTROL_XFR|CONTROL_HDR|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xea1a3 <OPEN|TRANSFERRING|STARTED|CONTROL_XFR|CONTROL_HDR|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xeb021 <OPEN|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0> status 0xeb023 <OPEN|TRANSFERRING|STARTED|SHORT_XFER_OK|BDMA_ENABLE|BDMA_SETUP|CURR_DMA_SET|CAN_CANCEL_IMMED|DOING_CALLBACK|0> The log is 90K. I can post it somewhere. Tom Dean
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped