Bug 106165

Summary: [vega10] vega56 VM_L2_PROTECTION_FAULT_STATUS in wine games
Product: DRI Reporter: Tom Englund <tomenglund26>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Tom Englund 2018-04-21 10:10:59 UTC
Device: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.16.3-1-ARCH, LLVM 6.0.0) (0x687f)
mesa Version: 18.0.1

when starting legion td 2 in wine my system freezes and these errors happends in my journal.

apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c192000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c212000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c292000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c312000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c60a000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c952000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c70a000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c68a000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c58a000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:190 vmid:5 pas_id:0)
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0:   at page 0x0000680c0c78b000 from 27
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x005C017D
apr 21 11:55:24 tom-pc kernel: amdgpu 0000:03:00.0: IH ring buffer overflow (0x000A2D40, 0x00002E00, 0x00022D60)
Comment 1 Martin Peres 2019-11-19 08:35:51 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/349.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.