From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1733722550==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2C88E6E17F for ; Sat, 28 Apr 2018 20:06:49 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1733722550== Content-Type: multipart/alternative; boundary="15249460090.c77AE.6102" Content-Transfer-Encoding: 7bit --15249460090.c77AE.6102 Date: Sat, 28 Apr 2018 20:06:49 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D106302 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=3D139204&action=3Dedit Isolated test case Summary: =3D=3D=3D=3D=3D=3D=3D=3D 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: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Valid texture content in pbuffer surface of Thread 1. Actual behavior: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --15249460090.c77AE.6102 Date: Sat, 28 Apr 2018 20:06:49 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 106302
Summary [radeonsi] Garbage content when accessing a texture in multip= le 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=
 [details]
Isolated test case

Summary:
=3D=3D=3D=3D=3D=3D=3D=3D
On radeonsi, when performing an "asynchronous texture upload" (th=
at 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:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Valid texture content in pbuffer surface of Thread 1.

Actual behavior:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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.
= --15249460090.c77AE.6102-- --===============1733722550== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1733722550==--