X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU)
Date: Tue, 27 Sep 2022 18:00:54 +0000	[thread overview]
Message-ID: <bug-216516-215701-XFDxDC3RfN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216516-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216516

--- Comment #16 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> And indeed, power usage went down to 2 % per hour! :-)
> So should I open a bug for s2idle in openSUSE instead!?

Eventually; yes.  But I think you need to further root cause why this is
happening in openSUSE before opening a bug asking them to change a policy or
userspace software.  Narrow down which wakeup trigger is causing the spurious
events, and confirm that in Ubuntu 22.10 that wakeup trigger is disabled.

> But I couldn't get the s2idle power usage significantly below 2 % per hour. 

When the power consumption is at this level in your test environment, can you
please double check with amd_pmc.dyndbg enabled matches a high percentage of
the time you were suspended? 

> Tomorrow I'm planning to do the debugging steps described by Mario in comment
> #14.
> So maybe with that the consumption can be brought further down for s2idle.

Yeah let's see if that series of patches changes anything.  Like I suggested on
the otherwise unpatched configuration you should also correlate the number you
get for time (in microseconds) you were in the deepest state against the amount
of time you were in suspend.

> But I also still the idea of using S3 (especially because of the very low
> power consumption).
> So I'd still like to see a fix for the commit initially mentioned. 
> Or maybe not a fix, but a kernel command line option to disable that
> behavior.

s2idle should be less power consumption than S3 on AMD SoCs and also have a
much faster suspend and wakeup process.
I suspect what is happening here is that HP's EC is issuing wakeups too
frequently and causing a wasted power consumption.  Let's see the information
from my other debugging steps and proposed patch if they help.

For your request I sent up https://patchwork.freedesktop.org/patch/504971/ for
discussion.  You can feel free to leave a Tested-by: comment there if that
works for you.

-- 
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:[~2022-09-27 18:01 UTC|newest]

Thread overview: 24+ 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 [this message]
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
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

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-XFDxDC3RfN@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