All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Eric Rannaud <eric.rannaud@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jon Kristensen <info@jonkri.com>
Subject: Re: i915: Regression: +4W in idle power use on Macbook Pro 15 (late 2013)
Date: Tue, 26 Aug 2014 14:06:04 +0300	[thread overview]
Message-ID: <20140826110604.GI4193@intel.com> (raw)
In-Reply-To: <CA+zRj8X5G3+5M5GdoXY+Go752EndpEAY0WXUFiomvZVx8q15QA@mail.gmail.com>

On Mon, Aug 25, 2014 at 05:19:49AM -0700, Eric Rannaud wrote:
> Hi Jani,
> 
> Is there a way to restore the prior lower power consumption when
> idling? As I understand it, FBC should not have a direct effect on
> power consumption when idle, only when the FB is actively refreshed.
> Is it understood why no FBC would have such a dramatic impact (+4W) on
> a system sitting idle?

FBC works best when the screen contents don't change. The more activity
on the screen the less effective FBC becomes. 4W sounds way too much for
FBC however. 0.4W is closer to what one might expect from FBC based on my
observations. 4W sounds more like the difference between min vs. max
display brightness to me.

> 
> I'm aware of i915.i915_enable_rc6=1 and i915.lvds_downclock=1, which I
> haven't yet tried. Is there anything else I should also try?
> 
> Thanks,
> Eric
> 
> On Mon, Aug 25, 2014 at 3:22 AM, Jani Nikula <jani.nikula@intel.com> wrote:
> >
> > [just moving from lkml to intel-gfx for a better fitting audience]
> >
> > On Mon, 25 Aug 2014, Jani Nikula <jani.nikula@intel.com> wrote:
> >> 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
> >
> > --
> > Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-08-26 11:06 UTC|newest]

Thread overview: 14+ 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
2014-08-25 10:22   ` Jani Nikula
2014-08-25 12:19     ` Eric Rannaud
2014-08-26 11:06       ` Ville Syrjälä [this message]
2014-08-26 13:38         ` Eric Rannaud
2014-08-26 14:57           ` Eric Rannaud
2014-08-26 20:59             ` Daniel Vetter
2014-08-26 23:00               ` Eric Rannaud
2014-08-27  9:17                 ` Ville Syrjälä
2014-08-27 17:50                   ` Eric Rannaud
2014-08-28 20:08                 ` Lu, Ran
2014-08-28 16:41     ` Sean V Kelley
2014-08-28 17:19       ` Eric Rannaud

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=20140826110604.GI4193@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eric.rannaud@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=info@jonkri.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.