All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 20 Apr 2026 20:00:45 +0000	[thread overview]
Message-ID: <bug-221383-215701-Wbo6XG4kdq@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 #6 from sindrehenriksen93@gmail.com ---
Tested as requested. All seven modules blacklisted:

  blacklist ideapad_laptop
  blacklist lenovo_wmi_other
  blacklist lenovo_wmi_helpers
  blacklist lenovo_wmi_capdata01
  blacklist lenovo_wmi_hotkey_utilities
  blacklist sparse_keymap
  blacklist platform_profile

`update-initramfs -u` after — without the initramfs rebuild
ideapad_laptop still loads early. Post-reboot, `lsmod` confirms none
of the seven is loaded. Testing only against /dev/input/event2 (AT
Translated Set 2 keyboard), since event5/event6 paths are gone with
these modules blacklisted.

Working state (post-boot, pre-suspend):

  volume-up   Fx press -> MSC_SCAN 0xb0  KEY_VOLUMEUP
  volume-down Fx press -> MSC_SCAN 0xae  KEY_VOLUMEDOWN
  mute        Fx press -> MSC_SCAN 0xa0  KEY_MUTE

So event2 works normally without any of these modules — the EC is
translating Fx to the E0-extended media scancodes and atkbd is
delivering them as expected.

Broken state (after s2idle resume, ~21 min suspend):

  volume-up   Fx press -> MSC_SCAN 0x3d  KEY_F3
  volume-down Fx press -> MSC_SCAN 0x3c  KEY_F2
  mute        Fx press -> MSC_SCAN 0x3b  KEY_F1

Same machine, same kernel, same blacklist still in effect. The EC has
stopped translating Fx to media scancodes and is emitting raw F-key
scancodes (0x3b..0x3d = F1..F3).

Conclusion: the regression reproduces with ideapad_laptop,
lenovo_wmi_*, sparse_keymap, and platform_profile all absent. None of
them is in the code path that breaks. Matches your firmware/EC
hypothesis.

Attaching the two evtest captures (event2, --grab):
  evtest-blacklisted-working.txt
  evtest-blacklisted-broken.txt

Happy to run further tests — e.g. dynamic_debug on the acpi/ec path
across suspend/resume, `pm_test core/platform/processor` to narrow the
phase, or acpidump/ectool snapshots in both states. Let me know what
would help most.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-04-20 20:00 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 [this message]
2026-04-20 20:02 ` bugzilla-daemon
2026-04-20 20:02 ` bugzilla-daemon
2026-04-21 14:51 ` bugzilla-daemon
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-Wbo6XG4kdq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.