From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752359AbbDMF7E (ORCPT ); Mon, 13 Apr 2015 01:59:04 -0400 Received: from mail-pd0-f179.google.com ([209.85.192.179]:36683 "EHLO mail-pd0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751184AbbDMF7C (ORCPT ); Mon, 13 Apr 2015 01:59:02 -0400 Date: Mon, 13 Apr 2015 11:28:46 +0530 From: Sudip Mukherjee To: Chris Wilson , Daniel Vetter , Jani Nikula , David Airlie , Ville =?iso-8859-1?Q?Syrj=E4l=E4?= , huax.lu@intel.com, Daniel Vetter , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Revert "drm/i915: Performed deferred clflush inside set-cache-level" Message-ID: <20150413055846.GA2775@sudip-PC> References: <1427814612-4157-1-git-send-email-sudipm.mukherjee@gmail.com> <20150331153549.GM18595@nuc-i3427.alporthouse.com> <20150401043150.GB4638@sudip-PC> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150401043150.GB4638@sudip-PC> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 01, 2015 at 10:01:50AM +0530, Sudip Mukherjee wrote: > On Tue, Mar 31, 2015 at 04:35:49PM +0100, Chris Wilson wrote: > > On Tue, Mar 31, 2015 at 08:40:12PM +0530, Sudip Mukherjee wrote: > > > This reverts commit <0f71979ab7fbd0c71c41c2798de3d33937915434>. > > > > > > my display was getting garbled for a moment very frequently. it looked > > > like when the screen was getting refreshed then something was going > > > wrong. > > > git bisect gave this as the first bad commit, and after reverting it > > > now display is not having that problem. > > > > Hmm, I fear you would be just papering over a bug. Could you please file > > a bug on bugs.freedesktop.org so that we can root cause this? > > -Chris > filed at https://bugs.freedesktop.org/show_bug.cgi?id=89857 > > since this patch workes perfectly for me, i guess i need to apply it to > every new release till you are able to root cause and fix it. I am having the same problem with v4.0 also. Though I guess there is some improvement as now the problem is not appearing as frequently as it used to be. And reverting the patch again completely removed the problem. regards sudip