<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - radeon - ring 0 stalled - GPU lockup - SI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107545#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - radeon - ring 0 stalled - GPU lockup - SI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107545">bug 107545</a>
from <span class="vcard"><a class="email" href="mailto:me@pc-networking-services.com" title="Christopher <me@pc-networking-services.com>"> <span class="fn">Christopher</span></a>
</span></b>
<pre>Hello,
I am getting similar issues with regards to fence wait timeouts. However I
have narrowed it further to it ONLY happening when gnome is running on xorg.
I have over the past month or so rebuilt my system from the ground up. I am
NOT using a distro that holds peoples hands with package managers and bloated
useless kernel modules. I use instructions from linuxfromscratch.org to build
the entire system from the latest stable sourcecode.
After I first boot into gnome, with it running on xorg, as soon as I have
logged in and click on activities on the gnome menu and select terminal, then
the little circle starts twirling, and after a few seconds the screen flashes,
and it momentarily goes to the grey login background, then flashes to what can
only be described as a mini pixal dump, then after a while it flashes back to
the login screen again and you need to login again. At this point, if you
click on the drop down list to see the types of login session available, gnome
on xorg is missing from the list. At this stage I login and going back and
activating gnome terminal is successfull, however the dmesg log shows that it
has ring stalled errors, and the dreaded parser error that has been mentioned
here.
If I start gnome on wayland, and then proceed to click on activities and then
on terminal to bring up gnome terminal, even though the circle twirls for a
long time after, the terminal window opens almost immediately and the output of
dmesg is free of the ring timeouts.
Running xorg by itself using twm with clock and xterm also produces a clean
dmesg log.
Please find the results attached for both boot tests. By the way this is on
one of the latest versions of the 4.18 kernel series available on kernel.org.
The version of Mesa used is: mesa-18.1.5</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>