<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - General artifacs shortly after CPU warming up" href="https://bugs.freedesktop.org/show_bug.cgi?id=101259#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - General artifacs shortly after CPU warming up" href="https://bugs.freedesktop.org/show_bug.cgi?id=101259">bug 101259</a> from <a class="email" href="mailto:clamfly@sina.com" title="liang <clamfly@sina.com>"> liang</a> <pre>I've tried bisecting, and found this: fbb32971651e7453498e082cabdd92d789417ab2 is the first bad commit commit fbb32971651e7453498e082cabdd92d789417ab2 Author: Kenneth Graunke <<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>> Date: Sun Apr 2 23:35:27 2017 -0700 i965/drm: Drop GEM_SW_FINISH stuff. This is only useful when doing an incoherent CPU mapping of the current scanout buffer. That's a terrible plan, so we never do it. We always use an uncached GTT map. So, this is useless. Drop the code. Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Acked-by: Jason Ekstrand <<a href="mailto:jason@jlekstrand.net">jason@jlekstrand.net</a>> :040000 040000 06f502cb5d96f477bf6fb20da5628d456ece07e2 1c0e3b96b6de0f8182f87068ff0454540cf77d6f M src As I said before, 17.0.x is not perfect, it still has few artifacts, very hard to noticed though. But after that commit, things got much worse.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>