Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

galp3-c: Multiple KF_E0 key presses on resume result in stuck key repeat #189

Open
crawfxrd opened this issue Apr 30, 2021 · 0 comments
Open
Labels
status:needs-repro Need to check if reproducible on newer version

Comments

@crawfxrd
Copy link
Member

crawfxrd commented Apr 30, 2021

This behavior seems limited to handling KF_E0 keys, as I have not reproduced it with Space or any letter keys.

I have only reproduced it on galp3-c. oryp5 produces the related atkbd warning, but not the key repeat behavior. gaze15 does not produce either (works correctly).

Unsure if this is a problem in the EC itself or something in Linux.

Steps to reproduce:

  1. Configure system to not lock on suspend
  2. Open terminal
  3. Run systemctl suspend
  4. Press any to wake from suspend
  5. As soon as the display turns on, repeatedly press any KF_E0 key (e.g., up arrow key)

Actual behavior:

First several key presses appear to work correctly. Eventually a single press is "missed". Then several appear to happen in rapid succession, as if it is "catching up" to the key presses. Finally, either the key itself or a seemingly arbitrary key is pressed. If you stop pressing the key at about this point, this arbitrary key will repeat indefinitely.

E.g.: Pressing up will typically result in 8 being repeated, and pressing down will typically result in 2 being repeated.

A warning is issued by Linux about handling the key.

atkbd serio0: Unknown key released (translated set 2, code 0xe0 on isa0060/serio0).
atkbd serio0: Use 'setkeycodes e060 <keycode>' to make it known.
@crawfxrd crawfxrd added the status:needs-repro Need to check if reproducible on newer version label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-repro Need to check if reproducible on newer version
Projects
None yet
Development

No branches or pull requests

1 participant