All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lutomirski <luto@mit.edu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.sf.net
Subject: Re: [resend] i915: high power consumption after suspend/resume
Date: Wed, 4 Nov 2009 23:00:14 -0500	[thread overview]
Message-ID: <cb0375e10911042000h3cf215a1o44add74510c15a1c@mail.gmail.com> (raw)
In-Reply-To: <cb0375e10910301155s5e2b2e79t562bfa798ba75e23@mail.gmail.com>

Here's some more info.  I write a little script:

#!/bin/sh

for ((i=0; $i < 15; i=$i+1)); do cat
/sys/class/power_supply/BAT0/power_now; sleep 1 ; done

echo 'Wedging'
echo 1 > /sys/kernel/debug/dri/0/i915_wedged

for ((i=0; $i < 15; i=$i+1)); do cat
/sys/class/power_supply/BAT0/power_now; sleep 1 ; done

I triggered the high power consumption twice today.  I logged out of
X, logged into a console, and ran the script each time.  (The first
time, I did 10 iterations, not 15.)  Here are the results:

9586000
9574000
9574000
9586000
9586000
9574000
9574000
9629000
9629000
9607000
Wedging
9607000
9614000
9614000
9173000
9173000
8775000
8775000
8535000
8535000
8341000

and

9080000
9080000
9022000
9022000
9112000
9112000
9100000
9100000
9100000
9100000
9123000
9123000
9112000
9112000
9135000
Wedging
9135000
9053000
9053000
8618000
8618000
8309000
8309000
8056000
8056000
7861000
7861000
7712000
7712000
7643000
7643000

so it looks like it's not a register setting after all.  Maybe my BIOS
leaves the renderer in some weird state.

--Andy

  reply	other threads:[~2009-11-05  4:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 16:39 i915: high power consumption after suspend/resume Andrew Lutomirski
2009-10-03 16:50 ` [resend] " Andrew Lutomirski
2009-10-05 16:21   ` Jesse Barnes
2009-10-08  3:44     ` Andrew Lutomirski
2009-10-29 16:47       ` Jesse Barnes
2009-10-29 17:22         ` Andrew Lutomirski
2009-10-29 17:40           ` Andrew Lutomirski
2009-10-30  6:25             ` Andrew Lutomirski
2009-10-30 15:37               ` Jesse Barnes
2009-10-30 18:55                 ` Andrew Lutomirski
2009-11-05  4:00                   ` Andrew Lutomirski [this message]
2009-11-05 16:28                     ` Jesse Barnes
2009-11-06 20:25                       ` Andrew Lutomirski
2009-11-06 21:57                         ` Jesse Barnes
2009-11-10 14:42                           ` Andrew Lutomirski

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=cb0375e10911042000h3cf215a1o44add74510c15a1c@mail.gmail.com \
    --to=luto@mit.edu \
    --cc=dri-devel@lists.sf.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --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 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.