FS#33967 - [linux] 3.8.x - 3.10.x Very high power consumption
Attached to Project:
Arch Linux
Opened by Link Mauve (linkmauve) - Friday, 22 February 2013, 12:52 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 07 October 2013, 10:49 GMT
Opened by Link Mauve (linkmauve) - Friday, 22 February 2013, 12:52 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 07 October 2013, 10:49 GMT
|
Details
Description:
Since the upgrade from 3.7.6 to 3.8 on my Lenovo X121e, the power consumption of the whole computer went from 8~10W to 15~19W, the heat went up too, without any other upgrade from the userland. I don’t run different programs and I don’t really know how to debug that, or which information to provide. Additional info: * package version(s) linux-3.8-1 Steps to reproduce: Install powertop Run it while on battery |
This task depends upon
Audio codec hwC0D0: IDT
Audio codec hwC0D3: Intel
both stuck at 100%. I _think_ that having powertop set "Enable Audio codec power management" to "Good" took care of it, but my battery was already flatlined (again, sigh). If that *is* the culprit, then we need to figure out how to fix this at boot time.
The other possibility is the GPU not entering RC6 (see bug #32025). Regardless of the culprit, I agree this is definitely a regression from 3.8 to 3.9. I'm guessing someone changed a default somewhere.
AfC
Having to run powertop all the time just to save my laptop from draining mercilessly is quite the pain.
AfC
Previous versions (I don't recall which ones exactly) used around 9W on battery, around 55°C - now it's running at ~25W on battery, 65 °C.
Powertop indicates very high "Display backlight" power usage, I see two of them, 8W each. Running at the lowest brightness setting doesn't affect the power usage very much.
I tested 3.10.2 too with the same result, the only usable kernel (i.e. without fan spinning during idle usage) is 3.5.6
Can you please create a file /etc/modprobe.d/snd-hda-intel.conf with this single line:
options snd-hda-intel power_save_controller=Y power_save=1
Then rmmod and modprobe or simple reboot the system. Does that help?