<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - R9285 Xonotic gpu lock since radeonsi: split si_emit_shader_pointer" href="https://bugs.freedesktop.org/show_bug.cgi?id=103413#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - R9285 Xonotic gpu lock since radeonsi: split si_emit_shader_pointer" href="https://bugs.freedesktop.org/show_bug.cgi?id=103413">bug 103413</a> from <a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> Andy Furniss</a> <pre>Lots of "normal" runs indicated the commit before the "bad" is OK - I've not locked doing many of vblank_mode=0 ./xonotic-linux64-glx -benchmarkruns 20 -benchmark demos/the-big-keybench.dem cpu & gpu set high for testing. vblank_mode=0 or the perf settings are not required to provoke lock, they are just much faster to get the multiple runs in. xonotic settings are ultra with aniso and aa highest, 1920x1080 fullscreen. Unfortunately, I tried a more abnormal test = with a 2160p framebuffer + panning and like that I can still lock. Locks are again in same place, but that place is different = frame 9411. Over time I'll try to go back further.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>