<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - TF2: GPU lockup on HD 7950"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96271#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - TF2: GPU lockup on HD 7950"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96271">bug 96271</a>
from <span class="vcard"><a class="email" href="mailto:hi+freedesktop@stephenliang.pw" title="Stephen Liang <hi+freedesktop@stephenliang.pw>"> <span class="fn">Stephen Liang</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=124225" name="attach_124225" title="Kernel log, dmesg, gallium debug logs during GPU hang and system crash">attachment 124225</a> <a href="attachment.cgi?id=124225&action=edit" title="Kernel log, dmesg, gallium debug logs during GPU hang and system crash">[details]</a></span>
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=noce,nohyperz GALLIUM_DDEBUG="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 was
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 this
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 happened
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="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. Please
let me know if you want me to try anything else.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>