From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215800] amd-pstate does not allow to set arbitrary maximum CPU frequency above 2200MHz for a desktop Zen 3 CPU
Date: Tue, 12 Apr 2022 08:50:44 +0000 [thread overview]
Message-ID: <bug-215800-137361-U8EFvraSCi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215800-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215800
--- Comment #10 from Artem S. Tashkinov (aros@gmx.com) ---
Even restoring scaling_max_freq by setting it to cpuinfo_max_freq doesn't fix
the issue.
Again, I'm repeating what I already said in the original bug report.
> For my Ryzen 7 5800X I've tried (under root) numbers from 600 000 to 2 200
> 000 and they all work:
>
> echo $number | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
>
> However anything above 2 200 000 instead makes **the CPU stay at 2.2GHz**.
Don't mind scaling_max_freq, it's scaling_cur_freq that never exceeds 2.2GHz!
--
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-04-12 10:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 1:16 [Bug 215800] New: amd-pstate does not allow to set arbitrary maximum CPU frequency above 2200MHz for a desktop Zen 3 CPU bugzilla-daemon
2022-04-05 1:31 ` [Bug 215800] " bugzilla-daemon
2022-04-11 7:22 ` bugzilla-daemon
2022-04-11 13:33 ` bugzilla-daemon
2022-04-11 16:28 ` bugzilla-daemon
2022-04-12 3:25 ` bugzilla-daemon
2022-04-12 4:15 ` bugzilla-daemon
2022-04-12 7:25 ` bugzilla-daemon
2022-04-12 7:26 ` bugzilla-daemon
2022-04-12 8:46 ` bugzilla-daemon
2022-04-12 8:50 ` bugzilla-daemon [this message]
2022-04-13 6:50 ` bugzilla-daemon
2022-04-13 7:06 ` bugzilla-daemon
2022-04-13 7:12 ` bugzilla-daemon
2022-04-13 9:41 ` bugzilla-daemon
2022-05-17 8:07 ` bugzilla-daemon
2022-05-17 8:25 ` bugzilla-daemon
2022-05-19 2:34 ` bugzilla-daemon
2022-05-19 2:41 ` bugzilla-daemon
2022-06-12 14:34 ` bugzilla-daemon
2022-06-12 14:54 ` bugzilla-daemon
2022-06-12 15:04 ` bugzilla-daemon
2022-06-13 11:16 ` bugzilla-daemon
2022-07-05 1:14 ` bugzilla-daemon
2022-07-06 22:10 ` bugzilla-daemon
2022-09-19 12:08 ` bugzilla-daemon
2022-10-12 2:36 ` bugzilla-daemon
2023-07-07 13:27 ` bugzilla-daemon
2023-07-07 13:30 ` bugzilla-daemon
2023-07-07 13:35 ` bugzilla-daemon
2023-07-07 14:51 ` bugzilla-daemon
2023-07-07 15:07 ` bugzilla-daemon
2023-07-07 15:23 ` bugzilla-daemon
2023-08-08 17:58 ` bugzilla-daemon
2023-09-15 10:22 ` bugzilla-daemon
2023-09-20 11:07 ` 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-215800-137361-U8EFvraSCi@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.