commit 3fac8978f5d353d350215d7d8dae977d65305f64 Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> Date: Thu Jan 30 16:05:48 2014 +0200 drm/i915: Tune down debug output when context is banned If we have stopped rings then we know that test is running so no need for spam. In addition, only spam when default context gets banned. v2: - make sure default context ban gets shown (Chris) - use helper for checking for default context, everywhere (Chris) v3: - dont be quiet when debug is set (Ben, Daniel) Reference: https://bugs.freedesktop.org/show_bug.cgi?id=73652 Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com> Reviewed-by: Ben Widawsky <ben@bwidawsk.net> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> seems to be implicated in render corruption of glxgears on an ivg:gt1 1007U Bizzare.
I've run the bisect twice, and manually confirmed the result (3fac8978f vs 3fac8978f^), it does seem to be that commit that introduces the corruption. I suspected the nearby IVB w/a changes, but alas.
Bewildering indeed ... Any change we can blame a difference between driver load and gpu reset on this bug here?
Today's attempt: commit 116f2b6da868dec7539103574d0421cd6221e931 Author: Chia-I Wu <olv@lunarg.com> Date: Tue Jan 28 13:29:34 2014 +0800 drm/i915: enable HiZ Raw Stall Optimization on IVB The optimization helps IVB too. No piglit regression. Signed-off-by: Chia-I Wu <olv@lunarg.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Which starts to make sense.
Reverting 116f2b6da868dec7539103574d0421cd6221e931 on d-i-n fixes the issue.
Created attachment 95081 [details] [review] Revert "drm/i915: enable HiZ Raw Stall Optimization on IVB"
Revert merged, thanks for tracking this down ;-) commit 0d77df01d342bf3691b1a1ea7d1bf570e31ab94a Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Mar 4 09:41:43 2014 +0000 Revert "drm/i915: enable HiZ Raw Stall Optimization on IVB"
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.