https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293036
Bug ID: 293036
Summary: vt console ignores hw.vt.kbd.evdev=1 and leaves
modifier state stuck after S3 resume on ThinkPad T14s
Gen1 AMD (15-STABLE regression)
Product: Base System
Version: 15.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
Hardware:
Lenovo ThinkPad T14s Gen1 (AMD)
OS:
FreeBSD 15.0-STABLE
Kernel: stable/15-n282158-808a573e6e14 GENERIC amd64
Console:
vt
Keyboard: atkbd via i8042 (PS/2)
Problem:
After S3 suspend/resume, the console keyboard no longer behaves correctly.
Ctrl and Alt modifiers appear logically stuck "down" and are injected as
literal input into password prompts and TUIs, making the console unusable.
Regression:
This system previously worked correctly on 15-STABLE.
No configuration changes were made.
The problem appeared after updating to a newer 15-STABLE snapshot.
Observed behavior:
- Keyboard works normally before suspend
- After resume:
* Ctrl/Alt are treated as input
* VT switching does not work
* TUIs cannot be navigated
- kbdmux, atkbd reset flags, and kbdcontrol do not resolve the issue
evdev interaction:
evdev devices exist and are functional:
kern.evdev.input.X.name: AT keyboard
Setting hw.vt.kbd.evdev=1 does NOT cause vt to bind evdev.
Disabling atkbd (hint.atkbd.0.disabled=1) results in no console keyboard at
all,
indicating vt is still bound to atkbd despite the evdev preference.
Workarounds:
- No reliable workaround exists for S3 on this kernel.
Expected behavior:
vt should:
- honor hw.vt.kbd.evdev=1, OR
- properly reset modifier state on resume
Actual behavior:
vt depends on atkbd and fails to clear modifier state after S3 resume.
--
You are receiving this mail because:
You are the assignee for the bug.
