<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730" href="https://bugs.freedesktop.org/show_bug.cgi?id=83319#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730" href="https://bugs.freedesktop.org/show_bug.cgi?id=83319">bug 83319</a> from <a class="email" href="mailto:Dieter@nuetzel-hh.de" title="Dieter Nützel <Dieter@nuetzel-hh.de>"> Dieter Nützel</a> <pre>Update, this one is NOT solved with current Mesa git. For EG+ (<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [r600g] GPU hang in 'gsraytrace' - NI/Turks (6670)" href="show_bug.cgi?id=91865">Bug 91865</a>) this is _fixed_ by 'accident' in Mesa git since: commit 2239f3eaff5c72c4cb1d4a5be97feb4af3d08d25 Author: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>> Date: Mon Nov 30 15:48:22 2015 +1000 r600/shader: emit tessellation factors to GDS at end of TCS. When we are finished the shader, we read back all the tess factors from LDS and write them to special global memory storage using GDS instructions. This also handles adding NOP when GDS or ENDLOOP end the TCS. Signed-off-by: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>> Dave and Marek any hints which could point in the right direction? What is different in this case between R600/R700 and EG+ (NI/Turks in my case) and what should I try next.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>