From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758603Ab2DJIr4 (ORCPT ); Tue, 10 Apr 2012 04:47:56 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:38484 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758564Ab2DJIry (ORCPT ); Tue, 10 Apr 2012 04:47:54 -0400 Message-ID: <4F83F3B5.8080704@suse.cz> Date: Tue, 10 Apr 2012 10:47:49 +0200 From: Jiri Slaby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120404 Thunderbird/13.0a2 MIME-Version: 1.0 To: Jesse Barnes CC: Chris Wilson , Jiri Slaby , LKML , dri-devel@lists.freedesktop.org Subject: Re: i915_driver_irq_handler: irq 42: nobody cared References: <4F717CE3.4040206@suse.cz> <4F717D80.9040207@suse.cz> <4F758400.3080907@suse.cz> <1333104359_155028@CP5-2952> <20120409101119.47e770b2@jbarnes-desktop> In-Reply-To: <20120409101119.47e770b2@jbarnes-desktop> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/09/2012 07:11 PM, Jesse Barnes wrote: > On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson > wrote: > >> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby >> 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? Note that I already attached their contents... This is what is in them (pipes 0 and 1): [ 3572.968581] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3572.977472] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3576.224839] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3576.243558] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3576.384912] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3576.403462] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3577.464100] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3577.477383] i915_driver_irq_handler: 0=00000000 1=00000000 [ 3577.829016] i915_driver_irq_handler: 0=00020000 1=00000000 [ 3577.830093] i915_driver_irq_handler: 0=00020000 1=00000000 I.e. the handler is called when IIR=0 and both pipe stats are 0. The stats are dumped this way: @@ -1416,6 +1417,14 @@ static irqreturn_t i915_driver_irq_handler(DRM_IRQ_ARGS) iir = new_iir; } + if (ret == IRQ_NONE && printk_ratelimit()) { + printk(KERN_DEBUG "%s:", __func__); + for_each_pipe(pipe) { + printk(KERN_CONT " %d=%.8x", pipe, + pipe_stats[pipe]); + } + } + return ret; } thanks, -- js suse labs