From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220116] amd_pmc - Last suspend didn't reach deepest state
Date: Wed, 04 Jun 2025 17:07:26 +0000 [thread overview]
Message-ID: <bug-220116-215701-gUGg2TabGB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220116-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220116
--- Comment #11 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
Your new report looks "better" actually. I see you're getting into hardware
sleep each time. If you run a longer cycle (say 60s), I bet you get higher
residency too.
Is the keyboard "working" after you've resumed? With all the errors listed for
it:
atkbd serio0: Failed to deactivate keyboard on isa0060/serio0
atkbd serio0: Failed to enable keyboard on isa0060/serio0
atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to
access hardware directly.
Other observations:
* AMW0 notify only happens on the first cycle.
* Spurious ack events happen on all the cycles.
* You've added i8042.noreset and i8042.nomux to kernel command line.
I would say drop the kernel i8042 parameters and just turn off the wakeup for
u8042 and try to run a few 60s cycles and see how things look.
I'll let Armin comment on the AMW0 device from the acpidump.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching someone on the CC list of the bug.
next prev parent reply other threads:[~2025-06-04 17:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-220116-215701@https.bugzilla.kernel.org/>
2025-06-03 20:38 ` [Bug 220116] amd_pmc - Last suspend didn't reach deepest state bugzilla-daemon
2025-06-04 11:31 ` bugzilla-daemon
2025-06-04 11:32 ` bugzilla-daemon
2025-06-04 17:07 ` bugzilla-daemon [this message]
2025-06-04 17:53 ` bugzilla-daemon
2025-06-04 17:55 ` bugzilla-daemon
2025-06-04 18:15 ` bugzilla-daemon
2025-06-04 18:16 ` bugzilla-daemon
2025-06-04 18:29 ` bugzilla-daemon
2025-06-04 18:32 ` bugzilla-daemon
2025-06-04 19:07 ` bugzilla-daemon
2025-06-04 19:12 ` bugzilla-daemon
2025-06-05 10:58 ` bugzilla-daemon
2025-06-05 11:34 ` bugzilla-daemon
2025-06-05 17:32 ` bugzilla-daemon
2025-06-05 17:32 ` bugzilla-daemon
2025-06-05 17:39 ` bugzilla-daemon
2025-06-05 18:04 ` bugzilla-daemon
2025-06-11 6:10 ` bugzilla-daemon
2025-06-11 14:12 ` bugzilla-daemon
2025-06-11 15:19 ` bugzilla-daemon
2025-06-11 15:20 ` bugzilla-daemon
2025-06-11 15:56 ` bugzilla-daemon
2025-06-17 21:43 ` bugzilla-daemon
2025-06-18 5:15 ` 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-220116-215701-gUGg2TabGB@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.