From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel.vetter@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"David Airlie" <airlied@linux.ie>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
huax.lu@intel.com, "Daniel Vetter" <daniel.vetter@ffwll.ch>,
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"
Date: Wed, 1 Apr 2015 10:01:50 +0530 [thread overview]
Message-ID: <20150401043150.GB4638@sudip-PC> (raw)
In-Reply-To: <20150331153549.GM18595@nuc-i3427.alporthouse.com>
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.
regards
sudip
>
> --
> Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2015-04-01 4:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 15:10 [PATCH] Revert "drm/i915: Performed deferred clflush inside set-cache-level" Sudip Mukherjee
2015-03-31 15:10 ` Sudip Mukherjee
2015-03-31 15:35 ` Chris Wilson
2015-03-31 15:35 ` Chris Wilson
2015-04-01 4:31 ` Sudip Mukherjee [this message]
2015-04-13 5:58 ` Sudip Mukherjee
2015-04-13 5:58 ` Sudip Mukherjee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150401043150.GB4638@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=huax.lu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.