From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99555] LIBGL_ALWAYS_INDIRECT=1 causes all opengl programms to crash on second frame
Date: Thu, 26 Jan 2017 20:40:44 +0000 [thread overview]
Message-ID: <bug-99555-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99555
Bug ID: 99555
Summary: LIBGL_ALWAYS_INDIRECT=1 causes all opengl programms to
crash on second frame
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: diplosarus@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
LIBGL_ALWAYS_INDIRECT=1 glxgears
fails on latest git on r600 with:
X Error of failed request: 255
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 42
Current serial number in output stream: 164
After rendering one frame. this is on a ATI HD5850. This is 100% repeatable and
occures with every opengl app. Direct Rendering works fine.
Indirect rendering works with the vesa x11 driver and llvmpipe. xf86-video-ati
versus xf86-video-modestetting both fail.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2612 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-26 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 20:40 bugzilla-daemon [this message]
2017-01-27 8:23 ` [Bug 99555] LIBGL_ALWAYS_INDIRECT=1 causes all opengl programms to crash on second frame 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-99555-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.