[Bug 98199] [HSW][REGRESSION][BISECTED] Messed up rendering after commit fcb5106

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=98199

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Martin Peres <martin.peres at free.fr> ---
(In reply to Jani Nikula from comment #6)
> (In reply to Martin Peres from comment #5)
> > (In reply to Martin Peres from comment #4)
> > > (In reply to Chris Wilson from comment #3)
> > > > Try commit f9326be5f1d3ff2c689de8a1754bdafd03879b58
> > > > Author: Chris Wilson <chris at chris-wilson.co.uk>
> > > > Date:   Thu Apr 28 09:56:45 2016 +0100
> > > > 
> > > >     drm/i915: Rearrange switch_context to load the aliasing ppgtt on first
> > > > use
> > > 
> > > Yes, it seems to fix the problem, at least with rendercheck. I will check
> > > visually when I arrive at the office.
> > > 
> > > Thanks a lot for the quick answer!
> > 
> > Verified visually. So, who gets to ping stable@ for linux4.7+? Should I do
> > it?
> 
> See if it applies cleanly, and send the backport request to the stable team,
> with me and/or intel-gfx in Cc.

So, it is already shipped in 4.8, so it would be backported only to 4.7... 

The patch does not apply cleanly but it did not seem like too much trouble to
make it apply. I could do this, but then what users would be impacted since
Arch is moving to 4.8 about this week, and fedora/ubuntu will move to 4.8.

What is the usual thing to do here? Marking as fixed because the patch is
already in a released kernel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161011/68a2cda2/attachment-0001.html>