From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753561AbcKGRJu (ORCPT ); Mon, 7 Nov 2016 12:09:50 -0500 Received: from mga03.intel.com ([134.134.136.65]:30184 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753138AbcKGRJt (ORCPT ); Mon, 7 Nov 2016 12:09:49 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,606,1473145200"; d="scan'208";a="783496158" From: Jani Nikula To: Martin Steigerwald Cc: Linus Torvalds , Intel Gfx Mailing List , Linux Kernel Mailing List Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4) In-Reply-To: <2766000.XjMLcDtyKU@merkaba> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <2656903.keIazZlQoI@merkaba> <87twbj8sb3.fsf@intel.com> <2766000.XjMLcDtyKU@merkaba> Date: Mon, 07 Nov 2016 19:09:36 +0200 Message-ID: <87k2cf8be7.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 07 Nov 2016, Martin Steigerwald wrote: > It is also the same kind of corruptions as shown in > > [Bug 177701] warning in intel_dp_aux_transfer > https://bugzilla.kernel.org/show_bug.cgi?id=177701 > > Just compare > > https://bugzilla.kernel.org/attachment.cgi?id=241801 > > with > > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png > > > However that bug report links to > > https://bugs.freedesktop.org/show_bug.cgi?id=97344 > > yet the patch mentioned in there does not fix the issue. So I wonder whether > bug #97344 and bug #177701 are really the same. They are the same, it's just that #177701 conflates two issues, a warning (tracked at fdo #973449) and a graphics corruption. The latter appears to be https://bugs.freedesktop.org/show_bug.cgi?id=98402. The fix has now been pushed to drm-intel-fixes branch of http://cgit.freedesktop.org/drm-intel, which is -rc4 plus half a dozen latest fixes. Please try that and report back. > Of course I can report a bug at fdo as well, but I am a bit confused > whether it may not already have been reported. Well I hope I get a > chance to report it there as well and you get to decide. If drm-intel-fixes doesn't fix the issue for you, please file a *new* bug over at the freedesktop.org bugzilla. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center