From: Jani Nikula <jani.nikula@intel.com>
To: Eric Rannaud <eric.rannaud@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Jon Kristensen <info@jonkri.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: i915: Regression: +4W in idle power use on Macbook Pro 15 (late 2013)
Date: Mon, 25 Aug 2014 13:19:05 +0300 [thread overview]
Message-ID: <87vbpglvmu.fsf@intel.com> (raw)
In-Reply-To: <CA+zRj8WfK3Dgcx2F-eOJ10ZroZaZDdB6NYp6SLpBs2eOu2bUOA@mail.gmail.com>
On Fri, 22 Aug 2014, Eric Rannaud <eric.rannaud@gmail.com> wrote:
> Hi,
>
> Between 3.15.4 and 3.15.8, there was an increase in idle power consumption on
> Apple Macbook Pro 15 (late 2013) on a freshly booted system (no wifi driver
> loaded; brightness set to 4/100; X running; no desktop environment, except
> Awesome), from 6.5W to about 10.5W, as reported by powertop.
>
> In the stable tree, it bisects to:
> commit f4db98240ac2c6d9d2118c6f82d483ff5293f1ed
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Fri Jun 6 10:37:11 2014 +0100
>
> drm/i915: Disable FBC by default also on Haswell and later
>
> commit 0368920e51ae0cded0eb518c340a4dd17764d461 upstream.
>
> It causes black screen on bootup and is approximately 100x
> slower than
> running with FBC disabled, so the GPU runs at a high
> frequency for much
> longer - completely contrary to the power saving claims.
> It also still
> has mutex deadlocks in multi-head scenarios, which can lead to a
> system/X lockup. These bugs were known before FBC was
> enabled by default
> on Haswell and still have not been fixed.
>
> The issue is still present in Linus' tree (v3.17-rc1-22-g480cadc2b7e0).
>
> With a 75Wh battery, that's a significant loss in battery life in normal use.
>
> I'll be happy to help test any potential fix.
The earlier regression trumps, and in this case it was enabling FBC by
default on Haswell. Sorry.
You can enable FBC with i915.enable_fbc=1 module parameter, but all bets
are off. See the commit message you quoted above. I don't recommend.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-08-25 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 17:40 i915: Regression: +4W in idle power use on Macbook Pro 15 (late 2013) Eric Rannaud
2014-08-25 10:19 ` Jani Nikula [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbpglvmu.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=eric.rannaud@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=info@jonkri.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox