All of lore.kernel.org
 help / color / mirror / Atom feed
From: lkml@pengaru.com
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: dri-devel@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7
Date: Mon, 9 Jan 2017 00:32:40 -0600	[thread overview]
Message-ID: <20170109063240.GB9125@shells.gnugeneration.com> (raw)

Hello all,

I'm experiencing display noise in the form of 8x1 pixel bars spuriously
appearing in random locations.  This doesn't happen on 4.9, the machine
is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS.

I was able to bisect the issue to a6a7cc4b7:

commit a6a7cc4b7db6deaeca11cdd38844ea147a354c7a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Nov 18 21:17:46 2016 +0000

    drm/i915: Always flush the dirty CPU cache when pinning the scanout
    
    Currently we only clflush the scanout if it is in the CPU domain. Also
    flush if we have a pending CPU clflush. We also want to treat the
    dirtyfb path similar, and flush any pending writes there as well.
    
    v2: Only send the fb flush message if flushing the dirt on flip
    v3: Make flush-for-flip and dirtyfb look more alike since they serve
    similar roles as end-of-frame marker.

Reproduction is simple, just run this native drm eye candy program:
https://github.com/vcaputo/rototiller

Thanks,
Vito Caputo

             reply	other threads:[~2017-01-09  6:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  6:32 lkml [this message]
2017-01-09 10:24 ` [PATCH] drm/i915: Flush untouched framebuffers before display on !llc Chris Wilson
2017-01-09 10:24   ` Chris Wilson
2017-01-09 10:52   ` Chris Wilson
2017-01-09 10:52     ` Chris Wilson
2017-01-09 13:48   ` kbuild test robot
2017-01-09 13:48     ` [Intel-gfx] " kbuild test robot
2017-01-09 11:19 ` [PATCH v2] " Chris Wilson
2017-01-09 11:19   ` Chris Wilson
2017-01-12 21:17   ` Chris Wilson
2017-01-12 21:17     ` Chris Wilson
2017-01-12 22:24     ` lkml
2017-01-12 22:38       ` Chris Wilson
2017-01-12 22:38         ` Chris Wilson
2017-02-01 10:24   ` Daniel Vetter
2017-02-01 10:24     ` [Intel-gfx] " Daniel Vetter
2017-02-01 10:48     ` Chris Wilson
2017-02-01 10:48       ` [Intel-gfx] " Chris Wilson
2017-01-09 13:01 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-01-30  2:04 ` BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7 lkml

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=20170109063240.GB9125@shells.gnugeneration.com \
    --to=lkml@pengaru.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.