Bug 917854 - kernel 3.8 has 50% increase in power consumption
Summary: kernel 3.8 has 50% increase in power consumption
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-04 22:48 UTC by Alessandro Guido
Modified: 2013-07-01 13:14 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-01 13:14:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Dmesg 3.7 (76.31 KB, text/plain)
2013-03-05 00:05 UTC, Alessandro Guido
no flags Details
Dmesg 3.8 (71.30 KB, text/plain)
2013-03-05 00:06 UTC, Alessandro Guido
no flags Details

Description Alessandro Guido 2013-03-04 22:48:54 UTC
With the upgrade to the 3.8 kernel, power consumption on a Dell XPS 14 resulted in an increase of a 50% (and more) when running on battery.

With 3.7, I observed (powertop, all tunings set to "Good") a power usage as low as 8W. With kernel 3.8 I'm not able to get any lower than 14W (and I can hear the fan is always running, while with 3.7 it didn't happen).

Booting with 3.7 restores the good behaviour.

Powertop output looks the same, so I haven't been able to pinpoint the problem more exactly.

Comment 1 Alessandro Guido 2013-03-05 00:05:59 UTC
Created attachment 705231 [details]
Dmesg 3.7

Comment 2 Alessandro Guido 2013-03-05 00:06:35 UTC
Created attachment 705232 [details]
Dmesg 3.8

Comment 3 Josh Boyer 2013-04-16 19:43:05 UTC
If you're still seeing this with 3.8.7, can you please use powertop on both the 3.7 and 3.8 kernels to see if there is a particular device that is causing significantly more wakeups, etc?  There is a known i915 issue with resets in bug 866212 but it's hard to tell if you are seeing that or something else.

Comment 4 Josh Boyer 2013-07-01 13:14:11 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.