<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - General artifacts shortly after CPU warming up" href="https://bugs.freedesktop.org/show_bug.cgi?id=101259#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - General artifacts 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>kernel 4.12.4 is out for arch users, so I gave it a try and have the folling. (a) mesa-17.0.5 & kernel-4.11.9, reported, not perfect but usable; (b) mesa-17.1.4 & kernel-4.11.9, reported, unusable; (c) mesa-17.1.4 & kernel-4.12.4, same as (a), not perfect but usable; (d) mesa-master(7ea4cda2ab) & kernel-4.12.4, really sketchy, no menu shown, worse than (b) (e) mesa-17.2-branchpoint & kernel-4.12.4, same as (d) (f) mesa-17.2-branchpoint & kernel-4.11.9, same as (d) It seems some modification in the kernel got things back on track, and later modifications in mesa between 17.1-branchpoint & 17.2-branchpoint break it again. So, stay with kernel-4.12.4, I do another bisect, between 17.1-branchpoint & 17.2-branchpoint ... > 38e2142f392f9b6ac78eab72a1f92dd37553e1d8 is the first bad commit > commit 38e2142f392f9b6ac78eab72a1f92dd37553e1d8 > Author: Kenneth Graunke <<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>> > Date: Mon Jul 17 12:46:58 2017 -0700 > > i965/bufmgr: Explicitly wait instead of using I915_GEM_SET_DOMAIN. > > With the advent of asynchronous maps, domain tracking doesn't make a > whole lot of sense. Buffers can be in use on both the CPU and GPU at ......</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>