Comment=
# 8
on bug 96271<=
/a>
from Stephen Liang
Created attachment 124225 [details]
Kernel log, dmesg, gallium debug logs during GPU hang and system crash
No good but I've got quite a bit of information! I tried with this command:
R600_DEBUG=3Dnoce,nohyperz GALLIUM_DDEBUG=3D"800 noflush" steam
steam://rungameid/440
The GPU recovered and I was able to alt-tab to gnome terminal and grab the
dmesg. See "dmesg_after_alt_tab.txt".
I then continued to play the game and it hung again. This time, the entire
screen froze with only the mouse being able to move. Luckily, this time I w=
as
able to drop to TTY4, and grab a dmesg. See "dmesg_after_hard_hang.txt=
", there
is certainly a lot more output here with quite a bit of call traces which I=
've
never seen before.
Now, I decided to restart X since the mouse still moved so I wondered if th=
is
is an X issue. So I ran "sudo service gdm restart" and it crashed=
the system
with a calltrace displayed on screen on text mode. On restart, I checked the
kernel logs and I can see a lot of call traces, so it seems whatever happen=
ed
ended up tainting the kernel requiring the system to need a hard reset. See
"kernel_log_during_gdm_restart.txt".
Finally, since I ran this with GALLIUM_DDEBUG=3D"800 noflush", I =
was able to
collect another gallium debug that goes along with this. I really hope this
information helps capture the state of the system at the time of crash. Ple=
ase
let me know if you want me to try anything else.