Comment # 17
on bug 109955
from Alex Deucher
(In reply to Jaap Buurman from comment #16) > Just got a crash in World of Warcraft as well, running via vkd3d. It happens > instantly after trying to log into the game world, so the issue is nicely > reproducible for me. If you want me to get any traces, please let me know > what you would like me to run to get them. dmesg logs for now: > > [ 78.450637] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450641] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d4b000 from 27 > [ 78.450642] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450648] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450650] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92553000 from 27 > [ 78.450652] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450656] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450658] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d4e000 from 27 > [ 78.450660] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450665] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450666] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92542000 from 27 > [ 78.450668] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450673] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450674] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d42000 from 27 > [ 78.450676] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450680] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450682] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92552000 from 27 > [ 78.450683] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450688] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450690] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d40000 from 27 > [ 78.450691] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450696] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450697] amdgpu 0000:09:00.0: in page starting at address > 0x0000850e92552000 from 27 > [ 78.450699] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450703] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450705] amdgpu 0000:09:00.0: in page starting at address > 0x0000984ec2d49000 from 27 > [ 78.450706] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.450711] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 > ring:158 vmid:1 pasid:32769, for process WoW.exe pid 2349 thread WoW.exe:cs0 > pid 2370) > [ 78.450713] amdgpu 0000:09:00.0: in page starting at address > 0x0000850ea1eb2000 from 27 > [ 78.450714] amdgpu 0000:09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0010113D > [ 78.454307] amdgpu 0000:09:00.0: IH ring buffer overflow (0x000BEDC0, > 0x0003EEC0, 0x0003EDE0) > [ 88.570062] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, > signaled seq=25317, emitted seq=25319 > [ 88.570099] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process WoW.exe pid 2349 thread WoW.exe:cs0 pid 2370 > [ 88.570102] amdgpu 0000:09:00.0: GPU reset begin! > [ 88.831392] amdgpu 0000:09:00.0: GPU reset > [ 89.356679] [drm] psp mode1 reset succeed > [ 89.475356] amdgpu 0000:09:00.0: GPU reset succeeded, trying to resume > [ 89.475465] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000). > [ 89.475508] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost! > [ 89.475642] [drm] PSP is resuming... > [ 89.623052] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE > [ 89.806625] [drm] SADs count is: -2, don't need to read it > [ 89.856619] [drm] SADs count is: -2, don't need to read it > [ 89.938255] [drm] UVD and UVD ENC initialized successfully. > [ 90.038674] [drm] VCE initialized successfully. > [ 90.039672] [drm] recover vram bo from shadow start > [ 90.047496] [drm] recover vram bo from shadow done > [ 90.047497] [drm] Skip scheduling IBs! > [ 90.047499] [drm] Skip scheduling IBs! > [ 90.047511] [drm] Skip scheduling IBs! > [ 90.047518] [drm] Skip scheduling IBs! > [ 90.047523] [drm] Skip scheduling IBs! > [ 90.047524] [drm] Skip scheduling IBs! > [ 90.047530] [drm] Skip scheduling IBs! > [ 90.047531] [drm] Skip scheduling IBs! > [ 90.047533] [drm] Skip scheduling IBs! > [ 90.047535] [drm] Skip scheduling IBs! > [ 90.047536] [drm] Skip scheduling IBs! > [ 90.047538] [drm] Skip scheduling IBs! > [ 90.047539] [drm] Skip scheduling IBs! > [ 90.047555] amdgpu 0000:09:00.0: GPU reset(2) succeeded! The GPU reset succeeded. You'll need to restart your desktop manager to recover because currently no desktop managers handle GPU reset errors and re-initialize their contexts.
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
