<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Any OpenCL application causes "*ERROR* ring gfx timeout" on Vega 64" href="https://bugs.freedesktop.org/show_bug.cgi?id=110637#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Any OpenCL application causes "*ERROR* ring gfx timeout" on Vega 64" href="https://bugs.freedesktop.org/show_bug.cgi?id=110637">bug 110637</a> from <a class="email" href="mailto:mezin.alexander@gmail.com" title="Alexander Mezin <mezin.alexander@gmail.com>"> Alexander Mezin</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=110637#c3">comment #3</a>) > More likely a bug in the mesa OpenCL code. If you want functional OpenCL, > you should use the ROCm OpenCL packages. I thought that buggy userspace shouldn't cause a complete GPU lockup like this... The kernel log says "GPU reset succeeded", but it leaves GNOME session completely unusable (hung, artifacts on screen), restarting GDM also fails, the only way to recover is rebooting (sometimes only through Sysrq) And also I get a very similar lockup (the same messages in kernel log, again with all kernel/firmware versions I tried) in a few Steam games running on Proton/DXVK. Will try different mesa versions</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>