From owner-freebsd-usb@freebsd.org Thu Feb 4 16:20:52 2021 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 623BF547FCF for ; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DWkLX28Jrz4YZS for ; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 49AD5547ECA; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4974F547FCE for ; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DWkLX1Yfsz4YcY for ; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 287FE6E53 for ; Thu, 4 Feb 2021 16:20:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 114GKqYd006936 for ; Thu, 4 Feb 2021 16:20:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 114GKqPb006935 for usb@FreeBSD.org; Thu, 4 Feb 2021 16:20:52 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 253249] USB keyboard: repeated and out of order characters Date: Thu, 04 Feb 2021 16:20:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: janm@transactionware.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2021 16:20:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253249 --- Comment #5 from janm@transactionware.com --- (In reply to Hans Petter Selasky from comment #4) I do not believe they are firmware upgradeable. A na=C3=AFve reading of the USB trace by just looking at the USB HID key co= des, gives me this sequence of events, from the 'c' keyboard down event. 'c' down: frame[0] READ 8 bytes 0000 00 00 06 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:33.960284 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 'c' down, 'o' down: 15:50:33.960285 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 06 12 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:34.000288 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 'c' up, 'o' down: 15:50:34.000289 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 00 12 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 'o' down, 'u' down: 15:50:34.032281 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 15:50:34.032283 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 18 12 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 'o' up, 'u' down: 15:50:34.064285 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 15:50:34.064286 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 18 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 'u' down, 'n' down: 15:50:34.096285 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 15:50:34.096286 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 18 11 00 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:34.136286 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes Not sure what this one is (I haven't looked at the protocol spec). 15:50:34.136287 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 01 01 01 01 01 01 -- -- -- -- -- -- -- -- |........ | 15:50:34.149057 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 'u' down, 'n' down, 't' down: 15:50:34.149057 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 18 11 17 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:34.174101 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 'u' up, 'n' down, 't' down: 15:50:34.174101 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 00 11 17 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:34.264291 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes 'n' up, 't' down: 15:50:34.264292 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 00 00 17 00 00 00 -- -- -- -- -- -- -- -- |........ | 15:50:34.277144 usbus0.4 SUBM-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D0= ,IVAL=3D10 frame[0] READ 8 bytes Nothing down: 15:50:34.277145 usbus0.4 DONE-INTR-EP=3D00000081,SPD=3DLOW,NFR=3D1,SLEN=3D8,IVAL=3D10,ERR=3D0 frame[0] READ 8 bytes 0000 00 00 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | That looks like a valid order to me, but I don't know the details of the protocol. I'm not sure how "counntu" could come from that sequence of event= s.=20 With the 'u' at the end of the keystrokes that made it to userland, it almo= st looks like the packets were processed out of order. Is that possible? --=20 You are receiving this mail because: You are the assignee for the bug.=