<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 3D & games produce periodic GPU crashes (Radeon R7 370)" href="https://bugs.freedesktop.org/show_bug.cgi?id=105425#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 3D & games produce periodic GPU crashes (Radeon R7 370)" href="https://bugs.freedesktop.org/show_bug.cgi?id=105425">bug 105425</a> from <a class="email" href="mailto:iive@yahoo.com" title="iive@yahoo.com">iive@yahoo.com</a> <pre>(In reply to MirceaKitsune from <a href="show_bug.cgi?id=105425#c46">comment #46</a>) > I found out what's causing the apitrace crash: It no longer happens when I > use fresh settings, therefore something in my config was breaking it. Upon > further inspection it seems to be one of the visual effects. I'll try again > with different settings, and see if I can find a config that still triggers > the GPU lockup without also making apitrace crash to the desktop. > > I also looked up where the kernel output should be located on openSUSE. I'm > told that it's /var/log/messages which indeed exists on my system. Next time > I experience the freeze, I will post that file here as instructed. You can report the apitrace crash to the apitrace issue tracker. Include everything needed to replicate it (aka Xonotic version, options, commands). <a href="https://github.com/apitrace/apitrace/issues">https://github.com/apitrace/apitrace/issues</a> You already have posted a /var/log/messages with a crash here, it doesn't have any kernel oops/panics. No point of posting another. See if there are any other /var/log/* files that might contain these. Here is how a shader hang look in my logs (that bug was reported and fixed): kernel: [19746.660911] radeon 0000:01:00.0: ring 0 stalled for more than 10030msec kernel: [19746.660915] radeon 0000:01:00.0: GPU lockup (current fence id 0x000000000039874d last fence id 0x0000000000398759 on ring 0) kernel: [19746.844799] radeon 0000:01:00.0: couldn't schedule ib kernel: [19746.844837] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! kernel: [19748.260945] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out. kernel: [19748.260965] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110). kernel: [19748.438730] radeon 0000:01:00.0: couldn't schedule ib kernel: [19748.438761] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>