From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107612] [Vega10] Hard Lock [gfxhub] VMC page fault when opening Mario Kart 8 in Cemu under wine
Date: Sun, 28 Apr 2019 00:14:04 +0000 [thread overview]
Message-ID: <bug-107612-502-0T4IioX4xD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107612-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 698 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107612
--- Comment #5 from coraxio <kazoon401+fd@gmail.com> ---
As far as I can tell, I'm having a similar problem with Pac-Man Championship
DX+. AMD Ryzen 5 2400G (Vega 11), AMDGPU drivers with up-to-date Arch software.
Since Pac-Man is a Windows game, I've run it through both Wine and Proton, and
each results in a hard lock with VMC page fault.
In particular, I can actually launch the game. But whenever I actually start a
level (which is when the graphics, simple as they are, become more intense), my
system locks up either instantly or within 5 seconds.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1555 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-28 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 13:29 [Bug 107612] [Vega10] Hard Lock [gfxhub] VMC page fault when opening Mario Kart 8 in Cemu under wine bugzilla-daemon
2018-08-18 23:50 ` bugzilla-daemon
2018-10-13 8:06 ` bugzilla-daemon
2019-01-30 11:30 ` bugzilla-daemon
2019-04-18 19:42 ` bugzilla-daemon
2019-04-28 0:14 ` bugzilla-daemon [this message]
2019-05-19 2:35 ` bugzilla-daemon
2019-05-22 15:06 ` 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-107612-502-0T4IioX4xD@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).