Commen=
t # 1
on bug 10086=
5
from Dieter N=C3=BCtzel
Hello Marc,
can you please verify, that it is a _combination_ of wireframe _and_
tessellation?
I've got that for ages with r600g, RV730 (HD 4650, 1GB, AGP) and NI/Turks XT
(HD 6670, 2 GB PCIe). As 'Heaven' (UH4) start 'normally' with tessellation
enabled and 'you' press 'F2' (enable wireframe) it could result in GPU lock=
up.
So please start 'Heaven', press 'F3' (disable tessellation) and last press =
'F2'
(enable wireframe). This 'version' works fine for me. It seems to be a
combination of both. But my systems mostly recover from the GPU lockup.
W'll try to get a new backtrace, soon.
Tessellation is so awfully _slow_ (hardware or 'only' software implemantati=
on)
that I think we have to look/point, there.
Bas (Radv) worked on radeonsi tessellation improvements.
See related links:
https://www.phoronix.com/scan.php?page=3Dnews_item&am=
p;px=3DR600g-Tessellation-Lands
https://www.phoronix.com/scan.php?page=3Dnews_ite=
m&px=3DRadeonSI-Tess-G3D-Benchmarks
Second:
I ran all the time with MESA_GL_VERSION_OVERRIDE=3D4.1COMPAT and 'Heaven' s=
how
display corruption (missing parts), but wireframe works. If I toggle
tessellation (F3) missing parts arise but without tessellation, as expected.
So for 'Heaven' I have to disable MESA_GL_VERSION_OVERRIDE and get the above
boom (GPU lockup).
=3D> tessellation / wireframe correlation
'All' old and Mesa git, Kernel 4.11-rc8 (and former)
Greetings,
Dieter