On mer, 2006-12-20 at 17:55 +0100, Sven Arvidsson wrote:
> Maybe a bug in the cpu frequency governor? There was a long discussion
> on debian-devel in the beginning of this month about the difference
> between the ondemand and the conservative governor.
I don't have any governor loaded when testing it, just the processor
module, without speedstep-centrino and cpufreq-* modules.
When running on AC there are 2 cstates :
# cat /proc/acpi/processor/CPU1/power
active state: C2
max_cstate: C8
bus master activity: 00000000
states:
C1: type[C1] promotion[C2] demotion[--]
latency[000] usage[00000010] duration[00000000000000000000]
*C2: type[C2] promotion[--] demotion[C1]
latency[001] usage[00005536] duration[00000000000041838680]
and 3 on battery :
# cat /proc/acpi/processor/CPU1/power
active state: C2
max_cstate: C8
bus master activity: 20000010
states:
C1: type[C1] promotion[C2] demotion[--]
latency[000] usage[00000010] duration[00000000000000000000]
*C2: type[C2] promotion[C3] demotion[C1]
latency[001] usage[00007935] duration[00000000000049878469]
C3: type[C3] promotion[--] demotion[C2]
latency[001] usage[00008673] duration[00000000000069020648]
Just with the processor module, frequency reported by x86info or
gkrellm-x86info goes from ~10MHz to 800MHz or 1800MHz (depending on
whether I booted on battery or on AC power).
What is strange is that it seems that I'm the only one having this issue
and only on my laptop.
regards,
strawks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
