From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221238] lg-laptop: Spurious ACK and dropped keystrokes caused by ACPI method calls conflicting with i8042 driver
Date: Sun, 15 Mar 2026 14:51:06 +0000 [thread overview]
Message-ID: <bug-221238-215701-ycEJIedUts@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221238-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221238
--- Comment #4 from Armin Wolf (W_Armin@gmx.de) ---
The ACPI bytecode indeed creates a operation region for the atkbd IO ports, but
said operation region is unused. So this cannot be the cause of your issues.
Can you check if the battery limit exposed by the driver actually works and
returns the correct values previously written to it?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are on the CC list for the bug.
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-03-15 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 11:15 [Bug 221238] New: lg-laptop: Spurious ACK and dropped keystrokes due to unprotected i8042 port access bugzilla-daemon
2026-03-15 11:18 ` [Bug 221238] " bugzilla-daemon
2026-03-15 11:29 ` [Bug 221238] lg-laptop: Spurious ACK and dropped keystrokes caused by ACPI method calls conflicting with i8042 driver bugzilla-daemon
2026-03-15 11:34 ` bugzilla-daemon
2026-03-15 13:56 ` bugzilla-daemon
2026-03-15 13:58 ` bugzilla-daemon
2026-03-15 14:51 ` bugzilla-daemon [this message]
2026-03-15 21:07 ` bugzilla-daemon
2026-03-19 4:04 ` bugzilla-daemon
2026-03-19 13:01 ` bugzilla-daemon
2026-03-25 23:18 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221238-215701-ycEJIedUts@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox