[Z77 Extreme4] scaling_min_freq wrong on my Intel CPU

Bug #1390902 reported by ahb
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cpufreqd (Ubuntu)
Triaged
Low
Unassigned

Bug Description

With my Intel CPU scaling does not work out of the box. The problem is that although the hardware limits are correctly detected only the "range" between 3.50 and 3.50 GHz is used:
cpufreq-info
cpufrequtils 008: 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
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 3.50 GHz
  available frequency steps: 3.50 GHz, 3.50 GHz, 3.40 GHz, 3.20 GHz, 3.10 GHz, 3.00 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 3.50 GHz and 3.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.50 GHz.
  cpufreq stats: ...

WORKAROUND: Uninstall package cpufreqd.

WORKAROUND: cat cpufreq_workaround.sh
#!/bin/sh
min_freq=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies | awk "{ print \$NF }")
echo "Setting scaling_min_freq to $min_freq"
for i in `seq 0 7`; do echo $min_freq > /sys/devices/system/cpu/cpu$i/cpufreq/scaling_min_freq; done

afterwards:
> cpufreq-info
cpufrequtils 008: 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
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 3.50 GHz
  available frequency steps: 3.50 GHz, 3.50 GHz, 3.40 GHz, 3.20 GHz, 3.10 GHz, 3.00 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 1.60 GHz and 3.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ahb 3853 F.... pulseaudio
 /dev/snd/controlC0: ahb 3853 F.... pulseaudio
Date: Sun Nov 9 13:54:23 2014
HibernationDevice: RESUME=UUID=1968620e-56f2-4ec6-b4ae-d2c601e8caa5
InstallationDate: Installed on 2014-08-28 (72 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB:
 0 VESA VGA
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=98ea3432-7344-4034-8652-46e5edf53f5b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.8
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: Z77 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/14/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
ahb (andreas-bihlmaier) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-2.90
summary: - scaling_min_freq wrong on Intel Core i{5,7} CPUs
+ [Z77 Extreme4] scaling_min_freq wrong on my Intel CPU
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
ahb (andreas-bihlmaier) wrote :

I will try a BIOS upgrade on this machine later on.
However, I doubt it will change anything since I have to totally different machines exhibiting the same problem (and it worked on the machine above an 12.04.5):

Machine 1: Lenovo X230 Laptop
Machine 2: Different desktop computer

Information for both machines is attached.

Revision history for this message
penalvch (penalvch) wrote :

ahb, just to clarify, this report is only scoped to the Z77 Extrem4 hardware, not any other. If you are having a problem with different hardware, please file a new report, one per hardware combination, via a terminal:
ubuntu-bug linux

As well, please do not tar or compress files as it makes it harder for developers to help you.

Revision history for this message
ahb (andreas-bihlmaier) wrote :

I'll comply to Ubuntu's bug procedure(s).
Yet, I think it is important from a developers point of view to know from the start that this issue is not related to a specify HW, but rather a more general problem (i.e. at least concerning the Z77 desktop, the X230 laptop and the Z87 desktop).

Unfortunately, it is not possible to add multiple files to a single comment.

Revision history for this message
ahb (andreas-bihlmaier) wrote :
Download full text (8.2 KiB)

Bug persists after BIOS update:

> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
P2.90
07/11/2013

> cpufreq-info
cpufrequtils 008: 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
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 3.50 GHz
  available frequency steps: 3.50 GHz, 3.50 GHz, 3.40 GHz, 3.20 GHz, 3.10 GHz, 3.00 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 3.50 GHz and 3.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.50 GHz.
  cpufreq stats: 3.50 GHz:99,99%, 3.50 GHz:0,00%, 3.40 GHz:0,00%, 3.20 GHz:0,00%, 3.10 GHz:0,00%, 3.00 GHz:0,00%, 2.80 GHz:0,00%, 2.70 GHz:0,01%, 2.50 GHz:0,00%, 2.40 GHz:0,00%, 2.30 GHz:0,00%, 2.10 GHz:0,00%, 2.00 GHz:0,00%, 1.90 GHz:0,00%, 1.70 GHz:0,00%, 1.60 GHz:0,00% (5)
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: 10.0 us.
  hardware limits: 1.60 GHz - 3.50 GHz
  available frequency steps: 3.50 GHz, 3.50 GHz, 3.40 GHz, 3.20 GHz, 3.10 GHz, 3.00 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 3.50 GHz and 3.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.50 GHz.
  cpufreq stats: 3.50 GHz:99,97%, 3.50 GHz:0,00%, 3.40 GHz:0,00%, 3.20 GHz:0,00%, 3.10 GHz:0,00%, 3.00 GHz:0,00%, 2.80 GHz:0,01%, 2.70 GHz:0,00%, 2.50 GHz:0,00%, 2.40 GHz:0,00%, 2.30 GHz:0,00%, 2.10 GHz:0,00%, 2.00 GHz:0,00%, 1.90 GHz:0,00%, 1.70 GHz:0,00%, 1.60 GHz:0,02% (8)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 3.50 GHz
  available frequency steps: 3.50 GHz, 3.50 GHz, 3.40 GHz, 3.20 GHz, 3.10 GHz, 3.00 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 3.50 GHz and 3.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 3.50 GHz.
  cpufreq stats: 3.50 GHz:99,97%, 3.50 GHz:0,00%, 3.40 GHz:0,00%, 3.20 GHz:0,00%, 3.10 GHz:0,00%, 3.00 GHz:0,01%, 2.80 GHz:0,00%, 2.70 GHz:0,00%, 2.50 GHz:0,01%, 2.40 GHz:0,00%, 2.30 GHz:0,00%, ...

Read more...

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

ahb, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing in your release) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 exactly shown as:
kernel-fixed-upstream-3.18-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.

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

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):
status: Confirmed → Incomplete
Revision history for this message
ahb (andreas-bihlmaier) wrote :
Download full text (4.2 KiB)

The upstream kernel did not fix the issue. Yet, cpufreq behaves differently now (my guess: different/missing kernel modules):

> cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.64 GHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 3.17 GHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 3.24 GHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 2.45 GHz.
analyzing CPU 4:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 3.79 GHz.
analyzing CPU 5:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 0.97 ms.
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 3.90 GHz and 3.90 GHz.
                  The governor ...

Read more...

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.18-rc4
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: latest-bios-2.90
removed: bios-outdated-2.90
Revision history for this message
ahb (andreas-bihlmaier) wrote :

After two hours of getting my GPU driver to work again due to installing and deinstalling mainline kernel package ...

Cause of problem found:
cpufreqd

If this package is not installed frequency scaling works - out of the box.

Solution: Bann cpufreqd from repositories.

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

ahb, given the new information you provided, please ignore the request to file this upstream. For now, let this be assigned to the cpufreqd package for the specialist on that to review.

As well, would you be able to provide more information on your use of cpufreqd (was it installed by default, did you configure it in any way, etc.).

description: updated
affects: linux (Ubuntu) → cpufreqd (Ubuntu)
Revision history for this message
ahb (andreas-bihlmaier) wrote :

cpufreqd was installed from standard repository with unchanged configuration (which worked perfectly in 12.04(.5)).

> apt-cache showpkg cpufreqd
Package: cpufreqd
Versions:
2.4.2-2ubuntu1 (/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages)
 Description Language:
                 File: /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages
                  MD5: 2e6607a4cd24cc140a7c1cd9613eaaab
 Description Language: en
                 File: /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en
                  MD5: 2e6607a4cd24cc140a7c1cd9613eaaab

Reverse Depends:
  cpufreqd:i386,cpufreqd
Dependencies:
2.4.2-2ubuntu1 - libc6 (2 2.15) libcpufreq0 (2 001) libsensors4 (2 1:3.0.0) libsysfs2 (0 (null)) lsb-base (2 3.0) cpufrequtils (0 (null)) acpid (0 (null)) cpudyn (0 (null)) cpudyn:i386 (0 (null)) powernowd (0 (null)) powernowd:i386 (0 (null)) cpufreqd:i386 (0 (null))
Provides:
2.4.2-2ubuntu1 -
Reverse Provides:

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.