From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109022] ring gfx timeout during particular shader generation on yuzu emulator
Date: Wed, 31 Jul 2019 20:16:19 +0000 [thread overview]
Message-ID: <bug-109022-502-3rinM3HPMF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109022-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2257 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109022
--- Comment #23 from e88z4 <felix.adrianto@gmail.com> ---
Hi,
Is there an update for this ticket? The issue is still easily be replicated in
the latest mesa on RadeonSI driver.
System information
Linux 5.2.2
Mesa-master
Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.2-htpc, LLVM 10.0.0)
I have tried different combination of llvm backend such as llvm-8, llvm-9, and
llvm-10. They produced the same error. Could this be a bug in amd llvm backend?
Previously, I have provided the api trace, I hope the trace can be used to
debug this issue.
I provided the latest error from today. They are the same error like before.
^[ [Jul31 16:10] amdgpu 0000:23:00.0: GPU fault detected: 147 0x0d604401
for process yuzu pid 15061 thread yuzu:cs0 pid 15068
[ +0.000004] amdgpu 0000:23:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x0C03F7AC
[ +0.000001] amdgpu 0000:23:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0E044001
[ +0.000002] amdgpu 0000:23:00.0: VM fault (0x01, vmid 7, pasid 32770) at page
201586604, read from 'TC5' (0x54433500) (68)
[ +5.312442] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out or interrupted!
[ +4.874028] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=24383, emitted seq=24385
[ +0.000066] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process yuzu pid 15061 thread yuzu:cs0 pid 15068
[ +0.000006] amdgpu 0000:23:00.0: GPU reset begin!
[ +0.584424] cp is busy, skip halt cp
[ +0.328786] rlc is busy, skip halt rlc
[ +0.001031] amdgpu 0000:23:00.0: GPU pci config reset
[ +0.463461] amdgpu 0000:23:00.0: GPU reset succeeded, trying to resume
[ +0.002152] [drm] PCIE GART of 256M enabled (table at 0x000000F400900000).
[ +0.000016] [drm] VRAM is lost due to GPU reset!
[ +0.087583] [drm] UVD and UVD ENC initialized successfully.
[ +0.099970] [drm] VCE initialized successfully.
[ +0.018504] amdgpu 0000:23:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR*
IB test failed on uvd (-110).
[ +0.003336] amdgpu 0000:23:00.0: ib ring test failed (-110).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3079 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-07-31 20:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 3:31 [Bug 109022] ring gfx timeout during particular shader generation on yuzu emulator bugzilla-daemon
2018-12-12 3:51 ` bugzilla-daemon
2018-12-12 4:04 ` bugzilla-daemon
2018-12-18 1:59 ` bugzilla-daemon
2018-12-20 12:22 ` bugzilla-daemon
2018-12-20 12:23 ` bugzilla-daemon
2018-12-20 12:25 ` bugzilla-daemon
2018-12-20 14:08 ` bugzilla-daemon
2019-01-29 4:06 ` bugzilla-daemon
2019-02-02 0:48 ` bugzilla-daemon
2019-03-06 8:36 ` bugzilla-daemon
2019-03-25 13:44 ` bugzilla-daemon
2019-03-25 13:48 ` bugzilla-daemon
2019-03-25 14:48 ` bugzilla-daemon
2019-05-26 23:19 ` bugzilla-daemon
2019-05-27 5:19 ` bugzilla-daemon
2019-05-27 5:20 ` bugzilla-daemon
2019-05-27 5:23 ` bugzilla-daemon
2019-05-27 5:28 ` bugzilla-daemon
2019-05-27 5:31 ` bugzilla-daemon
2019-05-27 23:14 ` bugzilla-daemon
2019-05-27 23:41 ` bugzilla-daemon
2019-05-28 3:25 ` bugzilla-daemon
2019-06-07 3:08 ` bugzilla-daemon
2019-07-31 20:16 ` bugzilla-daemon [this message]
2019-09-25 18:37 ` 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-109022-502-3rinM3HPMF@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.