New: lscpu reporting incorrect CPU current frequencies
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: [email protected]
Reporter: [email protected]
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
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 217597] lscpu reporting incorrect CPU current frequencies
https://bugzilla.kernel.org/show_bug.cgi?id=217597
Keyon ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Bisected commit-id| |f3eca381bd49
Priority|P3 |P2
Status|NEW |ASSIGNED
CC| |[email protected]
Assignee|[email protected] |[email protected]
Regression|No |YesSignature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.