From owner-freebsd-amd64@freebsd.org  Thu Jul  7 19:35:53 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ABBFB82738
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Thu,  7 Jul 2016 19:35:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AB62139F
 for <freebsd-amd64@FreeBSD.org>; Thu,  7 Jul 2016 19:35:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u67JZqf6028466
 for <freebsd-amd64@FreeBSD.org>; Thu, 7 Jul 2016 19:35:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209674] USB keyboard's keys become sticky
Date: Thu, 07 Jul 2016 19:35:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: usb
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: Scoobi_doo@yahoo.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209674-6-dnqE7NWFWc@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209674-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209674-6@https.bugs.freebsd.org/bugzilla/>
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-Mailman-Approved-At: Thu, 07 Jul 2016 20:29:22 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 19:35:53 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209674

Anthony Jenkins <Scoobi_doo@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Scoobi_doo@yahoo.com

--- Comment #5 from Anthony Jenkins <Scoobi_doo@yahoo.com> ---
(In reply to bourne.identity@hotmail.com from comment #2)
I think Hans was suggesting you run usbdump /continuously/, piping the outp=
ut
to a file, while waiting for the anomaly to occur.  You can redact the file=
 to
remove any USB events up to just before the anomaly occurs, before attachin=
g to
this bug.

usbdump -i usbus2 -f 4 -s 65536 -vvv | gzip -c > usbdump.gz

Anthony

--=20
You are receiving this mail because:
You are on the CC list for the bug.=