<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - ring gfx timeout during particular shader generation on yuzu emulator"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109022">109022</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>ring gfx timeout during particular shader generation on yuzu emulator
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>18.3
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Gallium/radeonsi
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>felix.adrianto@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>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.
<a href="https://drive.google.com/file/d/1MdR1c2g0pQ8ToTCAH53Jc9BUd3WFzbcg/view?usp=sharing">https://drive.google.com/file/d/1MdR1c2g0pQ8ToTCAH53Jc9BUd3WFzbcg/view?usp=sharing</a>
The bug can be easily reproduced by replaying the apitrace result very
consistently.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>