From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111591] [radeonsi/Navi] The Bard's Tale IV causes a GPU hang
Date: Mon, 09 Sep 2019 01:47:31 +0000 [thread overview]
Message-ID: <bug-111591-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111591
Bug ID: 111591
Summary: [radeonsi/Navi] The Bard's Tale IV causes a GPU hang
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: not set
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: shtetldik@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
When running the Bard's Tale IV, in the beginning of the game, if I turn
around, it consistently is causing a GPU hang. And I see this in dmesg:
[ 4246.501534] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out or interrupted!
[ 4251.365674] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
timeout, signaled seq=178390, emitted seq=178392
[ 4251.365740] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process BardsTale4-Linu pid 7251 thread BardsTale4:cs0 pid 7292
[ 4251.365742] [drm] GPU recovery disabled.
GPU: Sapphire Pulse RX 5700 XT
Kernel: 5.3.0-rc8+
OpenGL renderer string: AMD NAVI10 (DRM 3.33.0, 5.3.0-rc8+, LLVM 10.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.3.0-devel
(git-87fa8d9ebc)
Game version: GOG, release 1.0.0 (version 4.20.1 / 32050).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2866 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 reply other threads:[~2019-09-09 1:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 1:47 bugzilla-daemon [this message]
2019-09-09 5:24 ` [Bug 111591] [radeonsi/Navi] The Bard's Tale IV causes a GPU hang bugzilla-daemon
2019-09-09 23:11 ` bugzilla-daemon
2019-09-10 0:49 ` bugzilla-daemon
2019-09-10 1:14 ` bugzilla-daemon
2019-09-10 15:27 ` bugzilla-daemon
2019-09-10 15:31 ` bugzilla-daemon
2019-09-10 22:36 ` bugzilla-daemon
2019-09-10 23:13 ` bugzilla-daemon
2019-09-11 1:38 ` bugzilla-daemon
2019-09-11 3:12 ` bugzilla-daemon
2019-09-11 3:19 ` bugzilla-daemon
2019-09-11 3:35 ` bugzilla-daemon
2019-09-11 3:42 ` bugzilla-daemon
2019-09-11 3:49 ` bugzilla-daemon
2019-09-11 4:20 ` bugzilla-daemon
2019-09-11 17:44 ` bugzilla-daemon
2019-09-11 23:30 ` bugzilla-daemon
2019-09-12 0:52 ` bugzilla-daemon
2019-09-25 18:50 ` 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-111591-502@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.