From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 220433] New: Regression on AMD pstate cannot control turbo boost after wake from suspend
Date: Mon, 11 Aug 2025 05:20:41 +0000 [thread overview]
Message-ID: <bug-220433-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220433
Bug ID: 220433
Summary: Regression on AMD pstate cannot control turbo boost
after wake from suspend
Product: Power Management
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: me@gzgz.dev
Regression: No
Somewhere between 6.12.37 and 6.13.3, after a wake from suspend,
`/sys/devices/system/cpu/cpufreq/boost` no longer correspond to whether my CPU
is boosting. Even though `/sys/devices/system/cpu/cpufreq/boost` reads 0, my
CPU is clearly still boosting judging from both fan speed/heat and `cpuinfo`:
======
analyzing CPU 12:
driver: amd-pstate
CPUs which run at the same hardware frequency: 12
CPUs which need to have their frequency coordinated by software: 12
maximum transition latency: 20.0 us
hardware limits: 400 MHz - 3.20 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 400 MHz and 3.20 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: 3.79 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
amd-pstate limits:
Highest Performance: 196. Maximum Frequency: 4.46 GHz.
Nominal Performance: 119. Nominal Frequency: 3.20 GHz.
Lowest Non-linear Performance: 41. Lowest Non-linear Frequency: 1.10 GHz.
Lowest Performance: 15. Lowest Frequency: 400 MHz.
Preferred Core Support: 1. Preferred Core Ranking: 196.
======
(the CPU's max freq is 3.20 GHz without turbo boost, with turbo boost it can
get up to 4.1 GHz)
I'm on `amd_pstate=passive`, not running in active mode because I want to
control the frequencies and turbo boost.
I'm trying to bisect but I failed to build both 6.13 and 6.13.1 for some reason
:(
System info:
Solus 4.7 Endurance x86_64
CPU: AMD Ryzen 7 5800H with Radeon Graphics
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2025-08-11 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 5:20 bugzilla-daemon [this message]
2025-08-11 8:27 ` [Bug 220433] Regression on AMD pstate cannot control turbo boost after wake from suspend bugzilla-daemon
2025-08-11 22:54 ` 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-220433-137361@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