CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked

Bug #379873 reported by BearTM
98
This bug affects 19 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

The reported frequencies of an overclocked Core 2 Duo are incorrect. Benchmarking and performance testing can confirm that the CPU is running at the overclocked speeds, but the values reported through cpuinfo are the standard stock speeds.

CPU has been overclocked from stock 3.00GHz to 3.60GHz. This can be confirmed through dmidecode (output attached). The issue is that cpuinfo (and related utilities) all report the stock CPU speeds instead. This is only a visual/reporting issue. The CPU is still throttling correctly, and the speed is correct as per the overclocking ratio.

i.e. (tested and confirmed in benchmarks & Bogomips)
Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed
Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed

There are a few reports of this in the Ubuntu forums, however no resolution had been found. I have updated the BIOS on my motherboard (ASUS P5Q) to the latest available, with no changes. All other BIOS options are per standard - allowing CPU throttling/etc.

Bug #132403 makes reference to this similar issue, but this is not a BIOS problem, only a reporting problem.

Compare:
cat /proc/cpuinfo
cpufreq-info
dmidecode --type processor

Only dmidecode is reporting the correct CPU speed as set in the BIOS.

Regards,
    Robert.
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: cpufrequtils 006-2
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_NZ.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
BearTM (beartm) wrote :
Revision history for this message
BearTM (beartm) wrote :
Revision history for this message
BearTM (beartm) wrote :
Revision history for this message
BearTM (beartm) wrote :

Apologies - neglected to report on Ubuntu/kernel version information:

Description: Ubuntu 9.04
Release: 9.04
Linux thundercat 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

All latest updates/patches as available on May 24, 2009

Revision history for this message
James Snyder (jbsnyder-fanplastic) wrote :
Download full text (3.7 KiB)

I'm experiencing the same behavior:

Linux erlanger 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux

Ubuntu 9.10 64-bit. Core2 Quad Q8400.

# dmidecode 2.9
SMBIOS 2.4 present.

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
 Socket Designation: LGA775
 Type: Central Processor
 Family: Other
 Manufacturer: Intel
 ID: 7A 06 01 00 FF FB EB BF
 Version: Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
 Voltage: 1.3 V
 External Clock: 402 MHz
 Max Speed: 3800 MHz
 Current Speed: 3216 MHz
 Status: Populated, Enabled
 Upgrade: Socket LGA775
 L1 Cache Handle: 0x0005
 L2 Cache Handle: 0x0006
 L3 Cache Handle: 0x0007
 Serial Number: To Be Filled By O.E.M.
 Asset Tag: To Be Filled By O.E.M.
 Part Number: To Be Filled By O.E.M.

erlanger% cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips : 6400.55
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips : 6399.80
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
stepping : 10
cpu MHz : 2664.000
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips : 6399.76
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
stepping ...

Read more...

Revision history for this message
John Kuang (xiphosurus) wrote :

I have experienced this with 2 overclocked processors. The current one is an Intel E3300, stock is 2.5GHz (200*12.5). I pushed the fsb from 200 to 300, giving 3.75GHz (300*12.5). However, the cpu scaling shows 3.33 2.67 2.13 1.6 GHz. I'm guessing the standard stock speeds it is adhering to are based on 266 fsb. 266*12.5=3.33, 266*10=2.67, 266*8=2.13, 266*6=1.6.

"cat /proc/cpuinfo" & "cpufreq-info" show the wrong frequecies.
"dmidecode --type processor" shows it at 3.75GHz all the time, no matter which frequency was selected in CPU Frequency Scaling Monitor.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
BearTM (beartm) wrote :

Yes, the problem is still the same under Lucid - all latest updates:

Linux thundercat 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59 UTC 2010 x86_64 GNU/Linux

Still the same machine and same processor ... have upgraded throughout and no change.
 9.10 full reinstall
10.04 synaptic upgrade

CPU has been overclocked from stock 3.00GHz to 3.60GHz.
This can be confirmed through dmidecode (output attached).
cpuinfo (and related utilities) all report the stock CPU speeds instead.

This is only a visual/reporting issue. The CPU is still throttling correctly, and the speed is correct as per the overclocking ratio.

i.e. (tested and confirmed in benchmarks & Bogomips)
Reported 2.00Ghz = (3.6/3.0 * 2.0) = 2.40GHz True Clock Speed
Reported 3.00Ghz = (3.6/3.0 * 3.0) = 3.60GHz True Clock Speed

Fully up to date BIOS, (ASUS P5Q) - BIOS options standard except for overclock.

Output of dmidecode and cpuinfo attached.

Regards,
    Robert.

Revision history for this message
BearTM (beartm) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thanks for the reply
Can you please run in a terminal
apport-collect -p cpufrequtils 379873

affects: ubuntu → cpufrequtils (Ubuntu)
Revision history for this message
BearTM (beartm) wrote :

Ran the command:
- Authorised apport-collect to access LaunchPad

Output of command (for reference)

robert@thundercat:~$ apport-collect -p cpufrequtils 379873
The authorization page:
   (https://edge.launchpad.net/+authorize-token?oauth_token=858h97qhLdpKlW3VJzKD&allow_permission=WRITE_PRIVATE)
should be opening in your browser. After you have authorized
this program to access Launchpad on your behalf you should come
back here and press <Enter> to finish the authentication process.
Created new window in existing browser session.

Package cpufrequtils not installed and no hook available, ignoring
robert@thundercat:~$

Should I install cpufrequtils first? At present they have not been installed.

Cheers,
    Robert.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Yes, then retry if now the value are correct.
I was convinced that it was installed by default.

Revision history for this message
BearTM (beartm) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
BearTM (beartm) wrote :

Checked the output of:

cat /proc/cpuinfo - (Same as attached)
dmidecode - (Same as attached)
cpufreq-info (Output below)

---

root@thundercat:~# cpufreq-info
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 3.00 GHz
  available frequency steps: 3.00 GHz, 2.67 GHz, 2.34 GHz, 2.00 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 2.00 GHz and 3.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
  cpufreq stats: 3.00 GHz:1.52%, 2.67 GHz:0.04%, 2.34 GHz:0.03%, 2.00 GHz:98.41% (250583)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 2.00 GHz - 3.00 GHz
  available frequency steps: 3.00 GHz, 2.67 GHz, 2.34 GHz, 2.00 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 2.00 GHz and 3.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
  cpufreq stats: 3.00 GHz:1.67%, 2.67 GHz:0.03%, 2.34 GHz:0.04%, 2.00 GHz:98.26% (226133)
root@thundercat:~#

Hope this helps,
   Robert.

Changed in cpufrequtils (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
flar (asegaert) wrote :

This affects both of my computers, exactly as described in the first post.

Athlon 64 x2 4000 on Asus M2N-E motherboard running Lucid 32-bit
actual clock: 2362MHz
reported: 1000-2100Mhz (frequency scaling enabled in bios)
reported: 2362MHz (frequency scaling disabled in bios)

Phenom II x2 555BE on Gigabyte ga-ma785gm-us2h running Lucid 64-bit
actual clock: 3750MHz
reported: 800-3000MHz (frequency scaling enabled in bios)
reported: 3750MHz (frequency scaling disabled in bios)

Benchmarks confirm that this is only a reporting problem, both machines are actually running at higher speed than is reported when frequency scaling (Cool'N'Quiet) is enabled in bios.

Although everything seems to work fine, it would be nice if someone paid attention to this bug as it was a source of confusion for me (and probably others) and there is little documentation.

Revision history for this message
eZFlow (breakdevize) wrote :

confirmed. overclocked intel does not scale down with intel speedstep so it gets pretty hot with max speed all the time. also it displays the wrong speed (stock)

Revision history for this message
flar (asegaert) wrote :

Just to be clear, on my AMD systems, frequency scaling does work if "Cool'N'Quiet" is enabled in the BIOS, however the wrong speeds are reported.

Revision history for this message
Florian Schröck (mael-reverted) wrote :

i have the same issue
Intel Core 2 Quad Q9450 2,6 GHz overclocked to 3,2 Ghz

Changed in cpufrequtils (Ubuntu):
status: Confirmed → Opinion
Revision history for this message
BearTM (beartm) wrote :

I can absolutely verify and confirm that I get the same results as everyone in this thread:

Whether or not the CPU is running at 3.0GHz or is overclocked to 3.6GHz, the reported speed always remains 3.0Ghz.

The output of both dmidecode and by checking the actual processing speed with any application (bogomips), shows the exact overclocking ratio when compared to stock - as expected.

While it is only a reporting issue, as the CPU performance is correct - it does mean that I'm (always) multiplying the actual CPU speeds by 1.2 (3.6/3.0 GHz) for any performance calculations I might be doing.

The probable issue here is that dmidecode is collecting the correct bus overclocking information from the BIOS, and using that in the calculations; whereas cpufrequtils is either only collecting the stock information, or is defaulting to a standardised set of values; if for some reason the true information is unavailable (BIOS issues?). (ASUS P5Q Motherboard)

I have to say ... "OPINION" is actually an interesting (and can be quite useful) project status, however, I can absolutely "CONFIRM" this as an issue, and am available for any further testing or analysis.

Revision history for this message
Miguel Guedes (migdsb) wrote :

Suffering from this issue since ever I upped the BCLK frequency of my i7 930 -- the reported CPU freq does not reflect the actual Mobo settings (CPU-Z on Windows does, for instance.)

Also, I'm with BearTM on this one. IMHO, this issue shouldn't be filed under "OPINION" but rather under "CONFIRMED" given the proof that has been produced so far. BTW, I'm refraining from attaching dumps and whatnot as I don't think I'd add anything new.

Revision history for this message
Lasse Kärkkäinen (tronic+mb48) wrote :

Confirming this issue and switching status as per comments by others: the CPU frequency is certainly not a matter of opinion. Also changing it to affect the kernel, as that is where the problem lies (/proc/cpuinfo displays incorrect information). It seems to have nothing to do with frequency scaling utilities.

For the record, this is a regression and earlier (less than a year ago, I think) correct frequencies were displayed. It also affects Fedora.

affects: cpufrequtils (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Opinion → Confirmed
Revision history for this message
sqr163 (sqr163) wrote :

My Ubuntu affected with this issue too: 10.04 Lucid, kernel 2.6.32-30, Intel E6600 overclocked from 2.4GHz to 3.4GHz. I have windows XP installed on the same PC, and frequency scaling/reporting works fine (for example tools like cpuZ, OCCT, speedFan show correct frequency values).

Looks like wrong implementation of Intel SpeedStep in recent linux kernel (?).

Revision history for this message
RarSa (rarsa) wrote :

It also affects Debian test.

So it seems an upstream issue.

- If I set the CPU/HT reference clock at 200 MHz with a 16.5 ratio, it reports properly as 3.3 GHz max
- If I change CPU/HT reference clock to 234 MHz with a 14 ratio it reports the max frequency as 2.8 GHz eventhough it should be 3276 MHz.

Revision history for this message
penalvch (penalvch) wrote :

BearTM, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one at the top) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
John Kuang (xiphosurus) wrote :

I can confirm this bug is still exactly as described in 13.04. I may not have the latest kernel, but nothing has changed since the last activity in 2011, so this definitely is still a confirmed bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

John Kuang, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Daniel Forsberg (daniel-forsberg1) wrote :

This is still broken though... :-/

Revision history for this message
penalvch (penalvch) wrote :

Daniel Forsberg, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Uumak (uumak-tokabi-01) wrote :

Is this problem unsolvable?
Now this issue is almost 5 years old and it haven't been solved yet. Nothing changed, if you are overclocking, you can just displaying the stock frequencies, or with the command dmidecode --type processor
the maximum frequency can be displayed, or under Wine with Windows software (Aida, CPU-Z).
I have also overclocked my CPU, and I can't now display correct frequencies, just the stock (under Windows the frequency displaying is working properly).

Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
no longer affects: linux (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
penalvch (penalvch) wrote :

Uumak, please do not add stray bug tasks to this report. If you have a bug in another distro, please report it to their tracker directly. Despite this, if you have a bug in Ubuntu, and so your hardware and problem may be tracked, please feel free to file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
affects: linux (openSUSE) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
tags: removed: apport-collected cpufreq cpufreq-info cpuinfo dmidecode
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
RecceDG (reccedg) wrote :

See: http://www.gskill.us/forum/showthread.php?t=13415

After following the instructions from the RAM support tech:

- Change CPU bus to 233 from 200
- Change CPU multiplier to restore stock clock (actually a slight overclock)
- Change DRAM voltage from 1.5 to 1.6
- Increase CPU-NB voltage by 0.1V to 1.225v
- Manually input RAM timings

The BIOS reports everything took, but Ubuntu 14.04 is reporting a CPU processor speed of 2.8 Ghz and RAM speed of 1600 Mhz

See any of the Phoronix benchmarks posted there for evidence.

As far as I can tell, the CPU is running at the higher clock, but Ubuntu is mis-reporting.

Changed in linux (Ubuntu):
status: Expired → Confirmed
RecceDG (reccedg)
tags: added: apport-collected cpufreq cpufreq-info cpuinfo dmidecode
Revision history for this message
penalvch (penalvch) wrote :

RecceDG, it would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

tags: removed: apport-collected cpufreq cpufreq-info cpuinfo dmidecode
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Chris Placzek (chris-placzek) wrote :

Just want to chime in here. I have this problem as well. I have had it on several motherboards, several CPUs, and every version of Ubuntu and Debian I have had. I am currently on Lubuntu 16.04 with kernel 4.4.0-78 and this issue persists.

My CPU has a stock speed of 3166MHz on a 1333MHz bus. If I set my bus to 1600MHz, which runs the CPU at 3800MHz, everything reports CPU speed correctly. However, if I run my bus speed anywhere in between 1333MHz and 1600MHz, the CPU speed is *not* correctly reported.

Revision history for this message
vagrale (vagrale) wrote :
Download full text (3.9 KiB)

Same problem.

:~$ uname -a
Linux vagrale-desktop 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 17:59:49 UTC 2017 i686 athlon i686 GNU/Linux

:~$ sudo dmidecode -t processor | grep Speed
 Max Speed: 2700 MHz
 Current Speed: 3052 MHz

:~$ dmesg | grep MHz
[ 0.000000] tsc: Detected 3033.770 MHz processor
[ 1.955784] tsc: Refined TSC clocksource calibration: 3033.664 MHz

:~$ lscpu | grep MHz
CPU MHz: 1500.000
CPU max MHz: 2700,0000
CPU min MHz: 800,0000

:~$ cpupower -c all frequency-info
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 4.0 us
  hardware limits: 800 MHz - 2.70 GHz
  available frequency steps: 2.70 GHz, 2.10 GHz, 1.50 GHz, 800 MHz
  available cpufreq governors: conservative ondemand userspace powersave performance
  current policy: frequency should be within 800 MHz and 2.70 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.10 GHz (asserted by call to kernel)
  boost state support:
    Supported: no
    Active: no

analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 4.0 us
  hardware limits: 800 MHz - 2.70 GHz
  available frequency steps: 2.70 GHz, 2.10 GHz, 1.50 GHz, 800 MHz
  available cpufreq governors: conservative ondemand userspace powersave performance
  current policy: frequency should be within 800 MHz and 2.70 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.70 GHz (asserted by call to kernel)
  boost state support:
    Supported: no
    Active: no

:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 6
model name : AMD Athlon(tm) X2 215 Processor
stepping : 2
microcode : 0x10000c7
cpu MHz : 1500.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid eagerfpu pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs : tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs
bogomips : 6067.54
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor : 1
vendor_id : AuthenticAMD
cpu family : 16
model : 6
model name : AMD Athlon(tm) X2 215 Processor
stepping : 2
microcode : 0x10000c7
cpu MHz : 800.000
cache size : 512 KB
ph...

Read more...

Revision history for this message
vagrale (vagrale) wrote :
Download full text (3.4 KiB)

I found a solution with 'acpi=off'.
Now show the correct cpu MHz but doesn't work Frequency Scaling.

:~$ sudo dmidecode -t processor | grep Speed
 Max Speed: 2700 MHz
 Current Speed: 3051 MHz

:~$ dmesg | grep MHz
[ 0.000000] tsc: Detected 3033.877 MHz processor
vagrale@vagrale-desktop:~$ lscpu | grep MHz
CPU MHz: 3033.877

:~$ cpupower -c all frequency-info
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
  CPUs which run at the same hardware frequency: Not Available
  CPUs which need to have their frequency coordinated by software: Not Available
  maximum transition latency: Cannot determine or is not supported.
  hardware limits: Not Available
  available cpufreq governors: Not Available
  Unable to determine current policy
  current CPU frequency: Unable to call hardware
  current CPU frequency: Unable to call to kernel
  boost state support:
    Supported: no
    Active: no

analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
  CPUs which run at the same hardware frequency: Not Available
  CPUs which need to have their frequency coordinated by software: Not Available
  maximum transition latency: Cannot determine or is not supported.
  hardware limits: Not Available
  available cpufreq governors: Not Available
  Unable to determine current policy
  current CPU frequency: Unable to call hardware
  current CPU frequency: Unable to call to kernel
  boost state support:
    Supported: no
    Active: no

:~$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 6
model name : AMD Athlon(tm) X2 215 Processor
stepping : 2
microcode : 0x10000c7
cpu MHz : 3033.877
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid eagerfpu pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save
bugs : tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs
bogomips : 6067.75
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor : 1
vendor_id : AuthenticAMD
cpu family : 16
model : 6
model name : AMD Athlon(tm) X2 215 Processor
stepping : 2
microcode : 0x10000c7
cpu MHz : 3033.877
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid eagerfpu pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch os...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.