From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99349] Failed to build shader (translation from TGSI)
Date: Tue, 10 Jan 2017 17:24:46 +0000 [thread overview]
Message-ID: <bug-99349-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99349
Bug ID: 99349
Summary: Failed to build shader (translation from TGSI)
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: balalic.enver@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 128864
--> https://bugs.freedesktop.org/attachment.cgi?id=128864&action=edit
glxinfo
I'm using a Radeon HD6950, it fails to build a shader when playing "War
Thunder", renders the login screen fine, starts to build shaders and then fails
and spams the following in the console:
EE r600_state_common.c:799 r600_shader_select - Failed to build shader variant
(type=1) -1
EE r600_shader.c:183 r600_pipe_shader_create - translation from TGSI failed !
same thing happens a lof of shaders from shadertoy.com.
OS: OpenSUSE Tumbleweed, glxinfo attached
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2695 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:[~2017-01-10 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:24 bugzilla-daemon [this message]
2017-01-10 17:44 ` [Bug 99349] Failed to build shader (translation from TGSI) bugzilla-daemon
2017-05-17 6:45 ` bugzilla-daemon
2017-05-24 13:10 ` bugzilla-daemon
2017-05-24 14:56 ` bugzilla-daemon
2017-05-25 8:10 ` bugzilla-daemon
2017-05-25 9:32 ` bugzilla-daemon
2017-05-26 9:01 ` bugzilla-daemon
2017-05-26 9:03 ` bugzilla-daemon
2017-05-26 13:31 ` bugzilla-daemon
2017-05-26 20:24 ` bugzilla-daemon
2017-05-29 13:28 ` bugzilla-daemon
2017-06-02 17:55 ` bugzilla-daemon
2017-06-25 22:29 ` bugzilla-daemon
2017-06-26 6:03 ` bugzilla-daemon
2017-06-26 13:41 ` bugzilla-daemon
2017-07-11 23:07 ` bugzilla-daemon
2017-07-16 21:17 ` bugzilla-daemon
2017-09-08 5:56 ` bugzilla-daemon
2017-09-08 11:05 ` bugzilla-daemon
2018-03-26 13:13 ` bugzilla-daemon
2018-03-26 18:26 ` 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-99349-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).