dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105251] [Vega10]  GPU lockup on boot: VMC page fault
Date: Sat, 17 Nov 2018 22:57:00 +0000	[thread overview]
Message-ID: <bug-105251-502-mJwSb5uXpf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105251-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1534 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105251

--- Comment #59 from Benjamin Hodgetts <ben@xnode.org> ---
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:
==============
[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=1020, emitted seq=1023
==============

And then this when trying to run Super Mario Odyssey in Yuzu:
==============
[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=24703, emitted seq=24704
==============

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2315 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-11-17 22:57 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  9:39 [Bug 105251] [Vega10] GPU lockup on boot: VMC page fault bugzilla-daemon
2018-04-28  6:10 ` bugzilla-daemon
2018-04-29 13:29 ` bugzilla-daemon
2018-04-29 13:54 ` bugzilla-daemon
2018-05-24  5:24 ` bugzilla-daemon
2018-05-25 14:22 ` bugzilla-daemon
2018-06-01 17:31 ` bugzilla-daemon
2018-06-04 14:00 ` bugzilla-daemon
2018-06-04 17:52 ` bugzilla-daemon
2018-06-04 18:39 ` bugzilla-daemon
2018-06-05  8:50 ` bugzilla-daemon
2018-07-15 22:44 ` bugzilla-daemon
2018-07-15 22:56 ` bugzilla-daemon
2018-07-15 23:09 ` bugzilla-daemon
2018-07-16 15:13 ` bugzilla-daemon
2018-08-08 23:40 ` bugzilla-daemon
2018-08-14 19:19 ` bugzilla-daemon
2018-08-20  6:30 ` bugzilla-daemon
2018-08-20 15:13 ` bugzilla-daemon
2018-08-21  8:46 ` bugzilla-daemon
2018-08-21  8:48 ` bugzilla-daemon
2018-08-21 14:56 ` bugzilla-daemon
2018-08-21 15:12 ` bugzilla-daemon
2018-08-22 20:21 ` bugzilla-daemon
2018-08-24 14:11 ` bugzilla-daemon
2018-08-24 14:12 ` bugzilla-daemon
2018-08-24 14:24 ` bugzilla-daemon
2018-08-24 16:39 ` bugzilla-daemon
2018-08-24 19:35 ` bugzilla-daemon
2018-08-24 19:37 ` bugzilla-daemon
2018-08-25  2:48 ` bugzilla-daemon
2018-08-25  2:49 ` bugzilla-daemon
2018-08-25  5:59 ` bugzilla-daemon
2018-08-25  9:09 ` bugzilla-daemon
2018-08-27 16:12 ` bugzilla-daemon
2018-08-27 17:19 ` bugzilla-daemon
2018-08-27 23:14 ` bugzilla-daemon
2018-08-28 19:10 ` bugzilla-daemon
2018-08-28 19:20 ` bugzilla-daemon
2018-08-29  9:30 ` bugzilla-daemon
2018-08-29 14:32 ` bugzilla-daemon
2018-08-29 22:54 ` bugzilla-daemon
2018-08-30  1:37 ` bugzilla-daemon
2018-08-30  2:03 ` bugzilla-daemon
2018-08-30  2:41 ` bugzilla-daemon
2018-08-30 14:27 ` bugzilla-daemon
2018-08-30 14:33 ` bugzilla-daemon
2018-08-31 19:13 ` bugzilla-daemon
2018-09-03 13:26 ` bugzilla-daemon
2018-09-04 17:40 ` bugzilla-daemon
2018-09-06  4:07 ` bugzilla-daemon
2018-09-06  9:55 ` bugzilla-daemon
2018-09-11  8:36 ` bugzilla-daemon
2018-09-11 10:01 ` bugzilla-daemon
2018-09-12  3:26 ` bugzilla-daemon
2018-10-24  4:01 ` bugzilla-daemon
2018-10-24  8:38 ` bugzilla-daemon
2018-10-28 12:14 ` bugzilla-daemon
2018-10-28 23:19 ` bugzilla-daemon
2018-11-17 22:57 ` bugzilla-daemon [this message]
2018-11-18  1:13 ` bugzilla-daemon
2018-12-13  0:46 ` bugzilla-daemon
2018-12-13  9:05 ` bugzilla-daemon
2018-12-18  1:56 ` bugzilla-daemon
2018-12-18  2:08 ` bugzilla-daemon
2019-02-19  1:47 ` bugzilla-daemon
2019-05-19  2:38 ` bugzilla-daemon
2019-05-21 14:01 ` bugzilla-daemon
2019-05-21 14:02 ` bugzilla-daemon
2019-07-03 11:08 ` bugzilla-daemon
2019-07-04 15:19 ` bugzilla-daemon
2019-07-20 17:05 ` bugzilla-daemon
2019-07-22  7:40 ` bugzilla-daemon
2019-07-22  8:29 ` bugzilla-daemon
2019-07-22 20:15 ` bugzilla-daemon
2019-07-22 20:56 ` bugzilla-daemon
2019-07-22 20:57 ` bugzilla-daemon
2019-07-22 21:03 ` bugzilla-daemon
2019-07-22 21:06 ` bugzilla-daemon
2019-07-26 18:52 ` bugzilla-daemon
2019-11-19  8:31 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105251-502-mJwSb5uXpf@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).