All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 211791] AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency
Date: Sat, 13 Mar 2021 10:41:20 +0000	[thread overview]
Message-ID: <bug-211791-137361-jJD9wJiapI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211791-137361@https.bugzilla.kernel.org/>

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

Joshua (josh@sobo.red) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |josh@sobo.red

--- Comment #2 from Joshua (josh@sobo.red) ---
I'm still having an issue with frequencies being reported incorrectly. Here's a
thread for reference:
https://bbs.archlinux.org/viewtopic.php?pid=1961500#p1961500

I've updated to kernel version 5.11.6. If I watch /proc/cpuinfo, that seems to
be reporting somewhat accurately now. However, lscpu and most everything else
is still reporting inaccurately.

~ → uname -r
5.11.6-arch1-1
~ → lscpu | grep MHz
CPU MHz:                         3400.000
CPU max MHz:                     7228.3198
CPU min MHz:                     2200.0000
~ → geekbench --sysinfo | grep -E "Processor Information|Name|Base Frequency"
Processor Information
  Name                          AMD Ryzen 9 5950X
  Base Frequency                6.92 GHz

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

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

  parent reply	other threads:[~2021-03-13 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  1:41 [Bug 211791] New: AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency bugzilla-daemon
2021-02-16  1:41 ` [Bug 211791] " bugzilla-daemon
2021-03-13 10:41 ` bugzilla-daemon [this message]
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-jJD9wJiapI@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.