<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Random crashes/freezing with amdgpu Fury X mesa 11.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93652#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Random crashes/freezing with amdgpu Fury X mesa 11.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93652">bug 93652</a>
from <span class="vcard"><a class="email" href="mailto:boltronics@gmail.com" title="Adam Bolte <boltronics@gmail.com>"> <span class="fn">Adam Bolte</span></a>
</span></b>
<pre>My Fury X doesn't crash like it used to - no call traces in the kernels now.
But quite often the monitor will switch off and simply stay off. This happens
when I try to resume from suspend (happened to me today), or load a full-screen
app under Wine (eg. I got this with Jack Keane 2 and Wine and Nine yesterday).
I can hear the game running through the speakers, but the monitor has lost
signal.
Sometimes I can get the picture back by hitting Ctrl+Alt+F1 to switch to a
virtual console, and then Ctrl+Alt+F7 to switch back to Xorg. But sometimes I
have to slowly repeat this 20 or so times before the picture returns.
Another thing that sometimes gets the signal back is to unplug and replug the
DisplayPort monitor cable from the Fury X, but generally I have to do this 10
or more times before picture returns. I only do this if I'm not getting
anywhere by switching back and forth between virtual consoles and Xorg.
Interestingly, full-screen games seems to produce this problem *much* more
often than native games under Steam. In fact, I can't remember the last time I
had this problem with a Steam game. When using Wine, I try to run in window
mode to avoid this problem completely. I also try to avoid suspending, and
always turn my computer completely off. Obviously this is all quite
frustrating.
Not sure if it matters, but I'm using a BenQ XL2730Z at 143.something Hz (which
is the xrand preference over 144Hz for some reason). I'm not at my desktop now
so can't check exactly.</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>