From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: [PATCH] drm/i915/ilk: special case enabling of PCU_EVENT interrupt Date: Tue, 26 Aug 2014 21:03:11 +0200 Message-ID: <53FCD9EF.3060406@hartkopp.net> References: <1409009095-3621-1-git-send-email-jbarnes@virtuousgeek.org> <20140826072354.GY15520@phenom.ffwll.local> <20140826115256.432fc8b4@jbarnes-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [81.169.146.161]) by gabe.freedesktop.org (Postfix) with ESMTP id CF77B6E58E for ; Tue, 26 Aug 2014 12:03:20 -0700 (PDT) In-Reply-To: <20140826115256.432fc8b4@jbarnes-desktop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Jesse Barnes , Daniel Vetter Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On 26.08.2014 20:52, Jesse Barnes wrote: > On Tue, 26 Aug 2014 09:23:54 +0200 > Daniel Vetter wrote: >>> This happens in irq_postinstall before we've set the pm._irqs_disabled flag, >>> but shouldn't warn. So add a nowarn variant to allow this to happen w/o >>> a backtrace and keep the rest of the IRQ tracking code happy. >>> >> Also the commit message is a bit thin on the usual details like which >> commits introduced this regression, so that maintainers know where to >> apply this to. > > I don't have the commit... Oliver do you have it handy? > Hm - I really can not tell what has been done to introduce this regression. I just saw the warning on my machine after upgrading to 3.17 ... You can ask me about linux/net/can/ but not the drm stuff ;-) Cheers, Oliver