<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Tonga VM Faults since llvm ScheduleDAGInstrs: Rework schedule graph builder." href="https://bugs.freedesktop.org/show_bug.cgi?id=93264#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Tonga VM Faults since llvm ScheduleDAGInstrs: Rework schedule graph builder." href="https://bugs.freedesktop.org/show_bug.cgi?id=93264">bug 93264</a> from <a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> Andy Furniss</a> <pre>Maybe there is some mesa that doesn't do it I suppose. I don't update llvm as often as mesa so could have missed that. When I noticed this I reset mesa back to where the old bug fixes went in, as I knew that used to be good. It was still bad, then I tried it on older kernels, still bad so I got back on head and started testing llvm. On mesa head the llvm bisect does seem good - I haven't had much time, but a few runs with llvm sitting on the bad were all bad and a few on the one before all good. It was only a quick test - I didn't throw cpufreq into the mix. When I saw the result of the bisect I did think red herring as it wasn't AMD - but then was slightly relieved when AMD got a mention in the commit message.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>