https://bugs.freedesktop.org/show_bug.cgi?id=93706
Bug ID: 93706 Summary: Xorg freeze when running 3d app (Guild Wars 2) on RV620 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel@lists.freedesktop.org Reporter: gryffus@hkfree.org QA Contact: dri-devel@lists.freedesktop.org
Created attachment 121016 --> https://bugs.freedesktop.org/attachment.cgi?id=121016&action=edit dmesg after the screen freezes
When i try to run Guild Wars 2, the X screen freezes (i can move the mouse and i can hear sounds, but X is otherwise frozen) I'm adding dmesg logs. If you need anything more, please request.
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #121016|0 |1 is obsolete| |
--- Comment #1 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121017 --> https://bugs.freedesktop.org/attachment.cgi?id=121017&action=edit dmesg after the screen freezes 2
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #2 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121018 --> https://bugs.freedesktop.org/attachment.cgi?id=121018&action=edit Xorg.0.log after the screen freezes
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #3 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121019 --> https://bugs.freedesktop.org/attachment.cgi?id=121019&action=edit Wine log
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=92912
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=83319
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #4 from Lukáš Krejza gryffus@hkfree.org --- Maybe duplicate of some other bug? I get also freeze with gsraytrace, so it could be duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=83319 (or some other that i added to "See Also")
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=83285
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=88263
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.freedesktop.or | |g/show_bug.cgi?id=88263 |
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #5 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121020 --> https://bugs.freedesktop.org/attachment.cgi?id=121020&action=edit dmesg with R600_DEBUG=nohyperz R600_DEBUG=nosb gsraytrace
With R600_DEBUG=nohyperz R600_DEBUG=nosb, gsraytrace also freezes the GPU
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #6 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121021 --> https://bugs.freedesktop.org/attachment.cgi?id=121021&action=edit xorg log with R600_DEBUG=nohyperz R600_DEBUG=nosb gsraytrace
With R600_DEBUG=nohyperz R600_DEBUG=nosb, gsraytrace also freezes the GPU
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #7 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121022 --> https://bugs.freedesktop.org/attachment.cgi?id=121022&action=edit apitrace
I'm able to reproduce the freeze/GPU lockup using this trace
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #8 from Lukáš Krejza gryffus@hkfree.org --- Some more info:
Mesa git Kernel 4.4 X server 1.18.0
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #9 from Scott Moreau oreaus@gmail.com --- Created attachment 121024 --> https://bugs.freedesktop.org/attachment.cgi?id=121024&action=edit Crash dump with apitrace on sandybridge
(In reply to Lukáš Krejza from comment #7)
Created attachment 121022 [details] apitrace
I'm able to reproduce the freeze/GPU lockup using this trace
I am also able reproduce with this trace on intel sandybridge but it recovers successfully. The crash dump attachment is from /sys/class/drm/card0/error
Mesa git Kernel 4.4.0 X server 1.17.2 Intel Sandybridge
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=86720
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=88263
https://bugs.freedesktop.org/show_bug.cgi?id=93706
Lukáš Krejza gryffus@hkfree.org changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=91865
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #10 from Dieter Nützel Dieter@nuetzel-hh.de --- (In reply to Lukáš Krejza from comment #4)
Maybe duplicate of some other bug? I get also freeze with gsraytrace, so it could be duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=83319 (or some other that i added to "See Also")
Hello Lukáš,
as you own a Radeon HD 3400 RV620
'semilar' to my RV730 the 'gsraytrace' GPU hang is NOT soveld with current GIT. I'll update my bug report (Bug 83319), soon.
For EG+ (Bug 91865) this is _fixed_ by 'accident' in Mesa git since:
commit 2239f3eaff5c72c4cb1d4a5be97feb4af3d08d25 Author: Dave Airlie airlied@redhat.com 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 airlied@redhat.com
I'll have to talk with Dave and Marek what is different for R600/R700 and EG+ and what should I try next.
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #11 from Lukáš Krejza gryffus@hkfree.org --- Created attachment 121050 --> https://bugs.freedesktop.org/attachment.cgi?id=121050&action=edit Output from apitrace when replaying the trace
I have tried to replay the trace with nouveau and it did not crash and produced attached output.
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #12 from Dieter Nützel Dieter@nuetzel-hh.de --- (In reply to Lukáš Krejza from comment #11)
Created attachment 121050 [details] Output from apitrace when replaying the trace
I have tried to replay the trace with nouveau and it did not crash and produced attached output.
How do you did it?
If I run it on NI/Turks XT (HD 6670) for which 'gsraytrace' is fixed, it terminates in fractions of a second and print nothing.
apitrace replay gsraytrace.trace Rendered 0 frames in 0.101416 secs, average of 0 fps
https://bugs.freedesktop.org/show_bug.cgi?id=93706
--- Comment #13 from Michel Dänzer michel@daenzer.net --- It's better to assume for now that the Guild Wars 2 and gsraytrace hangs are caused by different problems. Please keep the gsraytrace related discussion on the existing report(s) about that, in order not to clutter up this report.
https://bugs.freedesktop.org/show_bug.cgi?id=93706
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #14 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/569.
dri-devel@lists.freedesktop.org