From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts
Date: Sat, 28 Apr 2018 20:06:49 +0000 [thread overview]
Message-ID: <bug-106302-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1794 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106302
Bug ID: 106302
Summary: [radeonsi] Garbage content when accessing a texture in
multiple shared EGL contexts
Product: Mesa
Version: 17.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: seb@vestigecounty.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 139204
--> https://bugs.freedesktop.org/attachment.cgi?id=139204&action=edit
Isolated test case
Summary:
========
On radeonsi, when performing an "asynchronous texture upload" (that is, a
texture upload on a secondary thread and secondary shared EGL context) the
produced texture is not usable on the main thread (contains garbage).
Steps to reproduce:
===================
1. Create an EGL context (with its own pbuffer surface) and make it current on
Thread 1.
2. Create another EGL context (with its own pbuffer surface) and make it
current on Thread 2.
3. Generate and upload a texture on Thread 2.
4. When Thread 2 is finished, pass the texture name to Thread 1.
5. Draw a textured quad on Thread 1 using the texture passed from Thread 2.
Expected behavior:
==================
Valid texture content in pbuffer surface of Thread 1.
Actual behavior:
================
Garbage is observed.
Behavior is observed in stock mesa in Ubuntu 17.10. Bug is not repro with
software renderer or the i915 driver. Please use the attached cpp file to
reproduce.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3319 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-04-28 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 20:06 bugzilla-daemon [this message]
2019-05-22 11:59 ` [Bug 106302] [radeonsi] Garbage content when accessing a texture in multiple shared EGL contexts bugzilla-daemon
2019-05-25 20:07 ` bugzilla-daemon
2019-05-27 18:47 ` bugzilla-daemon
2019-05-28 18:59 ` bugzilla-daemon
2019-05-29 8:00 ` 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-106302-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.