dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[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 100089] [regression] [bisected] Space Run rendering issues
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100089 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #10 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1259. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 100069] Dirt: Showdown bad performance and broken rendering with enabled advanced lightning
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100069 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #12 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1258. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 99859] Glamor Crashes on big endian Hardware
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99859 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #24 from GitLab Migration User <gitlab-migration(a)fdo.invalid> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1254. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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

[Bug 99504] Victor Vran and Tropico 5 flicker when refresh rate is above 60 Hz
by bugzilla-daemon＠freedesktop.org 25 Sep '19

25 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=99504 Bug ID: 99504 Summary: Victor Vran and Tropico 5 flicker when refresh rate is above 60 Hz 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: freedesktop(a)lanig.email QA Contact: dri-devel(a)lists.freedesktop.org Both games don't go above 60Hz with resolutions over 1080p on my setup but I will report this to the devs. Just for the case you like to reproduce the issue. With the newest driver version from the Padoka PPA, RX 480 and EIZO FS-2735 flickering happens when the refresh rate is set to 119Hz or 143Hz. (Ingame settings in Tropico and xrandr for Victor Vran). As far as I remember this happend also in the beginning, has been fixed at some point(but I am not 100% sure) and now happens again. The desktop doesn't suffer the same issue. OpenGL version string: 3.0 Mesa 17.1.0-devel - padoka PPA -- 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 September 2019