From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111763] ring_gfx hangs/freezes on Navi gpus
Date: Sat, 09 Nov 2019 20:12:17 +0000 [thread overview]
Message-ID: <bug-111763-502-L6zAGwXmob@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 965 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111763
James Wood <Chryseus8080@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Chryseus8080@gmail.com
--- Comment #27 from James Wood <Chryseus8080@gmail.com> ---
This doesn't seem to be exclusive to Navi GPUs, I've been having instances of
ring gfx timeouts freezing up the system in numerous games such as Project
Zomboid (was recently fixed by the developer) and ArmA 3 with the all too
familiar dmesg:
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed
out or interrupted!
drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
I'm using:
Radeon RX 590 Series (POLARIS10, DRM 3.33.0, 5.3.8-arch1-1, LLVM 9.0.0)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2255 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-09 20:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 12:01 [Bug 111763] ring_gfx hangs/freezes on Navi gpus bugzilla-daemon
2019-09-23 2:46 ` bugzilla-daemon
2019-09-23 6:56 ` bugzilla-daemon
2019-09-23 6:57 ` bugzilla-daemon
2019-09-23 7:00 ` bugzilla-daemon
2019-09-30 12:18 ` bugzilla-daemon
2019-09-30 15:10 ` bugzilla-daemon
2019-09-30 21:55 ` bugzilla-daemon
2019-09-30 22:02 ` bugzilla-daemon
2019-10-03 12:26 ` bugzilla-daemon
2019-10-11 13:37 ` bugzilla-daemon
2019-10-11 13:57 ` bugzilla-daemon
2019-10-15 12:58 ` bugzilla-daemon
2019-10-15 17:10 ` bugzilla-daemon
2019-10-23 7:26 ` bugzilla-daemon
2019-10-31 12:09 ` bugzilla-daemon
2019-10-31 12:11 ` bugzilla-daemon
2019-11-01 1:23 ` bugzilla-daemon
2019-11-01 16:26 ` bugzilla-daemon
2019-11-02 12:35 ` bugzilla-daemon
2019-11-02 23:11 ` bugzilla-daemon
2019-11-04 16:08 ` bugzilla-daemon
2019-11-04 16:10 ` bugzilla-daemon
2019-11-04 22:13 ` bugzilla-daemon
2019-11-05 6:07 ` bugzilla-daemon
2019-11-05 16:28 ` bugzilla-daemon
2019-11-09 2:54 ` bugzilla-daemon
2019-11-09 12:42 ` bugzilla-daemon
2019-11-09 20:12 ` bugzilla-daemon [this message]
2019-11-10 12:20 ` bugzilla-daemon
2019-11-10 13:50 ` bugzilla-daemon
2019-11-10 13:51 ` bugzilla-daemon
2019-11-10 13:53 ` bugzilla-daemon
2019-11-10 13:55 ` bugzilla-daemon
2019-11-10 13:58 ` bugzilla-daemon
2019-11-10 14:00 ` bugzilla-daemon
2019-11-10 14:04 ` bugzilla-daemon
2019-11-12 23:15 ` bugzilla-daemon
2019-11-13 0:04 ` bugzilla-daemon
2019-11-19 9:52 ` 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-111763-502-L6zAGwXmob@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox