From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215938] amd-pstate ignoring scaling_max_freq after waking from suspend
Date: Wed, 06 Jul 2022 06:00:40 +0000 [thread overview]
Message-ID: <bug-215938-137361-x327VlpRUc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215938-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215938
--- Comment #20 from a@annel.in ---
Guys, have you get amd_pstate working with schedutil governor?
On my system, it completely ignores frequency limits and boost state.
```
~ sudo cpupower frequency-set -g schedutil -d 1200MHz -u 1600MHz
~ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 400 MHz - 1.90 GHz
available cpufreq governors: ondemand performance schedutil
current policy: frequency should be within 1.20 GHz and 1.60 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.60 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.51 GHz.
AMD PSTATE Nominal Performance: 70. Nominal Frequency: 1.90 GHz.
AMD PSTATE Lowest Non-linear Performance: 41. Lowest Non-linear Frequency:
1.11 GHz.
AMD PSTATE Lowest Performance: 15. Lowest Frequency: 400 MHz.
```
Other governors (ondemand/performance) works as intended.
Is it a bug or something else?
--
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:[~2022-07-06 6:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:09 [Bug 215938] New: amd-pstate ignoring scaling_max_freq after waking from suspend bugzilla-daemon
2022-05-04 6:16 ` [Bug 215938] " bugzilla-daemon
2022-05-04 13:46 ` bugzilla-daemon
2022-05-20 8:37 ` bugzilla-daemon
2022-05-20 9:55 ` bugzilla-daemon
2022-05-20 9:56 ` bugzilla-daemon
2022-05-20 9:57 ` bugzilla-daemon
2022-05-31 2:55 ` bugzilla-daemon
2022-05-31 7:32 ` bugzilla-daemon
2022-06-09 14:59 ` bugzilla-daemon
2022-06-09 15:00 ` bugzilla-daemon
2022-06-09 15:15 ` bugzilla-daemon
2022-06-10 17:03 ` bugzilla-daemon
2022-06-11 3:33 ` bugzilla-daemon
2022-06-11 4:11 ` bugzilla-daemon
2022-06-13 1:56 ` bugzilla-daemon
2022-06-13 16:25 ` bugzilla-daemon
2022-06-29 15:35 ` bugzilla-daemon
2022-07-05 1:16 ` bugzilla-daemon
2022-07-05 7:36 ` bugzilla-daemon
2022-07-05 9:28 ` bugzilla-daemon
2022-07-06 6:00 ` bugzilla-daemon [this message]
2022-07-07 22:36 ` bugzilla-daemon
2025-04-04 13:09 ` bugzilla-daemon
2025-04-04 13:36 ` 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-215938-137361-x327VlpRUc@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.