From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756122Ab3GYOXo (ORCPT ); Thu, 25 Jul 2013 10:23:44 -0400 Received: from mail-wg0-f53.google.com ([74.125.82.53]:58248 "EHLO mail-wg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755609Ab3GYOXm (ORCPT ); Thu, 25 Jul 2013 10:23:42 -0400 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: <20130725133651.GI5939@phenom.ffwll.local> References: <87ehanx9bx.fsf@intel.com> <87bo5rx7m0.fsf@intel.com> <20130725133651.GI5939@phenom.ffwll.local> Date: Thu, 25 Jul 2013 16:23:40 +0200 Message-ID: Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] From: Sedat Dilek To: Sedat Dilek , Jani Nikula , Stephen Rothwell , intel-gfx , linux-kernel@vger.kernel.org, DRI , linux-next@vger.kernel.org Cc: Daniel Vetter Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 25, 2013 at 3:36 PM, Daniel Vetter wrote: > On Thu, Jul 25, 2013 at 12:37:44PM +0200, Sedat Dilek wrote: >> On Thu, Jul 25, 2013 at 12:21 PM, Jani Nikula >> wrote: >> > On Thu, 25 Jul 2013, Sedat Dilek wrote: >> >> On Thu, Jul 25, 2013 at 12:02 PM, Sedat Dilek wrote: >> >>> On Thu, Jul 25, 2013 at 11:44 AM, Jani Nikula >> >>> wrote: >> >>>> On Thu, 25 Jul 2013, Sedat Dilek wrote: >> >>>>> On Thu, Jul 25, 2013 at 7:12 AM, Stephen Rothwell wrote: >> >>>>>> Hi all, >> >>>>>> >> >>>>>> Changes since 20130724: >> >>>>>> >> >>>>>> Removed tree: >> >>>>>> arm-dt (at maintainer's request) >> >>>>>> >> >>>>>> The wireless-next tree lost its build failure and gained a conflict >> >>>>>> against Linus' tree. >> >>>>>> >> >>>>>> The tty tree lost its build failure. >> >>>>>> >> >>>>>> The staging tree gained a build failure for which I disabled a driver. >> >>>>>> >> >>>>>> ---------------------------------------------------------------------------- >> >>>>>> >> >>>>> >> >>>>> [ CCing drm and drm-intel folks ] >> >>>>> >> >>>>> With today's next-20130725 I see the following: >> >>>> >> >>>> Use of dev_priv->gt_lock in I915_WRITE through >> >>>> intel_disable_gt_powersave before spin lock init, caused by >> >>>> >> >>>> commit 181d1b9e31c668259d3798c521672afb8edd355c >> >>>> Author: Daniel Vetter >> >>>> Date: Sun Jul 21 13:16:24 2013 +0200 >> >>>> >> >>>> drm/i915: fix up gt init sequence fallout >> >>>> >> >>> >> >>> Ah, cool. >> >>> >> >>> I assumed/tested "drm/i915: fix the racy object accounting", but this >> >>> does not fix it. >> >>> Will try with yours. >> >>> >> >> >> >> Sorry, Jani. >> >> >> >> next-20130725 ships the patch you pointed, too. >> > >> > Confused. I meant that the above mentioned commit "drm/i915: fix up gt >> > init sequence fallout" causes the problem. The patch I included in my >> > mail should fix it. Could you try that please? >> > >> >> [ Note2myself: Do not read half of the message... ] >> >> The bad... Your patch needed some refresh against next-20130725 (guess >> it's against drm-intel-nightly). >> >> The good... YES, your patch fixes the issue for me! >> >> The ugly... /me. >> >> Feel free to add my: >> >> Tested-by: Sedat Dilek >> >> Thanks for the quick fix! > > Thanks a lot for the report, since this should be something I should have > caught. And for added insult the offending patch is already in Linus' tree > :( Patch merged to -fixes. Hmmm, don't you merge -fixes into -nightly? - Sedat - > -Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch