[gentoo-user-de] cpufreqd und ac=off

[Juergen Rose]

Hallo,

auf meinem Desktop PC waehlt cpufreqd den powersave governor aus, weil
er anscheinend der Meinung ist, dass das Netzteil keinen Wechselstrom
liefert. Wenn ich /etc/cpufreqd.conf die Verbosity auf 7 setze, finde
ich in /var/log/syslog die folgenden Ausgaben.

Apr 28 17:08:00 moose cpufreqd: alarm_handler            : Caught ALARM
signal (Alarm clock).
Apr 28 17:08:00 moose cpufreqd: cpufreqd_loop            : Current time
is: 1272467280::107891
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : called
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : CPU4
c_user=23506197 c_nice=173697 c_sys=3385811 c_idle=524786941
c_iowait=1490286 c_irq=20672 c_softirq=41746.
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : CPU0
c_user=4911353 c_nice=43049 c_sys=774609 c_idle=130630871
c_iowait=460293 c_irq=6047 c_softirq=12547.
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : CPU1
c_user=4479239 c_nice=42190 c_sys=727379 c_idle=133062909
c_iowait=445453 c_irq=5777 c_softirq=12469.
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : CPU2
c_user=6756081 c_nice=43417 c_sys=947265 c_idle=130687674
c_iowait=289936 c_irq=4441 c_softirq=9055.
Apr 28 17:08:00 moose cpufreqd: get_cpu                  : CPU3
c_user=7359523 c_nice=45039 c_sys=936557 c_idle=130405486
c_iowait=294603 c_irq=4405 c_softirq=7675.
Apr 28 17:08:00 moose cpufreqd: insert_tnode             : new node
(head)
Apr 28 17:08:00 moose cpufreqd: insert_tnode             : new node
(sar)
Apr 28 17:08:00 moose cpufreqd: programs_update          : read 219
processes
Apr 28 17:08:00 moose cpufreqd: acpi_battery_update      : average
battery life -1%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "AC Rule"
Apr 28 17:08:00 moose cpufreqd: acpi_ac_evaluate         : called: on
[off]
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "AC
Rule" score: 0%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "AC Off - Low Battery"
Apr 28 17:08:00 moose cpufreqd: acpi_ac_evaluate         : called: off
[off]
Apr 28 17:08:00 moose cpufreqd: rule_score               : Rule "AC Off
- Low Battery": ac matches.
Apr 28 17:08:00 moose cpufreqd: acpi_battery_evaluate    : called 0-30
[Avg:-1]
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "AC Off
- Low Battery" score: 51%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "AC Off - Medium Battery"
Apr 28 17:08:00 moose cpufreqd: acpi_ac_evaluate         : called: off
[off]
Apr 28 17:08:00 moose cpufreqd: rule_score               : Rule "AC Off
- Medium Battery": ac matches.
Apr 28 17:08:00 moose cpufreqd: acpi_battery_evaluate    : called 30-70
[Avg:-1]
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "AC Off
- Medium Battery" score: 51%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "AC Off - High Power"
Apr 28 17:08:00 moose cpufreqd: acpi_ac_evaluate         : called: off
[off]
Apr 28 17:08:00 moose cpufreqd: rule_score               : Rule "AC Off
- High Power": ac matches.
Apr 28 17:08:00 moose cpufreqd: acpi_battery_evaluate    : called 70-100
[Avg:-1]
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "AC Off
- High Power" score: 51%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "CPU Too Hot"
Apr 28 17:08:00 moose cpufreqd: acpi_temperature_evaluate: called 55-100
[Avg:0.0]
Apr 28 17:08:00 moose cpufreqd: cpu_evaluate             : CPU4
user=23506197 nice=173697 sys=3448229
Apr 28 17:08:00 moose cpufreqd: calculate_cpu_usage      : CPU
delta_activity=376 delta_time=796 weighted_activity=27012325.
Apr 28 17:08:00 moose cpufreqd: cpu_evaluate             : CPU4 47% -
min=50 max=100 scale=3.00
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "CPU Too
Hot" score: 0%
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Considering
Rule "Movie Watcher"
Apr 28 17:08:00 moose cpufreqd: programs_evaluate        : tree ptr
0x160cab0
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cab0
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cc70
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cb20
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cce0
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cdc0
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cb90
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cc00
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160ce30
Apr 28 17:08:00 moose cpufreqd: find_program             : tree ptr
0x160cd50
Apr 28 17:08:00 moose cpufreqd: acpi_battery_evaluate    : called 0-100
[Avg:-1]
Apr 28 17:08:00 moose cpufreqd: acpi_temperature_evaluate: called 0-60
[Avg:0.0]
Apr 28 17:08:00 moose cpufreqd: rule_score               : Rule "Movie
Watcher": acpi_temperature matches.
Apr 28 17:08:00 moose cpufreqd: update_rule_scores       : Rule "Movie
Watcher" score: 34%
Apr 28 17:08:00 moose cpufreqd: cpufreqd_loop            : Rule
unchanged ("AC Off - Low Battery"), doing nothing.

Wie kann cpufreqd denken, dass ac off ist, zumindest kriegen die "AC
OFF"-Regeln den hoechsten Score (51%)? Die CPU ist eine Core(TM)2 Quad
Q9650 CPU. Als Driver (nach cpufrq-info) wird  acpi-cpufreq benutzt.

Die folgenden Kerneloptionen haben etwas mit dem SYSFS zu tun:
root@moose:/home/rose/ISOs(29)# gzip -cd /proc/config.gz | grep -i sysfs
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_SYSFS=y

oder mit POWER:

root@moose:/home/rose/ISOs(60)# gzip -cd /proc/config.gz | grep -i power
# Power management and ACPI options
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_POWER_METER=m
CONFIG_ACPI_SYSFS_POWER=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
# CONFIG_X86_POWERNOW_K8 is not set
# Memory power savings
# CONFIG_INPUT_POWERMATE is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_SND_HDA_POWER_SAVE is not set
# CONFIG_POWER_TRACER is not set

Die Directories /proc/acpi/power_resource/, /proc/acpi/ac_adapter
und  /sys/class/power_supply/ sind leer. Warum eigentlich? Ist aber auf
allen anderen Rechner (mit Ausnahme meines Laptops) auch so, kann wohl
nicht die Ursache sein. Auf dem Laptop gibt es
unter /proc/acpi/ac_adapter ein Subdirectory AC/ mit der Datei state mit
dem Inhalt "online".

Wenn gnome-power-statistics starte habe ich nur den Prozessor Eintrag
und nicht den AC-Adapter und den Laptop-Batterie-Eintrag wie auf dem
Laptop.
Gibt es unter /proc oder /sys Eintraege, aus denen amn etwas ueber die
Vorstellungen von linux ueber die Stromversorgung des eigenen Rechners
erfahren kann?
 
Wenn ich on_ac_power aus den sys-power/pm-utils starte, erhalte ich
folgendes:
root@moose:/root(66)# on_ac_power
Error org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.UPower was not provided by any .service files
root@moose:/root(67)# echo $?
0
Neben der Fehlermeldung von freedesktop scheint der Rueckgabewert 0
anzuzeigen, dass mein Rechner doch denkt ac_power zu haben.

Alle Hinweise werden dankbar entgegengenommen.


-- 
Juergen Rose <rose@××××××××××××××.de>
Uni-Potsdam