dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 50657] New: [Evergreen,GIT,Tiling?] Occasional invalid command stream and subsequent performance increase
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=50657 Bug #: 50657 Summary: [Evergreen,GIT,Tiling?] Occasional invalid command stream and subsequent performance increase Classification: Unclassified 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: thomas.lindroth(a)gmail.com Starting Warcraft 3 in Wine sometimes failes because of invalid command stream. It happens in about 10% of all startup attempts. After a failed startup Warcraft normally starts fine again and with improved framerate. Normal framerate after clean reboot is 110fps and directly after error it jumps to 150fps. Other applications also get improved framerate. Street fighter 4 benchmark in wine goes from 50 to 61 and glxgears from 4,000 to 10,000. The increased performance lasts for about 2 min and drops back to normal after that. It will jump again next time the error is triggered. No rendering errors can be seen. No other applications besides war3 can trigger the failed command stream. Dmesg reports: radeon 0000:01:00.0: evergreen_surface_value_conv_check:325 depth invalid array mode 15 radeon 0000:01:00.0: evergreen_cs_track_validate_depth:645 depth invalid (0xffffffff 0x00000000 0xffffffff) radeon 0000:01:00.0: evergreen_packet3_check:2015 invalid cmd stream Same message every time. No other error reported in dmesg or Xorg.log Hardware is HD 6770. Using DDX,Mesa,libdrm from latest git. Kernel 3.4.0. "ColorTiling" "true" "ColorTiling2D" "true" "SwapbuffersWait" "false" "EnablePageFlip" "true" radeon.pcie_gen2=1 War3 is invoked as "vblank_mode=0 WINEDEBUG=fps wine war3.exe -opengl" in a wine virtual desktop. The error might be build related. Building mesa with --enable-debug triggers the error more often it seems. Pipeing the output of wine to file also triggers the error. Mesa built from gentoo ebuild ./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --enable-dri --enable-glx --enable-texture-float --disable-debug --enable-egl --disable-gbm --disable-gles1 --disable-gles2 --enable-glx-tls --disable-osmesa --enable-asm --enable-shared-glapi --disable-xa --disable-xorg --with-dri-drivers= --with-gallium-drivers=,swrast,r600 --with-egl-platforms=x11 --enable-gallium-egl --disable-d3d1x --disable-gallium-g3dvl --enable-gallium-llvm --disable-openvg --disable-r600-llvm-compiler --disable-vdpau --disable-xvmc -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 50450] New: OpenGL does not work or works very slowly on Radeon HD3850
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=50450 Bug #: 50450 Summary: OpenGL does not work or works very slowly on Radeon HD3850 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: maksbotan(a)gentoo.org Created attachment 62198 --> https://bugs.freedesktop.org/attachment.cgi?id=62198 lspci I have ATI Radeon HD3850 on AGP bus with Pentium-4 PC. I observe very strange behavior of OpenGL applications: KWin, qudos, doomsday run slowly even not with high quality settings; Quake4 demo from ID site crashes right after map loading, just when rendering starts i suppose, and X server crashes with it. I attach my glxinfo, kernel config and lspci. Versions of used software are: mesa, libdrm and xf86-video-ati from git, linux kernel kernel 3.3.5, X.org server 1.12.1. I think this is bug in mesa or xf86-video-ati related to my video card. Please help me. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 15

[Bug 50135] New: Unigine Heaven black stripes and weird shaders
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=50135 Bug #: 50135 Summary: Unigine Heaven black stripes and weird shaders Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: kam1kaz3(a)gmail.com Created attachment 61868 --> https://bugs.freedesktop.org/attachment.cgi?id=61868 day time rendered image 1 Black stripes appear across geometry, which appears to be wrongly computed shadows, but I'm not sure (see day_* attachments). And some weird rendering happens when night time is rendered (see night_* attachments) System: OS: Arch Linux Kernel: 3.4 RC7 OpenGL renderer string: Gallium 0.4 on AMD RV670 OpenGL version string: 2.1 Mesa 8.1-devel (git-27b821b) OpenGL shading language version string: 1.30 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 18

[Bug 49239] New: wine 1.5 will hand with some applications on evergreen_create_sampler_state ()
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=49239 Bug #: 49239 Summary: wine 1.5 will hand with some applications on evergreen_create_sampler_state () 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: alexandre.f.demers(a)gmail.com Created attachment 60718 --> https://bugs.freedesktop.org/attachment.cgi?id=60718 winedbg glide-init.exe backtrace when hanged If I try to run glide-init.exe with "winedbg glide-init.exe", the application will lock when I'll ask it to "Query OpenGL-infos". I was able to retrieve a backtrace. Backtrace attached. It was working at some point in the past, I would have to go back to a previous Wine version first to remove this variable from the equation, but I'm sure it's not from there. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 49140] New: r600_state_common.c:761:r600_draw_vbo: Assertion `0' failed
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 8

[Bug 48305] New: llpp gets segfault in r600g_dri.so
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 10

[Bug 47900] New: Sampler does not work with cubemaps in 16-bit component pixel format
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 3

[Bug 45709] New: r600g doesn't seem to flush when it should → visual stuck
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 7

[Bug 42025] New: [RADEON:KMS:R600] wine, Halo Trial: glPointSize error = INVALID_VALUE
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 2

[Bug 40790] New: r600g readPixSanity failure on RS880 Radeon HD 4250
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

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.

1 22

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015