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: Sun, 26 Apr 2026 02:59:20 +0000 [thread overview]
Message-ID: <bug-221383-215701-zF5Yv3z26w@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221383-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221383
Daniel Gibson (metalcaedes@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #309946|0 |1
is obsolete| |
--- Comment #42 from Daniel Gibson (metalcaedes@gmail.com) ---
Created attachment 309957
--> https://bugzilla.kernel.org/attachment.cgi?id=309957&action=edit
patch that adds sleeping for 2.5s before suspend for IdeaPad Slim 3 devices or
when setting delay_suspend=1
Now I'm using the existing quirks mechanism (fwbugs_list[]) to enable the
workaround on most devices that identify as LENOVO IdeaPad Slim 3.
It can also be explicitly enabled or disabled with a module argument:
amd_pmc.delay_suspend=1
to enable, 0 to disable (even if device is detected as affected) or -1 (the
default) to let fwbugs_list[] decide.
If this is used, a message like "Delaying suspend by 2.5s to avoid platform
bug" or "Delaying suspend by 2.5s because delay_suspend=1" is printed to dmesg,
so one can easily checked if it is active or not.
@Sindre: Please test this, and please disable any other workarounds for this
issue that you may have on your system while testing :)
--
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-26 2:59 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
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 [this message]
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-zF5Yv3z26w@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.