From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105339] Deadlock inside glClientWaitSync
Date: Fri, 09 Mar 2018 21:48:24 +0000 [thread overview]
Message-ID: <bug-105339-502-90wP4A22aT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105339-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105339
--- Comment #5 from Matias N. Goldberg <dark_sylinc@yahoo.com.ar> ---
I traced the regression to commit:
commit bc65dcab3bc48673ff6180afb036561a4b8b1119
Author: Nicolai Hähnle <nicolai.haehnle@amd.com>
Date: Fri Nov 10 10:58:10 2017 +0100
radeonsi: avoid syncing the driver thread in si_fence_finish
It is really only required when we need to flush for deferred fences.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Although I slightly suspect the former code was just making the race condition
much harder to trigger, considering I've played other Dolphin games in the past
(before this regression) and they ocasionally hanged in a similar way after 2-4
hours of continuous play or so (extremely rare to trigger) and it wouldn't
always happen (But that may have been a different bug).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1836 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 prev parent reply other threads:[~2018-03-09 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 23:55 [Bug 105339] Deadlock inside glClientWaitSync bugzilla-daemon
2018-03-05 0:56 ` bugzilla-daemon
2018-03-05 0:56 ` bugzilla-daemon
2018-03-05 1:02 ` bugzilla-daemon
2018-03-05 1:08 ` bugzilla-daemon
2018-03-09 21:48 ` bugzilla-daemon [this message]
2018-03-09 21:50 ` [Bug 105339] Deadlock inside glClientWaitSync [Regresion bc65dcab3bc48673ff6180afb036561a4b8b1119] bugzilla-daemon
2018-04-04 14:09 ` bugzilla-daemon
2018-05-01 16:24 ` bugzilla-daemon
2018-06-20 17:24 ` 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-105339-502-90wP4A22aT@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