[Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 25 15:28:55 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=105425

--- Comment #51 from MirceaKitsune <sonichedgehog_hyperblast00 at yahoo.com> ---
Created attachment 139103
  --> https://bugs.freedesktop.org/attachment.cgi?id=139103&action=edit
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?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180425/825310fc/attachment.html>


More information about the dri-devel mailing list