From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107891] [wine, regression, bisected] RAGE, Wolfenstein The New Order hangs in menu
Date: Mon, 10 Sep 2018 18:46:05 +0000 [thread overview]
Message-ID: <bug-107891-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1261 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107891
Bug ID: 107891
Summary: [wine, regression, bisected] RAGE, Wolfenstein The New
Order hangs in menu
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sa@whiz.se
QA Contact: dri-devel@lists.freedesktop.org
The games RAGE and Wolfenstein The New Order (using Wine) hangs after a short
while in the menu.
Trying older Mesa releases (and a hacked Wine to work around the need for a
compatibility context) 17.3.9 does not have this issue.
Bisecting lead to
bc65dcab3bc48673ff6180afb036561a4b8b1119
radeonsi: avoid syncing the driver thread in si_fence_finish
It is really only required when we need to flush for deferred fences.
It's not possibly to revert that commit cleanly on 18.2.0, but moving back "ctx
= threaded_context_unwrap_sync(ctx);" to its original place is enough to get
rid of the hang.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2649 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
next reply other threads:[~2018-09-10 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 18:46 bugzilla-daemon [this message]
2018-09-12 11:03 ` [Bug 107891] [wine, regression, bisected] RAGE, Wolfenstein The New Order hangs in menu bugzilla-daemon
2018-09-18 9:29 ` 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-107891-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.