Bugzilla – Bug 146608
Powersave polutes syslog when CPU doesn't support frequency scaling
Last modified: 2007-06-05 10:01:39 UTC
Since my laptop processor does not support frequency scaling (it's an Intel Celeron), Powersave sends the same warnings and errors to syslog everytime there is battery charging state event: [powersave]: WARNING (getCoresAffectedCpus:251) failed to get affected_cpus for cpu 0 [powersave]: WARNING (getCoresAffectedCpus:251) failed to get affected_cpus for cpu 0 [powersave]: ERROR (read_line:118) Could not open '/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor': No such file or directory [powersave]: WARNING (initSingleInterface:102) Kernel ondemand governor not working, trying userspace instead [powersave]: ERROR (read_line:118) Could not open '/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor': No such file or directory [powersave]: WARNING (initSingleInterface:91) Could not init userspace governor [powersave]: ERROR (initSingleInterface:104) Neither ondemand nor userspace governor working I have set CPUFREQ_ENABLED="off" in /etc/sysconfig/powersave/cpufreq (and afterwards ran SuSEconfig and restarted Powersave) but still the same messages are sent to syslog. Couldn't Powersave send those messages only when it starts, instead of each time the battery charging state changes?
This should already be fixed. Reassigning to Holger just to be sure.
Yes, the warning should not appear in newer version. But I have to look why CPUFREQ_ENABLED="off" does not have any effect.
It has to be CPUFREQ_ENABLED="no", but its functionality was corrupted anyway. Fixed in svn.
> It has to be CPUFREQ_ENABLED="no", but its functionality was corrupted anyway. From your comment I presume that, even after the fix, the user will still need to manually edit /etc/sysconfig/powersave/cpufreq and change CPUFREQ_ENABLED? If so, couldn't Powersave notice the processor does not support frequency scaling and automatically assume CPUFREQ_ENABLED="no"? (or show a warning only when it starts, but not on every battery state change?)
With the fix only one warning on daemon startup will be shown. Please reopen if that's not the case with beta3. Unfortunatelly, the fix for the CPUFREQ_ENABLED variable won't make it into beta4.