From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753252AbcFTIG4 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 20 Jun 2016 04:06:56 -0400
Received: from mga02.intel.com ([134.134.136.20]:30699 "EHLO mga02.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751099AbcFTIGu convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 20 Jun 2016 04:06:50 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.26,497,1459839600"; 
   d="scan'208";a="1005710402"
From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
        Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>,
        "Syrjala\, Ville" <ville.syrjala@intel.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window
In-Reply-To: <1466373202.2280.3.camel@HansenPartnership.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
References: <1464638381.2240.3.camel@HansenPartnership.com> <871t4ibr7k.fsf@intel.com> <1464701638.2234.1.camel@HansenPartnership.com> <87mvmp9z03.fsf@intel.com> <1466111747.2311.1.camel@HansenPartnership.com> <CAKMK7uGCn6rWGArnOah8bWojkWRdTPr8LeSdJb8iBojh8bHs-w@mail.gmail.com> <1466112547.2311.3.camel@HansenPartnership.com> <1466116932.2257.4.camel@HansenPartnership.com> <20160617072826.GI23520@phenom.ffwll.local> <87vb18uef2.fsf@intel.com> <1466204815.2199.2.camel@HansenPartnership.com> <1466373202.2280.3.camel@HansenPartnership.com>
User-Agent: Notmuch/0.22+12~gbdd9442 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu)
Date: Mon, 20 Jun 2016 11:03:44 +0300
Message-ID: <8737o89ti7.fsf@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


Cc: Ville

On Mon, 20 Jun 2016, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> OK, my candidate bad commit is this one:
>
> commit a05628195a0d9f3173dd9aa76f482aef692e46ee
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date:   Mon Apr 11 10:23:51 2016 +0300
>
>     drm/i915: Get panel_type from OpRegion panel details
>
> After being more careful about waiting to identify flicker, this one
> seems to be the one the bisect finds.  I'm now running v4.7-rc3 with
> this one reverted and am currently seeing no flicker problems.  It is,
> however, early days because the flicker can hide for long periods, so I
> 'll wait until Monday evening and a few reboots before declaring
> victory.

If that turns out to be the bad commit, it doesn't really surprise me,
and that in itself is depressing.

It might be helpful if you could add drm.debug=14 module parameter, and
provide dmesgs from boot both with and without the above commit (it's
enough to see i915 load). Please also provide
/sys/kernel/debug/dri/0/i915_opregion.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center