Comment # 40
on bug 105425
from iive@yahoo.com
It seems like the sysrq actually worked, I see it in the logs. The crash has happened around Apr20 15:54. Unfortunately the kernel error/panic message is missing in both logs. My distro doesn't have systemd, so I cannot tell you what the magic journalctl options are to get these messages out. On my system, these usually go in /var/log/syslog . See if you can find something more useful from about that time. As for the apitrace, it should work out of the box. First test it with: apitrace trace glxgears It should create a glxgears.trace . If you run it again, it would create glxgears.1.trace etc. It's important to be sure that you are using 64 bit apitrace with 64bit applications. apitrace trace ./xonotic-linux64-glx Should do the trick. First, start a game match and exit right away. Then try to replay the result with: apitrace replay xonotic-linux64.glx.trace This is to make sure that tracing is working properly. Then just make sure you have enough free space. Enable vsync, to limit the frames per second. Using smaller textures should also help with the trace size (textures are loaded at the level start, so playing longer match should help too). After you record a crash and reboot with sysrq, see if replaying the resulting trace file would cause hang at its end. You can compress the trace with `xz -9e xonotic*.trace` . Good Luck.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
