From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU)
Date: Fri, 23 Sep 2022 15:52:31 +0000 [thread overview]
Message-ID: <bug-216516-2300-471SLrdy9R@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216516-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216516
--- Comment #6 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> Tested s2idle with the openSUSE-15.4 stock kernel v5.14 and it consumed
> MASSIVELY more power than S3.
TONS and TONS of fixes have landed for s2idle since then. 5.15.y is the first
kernel that you should be confident to use it.
Please re-test with s2idle using 6.0-rc6. If that doesn't work let's fix it.
> Is "echo s2idle > /sys/power/mem_sleep" equivalent to enabling s2idle via
> ACPI?
So I wouldn't need to reboot to change ACPI for testing s2idle.
No, on AMD systems there are Pre-OS changes that occur when you use modern
standby/s2idle. If you use s2idle when the firmware is configured for S3 you
will never get into the proper power state.
> Actually S3 is very well hidden. I don't know a way to enable it directly in
> the BIOS. But it's in the ACPI tables.
As you're patching the firmware this is not a regression. It takes more to
properly enable S3 in Pre-OS code than changing a variable evaluated by the
Linux kernel's ACPI interpreter..
Thorsten - this is not a regression, patching the BIOS like this is completely
off the beating path. We can't possibly support S3 in Linux if the OEM doesn't
offer it in their BIOS.
kolAflash - Let's focus on fixing s2idle for your system. With 6.0-rc6 and an
"unpatched" BIOS let's see if you have any remaining problems with it.
--
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-23 15:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 2:05 [Bug 216516] New: s2ram freezes screen (Ryzen-5650U incl. Radeon GPU) 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 [this message]
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
[not found] <bug-216516-215701@https.bugzilla.kernel.org/>
2022-09-26 18:49 ` 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
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-2300-471SLrdy9R@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.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.