From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105339] Deadlock inside glClientWaitSync
Date: Sun, 04 Mar 2018 23:55:28 +0000 [thread overview]
Message-ID: <bug-105339-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105339
Bug ID: 105339
Summary: Deadlock inside glClientWaitSync
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: dark_sylinc@yahoo.com.ar
QA Contact: dri-devel@lists.freedesktop.org
Calling glClientWaitSync under specific conditions will run into an
unrecoverable deadlock.
The only known workaround is to issue a glFlush before glClientWaitSync.
I originally discovered this problem in the Dolphin Emulator, see ticket
https://bugs.dolphin-emu.org/issues/10904
However I am now reporting it because I was able to reproduce this bug
independently.
Reported affected systems so far:
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
16GB RAM (1 stick)
GPU: Radeon RX 560 Series (POLARIS11 / DRM 3.19.0 / 4.14.11, LLVM 6.0.0)
Mesa 18.1.0-devel (git-183ce5e629)
Xubuntu 17.10
Kernel 4.14.11
i3 4150 @ 3.50ghz
DDR3 12GB RAM
AMD R7 260X 2GB VRAM
Ubuntu 17.10
Kernel 4.15.4
Mesa 18.1.0-devel
I will try to upload a simple repro if I can in the next few hours.
I stumble on this issue because our Ogre 2.2 sample "Sample_PlanarReflections"
is affected by it.
My git version is stuck at 847d0a393d7f0f967f39302900d5330f32b804c8 due to an
unrelated regression reported at
https://bugs.freedesktop.org/show_bug.cgi?id=105218
However I know the bug is still present as of
1f5618e81c00199d3349b1ade797382635b2af85 (which is not latest)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3375 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-03-04 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 23:55 bugzilla-daemon [this message]
2018-03-05 0:56 ` [Bug 105339] Deadlock inside glClientWaitSync 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
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@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.