How to reduce power consumption

From ThinkWiki
Revision as of 16:27, 25 June 2007 by Benjamin Pineau (Talk | contribs) (→‎Tools: clarify)
Jump to: navigation, search

Reducing system power consumption will extend battery life, reduce system temperature and (on some models) reduce system fan noise. Power consumption can be greatly improved from a stock distribution configuration to a fine tuned system. The general rules are :

  • Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
  • Reduce polling on devices (drives, USB subsystem, nvram, ...)
  • Reduce hard drive activity
  • Reduce LCD brightness to the minimum you can stand
  • Reduce CPU wakeups, so it can stay longer in deep power saving c-states

Tools

Arjan van de Ven's PowerTOP utility is a gold mine to improve energy efficiency. This tool helps to easily detect the top power offenders, both userland and kernel modules, and sometime suggest fixes accordingly. PowerTOP users collected some tips & tricks and an informative faq. When you see an application causing a lot of wakeups in PowerTOP, you should strace it to understand what is happening.

To detect what make your disk spinning (a costly operation), 

sysctl vm.block_dump=1

will list all applications causing disks wakeups on the kernel's dmesg. Other tools for this purpose are blktrace and iostat.

BIOS settings

Some Thinkpad BIOS (like 2.08 BIOS on X40) offer two very lame options, with a very misleading online help (saying "Usually not needed"). That's 

CPU power management: (default disabled)
PCI bus power management: (default disabled)

You should indeed enable them, else the deepest C3 and C4 ACPI C-states are disabled.

CPU

Look at:

A good thing to keep in mind is that every CPU wakeup, even if it's for a trivial light job, reduce the time the CPU stays on a deep power saving C-state (like C3 or C4). Therefore you should ensure your applications stay really idle when they meant to be idle (track to short select timeouts in loop, etc.).

Also note that manually locking the CPU in the lowest P-state (frequency) available is not an efficient way to improve battery lifetime. This will cause the CPU to stay longer in C0 (power angry C-state) doing hard work when there is something to do, while it could have done this work faster by augmenting the CPU freq, and returned back faster to deeper, economic, C-state. The best is to let the kernel choose the appropriate CPU frequencies by itself. Have a look at this explanation from Intel's kernel developer Arjan van de Ven.

Kernel settings and patches

General settings

The 2.6.21 kernel brought some very effective changes (like dynticks). If it's not already on your distribution and you value power efficiency, you may think about compiling it (or a more recent one) yourself.

Here are a few options (beside the ACPI and APM related one) that matter by reducing power consumption or helping to diagnose consumers, From PowerTOP's FAQ : 

CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
# not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI

Those options are already in Fedora Core 7 and Ubuntu Gutsy default kernels. PowerTOP FAQ also suggest to disable CONFIG_IRQBALANCE et CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:

Useful Patchs

Thomas Gleixner High Resolution Timers (hrt) patchset brings some improvements, like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force enable HPET" patches (non HPET timers causes about 20-30 CPU wakeups/second). See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on Aggressive Link Power Management (ALPM) for the ahci driver. See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

Useful sysctls

The meaning of those settings are explained on the relevant sections of this document. But for convenience sake, we regroupe them here too.

Note that the "ondemand" scaling governor is recommended by Intel developpers for energy efficiency: it's expected to be more efficient than the "powersave" governor, and than userspace daemon (cpureq-utils, cpufreqd, powernowd...). Look here, there or here for a kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you run Kirsten patchset on AHCI SATA drives. 

echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

ATA drives

Hard drives and CDRom drives spinning is very costly. To improve battery lifetime, you should reduce disks access (or devices polling) the more you can.

Hard Drives

The files access time update, while mandated by POSIX, is causing lots of disks access, even for file accessed while on cache. If you don't use this feature, disable it via: 

mount -o remount,noatime /  # and so on for all mounted fs

The laptop_mode reduce disk usage by regrouping writes. You should enable it, at least while on battery. See Laptop-mode for more details: 

echo 5 > /proc/sys/vm/laptop_mode

The default kernel dirty page writeback frequency is very conservative. On a laptop running on battery, one might find more appropriate to reduce it: 

echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

Some power saving hard drives features can be activated with hdparm. For more details look at How to make use of Power Management features : 

hdparm -B 1 -S 12 /dev/sda # and/or any other disk device

Optical drive

The optical drive consumes about 1W even when not accessed.* Eject the UltraBay optical drive, or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).

The hald daemon polling tends to maintain the ATA buses out of power saving modes, and to wakeup CDROM drive. If you have a recent hald version, you can stop this polling when on battery (if your hald is not recent enough, consider stopping it on battery) : 

hal-disable-polling /dev/scd0 # or whatever your CD drive is

LCD Backlight/Brightness

The LCD backlight is one of the major power drain (usually consumes 5W or more at full brightness). So reducing brightness to the lowest readable level will save you a lot of battery lifetime. Also, don't forget to configure your screen saver to shutdown the screen backlight (and not to display some eye candy), when no activity for a few minutes.

If you're choosing your Thinkpad laptop model, keep in mind that the screen size affect the battery time greatly (more power needed for larger screens).

Graphic controllers

All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have the same bug causing very frequent CPU wakeups when DRI is activated, even when you don't use any 3D application. This problem is (partly) fixed on xorg git tree (but not released as of xorg 7.2). If you value more battery than 3D, you should disable DRI: put this on the /etc/X11/xorg.conf "Device" of you graphic controller: 

Option          "NoDRI"

Also be sure that DPMS is working (if not, had Option "DPMS" to your config).

On recent xrandr/xorg versions, you can disable the TV output when you're not using it, it saves about 1W: 

xrandr --output TV -off

See also:

USB Subsystem

The kernel support an efficient USB 2.0 power saving feature if you enabled CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device plugged (and beside, USB devices tends to suck power on their own), so avoid using such devices when on battery.

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go in a low power mode when you enabled it, even if you don't have any device plugged. You'd better remove it when you don't use a 1.1 device: 

rmmod uhci_hcd

If you don't intend to use any USB 1.1 only device (those tends to be rare anyway), the USB 1.1 support can also be totaly avoided. On Debian and derivatives, just do: 

echo "blacklist uhci_hcd" > /etc/modprobe.d/blacklist.

Sound

ALSA has a power saving feature that should be enabled on your kernel (CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in unless you muted all sound inputs (micro, line in etc.). This feature has to be activated with: 

echo Y > /sys/module/snd_ac97_codec/parameters/power_save

Seel also How to enable AC97 power saving.

Wireless Interface

Wireless network Consumes up to ~4W. To save power, you can kill the Wi-Fi radio when it's not in use: 

echo 1 > /sys/bus/pci/drivers/ipw2200/*/rf_kill

If you need Wi-Fi, you can also reduce power consumption (at the price of performances) by activating the power saving modes: 

iwpriv eth0 set_power 5 # or 7 (even more saving, less perfs)

Reducing Beacon intervals on your Access Point to 1 per second will also reduce network card interrupts, and helps power savings.

Ethernet Controler

If you don't use Wake-on-LAN, you should disable it for your network card, because it sucks a lot of power: 

ethtool -s eth0 wol d

If you can, try to reduce useless network activity coming to your NIC (ie. uneeded broadcasts), those cause interrupts and CPU wakeups.

Bluetooth

When you don't need bluetooth, disable it. Because of it's radio, bluetooth is not power friendly. 

hciconfig hci0 down ; rmmod hci_usb

System Fans

Consumes about 0.5W when running.

Misbehaving Userland

You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager and Evolution while on battery. Look at the PowerTOP's known problems list.

See Also

External resources

Retrieved from "https://www.thinkwiki.org/w/index.php?title=How_to_reduce_power_consumption&oldid=30680"