Comme=
nt # 47
on bug 10542=
5
from iive@yahoo.com
(In reply to MirceaKitsune from comment #46)
> I found out what's causing the apitrace crash: I=
t 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 tri=
ggers
> the GPU lockup without also making apitrace crash to the desktop.
>=20
> 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. Nex=
t 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).
https://github.com/=
apitrace/apitrace/issues
You already have posted a /var/log/messages with a crash here, it doesn't h=
ave
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 wa=
it
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)!