From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221383] ideapad_laptop: Fn hotkeys stop emitting after s2idle resume on IdeaPad Slim 3 14ARP10 (Ryzen 7735HS)
Date: Tue, 21 Apr 2026 14:51:20 +0000 [thread overview]
Message-ID: <bug-221383-215701-GQC5scVun0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221383-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221383
--- Comment #9 from Rong Zhang (i@rong.moe) ---
Thanks for testing.
I've just checked the decompiled ASL code of PNP0D80 (in SSDT4). Nothing stands
out, and the S0ix implementation seems appropriate.
The next thing that caught my eye was the "Failed to deactivate keyboard on
isa0060/serio0" error. Some devices can't handle this properly and will run
into a broken state. I am not sure whether your device falls into this
category, so please recompile the kernel using the following patch and see if
it helps.
diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
index 840cdf5878dc..7f5f1d1ca265 100644
--- a/drivers/input/keyboard/atkbd.c
+++ b/drivers/input/keyboard/atkbd.c
@@ -250,7 +250,7 @@ static unsigned int (*atkbd_platform_scancode_fixup)(struct
atkbd *, unsigned in
* Certain keyboards to not like ATKBD_CMD_RESET_DIS and stop responding
* to many commands until full reset (ATKBD_CMD_RESET_BAT) is performed.
*/
-static bool atkbd_skip_deactivate;
+static bool atkbd_skip_deactivate = 1;
static ssize_t atkbd_attr_show_helper(struct device *dev, char *buf,
ssize_t (*handler)(struct atkbd *, char *));
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-04-21 14:51 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 13:38 [Bug 221383] New: ideapad_laptop: Fn hotkeys stop emitting after s2idle resume on IdeaPad Slim 3 14ARP10 (Ryzen 7735HS) bugzilla-daemon
2026-04-18 13:39 ` [Bug 221383] " bugzilla-daemon
2026-04-18 13:39 ` bugzilla-daemon
2026-04-18 13:40 ` bugzilla-daemon
2026-04-18 13:40 ` bugzilla-daemon
2026-04-18 17:51 ` bugzilla-daemon
2026-04-20 20:00 ` bugzilla-daemon
2026-04-20 20:02 ` bugzilla-daemon
2026-04-20 20:02 ` bugzilla-daemon
2026-04-21 14:51 ` bugzilla-daemon [this message]
2026-04-21 15:40 ` bugzilla-daemon
2026-04-23 2:26 ` bugzilla-daemon
2026-04-23 2:34 ` bugzilla-daemon
2026-04-23 2:48 ` bugzilla-daemon
2026-04-23 2:57 ` bugzilla-daemon
2026-04-23 4:15 ` bugzilla-daemon
2026-04-23 4:16 ` bugzilla-daemon
2026-04-23 4:18 ` bugzilla-daemon
2026-04-23 4:19 ` bugzilla-daemon
2026-04-23 4:19 ` bugzilla-daemon
2026-04-23 4:20 ` bugzilla-daemon
2026-04-23 4:22 ` bugzilla-daemon
2026-04-23 4:24 ` bugzilla-daemon
2026-04-23 16:30 ` bugzilla-daemon
2026-04-23 19:33 ` bugzilla-daemon
2026-04-23 19:45 ` bugzilla-daemon
2026-04-24 4:03 ` bugzilla-daemon
2026-04-24 13:39 ` bugzilla-daemon
2026-04-24 20:19 ` bugzilla-daemon
2026-04-24 21:15 ` bugzilla-daemon
2026-04-24 21:21 ` bugzilla-daemon
2026-04-24 21:26 ` bugzilla-daemon
2026-04-24 21:50 ` bugzilla-daemon
2026-04-25 0:01 ` bugzilla-daemon
2026-04-25 0:45 ` bugzilla-daemon
2026-04-25 0:56 ` bugzilla-daemon
2026-04-25 1:06 ` bugzilla-daemon
2026-04-25 2:29 ` bugzilla-daemon
2026-04-25 15:32 ` bugzilla-daemon
2026-04-25 16:32 ` bugzilla-daemon
2026-04-25 17:13 ` bugzilla-daemon
2026-04-25 18:59 ` bugzilla-daemon
2026-04-26 2:59 ` bugzilla-daemon
2026-04-27 19:46 ` bugzilla-daemon
2026-04-27 19:55 ` bugzilla-daemon
2026-04-27 20:31 ` bugzilla-daemon
2026-04-28 0:28 ` bugzilla-daemon
2026-04-28 0:34 ` bugzilla-daemon
2026-04-28 1:20 ` bugzilla-daemon
2026-04-28 1:37 ` bugzilla-daemon
2026-04-28 1:41 ` bugzilla-daemon
2026-04-28 2:19 ` bugzilla-daemon
2026-04-28 2:25 ` bugzilla-daemon
2026-04-28 4:38 ` bugzilla-daemon
2026-04-28 4:39 ` bugzilla-daemon
2026-04-28 14:05 ` bugzilla-daemon
2026-04-28 14:54 ` bugzilla-daemon
2026-04-28 15:00 ` bugzilla-daemon
2026-04-28 15:21 ` bugzilla-daemon
2026-04-28 17:41 ` 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-221383-215701-GQC5scVun0@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