From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105251] [Vega10] GPU lockup on boot: VMC page fault Date: Sat, 17 Nov 2018 22:57:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0722777928==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 1181F89FF9 for ; Sat, 17 Nov 2018 22:57:01 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0722777928== Content-Type: multipart/alternative; boundary="15424954208.77e0AE8EF.21185" Content-Transfer-Encoding: 7bit --15424954208.77e0AE8EF.21185 Date: Sat, 17 Nov 2018 22:57:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105251 --- Comment #59 from Benjamin Hodgetts --- It's not just Cemu, it looks like it happens in Yuzu too. If you Google for "VMC page fault" then you'll find people running into that error in various other programs too. Personally, this is what I got when running MK8 in Cemu: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Sat Nov 17 22:29:43 2018] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:155 vmid:3 pasid:32769, for process Cemu.exe pid 963 thread Cemu.exe:cs0 pid 1035) at address 0x000080014189a000 from 27 VM_L2_PROTECTION_FAULT_STATUS:0x00301137 (repeated 7 times over the space of a few minutes) [Sat Nov 17 22:32:44 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=3D1020, emitted seq=3D1023 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D And then this when trying to run Super Mario Odyssey in Yuzu: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Sat Nov 17 22:47:26 2018] amdgpu 0000:03:00.0: [gfxhub] VMC page fault (src_id:0 ring:156 vmid:3 pasid:32769, for process yuzu pid 960 thread yuzu= :cs0 pid 972 at address 0x000080bd27743000 from 27 VM_L2_PROTECTION_FAULT_STATUS:0x00301138 [Sat Nov 17 22:47:36 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring = gfx timeout, signaled seq=3D24703, emitted seq=3D24704 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I'll look into getting the info dump that was requested earlier in the thre= ad to see if that helps, but the seemingly abandoned state of this bug is rath= er concerning. --=20 You are receiving this mail because: You are the assignee for the bug.= --15424954208.77e0AE8EF.21185 Date: Sat, 17 Nov 2018 22:57:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 59 on bug 10525= 1 from <= span class=3D"fn">Benjamin Hodgetts
It's not just Cemu, it looks like it happens in Yuzu too. If y=
ou Google for
"VMC page fault" then you'll find people running into that error =
in various
other programs too.

Personally, this is what I got when running MK8 in Cemu:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[Sat Nov 17 22:29:43 2018] amdgpu 0000:03:00.0: [gfxhub] VMC page fault
(src_id:0 ring:155 vmid:3 pasid:32769, for process Cemu.exe pid 963 thread
Cemu.exe:cs0 pid 1035) at address 0x000080014189a000 from 27
VM_L2_PROTECTION_FAULT_STATUS:0x00301137
(repeated 7 times over the space of a few minutes)
[Sat Nov 17 22:32:44 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma1 timeout, signaled seq=3D1020, emitted seq=3D1023
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

And then this when trying to run Super Mario Odyssey in Yuzu:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[Sat Nov 17 22:47:26 2018] amdgpu 0000:03:00.0: [gfxhub] VMC page fault
(src_id:0 ring:156 vmid:3 pasid:32769, for process yuzu pid 960 thread yuzu=
:cs0
pid 972 at address 0x000080bd27743000 from 27
VM_L2_PROTECTION_FAULT_STATUS:0x00301138
[Sat Nov 17 22:47:36 2018] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring =
gfx
timeout, signaled seq=3D24703, emitted seq=3D24704
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

I'll look into getting the info dump that was requested earlier in the thre=
ad
to see if that helps, but the seemingly abandoned state of this bug is rath=
er
concerning.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15424954208.77e0AE8EF.21185-- --===============0722777928== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0722777928==--