Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755488Ab3GYKUS (ORCPT ); Thu, 25 Jul 2013 06:20:18 -0400 Received: from mga03.intel.com ([143.182.124.21]:49014 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753369Ab3GYKUP (ORCPT ); Thu, 25 Jul 2013 06:20:15 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,742,1367996400"; d="scan'208";a="273060691" From: Jani Nikula To: sedat.dilek@gmail.com Cc: Stephen Rothwell , Daniel Vetter , intel-gfx , linux-kernel@vger.kernel.org, DRI , linux-next@vger.kernel.org Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <87ehanx9bx.fsf@intel.com> User-Agent: Notmuch/0.15.2+227~g0ff681e (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu) Date: Thu, 25 Jul 2013 13:21:43 +0300 Message-ID: <87bo5rx7m0.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2269 Lines: 71 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? BR, Jani. > > - Sedat - > > [1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/?id=next-20130725&qt=grep&q=drm%2Fi915%3A+fix+up+gt+init+sequence+fallout > [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=181d1b9e31c668259d3798c521672afb8edd355c > -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/