Month: May 2007
-
powertop: misc causes for wakeups
Cn Avg residency (10s) Long term residency avg C0 (cpu running) ( 1.9%) C1 0.0ms ( 0.0%) 0.0ms C2 13.3ms (67.5%) 13.4ms C3 10.9ms (26.9%) 10.5ms C4 8.2ms ( 3.6%) 8.4ms Wakeups-from-idle per second : 79.9 Top causes for wakeups: 19.0% (10.3) firefox-bin : schedule_timeout (process_timeout) 18.7% (10.1) <interrupt> : Intel ICH6 Modem, ipw2200, lan0…
-
Quote: credit to mat|gentoo in #gentoo@irc.freenode.net
mat|gentoo left the room (quit: “The day Microsoft makes something that doesn’t suck is the day they start making vacuum cleaners”). It made me giggle. heh
-
powerTOP: CPU governors
“Conservative” Governor 2.1% (10.0) cpufreq-set : cpufreq_governor_dbs (delayed_work_timer_f “Ondemand” Governor 32.2% (50.0) cpufreq-set : queue_delayed_work_on (delayed_work_timer_ The userspace, performance, powersave governors do not poll automatically therefore powerTOP doesn’t list them. The Ondemand governor is suitable while the laptop is powered by AC. While Conservative or powersave is logical to use on battery mode.
-
powerTOP
Intel has released a fascinating new utility that reveals what is preventing the CPU from going to sleep/low power state. A few of the bad actors I found on my system so far are ipw2200, hald, and audacious. hald appears to poll the disk constantly for something so it’s ide0 that appears active but not…