All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1
Date: Mon, 16 Jan 2017 01:01:07 +0000	[thread overview]
Message-ID: <bug-93652-502-ExqmNrnQj9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93652-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1711 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93652

--- Comment #18 from Adam Bolte <boltronics@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2498 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-01-16  1:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 14:42 [Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1 bugzilla-daemon
2016-01-10 17:26 ` bugzilla-daemon
2016-01-11  0:41 ` bugzilla-daemon
2016-02-19 21:14 ` bugzilla-daemon
2016-03-09  6:15 ` bugzilla-daemon
2016-03-14 13:42 ` bugzilla-daemon
2016-03-28  2:20 ` bugzilla-daemon
2016-03-29 19:18 ` bugzilla-daemon
2016-04-04  9:03 ` bugzilla-daemon
2016-05-10 20:16 ` bugzilla-daemon
2016-05-27 13:12 ` bugzilla-daemon
2016-06-27 13:28 ` bugzilla-daemon
2016-08-22  3:05 ` bugzilla-daemon
2016-10-30  1:34 ` bugzilla-daemon
2016-10-31 20:40 ` bugzilla-daemon
2017-01-14 14:32 ` bugzilla-daemon
2017-01-14 23:22 ` bugzilla-daemon
2017-01-14 23:43 ` bugzilla-daemon
2017-01-16  1:01 ` bugzilla-daemon [this message]
2017-05-20 15:51 ` bugzilla-daemon
2017-05-26 19:58 ` bugzilla-daemon
2019-09-17  3:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-93652-502-ExqmNrnQj9@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.