From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219110] amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume
Date: Mon, 26 Aug 2024 17:23:21 +0000 [thread overview]
Message-ID: <bug-219110-137361-w22G8Auoui@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219110-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219110
--- Comment #8 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
To me this sounds like a firmware bug. I can't seem to reproduce it.
I just had a try on an AMD reference system with a "AMD Ryzen 5 7640U w/ Radeon
760M Graphics" running PhoenixPI-FP8-FP7 1.1.0.2a.
For my kernel I used 6.11-rc4.
For userspace it's Ubuntu 24.04 userspace.
I ran "mpv bbb_sunflower_2160p_60fps_normal.mp4".
I then SSH'ed in from another system and looked at the average PPT value
reported by 'sensors'. It stay in the 8W range the whole time. Here was a
snapshot:
amdgpu-pci-c200
Adapter: PCI adapter
vddgfx: 900.00 mV
vddnb: 759.00 mV
edge: +39.0°C
PPT: 6.00 W (avg = 8.14 W)
I then stopped the video, suspended and started it back up and looked again.
Same ballpark.
You might look at the value for the MSR's that amd-pstate uses by using 'rdmsr
MSR' to see if they change in any notable way before or after suspend.
#define MSR_AMD_CPPC_CAP1 0xc00102b0
#define MSR_AMD_CPPC_ENABLE 0xc00102b1
#define MSR_AMD_CPPC_CAP2 0xc00102b2
#define MSR_AMD_CPPC_REQ 0xc00102b3
#define MSR_AMD_CPPC_STATUS 0xc00102b4
The most important one to check is MSR_AMD_CPPC_REQ.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-08-26 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 17:40 [Bug 219110] New: amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume bugzilla-daemon
2024-07-30 17:56 ` [Bug 219110] " bugzilla-daemon
2024-07-30 18:09 ` bugzilla-daemon
2024-07-30 18:29 ` bugzilla-daemon
2024-07-30 18:31 ` bugzilla-daemon
2024-08-23 18:07 ` bugzilla-daemon
2024-08-23 19:54 ` bugzilla-daemon
2024-08-23 19:56 ` bugzilla-daemon
2024-08-26 17:23 ` bugzilla-daemon [this message]
2024-08-26 18:14 ` bugzilla-daemon
2024-08-26 18:19 ` bugzilla-daemon
2024-08-26 18:22 ` bugzilla-daemon
2024-08-26 18:27 ` 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-219110-137361-w22G8Auoui@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).