You are not logged in.
My cpu is stocked at 800MHz, even if it supports up to 2GHz. Whatever I do it stays at 800MHz.
I am using the module "acpi-cpufreq" and the ondemand governor. "acpi-cpufreq" and "cpufreq-ondemand" are loaded from my /etc/rc.conf. I the daemon /etc/rc.d/cpufreq is loaded at boot (_not_ cpufreqd). Here is the content of /etc/conf.d/cpufreq:
#configuration for cpufreq control
# valid governors:
# ondemand, performance, powersave,
# conservative, userspace
governor="ondemand"# valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="800MHz"
max_freq="2.00GHz"
Here is the output of cpufreq-info:
cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 800 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 800 MHz - 2.00 GHz
available frequency steps: 2.00 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz
available cpufreq governors: conservative, userspace, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
Note that it reports 800MHz as the maximum freq...
Also, I cannot set manually the maximum frequency:
# echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
800000
I always used ondemand, but I can't figure out why I'm stuck at 800MHz since 2.6.24!!
Any clues?
Last edited by big_gie (2008-03-11 14:22:13)
Offline
Another weird thing is that:
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
2001000 2000000 1600000 1200000 800000
Why is it reporting "2001000"?? My processor (T7300) can only go at 2GHz, not higher...
Offline
In the past I had problems with the min/max settings in /etc/conf.d/cpufreq. The daemon seems to adjust the max frequency, for example, to less than (not less than or equal to) the frequency given in the max_freq= line. I think probably the best thing to do is to comment the min max frequencies out completely and let the daemon use the defaults for your processor. Not sure if this will help but it's worth a try...
Offline
I've read this on the forum while searching for a solution and tryed it but it doesn't work... Thanx anyway!
Offline
I've had some problems with cpufreqd setting my max_freq = min_freq when I resumed from suspend. I can't really narrow down a particular scenario, it just seems to occur at random. Anyways, I find that restarting cpufreqd helps, and if not, disabling it and setting the frequency manually using cpufreq-set seems to fix the problem.
Arch on a Thinkpad T400s
Offline
Thanx mint... But I'm not using cpufreqd. It is not even installed...
Offline
Hum really weird... Frequency scaling is back... really really weird...
Marked as solved.
Offline
The problem is still there. In fact, it comes and goes. It is really weird.
I compiled my kernel with cpufreq debug and booted with cpufreq.debug=7. I now get in my dmesg:
> dmesg | grep -i cpuf
[ 0.000000] Command line: root=/dev/sda6 ro quiet vga=791 splash resume=/dev/sda5 cpufreq.debug=7 5
[ 0.000000] Kernel command line: root=/dev/sda6 ro quiet vga=791 splash resume=/dev/sda5 cpufreq.debug=7 5
[ 16.541557] acpi-cpufreq: acpi_cpufreq_init
[ 16.541563] acpi-cpufreq: acpi_cpufreq_early_init
[ 16.541838] cpufreq-core: trying to register driver acpi-cpufreq
[ 16.541845] cpufreq-core: adding CPU 0
[ 16.541850] acpi-cpufreq: acpi_cpufreq_cpu_init
[ 16.542135] acpi-cpufreq: HARDWARE addr space
[ 16.542163] acpi-cpufreq: get_cur_freq_on_cpu (0)
[ 16.542180] acpi-cpufreq: get_cur_val = 100664850
[ 16.542187] acpi-cpufreq: cur freq = 1200000
[ 16.542408] acpi-cpufreq: CPU0 - ACPI performance management activated.
[ 16.542414] acpi-cpufreq: *P0: 2001 MHz, 32000 mW, 10 uS
[ 16.542417] acpi-cpufreq: P1: 2000 MHz, 31000 mW, 10 uS
[ 16.542423] acpi-cpufreq: P2: 1600 MHz, 22000 mW, 10 uS
[ 16.542428] acpi-cpufreq: P3: 1200 MHz, 13000 mW, 10 uS
[ 16.542434] acpi-cpufreq: P4: 800 MHz, 10000 mW, 10 uS
[ 16.542495] cpufreq-core: CPU 1 already managed, adding link
[ 16.542503] cpufreq-core: setting new policy for CPU 0: 800000 - 2001000 kHz
[ 16.542508] acpi-cpufreq: acpi_cpufreq_verify
[ 16.542525] acpi-cpufreq: acpi_cpufreq_verify
[ 16.542556] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 16.542558] cpufreq-core: governor switch
[ 16.542563] cpufreq-core: __cpufreq_governor for CPU 0, event 1
[ 16.542583] cpufreq-core: governor: change or update limits
[ 16.542586] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 16.542592] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
[ 16.542597] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
[ 16.542611] cpufreq-core: notification 0 of frequency transition to 800000 kHz
[ 16.542618] cpufreq-core: notification 0 of frequency transition to 800000 kHz
[ 16.542649] cpufreq-core: notification 1 of frequency transition to 800000 kHz
[ 16.542657] cpufreq-core: notification 1 of frequency transition to 800000 kHz
[ 16.542667] cpufreq-core: initialization complete
[ 16.542675] cpufreq-core: adding CPU 1
[ 16.542688] cpufreq-core: driver acpi-cpufreq up and running
[ 27.817703] cpufreq-core: setting new policy for CPU 0: 800000 - 800000 kHz
[ 27.817714] acpi-cpufreq: acpi_cpufreq_verify
[ 27.817742] acpi-cpufreq: acpi_cpufreq_verify
[ 27.817766] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 27.817775] cpufreq-core: governor: change or update limits
[ 27.817779] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 27.820575] cpufreq-core: setting new policy for CPU 0: 800000 - 800000 kHz
[ 27.820585] acpi-cpufreq: acpi_cpufreq_verify
[ 27.820610] acpi-cpufreq: acpi_cpufreq_verify
[ 27.820634] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 27.820639] cpufreq-core: governor: change or update limits
[ 27.820643] cpufreq-core: __cpufreq_governor for CPU 0, event 3
So it seems my cores boot at 2GHz, then get stucks at 800MHz:
[ 16.542503] cpufreq-core: setting new policy for CPU 0: 800000 - 2001000 kHz
[ 16.542508] acpi-cpufreq: acpi_cpufreq_verify
[ 16.542525] acpi-cpufreq: acpi_cpufreq_verify
[ 16.542556] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
Maybe "acpi_cpufreq_verify" has a bug?
The computer is a Dell Latitude D830 with an Intel Core 2 Duo T7300 2GHz processor.
Any clues?
Thanx
Offline
I've been having the same issue on my Dell Latitude C400 for a few weeks now. At seemingly random times, the fan will kick into high gear and the cpu will scale back to the minimum. Both will be stuck like this (fan never scales back, cpu never scales up) and there is no way to override them without rebooting - I've tried manually setting the freq, using a different governor, etc etc. It seems like it might be triggered by the cpu temperature. I've tried downgrading a number of packages without success, but I wasn't too exhaustive about since I'm not sure what package triggered this problem.
Also, there are some similar bug reports - e.g https://bugs.launchpad.net/ubuntu/+sour … +bug/88899
Last edited by stonecrest (2008-03-08 21:17:02)
I am a gated community.
Offline
I tried removing dsdt from my mkinitcpio.conf's hook and rebuilding. Still nothing...
I saw this kernel bug which seems related: http://bugzilla.kernel.org/show_bug.cgi?id=9636
I also upgraded my bios (from A04 to A09) but still the same...
The laptop is not hot. Processor temperature is around 44o C.
Offline
I upgraded to A10, and for a couple of minutes I was able to get 2GHz, but now I'm back to 800MHz...
If I set the perfomance governor I get:
[ 3065.949556] cpufreq-core: setting new policy for CPU 0: 800000 - 800000 kHz
[ 3065.949569] acpi-cpufreq: acpi_cpufreq_verify
[ 3065.949575] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
[ 3065.949586] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
[ 3065.949599] acpi-cpufreq: acpi_cpufreq_verify
[ 3065.949608] freq-table: request for verification of policy (800000 - 800000 kHz) for cpu 0
[ 3065.949614] freq-table: verification lead to (800000 - 800000 kHz) for cpu 0
[ 3065.949624] cpufreq-core: new min and max freqs are 800000 - 800000 kHz
[ 3065.949628] cpufreq-core: governor switch
[ 3065.949637] cpufreq-core: __cpufreq_governor for CPU 0, event 2
[ 3065.949695] cpufreq-core: __cpufreq_governor for CPU 0, event 1
[ 3065.949704] performance: setting to 800000 kHz because of event 1
[ 3065.949714] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
[ 3065.949719] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
[ 3065.949729] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
[ 3065.949734] freq-table: target is 4 (800000 kHz, 4)
[ 3065.949743] acpi-cpufreq: Already at target state (P4)
[ 3065.949747] cpufreq-core: governor: change or update limits
[ 3065.949756] cpufreq-core: __cpufreq_governor for CPU 0, event 3
[ 3065.949761] performance: setting to 800000 kHz because of event 3
[ 3065.949770] cpufreq-core: target for CPU 0: 800000 kHz, relation 1
[ 3065.949775] acpi-cpufreq: acpi_cpufreq_target 800000 (0)
[ 3065.949784] freq-table: request for target 800000 kHz (relation: 1) for cpu 0
[ 3065.949790] freq-table: target is 4 (800000 kHz, 4)
[ 3065.949798] acpi-cpufreq: Already at target state (P4)
Offline
This is getting really weird...
Yesterday cpufreq was working. But now it doesn't... What changed from yesterday was that I was using an external monitor and a usb mouse/keyboard. I wont be able to reuse those until a couple of hours, but shouldn't these items interfere with cpufreq?!?
Offline
Me again...
I tried booting with the usb keyboard and monitor attached, and miracle, cpufreq was back and running.
So I tried without the monitor and keyboard... cpufreq was running too!!!
I'm really out of ideas...
What could be the cause of that?
Also, i think this problem would be easier to size if "CONFIG_CPU_FREQ_DEBUG" was set... Is there a reason it isn't? Does it slow things? Or break some systems? When the option is set, it still needs to be started with a boot parameter...
Offline
Now I have the same behaviour with kernel 2.6.25.3
When plugged in, I am stucked at 800MHz (the minimum). When I unplug the AC or dock the laptop, I get the full range of frequency with a maximum of 2GHz.
Offline
I have similar issues with kernel26-2.6.25.4-1
Just to tell you that you are not alone
The cpu is at full speed all the time. When I unplug the AC, it goes slower, but only for a few seconds and comes back to full speed.
I have no time to test at the moment so I will move back to 2.6.24.
Offline
problems here as well with cpufreq
here is what I get after the last kernel update (fallback doesn't help)
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
this problem started out of the blue.
What the heck is going on here? My cpu is stuck at 800MHZ and it can go to 2.2GhZ. It is crawling here!
Offline
Whether my laptop is plugged into AC or not has no bearing on this issue for me, I'm always stuck in the lowest frequency. I do remember seeing a bugzilla kernel report on the issue regarding AC/battery though.
I am a gated community.
Offline
I've also had (or still have) problems with cpufreq since the upgrade to kernel 2.6.25. Since my box is pretty old, I'm using the p4_clockmod module. I've reported my problems here:
http://bugs.archlinux.org/task/10505
What I do not report explicitly in that report is that it seems that I've got it working by not specifying any min_freq or max_freq in /etc/conf.d/cpufreq. cpufreq is still reporting insane cpu frequencies but the frequency scaling _seems_ to work anyway. Don't know if it is applicable here, but try doing that and see what happens.
The reason for the error message that Cippa Lippa mentioned above may be due to that the min_freq/max_freq settings in /etc/conf.d/cpufreq are incompatible with the frequencies that cpufreq thinks the cpu is capable of. That may also be the reason that the cpu appears "stuck" on a certain frequency.
Offline
well, the whole thing is acting ultraweird and completely erratic
it started working again yesterday for some reason and now instead it is mostly stuck at 1.2GhZ even though sometimes it goes to 1.6 (never seen before).
Now, for example I changed the governor from conservative to ondemand and now it seems to be working again
I think there is something real fishy going on here
regarding the bug post, I have no p4_clockmod module and I still observe the same behaviour
Offline
another update
the cpufreq seems to go awry after recovering from standby. It needs to be restarted in order to start working again, otherwise I get it stuck at 800 MhZ or 2.2GHz no matter what I do
Offline
Have you guys tried cpufreq-set manually?
cpufreq-set -c 0 -u 2.00GHz
cpufreq-set -c 1 -u 2.00GHz
Last edited by schivmeister (2008-06-02 08:21:01)
I need real, proper pen and paper for this.
Offline
The problem is more deep then using cpufreq-set.
It's the driver that fails to detect the correct possible frequencies, depending on certain parameters. For me with kernel 2.6.25.3, I get all the possible frequencies (800MHz up to 2GHz) when the AC is unplugged and when I am docked, and a maximum of 800MHz when AC is plugged in...
Offline
the recent update on cpufreq-utils hasn't changed the problem for me...
Offline
The problem I have is caused by not powerful enough AC adapter. My Dell Latitude D830 needs a 90W adapter, but Dell sold me a 65W one. See http://bugs.archlinux.org/task/10106
Unfortunately, the bug was closed quite roughly...
Offline
I have/had a similar problem with a Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz:
if I ran /etc/rc.d/cpufreq, the frequency would not go to the highest step (max was 1.33GHz).
Without acpi-cpufreq loaded, the cpu runs at its proper frequency; when I loaded the module later, and set the ondemand governor, without setting any minimum or maximum frequencies (like that cpufreq script does), then the frequency appears to scale properly.
Maybe this was your problem?
Maybe I'm crazy?
Offline