From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 221473] New: amd-pstate dynamic EPP regression on Ryzen 5 3600
Date: Wed, 06 May 2026 18:10:35 +0000 [thread overview]
Message-ID: <bug-221473-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221473
Bug ID: 221473
Summary: amd-pstate dynamic EPP regression on Ryzen 5 3600
Product: Power Management
Version: 2.5
Kernel Version: 7.1.0-rc2
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: stuartmeckle@gmail.com
CC: mario.limonciello@amd.com
Regression: Yes
Bisected e30ca6dd5345c5b8ba05f346a8e81105352fe571
commit-id:
Created attachment 310042
--> https://bugzilla.kernel.org/attachment.cgi?id=310042&action=edit
dmesg and config
amd-pstate dynamic EPP regression on Ryzen 5 3600
My CPU which normally boosts to 4.0GHz (PBO enabled) was stuck at 1.7GHz under
full load. Same result with CONFIG_X86_AMD_PSTATE_DYNAMIC_EPP set to either 'y'
or 'n'. I bisected to this commit:
commit e30ca6dd5345c5b8ba05f346a8e81105352fe571
Author: Mario Limonciello (AMD) <superm1@kernel.org>
cpufreq/amd-pstate: Add dynamic energy performance preference
Arch Linux
Linux version 7.1.0-rc2-00099-gadc1e5c6203c (stuart@romano) (gcc (GCC) 16.1.1
20260430, GNU ld (GNU Binutils) 2.46.0) #1 SMP PREEMPT_DYNAMIC Wed May 6
15:30:26 UTC 2026
Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F67 10/28/2025
Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
AMD Ryzen 5 3600 6-Core Processor
32GB DDR4 DRAM F4-3000C16-8GVRB
CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
CONFIG_X86_AMD_PSTATE=y
CONFIG_X86_AMD_PSTATE_DEFAULT_MODE=3
CONFIG_X86_AMD_PSTATE_DYNAMIC_EPP=y
CONFIG_X86_AMD_PSTATE_UT=m
==> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus <==
0
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_highest_perf <==
166
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_hw_prefcore <==
enabled
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_lowest_nonlinear_freq <==
1723944
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_prefcore_ranking <==
171
==> /sys/devices/system/cpu/cpu0/cpufreq/boost <==
1
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_avg_freq <==
1723944
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq <==
557747
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency <==
0
==>
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
<==
default performance balance_performance balance_power power custom
==> /sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference <==
performance
==> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus <==
0
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors <==
performance powersave
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq <==
1736801
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver <==
amd-pstate-epp
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor <==
powersave
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq <==
1723944
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed <==
<unsupported>
For comparison, here are the same settings on kernel 7.0.3-arch1-2:
==> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus <==
0
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_highest_perf <==
166
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_hw_prefcore <==
enabled
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_lowest_nonlinear_freq <==
1723944
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/amd_pstate_prefcore_ranking <==
171
==> /sys/devices/system/cpu/cpu0/cpufreq/boost <==
1
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_avg_freq <==
3656148
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq <==
557747
==> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency <==
0
==>
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
<==
default performance balance_performance balance_power power
==> /sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference <==
balance_performance
==> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus <==
0
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors <==
performance powersave
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq <==
3693566
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver <==
amd-pstate-epp
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor <==
powersave
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq <==
4208451
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq <==
1723944
==> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed <==
<unsupported>
--
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:[~2026-05-06 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 18:10 bugzilla-daemon [this message]
2026-05-07 20:36 ` [Bug 221473] amd-pstate dynamic EPP regression on Ryzen 5 3600 bugzilla-daemon
2026-05-07 20:53 ` 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-221473-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 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.