<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Texture flicker in native Dota2 in mesa 9.2.0rc1" href="https://bugs.freedesktop.org/show_bug.cgi?id=68451#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Texture flicker in native Dota2 in mesa 9.2.0rc1" href="https://bugs.freedesktop.org/show_bug.cgi?id=68451">bug 68451</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to <a href="show_bug.cgi?id=68451#c8">comment #8</a>) > Alex, your suggestion doesn't seem to work. > Regardless, you would need to do make clean/distclean after each bisection step. > Emil, sorry, I don't really know what to do with these hashes - if you give > me the git command to run in the repo, I could try that... > this should do the job $ git cherry-pick $hash Note: you might need to pick one, two, etc of the hashes depending on where exactly your HEAD is (i.e. some of the patches may be already applied). In theory all of those should apply cleanly (git will not complain), although you may not be so lucky. > I can get current HEAD (58251) compiled, running, and the regression is > still there. Once I start bisecting, though, the "scanner" error as in > <a href="show_bug.cgi?id=68451#c5">comment 5</a> happens. > Once you take a quick look at the patches mentioned you will see which one resolves what issue (git show $hash), and you'll be able to pick the correct ones. > Also, I've managed to get some screenshots of the corruption, see attached. Indeed your issue seems different from the one I've mentioned.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>