From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758474Ab2ECT4S (ORCPT ); Thu, 3 May 2012 15:56:18 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:36909 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758338Ab2ECT4O (ORCPT ); Thu, 3 May 2012 15:56:14 -0400 Message-ID: <4FA2E2D8.5050303@suse.cz> Date: Thu, 03 May 2012 21:56:08 +0200 From: Jiri Slaby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120428 Thunderbird/14.0a2 MIME-Version: 1.0 To: Jesse Barnes , Chris Wilson , Jiri Slaby , LKML , dri-devel@lists.freedesktop.org Subject: Re: i915_driver_irq_handler: irq 42: nobody cared References: <4F758400.3080907@suse.cz> <1333104359_155028@CP5-2952> <20120409101119.47e770b2@jbarnes-desktop> <4F83F3B5.8080704@suse.cz> <20120410092619.26a15165@jbarnes-desktop> <4F8477D1.4080102@suse.cz> <20120410113448.540e4c1d@jbarnes-desktop> <4F848F88.7060009@suse.cz> <20120410203212.GN4115@phenom.ffwll.local> <20120410133411.52dc52ed@jbarnes-desktop> <20120411104012.GI4296@phenom.ffwll.local> In-Reply-To: <20120411104012.GI4296@phenom.ffwll.local> X-Enigmail-Version: 1.5pre 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/11/2012 12:40 PM, Daniel Vetter wrote: > On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote: >> On Tue, 10 Apr 2012 22:32:12 +0200 >> Daniel Vetter wrote: >> >>> On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote: >>>> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- >>>> SERR- >>> >>>> I tried 3.2 and 3.3. Although the spurious interrupts were always >>>> there, they occurred with frequency lower by a magnitude (15 vs. 300 >>>> after X starts). So I bisected that and it lead to a commit which >>>> fixes bad tiling for me: >>>> http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=for-jiri&id=79710e6ccabdac80c65cd13b944695ecc3e42a9d >>> >>> Pipelined fencing is pretty much just broken and we'll completely rip it >>> out in 3.5. Does this also happen with 3.4-rc2? >> >> Does INTx- stay that way? Or does it frequently read INTx+ if you >> sample it a lot? If it stays as INTx-, then something other than the >> GPU is getting stuck (though it's possible this could be related to >> pipelined fencing, if the fences are programmed to point at some funky >> memory space). Hi and sorry for the delay. It stays INTx-. And I tested that with patch removing fencing. > Shot in the dark, let's disable msi a bit. Can you try the below patch? Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is busted, either in the card, the chipset or the kernel. Any idea how to find out? thanks, -- js suse labs