dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 100784] Fullscreen fade transitions in starsector run at a few frames per second
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100784 Bug ID: 100784 Summary: Fullscreen fade transitions in starsector run at a few frames per second Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: jon(a)moozaad.co.uk QA Contact: dri-devel(a)lists.freedesktop.org The game generally runs at the 60fps cap with this exception. Game forum bug link: http://fractalsoftworks.com/forum/index.php?topic=11972.0 http://i.imgur.com/5zbBSCc.png (see the double prongs on the draw calls, the buffer wait is just an alt-tab) I'm running Opensuse Tumbleweed (mesa 17.0.3/kernel 4.10.10) on a Fury X. Reproduction: Launch star sector (any resolution, windowed or fullscreen) Get into the game (skip tutorials etc) Initiated a UI transition (easiest is press tab for map, left click a planet to show planet info) I'm working on getting an API trace. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 100638] Shadow of mordor crash Mesa: User error: GL_INVALID_VALUE in glFlushMappedBufferRange(offset 2097060 + length 480 > mapped length 2097152)
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100638 Bug ID: 100638 Summary: Shadow of mordor crash Mesa: User error: GL_INVALID_VALUE in glFlushMappedBufferRange(offset 2097060 + length 480 > mapped length 2097152) Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: edisonalvarez(a)arnet.com.ar QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130770 --> https://bugs.freedesktop.org/attachment.cgi?id=130770&action=edit dmesg It crashes randomly if I reset the graphics settings to default it doesn't happen again for some time, then it crashes again and I have to reset the settings because it won't start. I using DAL/DC kernel staging from git 4.9.20, but it happens with other kernels. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 100400] Game Valhalla Hills crash on startup
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100400 Bug ID: 100400 Summary: Game Valhalla Hills crash on startup Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: beham.christopher(a)gmx.at QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130460 --> https://bugs.freedesktop.org/attachment.cgi?id=130460&action=edit Output of the game execution logged with script The Game Valhalla Hills crashes for me on Mesa 17.0.2 on Archlinux. I tried the mesa packages from the standard archlinux extra repo. To get a little bit more information I added the line '--enable-debug \' to ./configure in the mesa_archlinux_package_source_files and created the packages and installed the packages mesa and mesa-vdpau, except from builded with enabled debug these packages are the same as from the standard archlinux extra repo. The attached file run is the output of executing: ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose ./ValhallaHills-Linux-Shipping The attached file gdb is the output of executing: ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose gdb ./ValhallaHills-Linux-Shipping I also tried to play with MESA_GL_VERSION_OVERRIDE (the game seems to need at least 3.2) and MESA_GLSL_VERSION_OVERRIDE (the game seems to need at least 150) but with no effects on the error outputs. The game works very well when using the amdgpu-pro driver version 16.60.379184 and turning off vsync in the game options. But I want to keep Mesa because of the need to downgrade packages for amdgpu-pro and bad performance on Grid Autosport. The game also works with an old nvidia GeForce GT240 in my old PC in my cellar with both nvidia version 340 and mesa nouveau driver, with colour and blinking light issues but quite playable. -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 100239] Incorrect rendering in CS:GO
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100239 Bug ID: 100239 Summary: Incorrect rendering in CS:GO Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: network723(a)rkmail.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130271 --> https://bugs.freedesktop.org/attachment.cgi?id=130271&action=edit Broken AUG scope In windows, when you're aiming with AUG the screen around the scope is blurred. On Mesa we have strange black pattern. The pattern changes on each cs:go restart. I can reproduce it on Mesa 17.1-git + llvm 5.0 + RX480 and on stock Ubuntu 16.04.2 (Mesa 13.0, I believe) + R7 240 Note: green rectangles are not the bug, it's me hiding my steam name. -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 100166] Colored terrain/tents in Shadow of Mordor during weather storms
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100166 Bug ID: 100166 Summary: Colored terrain/tents in Shadow of Mordor during weather storms Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: vedran(a)miletic.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130170 --> https://bugs.freedesktop.org/attachment.cgi?id=130170&action=edit Colored terrain (See attached screenshot.) I am running latest LLVM and Mesa git on Tonga (R9 380X). Not sure if this is a regression or not. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 100024] [radeonsi] Failed to find memory space for buffer eviction when calling glTexSubImage2D with 16384 / 2
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100024 Bug ID: 100024 Summary: [radeonsi] Failed to find memory space for buffer eviction when calling glTexSubImage2D with 16384 / 2 Product: DRI Version: XOrg git Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: julien.isorce(a)gmail.com Created attachment 130005 --> https://bugs.freedesktop.org/attachment.cgi?id=130005&action=edit new piglit test max-texture-size2 to reproduce the problem / [AMD/ATI] Cape Verde PRO [FirePro W600] / The piglit test max-texture-size2 prints: GL_TEXTURE_RECTANGLE, Internal Format = GL_RGBA8, Largest Texture Size = 16384 radeon: Not enough memory for command submission. [drm:radeon_cs_ioctl [radeon]] *ERROR* Failed to parse relocation -12! (ENOMEM) PIGLIT: {"subtest": {"GL_TEXTURE_RECTANGLE-GL_RGBA8" : "pass"}} It says it passes but internally it fails. It looks like a bug from the TTM GPU memory manager subsystem in the linux kernel. To reproduce just run: RADEON_THREAD=false DISPLAY=:0 PIGLIT_SOURCE_DIR=/home/julien/dev/piglit/ PIGLIT_PLATFORM=mixed_glx_egl ./bin/max-texture-size -fbo -auto I set RADEON_THREAD=false to make it easier since the problem also appears with true. I attached a new and more minimal piglit test "max-texture-size2" that reproduces the problem. A workaround of the problem is to use GL fence as the new test also demonstrates setting the env var USE_FENCE. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 99974] Pinned memory is extremely slow on Dolphin
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99974 Bug ID: 99974 Summary: Pinned memory is extremely slow on Dolphin Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: akz(a)tutanota.com QA Contact: dri-devel(a)lists.freedesktop.org When running Dolphin with the OpenGL backend and pinned memory enabled, I get terrible performance. Getting about 10-20fps in a 60fps game with pinned memory, and full 60fps without it. This was discussed on dolphin's IRC channel earlier today, and this PR was made to disable it. If it gets committed you'll have to use a build without that code to test it I think. https://github.com/dolphin-emu/dolphin/pull/4973/commits/005e6796b85341a3e7… I'm using an RX460, Linux 4.10.0, mesa/llvm/xorg-server all built from git, although it happens on older stable versions too. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 99782] Driver lockup using dolphin in specific areas
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99782 Bug ID: 99782 Summary: Driver lockup using dolphin in specific areas Product: Mesa Version: git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: radeon.20.mathieui(a)dfgh.net QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 129537 --> https://bugs.freedesktop.org/attachment.cgi?id=129537&action=edit Dolphin FIFO log that triggers the lockup Using my RX 470 card and mesa, my video driver locks up in specific parts of a game (Fire Emblem: Radiant Dawn) using the Dolphin emulator. I can still interact with the system using ssh, but the screen stays frozen at the exact moment and stays unresponsive until reboot (trying to kill dolphin leads to a zombie). I tried with all stable mesa versions between 13.0 and 13.0.4, and a fairly recent git version (3f064e9a40), and I can reproduce the lockup every time. I attached a dolphin fifo log which triggers the bug and can be run without owning the game. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 99710] [amdgpu R9 390] GPU hang when playing Hearthstone in Wine
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99710 Bug ID: 99710 Summary: [amdgpu R9 390] GPU hang when playing Hearthstone in Wine Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: garththeisen(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 129407 --> https://bugs.freedesktop.org/attachment.cgi?id=129407&action=edit DDEBUG_DUMP_#1 Repeatedly able to hang system running Hearthstone via Wine. The crash is never predictable but it often occurs right as the game is entering a multiplayer match or some short while after. Screen goes blank and system is unresponsive, no luck with Magic SysRq key in most cases. System Profile ... GPU: R9 390X Distro: Gentoo Kernel: Linux 4.9.8 KMD: amdgpu UMD: Mesa (git) -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 99685] [amdgpu R9 390X] GPU hang on windows switching while running Quetoo
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99685 Bug ID: 99685 Summary: [amdgpu R9 390X] GPU hang on windows switching while running Quetoo Product: Mesa Version: 17.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: dev(a)illwieckz.net QA Contact: dri-devel(a)lists.freedesktop.org Hi, I trigger a GPU hang whenever I switch between the Quetoo window and another windows using Alt+Tab. A map must be loaded to trigger the hang. Once the GPU hanged, the display does not update (but everything else is still running, I can hear sound effects, connect from a remote computer to monitor things etc) and every action that query the GPU will hang, for example after the display hang, it's not possible to run clinfo otherwise it will never return. GPU: R9 390X Distro: Ubuntu 16.10 Kernel: Linux 4.9.0-6.1 (from https://liquorix.net/ ) KMD: amdgpu UMD: Mesa 17.1.0-devel (from https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa ) How to trigger the bug: 1. Untar Quetoo prebuild binary (from http://quetoo.org/pages/downloads ) 2. run bin/quetoo-update to get data 3. delete lib/libdrm.so.2 and lib/libstdc++.so.6 from quetoo dir if needed 4. run bin/quetoo 5. load a map (or join a server) 6. do the Alt+Tab thing to switch between windows and come back to Quetoo. If you want to build quetoo yourself, you can run it that way after having built it: $ src/main/quetoo -p …/quetoo/share/default -p …/quetoo/lib/default "…/quetoo" being the path where you ran quetoo-update before (share/default contains pk3 game data and lib/default contains glsl etc.) I don't know if the bug is on Mesa side or kernel side. dmesg http://pastebin.com/eQt6radD Xorg.0.log http://pastebin.com/Ge11mwN6 journactl /usr/lib/gdm3/gdm-x-session http://pastebin.com/3hYX08H7 -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017