dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 26 May 2019 23:19:19 +0000	[thread overview]
Message-ID: <bug-109022-502-UZdoiwifAe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109022-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from e88z4 <felix.adrianto@gmail.com> ---
I tried to reproduce this bug again with latest mesa master (659aa3dd651). My
kernel is 5.1.3 and yuzu-canary #2318. The behaviour of the softlock is
slightly changed. Yuzu didn't crash anymore but rendering was super slow. I was
able to kill the application without using SSH. The following error was
produced from dmesg.

[ 5179.131132] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5183.739102] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5189.883024] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5193.979037] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5204.218939] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5214.458837] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5224.698730] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5229.818653] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5234.938622] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5234.938680] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5241.850516] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5245.178534] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered
[ 5251.322426] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
fences timed out.
[ 5255.418427] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but
soft recovered

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

[-- Attachment #1.2: Type: text/html, Size: 2714 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

  parent reply	other threads:[~2019-05-26 23:19 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 [this message]
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
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-UZdoiwifAe@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