All of 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: Wed, 12 Dec 2018 04:04:12 +0000	[thread overview]
Message-ID: <bug-109022-502-ILqSbxWX8c@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109022-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from e88z4 <felix.adrianto@gmail.com> ---
Out of 10 times replaying the trace, I was able to reproduce the bug twice. 

[  540.189992] amdgpu 0000:23:00.0: GPU fault detected: 147 0x09088402 for
process glretrace pid 2006 thread glretrace:cs0 pid 2007
[  540.190000] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x00001121
[  540.190004] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0E084002
[  540.190010] amdgpu 0000:23:00.0: VM fault (0x02, vmid 7, pasid 32771) at
page 4385, read from 'TC7' (0x54433700) (132)
[  550.275970] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=20845, emitted seq=20848

The error message from dmesg is identical when producing the bug from apitrace.

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

[-- Attachment #1.2: Type: text/html, Size: 1723 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:[~2018-12-12  4:04 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 [this message]
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
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-ILqSbxWX8c@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.