Re: [PATCH] drm/i915/ilk: special case enabling of PCU_EVENT interrupt

[Jesse Barnes <jbarnes@virtuousgeek.org>]

On Tue, 26 Aug 2014 21:03:11 +0200
Oliver Hartkopp <socketcan@hartkopp.net> wrote:

> On 26.08.2014 20:52, Jesse Barnes wrote:
> > On Tue, 26 Aug 2014 09:23:54 +0200
> > Daniel Vetter <daniel@ffwll.ch> 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 ;-)

I think it was this one Daniel, or the combination of patches around it:

commit 95f25beddba2ec9510b249740bacc11eca70cf75
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Fri Jun 20 09:29:22 2014 -0700

    drm/i915: set pm._irqs_disabled at IRQ init time


-- 
Jesse Barnes, Intel Open Source Technology Center