<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - System randomly freezes or crashes to the login screen, glitches until rebooted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100306#c38">Comment # 38</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - System randomly freezes or crashes to the login screen, glitches until rebooted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100306">bug 100306</a>
from <span class="vcard"><a class="email" href="mailto:sonichedgehog_hyperblast00@yahoo.com" title="MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com>"> <span class="fn">MirceaKitsune</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=133368" name="attach_133368" title="Output of "dmesg -w" (full)">attachment 133368</a> <a href="attachment.cgi?id=133368&action=edit" title="Output of "dmesg -w" (full)">[details]</a></span>
Output of "dmesg -w" (full)
Full output of "dmesg -w", recorded by running "dmesg -w > filename.txt". The
previous one was incomplete as it was subject to console line limitations,
cutting off the moment when the crash actually occurs. I left the command
running in a different runlevel; This time the crash didn't shut down the
monitor after switching to it (Control + Alt + F1) so I was able to cleanly
shut down dmesg then issue a normal reboot. I waited there for about 5 minutes
before doing so, to give dmesg time to record as much information as possible.
The crash appears to start at the following lines:
[112873.658950] radeon 0000:03:00.0: ring 4 stalled for more than 10024msec
[112873.658953] radeon 0000:03:00.0: GPU lockup (current fence id
0x000000000072f6bd last fence id 0x000000000072f6c1 on ring 4)</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>