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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel