Comment # 52
on bug 105425
from iive@yahoo.com
(In reply to MirceaKitsune from comment #51) > Created attachment 139103 [details] > Output of: systemctl | grep running > > (In reply to iive from comment #50) > > I've preformed many more tests during the past two hours, getting nearly a > dozen freezes in the process. I tried with both the glx and sdl versions of > Xonotic, and even ran the "Alt + SysRq + RESUB" combination at different > rates (instantly as well as 1 minute in between each press). Before each > test I made sure the SysRq keys are working, by using "Alt + SysRq + H" then > checking that the help message appears at the end of the "dmesg" output. > > In all cases the trace file never catches the crash: Either I find a zero > byte file when I reboot, either it ends several seconds before the crash. > > I couldn't find any obviously useless systemctl services that I can shut > down (such as Apache). In case there is anything dangerous or that I could > disable in there, I'm attaching the output of "systemctl | grep running". > > I'm clearly going to need a different approach to recording this trace: > apitrace must be dying the moment the lockup occurs, so it never finishes > writing the complete trace file. I found some info on how a trace can be > played back from a remote machine, but not how to record it from one. What > should I do next? I'm running out of ideas. I just want to make sure that the `apitrace` you are using is recent enough. The last release of apitrace-7.1 is almost 3 years old and there are many fixes that it is missing. For example, there is 2 years old commit that calls "localWrite.flush()" on "_exit".
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
