From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU)
Date: Thu, 29 Sep 2022 23:52:15 +0000 [thread overview]
Message-ID: <bug-216516-215701-57xTkpWtTh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216516-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216516
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DOCUMENTED
--- Comment #27 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> Compiled with all patches from comment #14, 1) and 2).
OK, I also sent that new idlemask patch I suggested to the mailing list for the
future to make debugging easier.
https://patchwork.kernel.org/project/platform-driver-x86/patch/20220929215042.745-1-mario.limonciello@amd.com/
I don't have any evidence that the usleep_range() change helped in any way, so
I won't send that for now.
If you discover that is required for good battery life on your side let me know
and I'll cleanup a more proper variation of it to send out.
> Here are the first results.
OK so the idle mask doesn't "change" from one time to another in any unexpected
ways to me.
> [ 90.048438] PM: Triggering wakeup from IRQ 9
> [ 90.048801] PM: Triggering wakeup from IRQ 1
When you see two IRQs like this; it's a firmware bug as described in the other
report I mentioned above. HP will need to issue a new BIOS to fix this.
This is a laptop certified with Ubuntu (see
https://ubuntu.com/certified/202206-30367). You should contact HP support and
ask them for a BIOS fix.
> [ 332.466583] PM: Triggering wakeup from IRQ 9
When you're seeing these alone in the middle of the sleep it's because of the
EC GPE firing to do $something. In this case I believe it's the EC trying to
notify a new battery level. Due to the above bug I mentioned I think these
together will "prevent" it from going back to the deepest state.
> That workaround works very well! Thanks :-)
Sure. This is going to limit you quite a bit in terms of wakeup sources, but
IMO I think it's a worthwhile trade off for this problem. You should hopefully
be getting much better power consumption now over s2idle.
--
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:[~2022-09-29 23:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216516-215701@https.bugzilla.kernel.org/>
2022-09-26 18:49 ` [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU) bugzilla-daemon
2022-09-27 13:15 ` bugzilla-daemon
2022-09-27 18:00 ` bugzilla-daemon
2022-09-27 18:05 ` bugzilla-daemon
2022-09-27 18:07 ` bugzilla-daemon
2022-09-28 15:55 ` bugzilla-daemon
2022-09-28 16:29 ` bugzilla-daemon
2022-09-28 16:36 ` bugzilla-daemon
2022-09-28 16:57 ` bugzilla-daemon
2022-09-28 17:06 ` bugzilla-daemon
2022-09-28 23:45 ` bugzilla-daemon
2022-09-29 21:14 ` bugzilla-daemon
2022-09-29 23:29 ` bugzilla-daemon
2022-09-29 23:52 ` bugzilla-daemon [this message]
2022-09-30 0:37 ` bugzilla-daemon
2022-09-30 1:01 ` bugzilla-daemon
2022-09-30 10:38 ` bugzilla-daemon
2022-09-30 12:32 ` bugzilla-daemon
2022-09-30 15:50 ` bugzilla-daemon
2022-10-03 17:21 ` bugzilla-daemon
2022-10-12 17:39 ` bugzilla-daemon
2022-10-12 17:53 ` bugzilla-daemon
2022-10-12 18:04 ` bugzilla-daemon
2022-10-13 1:17 ` bugzilla-daemon
2022-09-23 2:05 [Bug 216516] New: " bugzilla-daemon
2022-09-23 2:15 ` [Bug 216516] " bugzilla-daemon
2022-09-23 7:23 ` bugzilla-daemon
2022-09-23 9:16 ` bugzilla-daemon
2022-09-23 12:13 ` bugzilla-daemon
2022-09-23 15:46 ` bugzilla-daemon
2022-09-23 15:52 ` bugzilla-daemon
2022-09-23 16:07 ` bugzilla-daemon
2022-09-23 18:33 ` bugzilla-daemon
2022-09-23 18:41 ` bugzilla-daemon
2022-09-25 9:29 ` bugzilla-daemon
2022-09-25 9:50 ` bugzilla-daemon
2022-09-25 23:02 ` bugzilla-daemon
2022-09-26 18:33 ` bugzilla-daemon
2022-09-26 18:49 ` bugzilla-daemon
2022-09-26 18:49 ` 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-216516-215701-57xTkpWtTh@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.