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: Wed, 12 Dec 2018 03:31:03 +0000	[thread overview]
Message-ID: <bug-109022-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109022
           Summary: ring gfx timeout during particular shader generation
                    on yuzu emulator
           Product: Mesa
           Version: 18.3
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: felix.adrianto@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

How to reproduce the issue?
1. Using yuzu emualtor latest canary build.
2. Load Super Mario Odyssey.
3. Create a new game.
4. Wait until Mario jumps for the first time after being woken up by Cappy. 
5. Graphic crashes but system is still accessible through SSH

Error message:
[  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

System specification:
AMD Ryzen 5 2600
ASRock B540M with latest bios update
16 GB DDR4 RAM
MSI RX580 Gaming X
Debian Sid 
Kernel 4.20-rc6
Mesa 18.3.1

This bug occurs in all combinations of kernel 4.17, 4.18, 4.19, 4.20,
drm-next-4.2.1-wip with mesa 18.2, 18.3, 19.0-development

I am able to get the apitrace result. It can be downloaded from my google
drive.
https://drive.google.com/file/d/1MdR1c2g0pQ8ToTCAH53Jc9BUd3WFzbcg/view?usp=sharing

The bug can be easily reproduced by replaying the apitrace result very
consistently.

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

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

             reply	other threads:[~2018-12-12  3:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  3:31 bugzilla-daemon [this message]
2018-12-12  3:51 ` [Bug 109022] ring gfx timeout during particular shader generation on yuzu emulator 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
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@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