Your message dated Sat, 27 Sep 2014 11:30:32 +0200
with message-id <[email protected]>
and subject line closing report
has caused the Debian Bug report #692552,
regarding cpufreqd: has all CPU cores run at full speed upon installation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
692552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692552
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: cpufreqd
Version: 2.4.2-1
Severity: important
*** Please type your report below this line ***
Installing cpufreqd shows paradox results. Without cpufreqd CPU-frequency
scaling works
perfectly fine on my PC. Once it is installed, all CPU-cores run at full speed.
I do not
like this at all. Changing the configuration file according to what my CPU
actually
provides (see below) did not have any effect.
I do not know enough to tell, why CPU-frequency-scaling works by default on my
system
when newly installed, but does not work anymore, once cpufreqd is installed. On
other
systems I saw different outcomes, when chanching /etc/cpufreqd.conf. Maybe this
is due to
some shortcoming of CPU-sensors ?
The only way to revert this seems to be uninstalling cpufreqd again and
rebooting the
machine, then everything is as it was before.
- -- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.23ldt (SMP w/3 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cpufreqd depends on:
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libcpufreq0 007-1+squeeze1 shared library to deal with the cp
ii libsensors4 1:3.1.2-6 library to read temperature/voltag
ii libsysfs2 2.1.0+repack-1 interface library to sysfs
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
Versions of packages cpufreqd recommends:
ii acpid 1:2.0.7-1squeeze4 Advanced Configuration and Power I
Versions of packages cpufreqd suggests:
ii cpufrequtils 007-1+squeeze1 utilities to deal with the cpufreq
- -- Configuration Files:
/etc/cpufreqd.conf changed:
[General]
pidfile=/var/run/cpufreqd.pid
poll_interval=2
verbosity=4
[/General]
[Profile]
name=On Demand High
minfreq=50%
maxfreq=100%
policy=ondemand
[/Profile]
[Profile]
name=Performance High
minfreq=100%
maxfreq=100%
policy=performance
[/Profile]
[Profile]
name=Performance Low
minfreq=80%
maxfreq=80%
policy=performance
[/Profile]
[Profile]
name=Powersave High
minfreq=60%
maxfreq=60%
policy=powersave
[/Profile]
[Profile]
name=Powersave Low
minfreq=40%
maxfreq=40%
policy=powersave
[/Profile]
[Rule]
name=AC Rule
ac=on # (on/off)
profile=On Demand High
[/Rule]
[Rule]
name=AC Off - High Power
ac=off # (on/off)
battery_interval=70-100
profile=Performance Low
[/Rule]
[Rule]
name=AC Off - Medium Battery
ac=off # (on/off)
battery_interval=30-70
profile=Powersave High
[/Rule]
[Rule]
name=AC Off - Low Battery
ac=off # (on/off)
battery_interval=0-30
profile=Powersave Low
[/Rule]
[Rule]
name=CPU Too Hot
acpi_temperature=55-100
cpu_interval=50-100
profile=Performance Low
[/Rule]
[Rule]
name=Movie Watcher
programs=xine,mplayer,gmplayer
battery_interval=0-100
acpi_temperature=0-60
cpu_interval=0-100
profile=Performance High
[/Rule]
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlCaS2cACgkQ5+rBHyUt5wsFZgCgk6nq36iYF2LYvtl7miEoH2mR
baAAoMBNc6t+O38tDHZsZnENSsZA6iwz
=FohI
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There is no use keeping this report open, because this problem is not
reproducible
anymore.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlQmg7kACgkQ5+rBHyUt5wsOgQCgg6NqxpNiQYZ5y0t4HKd7PRh6
jPIAniOIj/p+EPLqL/51KEqsOoLoRE1d
=K0JE
-----END PGP SIGNATURE-----
--- End Message ---
