Bug 113615

Created attachment 47883 [details]
/var/log/messages

There are lots of diagnostic error messages in the syslog. Even if they 
say "Error" this doesn't actually have to be an error. 
 
Can you please describe what is not working? 

I thought the Error was clear.

One consequence I found is a problem with kpowersave.
The setting under SetCPU Frequence Policy is Dynamic by default.
Changing to Performance and Powersave is possible, but by changing back to
Dynamic Window with a Warning! occurs: CPU Freq Policy Dynamic could not be set.
After a klick in kpowersave icon again menu point "SetCPU Frequency Policy" in
PullDownMenu is gone. Ok, it can be a bug in kpowersave as well.
Two entries from logfile messages to this failure:
Aug 30 13:00:41 Test [powersave]: WARNING (setMode:143) Could not set on_demand
governor. Isthe module loaded?
Aug 30 13:00:41 Test [powersave]: ERROR (handleActionMessage:1822) Could not set
dynamic mode

The module should be loaded, look to the list.
Test:~ # modprobe -l | grep cpufreq
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/cpufreq_powersave.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/cpufreq_stats.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/cpufreq_userspace.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/cpufreq_ondemand.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/cpufreq_conservative.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/drivers/cpufreq/freq_table.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/longrun.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k8.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k7.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k6.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-smi.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-lib.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-ich.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/longhaul.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/p4-clockmod.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/cpufreq-nforce2.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/gx-suspmod.ko
/lib/modules/2.6.13-rc6-git13-4-default/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko

Thanks. It's always helpful to have both the diagnostic output of the 
application and a description of the symptoms. 
 
Thomas, Pavel - looks like another issue with the ondemand cpufreq 
governor. 

Can you confirm that ondemand is really loaded according to lsmod?

Can you do echo to /sys/.../governor file to confirm that setting ondemand
governor really fails? And see dmesg if something goes on there?

/proc/modules shows
cpufreq_ondemand 6044 0 - Live 0xf0ea0000
cpufreq_userspace 4444 0 - Live 0xf0ea3000
cpufreq_powersave 1792 0 - Live 0xf0e88000

Sorry, this with /sys/... is for me not comprehensible. Could you describe this
little more detailed, what you need?

This is a userspace problem (powersave daemon).
Seems as if something has been forgotten to check when switching modes?!?
I'll have a look and come back if I need more info...

which cpufreq module is used? speedstep-ich? This one is too slow for ondemand
IIRC (will have to test), so you must use the userspace governor with

CPUFREQ_CONTROL=userspace
in /etc/sysconfig/powersave/cpufreq

this might be a duplicate of bug #114616

I did CPUFREQ_CONTROL=userspace and now the CPU-speed was reduced to 730 MHz.

kpowersave showed:
Pluged in -- 98% charged -- 731 MHz

I plugged off the power and after 12 minutes the icon changed to status battery
and showed:
Running batteries -- 94% charged (3:47 hours remaining) -- 997 MHz

Something goes wrong! The speed is now unplugged higher then plugged?

----- logfile messages -----
Sep  3 14:36:21 linux rcpowersaved: enter 'speedstep_ich' into CPUFREQD_MODULE
in /etc/sysconfig/powersave/cpufreq.
Sep  3 14:36:21 linux rcpowersaved: this will speed up starting powersaved and
avoid unnecessary warnings in syslog.
Sep  3 14:36:22 linux [powersave]: WARNING (initHal:54) hal not ready. We will
try later...This may sometimes happen dur

lsmod | grep speed
speedstep_ich           5004  0
speedstep_lib           4228  1 speedstep_ich
freq_table              4612  1 speedstep_ich

----- hwinfo 1 plugged on -----
56: None 00.0: 10103 CPU
  [Created at cpu.290]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: Intel
  Vendor: "GenuineIntel"
  Model: 6.11.1 "Intel(R) Pentium(R) III Mobile CPU      1000MHz"
  Features:
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse
  Clock: 730 MHz
  Cache: 512 kb
  Config Status: cfg=new, avail=yes, need=no, active=unknown

----- hwinfo 2 plugged off -----
56: None 00.0: 10103 CPU
  [Created at cpu.290]
  Unique ID: rdCR.j8NaKXDZtZ6
  Hardware Class: cpu
  Arch: Intel
  Vendor: "GenuineIntel"
  Model: 6.11.1 "Intel(R) Pentium(R) III Mobile CPU      1000MHz"
  Features:
fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse
  Clock: 996 MHz
  Cache: 512 kb
  Config Status: cfg=new, avail=yes, need=no, active=unknown

kpowersave only shows a momentary snapshot of current cpufreq.
Maybe something pushed CPU load and cpufreq went up.

Better use:
watch -n1 cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

also watch top whether your CPU load.
Seife can you watch this bug, I try to solve some ACPI issues currently...,
reassign it to me if you also have too much workload ...

Hi Thomas, what a sense it should make to use scaling_cur_freq? The results are
always the same. 
I tested again with power and battery status. I found that the status of the cpu
frequence changed after I disconnected power and I stopped and started
kpowersave. But there is no difference in scaling_cur_freq, kpowersave,
/proc/cpuinfo or hwinfo about the cpu frequence.

Created attachment 48874 [details]
/var/log/messages

I have started the daemon in debug mode /usr/sbin/powersaved -d -f
/var/run/acpid.socket -v 16 .
Interesting is the first change from 997 MHz (Line 96) to 731 MHz (Line 104).

you are missing lots of messages if you only include "DEBUG", so please repeat
this with "-v 31" to get also INFO, DIAG, etc.

i can not reproduce this. Are you sure that your AC profile does not have
different cpufreq settings than your battery profile? For me the frequency is
the same on AC and on battery, dynamic mode works fine on both.
There could be some interaction with weird BIOS settings, but i doubt it.

Holger, if you want to play with this: the Armada e500 on my shelf is running
with a P3 coppermine (550/700MHz).

Pavel, there is probably not much you can help here, so i'll remove you from cc :-)

Created attachment 49487 [details]
/var/log/messages

I changed the line 262 in file /etc/init.d/powersaved in startproc
/usr/sbin/powersaved -d -f /var/run/acpid.socket -v31
and started the system new. This is the logfile from this coldstart. See line
294. The CPU speed is changed here.

the speed is changed lots of times in this logfile:

seife@strolchi:~> grep setSpeed /tmp/messages
Sep 10 10:17:00 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:02 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:09 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:10 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:11 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:13 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:23 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:24 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:25 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:26 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:27 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:31 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:32 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:36 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:37 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:43 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:44 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:44 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:45 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:45 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:45 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:46 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:50 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:17:51 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:18:00 linux [powersave]: Info (setSpeed:90) Speed set to: 997500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
Sep 10 10:18:00 linux [powersave]: Info (setSpeed:90) Speed set to: 731500KHz 
in file /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed

so this actually seems to work. Also i cannot reproduce this on my speedstep-ich
machines. Since we changed the logmessage to point to the userpace governor, i
consider this bug fixed.

*** Bug 118735 has been marked as a duplicate of this bug. ***