<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - kernel Oops when provoking GPU lock." href="https://bugs.freedesktop.org/show_bug.cgi?id=60254#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - kernel Oops when provoking GPU lock." href="https://bugs.freedesktop.org/show_bug.cgi?id=60254">bug 60254</a> from <a class="email" href="mailto:lists@andyfurniss.entadsl.com" title="Andy Furniss <lists@andyfurniss.entadsl.com>"> Andy Furniss</a> <pre>(In reply to <a href="show_bug.cgi?id=60254#c1">comment #1</a>) > (In reply to <a href="show_bug.cgi?id=60254#c0">comment #0</a>) > > The GPU lock with Rv670 and openarena is nothing new - it seems to have been > > a feature for almost a year (I haven't used rv670 for most of that time). > > > > On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke > > it on my AGP box and got - > > Hmm I just managed to get the same running drm-fixes so it's not wip maybe > it's because I am now using llvm. In the (no llvm) past with other kernels > this GPU lock normally went quite well - the game often just continued for a > while, until it hit another one. It's nothing to do with llvm seems like it's a feature of more recent kernels.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>