From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 93178] Textures are filled with garbage
Date: Tue, 01 Dec 2015 03:28:09 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0854193329=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 5AE8B89FDE
for ; Mon, 30 Nov 2015 19:28:09 -0800 (PST)
In-Reply-To:
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
--===============0854193329==
Content-Type: multipart/alternative; boundary="1448940489.7D5b21.1066"; charset="UTF-8"
--1448940489.7D5b21.1066
Date: Tue, 1 Dec 2015 03:28:09 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
https://bugs.freedesktop.org/show_bug.cgi?id=3D93178
--- Comment #2 from Michel D=C3=A4nzer ---
Replaying the trace on radeonsi generates lots of GL API errors:
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete
framebuffer)
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays(incomple=
te
framebuffer)
Mesa: 1 similar GL_INVALID_FRAMEBUFFER_OPERATION errors
(repeated several times)
Mesa: User error: GL_INVALID_ENUM in
glRenderbufferStorage(internalFormat=3DGL_SLUMINANCE8)
Mesa: User error: GL_INVALID_ENUM in
glRenderbufferStorage(internalFormat=3DGL_SLUMINANCE8_ALPHA8)
(the first three lines repeated several times again)
I think those errors could explain the incorrect rendering. Which driver was
the apitrace captured with? Does the same problem occur when running the
application with radeonsi directly?
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1448940489.7D5b21.1066
Date: Tue, 1 Dec 2015 03:28:09 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Comment=
# 2
on bug 93178<=
/a>
from Michel D=C3=A4nzer
Replaying the trace on radeonsi generates lots of GL API error=
s:
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete
framebuffer)
Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glDrawArrays(incomple=
te
framebuffer)
Mesa: 1 similar GL_INVALID_FRAMEBUFFER_OPERATION errors
(repeated several times)
Mesa: User error: GL_INVALID_ENUM in
glRenderbufferStorage(internalFormat=3DGL_SLUMINANCE8)
Mesa: User error: GL_INVALID_ENUM in
glRenderbufferStorage(internalFormat=3DGL_SLUMINANCE8_ALPHA8)
(the first three lines repeated several times again)
I think those errors could explain the incorrect rendering. Which driver was
the apitrace captured with? Does the same problem occur when running the
application with radeonsi directly?
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1448940489.7D5b21.1066--
--===============0854193329==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============0854193329==--