Bug 79871

Summary: Klaptopdameon does not read the cpu frequency properly
Product: [Unmaintained] klaptopdaemon Reporter: Riku Voipio <nchip>
Component: generalAssignee: Paul Campbell <paul>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Riku Voipio 2004-04-18 11:28:03 UTC 
Version:            (using KDE KDE 3.2.1)
Installed from:    Debian testing/unstable Packages

The KLaptop Daemon does not report the CPU frequency properly.
The it relies entirely on the info in /proc/cpuinfo which only
reports the maximum CPU speed but not the current one on kernel 2.6.
The actualy frequency is reported on different places in either proc or
sysfs.
namely:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed

or

/proc/sys/cpu/0/speed

Therefore the display of the current cpu frequence shows
a wrong value if power management and speed scaling is used.


forwarded from: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244317
Comment 1 Volker Krause 2004-04-18 13:47:21 UTC 
> The KLaptop Daemon does not report the CPU frequency properly.
> The it relies entirely on the info in /proc/cpuinfo which only
> reports the maximum CPU speed but not the current one on kernel 2.6.

This is a bug in early 2.6 kernels and is fixed in 2.6.5 already.

> The actualy frequency is reported on different places in either proc or
> sysfs.
> namely:
>
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed

This is part of the CPUFreq userspace governor, which might not be available 
on all system (in contrast to /proc/cpuinfo).

> or
> /proc/sys/cpu/0/speed

Even worse, this is the deprecated interface of the CPUFreq userspace 
governor.

Both interfaces don't have more accurate information than /proc/cpuinfo (at 
least after it has been fixed in 2.6.5). So I don't see a point in supporting 
these additional interfaces just as a workaround on a few early 2.6 kernels.
Comment 2 Riku Voipio 2004-04-18 23:25:01 UTC 
Comments from the original reporter:

As Volker suggestet, the problem indeed is fixed at the 2.6.5 kernel.
The frequency now is correctly reported in the klaptop applet.

Again sorry for the false warning.

And thanks for the fast responses.

Werner Punz