https://bugs.freedesktop.org/show_bug.cgi?id=49140
Bug #: 49140
Summary: r600_state_common.c:761:r600_draw_vbo: Assertion `0'
failed
Classification: Unclassified
Product: Mesa
Version: git
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bgz.marko(a)gmail.com
Created attachment 60568
--> https://bugs.freedesktop.org/attachment.cgi?id=60568
R600_DUMP_SHADERS
Hello,
I have an application using a rather complex shader with some branching -
while/if. Applications fails with r600 driver giving the following error:
EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !
r600_state_common.c:761:r600_draw_vbo: Assertion `0' failed.
It seems something goes wrong in the branching section, since it works if I
comment it. The same shader works fine using either LIBGL_ALWAYS_SOFTWARE=1 or
fglrx. Also, I can remember working it fine with some older revision of R600,
unfortunately I don't know which one exactly.
I have attached R600_DUMP_SHADERS output. If needed I can also provide links to
source code or any other data that may be helpful in debugging.
Some relevant parts of glxinfo:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 8.1-devel (git-1a33c1b precise-oibaf-ppa)
Best regards,
Marko
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=48305
Bug #: 48305
Summary: llpp gets segfault in r600g_dri.so
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: myxolmyxmyx(a)yopmail.com
Loading any pdf with llpp produces segfault.
Message in dmesg:
[115638.669260] llpp[15916] general protection ip:b64f6d84 sp:bfe416dc error:0
in r600g_dri.so[b62d3000+a72000]
mupdf that is used by llpp works flawlessly on r600g. And llpp works on fglrx.
I'm using Radeon 2600 PRO AGPx4.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=47900
Bug #: 47900
Summary: Sampler does not work with cubemaps in 16-bit
component pixel format
Classification: Unclassified
Product: Mesa
Version: 8.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: llyzs(a)163.com
If a cubemap is created using 16-bit component pixel format like
PIPE_FORMAT_R16G16B16A16_UNORM or PIPE_FORMAT_R16G16B16A16_FLOAT, it will not
be sampled correctly in fragment shader and generate garbage output. Those
16-bit formats works just fine when using in 2D texture, and the cubemap using
8-bit format also works. It's just the combination cubemap+16bit that does not
work.
Any hints?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=45709
Bug #: 45709
Summary: r600g doesn't seem to flush when it should → visual
stuck
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
URL: http://bugs.winehq.org/show_bug.cgi?id=29802
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: kai(a)dev.carbon-project.org
Yesterday I filed [0] in Wine's bug tracker. But now, after some replies there
(works with the proprietary nVidia driver) and an apitrace [1] (over 200 MB,
please download it only, if you can help) I concluded with the awesome help of
José Fonseca, that the bug is most likely in the driver (please note, that it
is also possible, that the issue is lurking e.g. in the common Gallium3D code).
In short, when I start Dungeon Keeper 2 with Wine I see everything until the
intro/logo videos end and then are stuck with the last video frame. I don't get
to see the main menu. Even though the menu is rendered as can be seen from the
trace.
Replaying the trace with and without -sb doesn't make a difference. In both
cases the replay shows the menu, while a live Wine "window" does not.
Please let me know, if you need something else.
Used stack:
libdrm: 2.4.30-1
Mesa: master/0fcc5189 (r600g)
Linux: 3.2.3
DDX: 6.14.3 + commits from Git up until and including master/ae45d7e6
X.org: 1.11.3.901 (1.11.4 RC 1)
Hardware: 1002:9553
Wine: 1.4 RC2
[0] <http://bugs.winehq.org/show_bug.cgi?id=29802>
[1] <http://dev.carbon-project.org/debian/wine.bugs/29802/DK2.trace>
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=42025
Bug #: 42025
Summary: [RADEON:KMS:R600] wine, Halo Trial: glPointSize error
= INVALID_VALUE
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bpaterni(a)gmail.com
I'm trying to get the Halo: Combat Evolved Trial to launch on my machine and
I'm thinking this may be a mesa bug rather than a wine bug. So I'm posting here
first.
The game looks like it launches okay, but as soon as the menu pops up, the game
screen starts to flicker different solid colors. I can hear the halo theme in
the background so I know the application hasn't crashed entirely.
I've tried mesa's software renderer (llvmpipe). It does not experience the same
solid color flickering as r600g does. Although another (unrelated) exception
occurs if I do use llvmpipe.
An apitrace of what I'm experiencing should be located here:
http://bayfiles.com/file/18s1/EWVVJ9/halo-trial.trace.gz
You should be able to find the halo trial install/executable online for free
somewhere with a google search. I don't think Bungie or Microsoft host the file
themselves anymore, but you should be able to find it on one of the many free
hosting sites available.
environment info:
Debian unstable/experimental with distro provided kernel 3.0.0-2-amd644
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.12-devel (git-3560027)
wine-1.3.30-293-g7fa15c5
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=40790
Summary: r600g readPixSanity failure on RS880 Radeon HD 4250
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: nmiell(a)gmail.com
Created an attachment (id=51059)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51059)
Results for glean/readPixSanity
readPixSanity fails with both Mesa 7.11 and current git
(2154c672b3f2a0f3de7aaacd9260954b9310262a) on ATI Technologies Inc RS880
[Radeon HD 4250] using the Gallium R600 driver.
Test failure is:
readPixSanity: FAIL rgba8, db, z24, s8, win+pmap, id 33
Depth worst-case error was 8.39711 bits at (31, 31)
expected 0.10967; got 0.10965.
RGBA largest readback error was 0 bits
Depth largest readback error was 8.39711 bits
readPixSanity: FAIL rgba8, db, z24, s8, win+pmap, id 34
Depth worst-case error was 8.39711 bits at (31, 31)
expected 0.10967; got 0.10965.
RGBA largest readback error was 0 bits
Depth largest readback error was 8.39711 bits
readPixSanity: FAIL rgba8, db, z24, s8, win+pmap, id 109
Depth worst-case error was 8.39711 bits at (31, 31)
expected 0.10967; got 0.10965.
RGBA largest readback error was 0 bits
Depth largest readback error was 8.39711 bits
In addition, the following X error is generated:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 136 (DRI2)
Minor opcode of failed request: 8 (DRI2SwapBuffers )
Resource id in failed request: 0x220000b
Serial number of failed request: 1280
Current serial number in output stream: 1280
Relevant packages:
xorg-x11-server-Xorg-1.10.4-1.fc15.x86_64
xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64
kernel-2.6.40.4-5.fc15.x86_64 (that's 3.0.4 with a mangled version)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=39714
Summary: Slow and choppy 3D performace on evergreen after
pm-suspend
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bugs.xorg(a)boris64.net
Created an attachment (id=49783)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49783)
dmesg including pm-suspend event
I get very slow and choppy 3d performance after suspending my computer.
This is valid for glxgears (i-know-it's-not-a-benchmark), kwin and others.
After restarting the 3d application speed seems to be normal/ok again.
Example:
[glxgears output]
17641 frames in 5.0 seconds = 3528.125 FPS
18396 frames in 5.0 seconds = 3679.087 FPS
22768 frames in 5.0 seconds = 4553.543 FPS
18280 frames in 5.0 seconds = 3655.863 FPS
16051 frames in 5.0 seconds = 3210.111 FPS
16030 frames in 5.0 seconds = 3205.946 FPS
18157 frames in 5.0 seconds = 3628.626 FPS
18182 frames in 5.0 seconds = 3636.259 FPS
...
(-> pm-msuspend here <-)
...
12270 frames in 19.1 seconds = 641.561 FPS
4518 frames in 5.0 seconds = 903.255 FPS
4721 frames in 5.0 seconds = 944.181 FPS
4750 frames in 5.0 seconds = 949.833 FPS
4724 frames in 5.0 seconds = 944.745 FPS
4759 frames in 5.0 seconds = 951.687 FPS
4535 frames in 5.0 seconds = 905.757 FPS
4557 frames in 5.0 seconds = 911.264 FPS
[/glxgears output]
Used drivers+software:
-xorg-server-1.10.3
-mesa(r600g)/ddx/libdrm from git (latest)
-kernel-3.0.0
If you need more infos/logs, please do not hesitate to ask.
Thank you in advance!
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=38941
Summary: Wrong render in Blender with clipping border active in
edit mode
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: kam1kaz3(a)gmail.com
Created an attachment (id=48737)
--> (https://bugs.freedesktop.org/attachment.cgi?id=48737)
wrong render
When we enable the clipping border (Alt+B) in Blender and enter edit mode, the
vertex handles (small quads) are misplaced and huge. This is better seen after
rotating the camera.
LIBGL_ALWAYS_SOFTWARE=1 works fine.
Correct rendering:
http://wiki.blender.org/index.php/Doc:Manual/3D_interaction/Navigating/3D_V…
Wrong rendering: See attached screenshot.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=38710
Summary: GTA Vice City hangs in initial menu
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: j.suarez.agapito(a)gmail.com
I am filing this bug as requested in this wine bug report since the bug seems
to affect the r600g driver rather than wine itself.
http://bugs.winehq.org/show_bug.cgi?id=27609
Please, if any additional information is needed, let me know.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=37417
Summary: No Alpha Channel for all XPixmaps with KWin+GLES
Product: Mesa
Version: 7.10
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: mgraesslin(a)kde.org
Created an attachment (id=46961)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46961)
ARGB window without alpha channel
After updating mesa on Debian Testing to package version 7.10.2-2 everything
mapped from a XPixmap lost the Alpha Channel. ARGB windows are no longer
translucent (screenshot attached) as well everything else mapped from an
XPixmap. This only affects OpenGL ES/EGL build of KWin, building against
desktop GL/GLX does not show the symptoms.
Debug output of KWin with GLES:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV710
OpenGL version string: OpenGL ES 2.0 Mesa 7.10.2
OpenGL shading language version string: OpenGL ES GLSL ES 1.0.16
Driver: R600G
GPU class: R700
OpenGL version: 2.0
GLSL version: 1.0.16
Mesa version: 7.10.2
X server version: 1.10.1
Linux kernel version: 2.6.38
Direct rendering: yes
Requires strict binding: yes
GLSL shaders: yes
Texture NPOT support: yes
Debug output of KWin with GLX:
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV710 954F) 20090101
TCL DRI2
OpenGL version string: 2.1 Mesa 7.10.2
OpenGL shading language version string: 1.20
Driver: R600C
GPU class: R700
OpenGL version: 2.1
GLSL version: 1.20
Mesa version: 7.10.2
X server version: 1.10.1
Linux kernel version: 2.6.38
Direct rendering: yes
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
This worked fine until update of the package. KWin has not changed (recent
master, build from today).
If you need any help to investigate, please ask. We want to push the GLES build
of KWin with our upcoming release (beta 1 next week).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.