Comment # 41
on bug 105733
from Philipp
I can second much of what John W. says. The crashes have become less frequent
with recent fimware/kernel versions, but they still happen.
Also for me the crashes only started on my vega 64, when I threw out my ancient
Intel CPU and replaced it with an AMD Ryzen 5 1600 on a GR-AB350M-Gaming 3
Board.
I've done stability tests on that other OS, so I don't think I've got faulty
hardware here.
One of my crash logs:
Nov 16 15:18:29 localhorst kernel: amdgpu 0000:08:00.0: [gfxhub] VMC page fault
(src_id:0 ring:158 vmid:7 pasid:32776, for process RocketLeague pid 6347 thread
RocketLeag:cs0 pid 6400
)
Nov 16 15:18:29 localhorst kernel: amdgpu 0000:08:00.0: at address
0x0000800319593000 from 27
Nov 16 15:18:29 localhorst kernel: amdgpu 0000:08:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x0070053C
Nov 16 15:18:30 localhorst kernel: amdgpu 0000:08:00.0: [gfxhub] VMC page fault
(src_id:0 ring:220 vmid:7 pasid:32776, for process RocketLeague pid 6347 thread
RocketLeag:cs0 pid 6400
)
Nov 16 15:18:30 localhorst kernel: amdgpu 0000:08:00.0: at address
0x00008201004e0000 from 27
Nov 16 15:18:30 localhorst kernel: amdgpu 0000:08:00.0:
VM_L2_PROTECTION_FAULT_STATUS:0x007013B8
Nov 16 15:18:40 localhorst kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring gfx timeout, signaled seq=38153, emitted seq=38155
Nov 16 15:18:40 localhorst kernel: [drm] GPU recovery disabled.