NetBSD Problem Report #55998

From www@netbsd.org  Thu Feb 18 08:33:35 2021
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id CD3651A9217
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 18 Feb 2021 08:33:35 +0000 (UTC)
Message-Id: <20210218083334.DEBCC1A9248@mollari.NetBSD.org>
Date: Thu, 18 Feb 2021 08:33:34 +0000 (UTC)
From: mail@artemis.sh
Reply-To: mail@artemis.sh
To: gnats-bugs@NetBSD.org
Subject: Many keyboard events dropped on raspberry pi 3 using aarch64, works fine under armv7hf
X-Send-Pr-Version: www-1.0

>Number:         55998
>Category:       port-evbarm
>Synopsis:       Many keyboard events dropped on raspberry pi 3 using aarch64, works fine under armv7hf
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-evbarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 18 08:35:00 +0000 2021
>Originator:     Artemis Everfree
>Release:        9.1
>Organization:
>Environment:
>Description:
NetBSD drops many keyboard events on my Raspberry Pi 3 when using the aarch64 "arm64.img" boot image. This occurs on the TTY and under X. This leads to keys getting stuck, due to dropped key release events. Key presses are also missed, at times requiring 5 to 10 physical presses to register a single press in the system. As a result, my keyboard is basically unusable.

The keyboard does work fine for about 5 seconds after being plugged in, before exhibiting this behavior. Curiously, this problem is not present at all when using the armv7hf image.

My keyboard uses an atmega32u4 microcontroller running the QMK keyboard firmware. Unfortunately, that's true for every keyboard I own, so I can't isolate whether the problem is present with only this keyboard firmware. However, I have not had this issue with this keyboard on any other system.

I wanted to see if this problem is present in -CURRENT, but the aarch64 image for that won't boot successfully right now, so I'm not sure if it's also present there or not.
>How-To-Repeat:
- Boot the aarch64 image on a Raspberry Pi 3
- Plug in a keyboard
- Attempt to use it for a few minutes.
- If this doesn't cause the issue, it may be dependent on the keyboard hardware.
>Fix:
Use armv7hf instead of aarch64

Home	PR Database Search