From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jiri Slaby <jslaby@suse.cz>, Jiri Slaby <jirislaby@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: i915_driver_irq_handler: irq 42: nobody cared
Date: Mon, 9 Apr 2012 10:11:19 -0700 [thread overview]
Message-ID: <20120409101119.47e770b2@jbarnes-desktop> (raw)
In-Reply-To: <1333104359_155028@CP5-2952>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Fri, 30 Mar 2012 11:45:43 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby <jslaby@suse.cz> wrote:
> > I don't know what to dump more, because iir is obviously zero too. What
> > other sources of interrupts are on the (G33) chip?
>
> IIR is the master interrupt, with chained secondary interrupt statuses.
> If IIR is 0, the interrupt wasn't raised by the GPU.
I've actually seen cases where one of the PIPE*STAT regs is stuck, and
even if IIR is 0 we still get interrupts... Jiri can you verify the
PIPE*STAT regs have bits set, maybe one or more we don't check for?
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-09 17:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F717CE3.4040206@suse.cz>
2012-03-27 8:42 ` i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-03-30 9:59 ` Jiri Slaby
2012-03-30 10:45 ` Chris Wilson
2012-03-30 12:11 ` Jiri Slaby
2012-03-30 12:24 ` Chris Wilson
2012-04-06 21:31 ` i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?] Jiri Slaby
2012-04-06 22:40 ` Thomas Gleixner
2012-04-09 17:12 ` Jesse Barnes
2012-04-09 17:52 ` Dave Airlie
2012-04-10 8:44 ` Jiri Slaby
2012-04-10 8:50 ` Daniel Vetter
2012-04-10 8:52 ` i915_driver_irq_handler: irq 42: nobody cared Jiri Slaby
2012-04-10 16:50 ` Marcin Slusarz
2012-04-09 17:11 ` Jesse Barnes [this message]
2012-04-10 8:47 ` Jiri Slaby
2012-04-10 8:58 ` Daniel Vetter
2012-04-10 9:48 ` Jiri Slaby
2012-04-10 16:26 ` Jesse Barnes
2012-04-10 18:11 ` Jiri Slaby
2012-04-10 18:34 ` Jesse Barnes
2012-04-10 19:52 ` Jiri Slaby
2012-04-10 20:32 ` Daniel Vetter
2012-04-10 20:34 ` Jesse Barnes
2012-04-11 10:40 ` Daniel Vetter
2012-05-03 19:56 ` Jiri Slaby
2012-05-03 21:15 ` Daniel Vetter
2012-05-03 21:16 ` Jiri Slaby
2012-05-03 21:54 ` Jesse Barnes
2012-05-03 23:15 ` Ben Widawsky
2012-04-11 6:29 ` Michel Dänzer
2012-04-11 16:03 ` Jesse Barnes
[not found] ` <20120327085749.GE4276@phenom.ffwll.local>
2012-03-27 10:54 ` Jiri Slaby
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=20120409101119.47e770b2@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--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