From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216516] s2ram freezes screen (Ryzen-5650U incl. Radeon GPU)
Date: Sun, 25 Sep 2022 09:29:40 +0000 [thread overview]
Message-ID: <bug-216516-2300-B4dmqaDHNo@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 #10 from kolAflash (kolAflash@kolahilft.de) ---
Created attachment 301870
--> https://bugzilla.kernel.org/attachment.cgi?id=301870&action=edit
kernel log for s2idle: v6.0-rc6 with CONFIG_AMD_PMC enabled
(In reply to Mario Limonciello (AMD) from comment #9)
> You're missing CONFIG_AMD_PMC.
Compiled with CONFIG_AMD_PMC.
Going to s2idle two times.
(first time just for a few seconds)
The good news:
With CONFIG_AMD_PMC in s2idle the screen doesn't freeze.
The bad news:
After less than 8 hours in s2idle the battery went from 60 % to 0 % !!!
That's why there's no second wakeup.
(system was down because battery was drained)
With S3 the battery will loose less than 5 % charge in the same time.
And the notebook is brand new. So there should be no battery degradation.
... just did another s2idle test and battery went from 67 % to 58 % in one
hour.
(In reply to Mario Limonciello (AMD) from comment #6)
> [...]
> 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.
I think you exaggerate a little.
I'm just enabling existing OEM code!
Also I wouldn't say this is patching the firmware, because it's just the ACPI
data, not the BIOS software.
Just changing the existing "if" statement.
See: comment #5
I'm pretty sure there's a way to enable this OEM code without recompiling the
ACPI data. Probably by setting the MSCE variable with a hidden BIOS option or
something else I haven't found yet.
--
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-25 9:29 UTC|newest]
Thread overview: 16+ 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
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 [this message]
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-2300-B4dmqaDHNo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox