From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 211791] New: AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency
Date: Tue, 16 Feb 2021 01:41:11 +0000 [thread overview]
Message-ID: <bug-211791-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=211791
Bug ID: 211791
Summary: AMD CPU /proc/cpuinfo reported max potential boost
frequency instead of actual operating frequency
Product: Power Management
Version: 2.5
Kernel Version: 5.11.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: me@rin.cat
Regression: No
Created attachment 295305
--> https://bugzilla.kernel.org/attachment.cgi?id=295305&action=edit
/proc/cpuinfo log
Overview:
The /proc/cpuinfo reported wrong operating frequency, where my AMD 3900X
shows over 6 GHz when idle.
This may be caused by the 5.11 AMD CPU frequency / CPPC fix.
Steps to Reproduce:
cat /proc/cpuinfo
or
lscpu
Actual Results:
Reported operating frequency far beyond actual. (Over 6 GHz)
Expected Results:
Reported actual operating frequency.
Build Date & Hardware:
Build 2021-02-15 on Gentoo
CPU: AMD Ryzen 9 3900X 12-Core Processor
AMD AGESA: ComboAM4PIV2 1.2.0.0
CPPC: enabled
Additional Information:
/sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq reported correct
frequency.
--
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:[~2021-02-16 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 1:41 bugzilla-daemon [this message]
2021-02-16 1:41 ` [Bug 211791] AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency bugzilla-daemon
2021-03-13 10:41 ` bugzilla-daemon
2021-04-20 8:55 ` bugzilla-daemon
2021-04-20 10:20 ` Huang Rui
2021-04-20 10:20 ` bugzilla-daemon
2021-04-30 18:22 ` bugzilla-daemon
2021-05-14 2:27 ` bugzilla-daemon
2022-05-06 19:10 ` 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-211791-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.