Problem with high power drain in ACPI sleep
Problem descriptionSeveral people realized that their ThinkPads eat up too much power while suspended to ram via ACPI. Compared to APM suspend to ram the power drain is experienced to be about 10 times as high, 2-5 Watts. This empties the battery within one or two days. |
Affected Models
| affected models | unaffected models |
|---|---|
|
- Different symptoms have been reported for different models. In some models the origin of the power drain is obvious (backlight on during suspend), in other models there is no obvious reason.
- On some models/configurations the higher power drain couldn't even be realized or was at least significantly lower.
- The T4x ThinkPad series and other Radeon based models suspend to ram just fine, and there are no components that are obviously left powered up. The UltraBay and network light is on, but that is the same under windows (but under APM sleep to RAM those lights are OFF). For these models the higher power drain is caused by a driver problem and can be fixed in software. This fix has not yet made its way into the official kernel (as of linux 2.6.12).
The table on the right gives an overview of the models suffering from the mysterious power drain. To find out about your model, you may use the following script. It creates a file /var/log/battery.log which will tell you if you are affected or not.
Affected Operating Systems
- Linux, all flavours.
- Windows, for some models as well (only when using non-IBM drivers).
- FreeBSD (on the A22M)
Status
- The cause of the mysterious power drain is the Radeon GPU, which requires extra steps to suspend properly. Unfortunately, this fix might break non-ThinkPad machines and therefore is not yet in the official kernel sources.
- The official bugzilla entry for the radeon suspend issue is in the OSDL Bugzilla. There you can find a patch which will solve the power drain issue.
- Most certainly, the DSDT is not at fault. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)
- Some additional power savings can be achieved by turning off the wake-on-lan (
# ethtool -s eth0 wol d). The power drain of the wol feature is far smaller than the radeon bug, but can be noticeable.
Solutions
For ThinkPads with Radeon graphic chips
You must use a patched version of the radeon frame buffer, even if you are only interested in using the X window system. This modified radeon frame buffer then suspends the radeon chip correctly during ACPI sleep. This patch is not yet in the official (kernel.org) kernels.
The patch contains a list of ThinkPads where it is known to work, and by default only activates on these machines. If you think that your computer would profit from the patch as well, you can force it by including the module parameter force_sleep=1. If it doesn't work this can result in system hangs.
Technical Background
The patch removes the CONFIG_PPC_PMAC condition for enabling D2 sleep in drivers/video/aty/radeon_pm.c as discussed in kernel bug 3022.
Fedora Core
- Fedora Core 4: Fedora ships a patched radeon frame buffer (radeonfb.ko), but you must enable it yourself. Fedora compiles it as a module rather than including it in the kernel, therefore you cannot activate it at boot time without a custom initrd. You must arrange for the module to be loaded before X starts (for example, using an init script).
- Fedora Core 3: this is also true for updated kernels (at least for kernel-2.6.12-1.1376_FC3) but not for the initially shipped version.
There are precompiled patched kernels available as well, that do not need an initrd modification:
These kernels contain additional ThinkPad-related patches, including Software Suspend 2 and trackpoint support. Suspend to disk and suspend to ram should work with them. If your ThinkPad model is not yet whitelisted in the patch, you might have to enable the radeon fix by including the parameter video=radeonfb:force_sleep on the kernel command line.
If you try, please send the result (hang yes/no, battery drain yes/no) with the precise model number (i.e. IBM ThinkPad T41 2379-DJU) to vbraun at physics dot upenn dot edu, it would be nice if your subject line would include "RADEONFB:" to make sure that I do not miss any emails.
testing radeonfb without changing initrd
If you want to try the radeon frame buffer, you can enable it as follows:
- First, switch to a console (CtrlAltF1) and log in as root.
- Stop X:
# init 3 - Now you can load the module:
# modprobe radeonfb force_sleep=1 - Finally, resume X:
# init 5
including radeonfb into your initrd
As an alternative you can build your customized initrd. This is as simple as running
# mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> `uname -r`
and replacing the initrd in /boot/grub/grub.conf with your new one. You also need to add the kernel command line argument video=radeonfb:force_sleep.
Gentoo
After installing the patch on Gentoo (it works fine with gentoo-sources: # cd /usr/src/linux/drivers/video/aty, and execute # patch -p4 < <patchname>, then recompile the kernel), one needs to add video=radeonfb:force_sleep to the kernel parameters.
Another possible solution
It is possible that radeontool will help some people with this case. (simply run radeontool light off before suspend and radeontool light on after resume). A radeontool patch for freebsd is here: http://www.init-main.com/radeontool.patch (by Takanori Watanabe).
For models without Radeon graphics
The Problem seems to be solved when you use the vbetool to turn the LCD off before suspending ...
# vbetool dpms off
and turning it on afterwards again...
# vbetool dpms on
You have to change to a normal console before turning the LCD off. Additionally you have to deactivate the Wake-On-Lan feature like mentioned above ...
# ethtool -s eth0 wol d
With these commands used together the "testing script" reports no high power drain while suspending.
Other problems causing the power drain
On my R51 using Gentoo Linux, the high power drain was not caused by the graphics adaptor but by several components not powered down properly before putting the Thinkpad into S3.
If the above did not help you, this might do:
Walk through
/sys/devices/*/*/power/state
and try to disable each of it, every time checking the power drain. (See linux/Documentation/power/devices.txt for values to write into the state-files. 3 should be the value you want to try) Do the same for other components (Like the Ultrabay, etc.). Please add your experiences here.
R51: Ultrabay and networking
On my system, ultrabay and networking light were still on while in S3. So were the devices theirselves.
echo -n eject > /proc/acpi/ibm/bay # Disable ultrabay ethtool -s eth0 wol d # Disable Wake-On-Lan (And so the eth-adaptor) echo mem > /sys/power/state # Sleep
For me, this lowered the power drain from >700mW to 338 mW.
