cpufreqd sets minimum frequency to maximum frequency possible.

Bug #436356 reported by laptoplinux
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I had an interesting and frustrating problem.

I had to reinstall Jaunty due to a borked Karmic upgrade. Prior to that I was successfully running cpu frequency scaling and could use the gnome applet as well.

So I am setting it up again on a clean install of Jaunty and it works fine. I could change frequencies with the gnome applet etc, I reboot once and something went wacko.

The applet will let me select different frequencies/governors but would not actually change the frequency! After doing some troubleshooting I discovered that the minimum frequency had somehow become set to the highest frequency possible.
Hopefully the info below will make what I am trying to explain clearer.

************************************************************************************
cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: p4-clockmod
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 175 MHz - 1.40 GHz
  available frequency steps: 175 MHz, 350 MHz, 525 MHz, 700 MHz, 875 MHz, 1.05 GHz, 1.23 GHz, 1.40 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 1.40 GHz and 1.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.40 GHz.
  cpufreq stats: 175 MHz:0.00%, 350 MHz:0.00%, 525 MHz:0.00%, 700 MHz:0.00%, 875 MHz:0.00%, 1.05 GHz:0.00%, 1.23 GHz:0.00%, 1.40 GHz:0.00%
******************************************************************************************
cat scaling_min_freq 1400000
******************************************************************************************

So for some reason I could not understand, cpu frequency scaling thought that the minimum speed is 1400000 and the maximum is 1400000 which is causing my problem.

It turns out that Jaunty doesn't like cpufreqd which is odd given I had successfully used it for quite sometime. cpufreqd forces the minimum frequency value to be the same as the maximum so I will also file it as a bug.

The powernowd and cpydyn function properly. Data follows:

cpufreqd
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_*175000 350000 525000 700000 875000 1050000 1225000 1400000
conservative ondemand userspace powersave performance
1400000
p4-clockmod
powersave
1400000
1400000
<unsupported>

powernowd
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_*175000 350000 525000 700000 875000 1050000 1225000 1400000
conservative ondemand userspace powersave performance
175000
p4-clockmod
ondemand
1400000
175000
<unsupported>

cpudyn
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_*175000 350000 525000 700000 875000 1050000 1225000 1400000
conservative ondemand userspace powersave performance
1400000
p4-clockmod
performance
1400000
175000
<unsupported>

Tags: jaunty
Revision history for this message
Mark Garland (p-launchpad-markgarland-co-uk) wrote :
Download full text (4.1 KiB)

Hi,

I am getting the same issue.

Seems to me that the /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq file is set incorrectly to the highest value.

Hope the below is of use.

---

mark@titanic:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
2793000 2660000 2527000 2394000 2261000 2128000 1995000 1862000 1729000 1596000 1463000 1330000 1197000
mark@titanic:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
2793000 *********** wrong. Should be the lowest value - 1197000 for me ***********
mark@titanic:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
2793000

uname -a:
Linux titanic 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

cpufreq-info:
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1.20 GHz - 2.79 GHz
  available frequency steps: 2.79 GHz, 2.66 GHz, 2.53 GHz, 2.39 GHz, 2.26 GHz, 2.13 GHz, 2.00 GHz, 1.86 GHz, 1.73 GHz, 1.60 GHz, 1.46 GHz, 1.33 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 2.79 GHz and 2.79 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.79 GHz.
  cpufreq stats: 2.79 GHz:100.00%, 2.66 GHz:0.00%, 2.53 GHz:0.00%, 2.39 GHz:0.00%, 2.26 GHz:0.00%, 2.13 GHz:0.00%, 2.00 GHz:0.00%, 1.86 GHz:0.00%, 1.73 GHz:0.00%, 1.60 GHz:0.00%, 1.46 GHz:0.00%, 1.33 GHz:0.00%, 1.20 GHz:0.00%
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 1.20 GHz - 2.79 GHz
  available frequency steps: 2.79 GHz, 2.66 GHz, 2.53 GHz, 2.39 GHz, 2.26 GHz, 2.13 GHz, 2.00 GHz, 1.86 GHz, 1.73 GHz, 1.60 GHz, 1.46 GHz, 1.33 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 2.79 GHz and 2.79 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.79 GHz.
  cpufreq stats: 2.79 GHz:99.94%, 2.66 GHz:0.00%, 2.53 GHz:0.00%, 2.39 GHz:0.00%, 2.26 GHz:0.00%, 2.13 GHz:0.00%, 2.00 GHz:0.00%, 1.86 GHz:0.00%, 1.73 GHz:0.00%, 1.60 GHz:0.00%, 1.46 GHz:0.00%, 1.33 GHz:0.00%, 1.20 GHz:0.06% (2)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 2
  hardware limits: 1.20 GHz - 2.79 GHz
  available frequency steps: 2.79 GHz, 2.66 GHz, 2.53 GHz, 2.39 GHz, 2.26 GHz, 2.13 GHz, 2.00 GHz, 1.86 GHz, 1.73 GHz, 1.60 GHz, 1.46 GHz, 1.33 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 2.79 GHz and 2.79 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.79 GHz.
  cpufreq stats: 2.79 GHz:99.94%, 2.66 GHz:0.00%, 2.53 GHz:0.00%, 2.39 GHz:0.00%, 2...

Read more...

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

Hello
Is this issue present with the latest updated lucid's packages?
I can't reproduce it
thanks
fabio

tags: added: jaunty
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

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

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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