From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217597] New: lscpu reporting incorrect CPU current frequencies
Date: Mon, 26 Jun 2023 17:44:45 +0000 [thread overview]
Message-ID: <bug-217597-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217597
Bug ID: 217597
Summary: lscpu reporting incorrect CPU current frequencies
Product: Power Management
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: yang.jie@linux.intel.com
Regression: No
From Linux kernel v5.18 on, we notice that the cur_freq of CPU cores are not
correct from time to time, the cur_freq could even be > the maximum ones, as
below:
# lscpu -e
CPU SOCKET CORE ONLINE MAXMHZ MINMHZ MHZ
0 0 0 yes 4200.0000 800.0000 4200.0000
1 0 0 yes 4200.0000 800.0000 4200.0000
2 0 1 yes 4200.0000 800.0000 4200.0000
3 0 1 yes 4200.0000 800.0000 3600.0000
4 0 2 yes 3000.0000 800.0000 1732.7410
5 0 3 yes 3000.0000 800.0000 1685.1310
6 0 4 yes 3000.0000 800.0000 1715.8409
7 0 5 yes 3000.0000 800.0000 3600.0000
8 0 6 yes 3000.0000 800.0000 1716.0790
9 0 7 yes 3000.0000 800.0000 3600.0000
10 0 8 yes 3000.0000 800.0000 1603.4210
11 0 9 yes 3000.0000 800.0000 3600.0000
Here, the cur_freq of core 7, 9, 11 looks incorrect.
With v5.17, we get the correct ones as below:
# lscpu -e
CPU SOCKET CORE ONLINE MAXMHZ MINMHZ MHZ
0 0 0 yes 4200.0000 800.0000 4199.8760
1 0 0 yes 4200.0000 800.0000 1444.7260
2 0 1 yes 4200.0000 800.0000 1554.8870
3 0 1 yes 4200.0000 800.0000 1577.0760
4 0 2 yes 3000.0000 800.0000 1800.5040
5 0 3 yes 3000.0000 800.0000 1767.4659
6 0 4 yes 3000.0000 800.0000 1800.3500
7 0 5 yes 3000.0000 800.0000 1600.4460
8 0 6 yes 3000.0000 800.0000 1597.0200
9 0 7 yes 3000.0000 800.0000 1681.0930
10 0 8 yes 3000.0000 800.0000 1700.8730
11 0 9 yes 3000.0000 800.0000 1785.5389
12 0 10 yes 2100.0000 800.0000 1202.8650
13 0 11 yes 2100.0000 800.0000 1597.0270
--
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:[~2023-06-26 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 17:44 bugzilla-daemon [this message]
2023-06-26 17:57 ` [Bug 217597] lscpu reporting incorrect CPU current frequencies 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-217597-137361@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox