All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Andrew Lutomirski <luto@mit.edu>, intel-gfx@lists.freedesktop.org
Subject: Re: [regression?] i915 generating wakeups even when idle
Date: Tue, 07 Dec 2010 22:13:15 +0000	[thread overview]
Message-ID: <b9dded$haijsn@orsmga002.jf.intel.com> (raw)
In-Reply-To: <AANLkTinfbkOeLvgi-eWTV2H1pERJJBdFogwZsyiTX2jq@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Tue, 7 Dec 2010 16:31:24 -0500, Andrew Lutomirski <luto@mit.edu> wrote:
> On Tue, Dec 7, 2010 at 4:03 PM, Andrew Lutomirski <luto@mit.edu> wrote:
> > Hi all-
> >
> > Somewhere between Fedora 13 (with 2.6.35, I think) and Fedora 14 +
> > 2.6.36.1, i915 started generating exactly 50 interrupts per second
> > (suspiciously equal to my refresh rate) when X is running.  I have the
> > Xorg driver 2.12.0 (specifically
> > xorg-x11-drv-intel-2.12.0-6.fc14.1.x86_64).  When I switch to a text
> > console but leave X running, the interrupts stop.
> >
> > Any ideas what to look at?
> 
> Quitting compiz fixes it.  Suspending compiz also fixes it.

So it is the vblank interrupt. The vblank interrupt is get alive for a few
seconds after the last use. If it keeps going, then either the system is
as idle as you believe or we lost track of the last user and forget to
switch off the interrupt.

drm.debug=0xf (echo 0xf > /sys/module/drm/parameters/debug) will have the
gory details of who/when triggers the vblank interrupt.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2010-12-07 22:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 21:03 [regression?] i915 generating wakeups even when idle Andrew Lutomirski
2010-12-07 21:31 ` Andrew Lutomirski
2010-12-07 22:12   ` Jesse Barnes
2010-12-07 22:13   ` Chris Wilson [this message]
2010-12-07 22:26     ` Andrew Lutomirski
2010-12-08 18:17     ` Andrew Lutomirski
2010-12-08 18:33       ` [TERRIBLE PATCH] " Andrew Lutomirski
2010-12-09 17:20         ` Jesse Barnes
2010-12-09 17:47           ` Andrew Lutomirski
2010-12-09 18:23             ` Jesse Barnes
2010-12-09 18:32               ` Andrew Lutomirski
2010-12-09 18:44                 ` Jesse Barnes

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='b9dded$haijsn@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luto@mit.edu \
    /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.