[Bug 217931] amd-pstate lacks crucial features: CPU frequency and boost control

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=217931

--- Comment #27 from AlexDeLorenzo.dev (alex.delorenzo@gmail.com) ---
(In reply to Mario Limonciello (AMD) from comment #16)
> When you say getting stuck in lowest supported frequency does it resemble
> bug 218305 perhaps?

Looking at bug 218305, I haven't noticed if the issue is triggered by
suspend/resume or restart cycles. I'm on a laptop that regularly goes through
several days of use before being rebooted, so it's possible. I'll keep an eye
out to see if that's related. From what I experienced, the issue would occur
while using the machine for a few hours, and the issue would "fix" itself upon
a suspend/resume or restart.

As far as similarities to bug 218305, I'm also running a Ryzen APU (on Zen 3
and not 4) on an HP Dev One, which I believe is a modified Elitebook 845 G8 or
G9. However, I've been told by HP support and the System76 team they outsourced
the project to that the firmware on the Dev One was custom written for the
project and unrelated to the standard Elitebook line's firmware.

I also use `ryzenadj` to set STAPM, PPT FAST and SLOW limits. Like in bug
218305, I also leave my laptop plugged in the majority of the time.

When I experience the issue again, I'll look at more diagnostics to see if it's
like bug 218305. 

> What is your CPU scaling governor when it happened? 

I use the amd-pstate-epp driver in active mode, and alternate between the
powersave and performance governors depending on whether I'm on battery power
or not, and delegate that switch to power-profiles-daemon versus using sysfs.

It's happened while on AC power, so it is likely I was using the performance
governor when I experienced the issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.