mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2020-07-16T12:58:13Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1367[SKL/Iris] Random asserts in SynMark Multithread test: "pipe_reference_descri...2020-07-16T12:58:13ZBugzilla Migration User[SKL/Iris] Random asserts in SynMark Multithread test: "pipe_reference_described: Assertion `count != -1' failed"## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111748)](https://bugs.freedesktop.org/show_bug.cgi?id=111748)**
## Description
Setup:
* HW: SKL GT2 i5-6600K
* OS: Ubuntu 18.04
* S...## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111748)](https://bugs.freedesktop.org/show_bug.cgi?id=111748)**
## Description
Setup:
* HW: SKL GT2 i5-6600K
* OS: Ubuntu 18.04
* SW: Git versions of drm-tip kernel, X server, SynMark2 v7.0
* Mesa: 68820007fddbb5b79f1b2b08e66ef14092053a95 (2019-09-18 15:16:36 radv: fix loading 64-bit GS inputs)
Test-case:
* Run multiple times:
./synmark2 OglMultithread
Expected outcome:
* Works fine, as with i965 driver
Actual outcome:
* Half of the runs hit following assert:
src/gallium/auxiliary/util/u_inlines.h:87:pipe_reference_described: Assertion `count != -1' failed.
Because of [bug 111385](https://bugs.freedesktop.org/show_bug.cgi?id=111385), I don't know when this issue started. That may also have been affected by enabling VT-d (which allows kernel to enable GPU IOMMU).
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=111385https://gitlab.freedesktop.org/mesa/mesa/-/issues/1366Tropico 6 apitrace throws error into logs2019-11-01T10:15:56ZBugzilla Migration UserTropico 6 apitrace throws error into logs## Submitted by Denis
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111676)](https://bugs.freedesktop.org/show_bug.cgi?id=111676)**
## Description
Hi, during testing this issue => https://bugs.freedesktop.or...## Submitted by Denis
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111676)](https://bugs.freedesktop.org/show_bug.cgi?id=111676)**
## Description
Hi, during testing this issue => https://bugs.freedesktop.org/show_bug.cgi?id=111631 I found out that iris throws exception into logs (exactly in the end of the apitrace)
/usr/bin/glretrace+0x25fa21
/usr/lib/libpthread.so.0+0x13cff
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: unsafe_free+0x72461c: ../src/util/ralloc.c:297
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: unsafe_free+0x7245ee: ../src/util/ralloc.c:292
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: ralloc_free+0x72450f: ../src/util/ralloc.c:262
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: iris_delete_shader_state+0x8d1cad: ../src/gallium/drivers/iris/iris_program.c:2194
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: iris_delete_fs_state+0x8d1d90: ../src/gallium/drivers/iris/iris_program.c:2225
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: cso_delete_fragment_shader+0x13df75: ../src/gallium/auxiliary/cso_cache/cso_context.c:662
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: free_zombie_shaders+0x4969b8: ../src/mesa/state_tracker/st_context.c:397
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_context_free_zombie_objects+0x496b0c: ../src/mesa/state_tracker/st_context.c:431
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_flush+0x49527a: ../src/mesa/state_tracker/st_cb_flush.c:60
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_glFlush+0x495398: ../src/mesa/state_tracker/st_cb_flush.c:100
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: _mesa_flush+0x1df957: ../src/mesa/main/context.c:1886
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: _mesa_Flush+0x1dfadf: ../src/mesa/main/context.c:1924
/usr/bin/glretrace+0xe467d
/usr/bin/glretrace+0x5d528
/usr/bin/glretrace+0x5fead
/usr/bin/glretrace+0x57f20
/usr/lib/libc.so.6: __libc_start_main+0xf2
/usr/bin/glretrace: _start+0x2d
?
apitrace: info: taking default action for signal 11
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1365Unreal 4 Elemental and MatineeFightScene demos misrender2019-11-25T23:55:46ZBugzilla Migration UserUnreal 4 Elemental and MatineeFightScene demos misrender## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111636)](https://bugs.freedesktop.org/show_bug.cgi?id=111636)**
## Description
Unreal 4's Elemental demo misrenders on iri...## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111636)](https://bugs.freedesktop.org/show_bug.cgi?id=111636)**
## Description
Unreal 4's Elemental demo misrenders on iris - a bunch of the geometry goes haywire. I am not sure why yet.
https://wiki.unrealengine.com/Linux_Demos
Version: gitIris as Default Driverhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1364[Bisected]. Gallium-nine. Apitrace from the "Just cause" game leads to gpu hang2019-10-17T09:00:51ZBugzilla Migration User[Bisected]. Gallium-nine. Apitrace from the "Just cause" game leads to gpu hang## Submitted by Denis
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111619)](https://bugs.freedesktop.org/show_bug.cgi?id=111619)**
## Description
During checking apitrace for the game Just Cause (using gall...## Submitted by Denis
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111619)](https://bugs.freedesktop.org/show_bug.cgi?id=111619)**
## Description
During checking apitrace for the game Just Cause (using gallium-nine) I faced with gpu hang.
Configuration:
Manjaro OS
mesa-git master
gallium-nine => Native Direct3D 9 v0.4.0.294-release is active.
KBL cpu (HD630)
Actually trace on latest mesa master has a good rendering picture and gpu hang (on lower mesa versions picture can be corrupted). Keep in mind, that you may need release mesa version, because on debug you may got this assertion:
>../src/gallium/drivers/iris/iris_state.c:2536: iris_set_constant_buffer: Assertion `index > 0' failed.
Hang is stable on 351516 call.
Bisected to:
3b6d787e404181758227e205eda03600b25c1fd9 is the first bad commit
commit 3b6d787e404181758227e205eda03600b25c1fd9
Author: Timur Kristóf <timur.kristof@gmail.com>
Date: Fri Jun 14 14:03:28 2019 +0200
iris: move sysvals to their own constant buffer
This commit moves the sysvals to a separate, new constant buffer
at the end (before the shader constants). It also allows us to
remove the special handling we had for cbuf0, and enables all
constant buffers to support user-specified resources and user
buffers.
v2: (by Kenneth Graunke)
Rebase on the previous patch to fix system value uploading.
Fix disk cache num_cbufs calculation
Fix passthrough TCS to report num_cbufs = 1 so upload actually occurs
Change upload_sysvals to assert that num_cbufs > 0 when
num_system_values > 0.
Signed-off-by: Timur Kristóf <timur.kristof@gmail.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
src/gallium/drivers/iris/iris_context.h | 3 +-
src/gallium/drivers/iris/iris_disk_cache.c | 6 ++-
src/gallium/drivers/iris/iris_draw.c | 2 +-
src/gallium/drivers/iris/iris_program.c | 60 ++++++++--------------
src/gallium/drivers/iris/iris_state.c | 80 ++++++++++++++++--------------
5 files changed, 73 insertions, 78 deletions
Link to apitrace => https://drive.google.com/open?id=1MCYg7ncKg30VX_TPnGEIRp6W3HdRMs3C
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1363Mismatch in modifiers between winsys handle and dmabuf fd2019-11-08T09:42:57ZBugzilla Migration UserMismatch in modifiers between winsys handle and dmabuf fd## Submitted by Link Mauve
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111589)](https://bugs.freedesktop.org/show_bug.cgi?id=111589)**
## Description
In iris_resource_from_handle(), when a Wayland client c...## Submitted by Link Mauve
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111589)](https://bugs.freedesktop.org/show_bug.cgi?id=111589)**
## Description
In iris_resource_from_handle(), when a Wayland client created an I915_FORMAT_MOD_Y_TILED_CCS buffer, whandle->modifier and res->bo->tiling_mode end up desynchronised, the first one being Y-tiled, the second linear, leading to the assert on line 967 to crash Weston.
I haven’t been able to figure out where this bo gets created without the proper tiling mode though, but the resource doesn’t have the CCS aux bo either.
A I915_FORMAT_MOD_Y_TILED buffer works, as does a linear one.
Running latest ArchLinux, Mesa f83f9d7daa (master), Weston master, testing with Dolphin on this PR: https://github.com/dolphin-emu/dolphin/pull/7452
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1362Performance issues on Iris 550/Skylake2022-07-28T10:14:36ZBugzilla Migration UserPerformance issues on Iris 550/Skylake## Submitted by Cedric Sodhi
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111558)](https://bugs.freedesktop.org/show_bug.cgi?id=111558)**
## Description
Unfortunally, I don't have much more to report than I...## Submitted by Cedric Sodhi
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111558)](https://bugs.freedesktop.org/show_bug.cgi?id=111558)**
## Description
Unfortunally, I don't have much more to report than I'm seing performance issues under Wayland/Sway. Starting the compositor, spawning a terminal, operating in the terminal, all these actions are significantly (usually a couple of seconds) delayed. No crashes occur and nothing is brought up in dmesg.
Mesa was compiled by portage from master@04.09.2019 with:
meson --buildtype plain --wrap-mode nodownload -Dplatforms=surfaceless,wayland,drm -Dllvm=false -Dlmsensors=false -Dlibunwind=false -Dgallium-nine=false -Dgallium-va=false -Dgallium-vdpau=false -Dgallium-xa=false -Dgallium-xvmc=false -Dgallium-opencl=disabled -Dosmesa=none -Dbuild-tests=false -Dglx=disabled -Dshared-glapi=true -Ddri3=true -Degl=true
-Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=false -Dselinux=false -Dvalgrind=false -Ddri-drivers= -Dgallium-drivers=iris,swrast -Dvulkan-drivers=intel -Dvulkan-overlay-layer=false --buildtype plain -Db_ndebug=true
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1361gdm freezes when using iris driver on Intel HD5202019-12-12T15:26:39ZBugzilla Migration Usergdm freezes when using iris driver on Intel HD520## Submitted by David Heidelberg `@okias`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111535)](https://bugs.freedesktop.org/show_bug.cgi?id=111535)**
## Description
HW: Dell 7350 Intel HD520.
SW: Gentoo, k...## Submitted by David Heidelberg `@okias`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111535)](https://bugs.freedesktop.org/show_bug.cgi?id=111535)**
## Description
HW: Dell 7350 Intel HD520.
SW: Gentoo, kernel 5.2.11, ~amd64, Wayland setup.
When using
MESA_LOADER_DRIVER_OVERRIDE=iris
in /etc/environment, gdm freeze. Only printed lines into logs are:
gnome-shell[932]: meta_drm_buffer_gbm_new failed: drmModeAddFB failed: Nepřípustný argument (translated as Unacceptable argument)
gnome-shell[932]: meta_drm_buffer_gbm_new failed: drmModeAddFB failed: Nepřípustný argument (translated as Unacceptable argument)
I tried compile git mesa with debug, but it didn't get me further.
Feel free to ask me to get specific debugging, can compile mesa/libdrm or kernel with specific patches.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1360[bisected][skl] Graphical corruption in kwin effects2022-06-02T22:36:08ZBugzilla Migration User[bisected][skl] Graphical corruption in kwin effects## Submitted by Mike Lothian `@FireBurn`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111499)](https://bugs.freedesktop.org/show_bug.cgi?id=111499)**
## Description
I've traced it back to:
commit 0f5be81ed...## Submitted by Mike Lothian `@FireBurn`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#111499)](https://bugs.freedesktop.org/show_bug.cgi?id=111499)**
## Description
I've traced it back to:
commit 0f5be81eddfbdcb39a0de10afac2b2ec74790e70
Author: Jordan Justen <jordan.l.justen@intel.com>
Date: Mon Jun 24 19:24:37 2019 -0700
iris: Expose aux buffer as 2nd plane w/modifiers
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
I'm forcing Iris as my main OpenGL driver, i965 isn't compiled and I'm using:
From 49b8c274947d4b625c2a9e0a1fdcb631a73d4903 Mon Sep 17 00:00:00 2001
From: Kenneth Graunke <kenneth@whitecape.org>
Date: Mon, 14 Jan 2019 00:32:33 -0800
Subject: [PATCH] NOT-FOR-UPSTREAM-YET: loader - prefer iris over i965
This lets me avoid having to set MESA_LOADER_DRIVER_OVERRIDE everywhere
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1358[bisected] Steam crashes when newest Iris built with LTO2020-06-28T00:16:30ZBugzilla Migration User[bisected] Steam crashes when newest Iris built with LTO## Submitted by Mike Lothian `@FireBurn`
Assigned to **Mark Janes `@majanes`**
**[Link to original bug (#111376)](https://bugs.freedesktop.org/show_bug.cgi?id=111376)**
## Description
I've bisected back to https://gitlab.freedeskt...## Submitted by Mike Lothian `@FireBurn`
Assigned to **Mark Janes `@majanes`**
**[Link to original bug (#111376)](https://bugs.freedesktop.org/show_bug.cgi?id=111376)**
## Description
I've bisected back to https://gitlab.freedesktop.org/mesa/mesa/commit/0fd4359733e6920d5cac9596eeada753a587a246
I was seeing steam[1804860]: segfault at 0 ip 00000000f6371b97 sp 00000000fff096c0 error 6 in iris_dri.so[f5cf7000+1134000] in my dmesg
Here's the build:
meson --buildtype plain --libdir lib --localstatedir /var/lib --prefix /usr --sysconfdir /etc --wrap-mode nodownload --cross-file /var/tmp/portage/media-libs/mesa-9999/temp/meson.i686-pc-linux-gnu.x86 -Dplatforms=surfaceless,x11,wayland,drm -Dllvm=true -Dlmsensors=true -Dlibunwind=false -Dgallium-nine=true -Dgallium-va=true -Dva-libs-path=/usr/lib/va/drivers -Dgallium-vdpau=true -Dgallium-xa=false -Dgallium-xvmc=false -Dgallium-opencl=disabled -Dglx-read-only-text=false -Dosmesa=none -Dbuild-tests=false -Dglx=dri -Dshared-glapi=true -Ddri3=true -Degl=true -Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=false -Dselinux=false -Dvalgrind=false -Ddri-drivers= -Dgallium-drivers=iris,radeonsi,swrast -Dvulkan-drivers=amd,intel -Dvulkan-overlay-layer=true --buildtype plain -Db_ndebug=true /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999 /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999-abi_x86_32.x86
The Meson build system
Version: 0.51.1
Source dir: /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999
Build dir: /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999-abi_x86_32.x86
Build type: cross build
Program python found: YES (/var/tmp/portage/media-libs/mesa-9999/temp/python3.7/bin/python)
Project name: mesa
Project version: 19.2.0-devel
Appending CFLAGS from environment: '-O3 -march=native -pipe -flto=8'
Appending LDFLAGS from environment: '-O3 -march=native -pipe -flto=8 -Wl,-O2 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--build-id=sha1'
C compiler for the build machine: x86_64-pc-linux-gnu-gcc -m32 (gcc 9.1.0 "x86_64-pc-linux-gnu-gcc (Gentoo 9.1.0-r1 p1.1) 9.1.0")
Appending CXXFLAGS from environment: '-O3 -march=native -pipe -flto=8'
Appending LDFLAGS from environment: '-O3 -march=native -pipe -flto=8 -Wl,-O2 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--build-id=sha1'
C++ compiler for the build machine: x86_64-pc-linux-gnu-g++ -m32 (gcc 9.1.0 "x86_64-pc-linux-gnu-g++ (Gentoo 9.1.0-r1 p1.1) 9.1.0")
C compiler for the host machine: x86_64-pc-linux-gnu-gcc -m32 (gcc 9.1.0 "x86_64-pc-linux-gnu-gcc (Gentoo 9.1.0-r1 p1.1) 9.1
And a backtrace from an unstripped mesa
Thread 1 "steam" received signal SIGSEGV, Segmentation fault.
0xf632d4ad in ralloc_steal () from /usr/lib/dri/iris_dri.so
```
(gdb) bt
#0 0xf632d4ad in ralloc_steal () from /usr/lib/dri/iris_dri.so
#1 0xf63efe93 in steal_memory(ir_instruction*, void*) [clone .lto_priv.0] () from /usr/lib/dri/iris_dri.so
#2 0xf63ee7ca in ir_hierarchical_visitor::visit_enter(ir_function*) () from /usr/lib/dri/iris_dri.so
#3 0xf63ee0b1 in ir_function::accept(ir_hierarchical_visitor*) () from /usr/lib/dri/iris_dri.so
#4 0xf6678787 in _mesa_get_fixed_func_fragment_program () from /usr/lib/dri/iris_dri.so
#5 0xf675c65b in update_program () from /usr/lib/dri/iris_dri.so
#6 0xf6772b2f in _mesa_update_state_locked () from /usr/lib/dri/iris_dri.so
#7 0xf6773237 in _mesa_update_state () from /usr/lib/dri/iris_dri.so
#8 0xf6497467 in _mesa_Clear () from /usr/lib/dri/iris_dri.so
#9 0xed1ae806 in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/vgui2_s.so
#10 0xed1bd4ed in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/vgui2_s.so
#11 0xf054bc6d in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/steamui.so
#12 0xf054bef5 in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/steamui.so
#13 0xf053e28f in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/steamui.so
#14 0xf0491eaa in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/steamui.so
#15 0xf0493c2e in ?? () from /home/fireburn/.local/share/Steam/ubuntu12_32/steamui.so
#16 0x5658e1b0 in RunSteam(int, char**, bool) ()
#17 0x5658f0ab in ?? ()
#18 0x5657a06c in ?? ()
#19 0xf78a5021 in __libc_start_main () from /lib/libc.so.6
#20 0x5657dd29 in _start ()
```
Version: gitMark JanesMark Janeshttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1357[gen9 iris atom] Unigine Heaven gpu hang2022-07-25T10:00:22ZBugzilla Migration User[gen9 iris atom] Unigine Heaven gpu hang## Submitted by Mark Janes `@majanes`
Assigned to **Kenneth Graunke `@kwg`**
**[Link to original bug (#111203)](https://bugs.freedesktop.org/show_bug.cgi?id=111203)**
## Description
Created attachment 144859
card0 error from bxt H...## Submitted by Mark Janes `@majanes`
Assigned to **Kenneth Graunke `@kwg`**
**[Link to original bug (#111203)](https://bugs.freedesktop.org/show_bug.cgi?id=111203)**
## Description
Created attachment 144859
card0 error from bxt HD505
Running unigine heaven on BXT with iris generates gpu hang after about a minute. Bisected to:
dcfca0af7c5c2938d01abd7374b57ab242715508
Author: Kenneth Graunke <kenneth@whitecape.org>
iris: Set XY Clipping correctly.
I was setting it based off a pipe_rasterizer_state field that appears
to be entirely dead outside of the draw module respecting it.
I should be setting it when the primitive type reaching the SF is
neither points nor lines. This is, unfortunately, rather dirty,
as we have to look at the rasterizer state, the geometry shader state,
the tessellation evaluation shader state, and the primitive type...
**Attachment 144859**, "card0 error from bxt HD505":
[error.txt](/uploads/19de575e9001e65741e213fe0e4da348/error.txt)
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=103556Kenneth Graunkekenneth@whitecape.orgKenneth Graunkekenneth@whitecape.orghttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1356[regression][bisected] KHR-GL46.shader_subroutine.control_flow_and_returned_s...2020-12-28T12:36:17ZBugzilla Migration User[regression][bisected] KHR-GL46.shader_subroutine.control_flow_and_returned_subroutine_values_used_as_subroutine_input XFBed invalid data failure## Submitted by clayton craft `@craftyguy`
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#110518)](https://bugs.freedesktop.org/show_bug.cgi?id=110518)**
## Description
XFBed data was found to be invalid at ...## Submitted by clayton craft `@craftyguy`
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#110518)](https://bugs.freedesktop.org/show_bug.cgi?id=110518)**
## Description
XFBed data was found to be invalid at index [0]for the following subroutine location configuration: bool_operator1_subroutine_location:[1] bool_operator2_subroutine_location:[0] vec4_operator1_subroutine_location:[2] vec4_operator2_subroutine_location:[2]; expected data:1, found:2
XFBed data was found to be invalid at index [1]for the following subroutine location configuration: bool_operator1_subroutine_location:[1] bool_operator2_subroutine_location:[0] vec4_operator1_subroutine_location:[2] vec4_operator2_subroutine_location:[2]; expected data:0.888889, found:8
Full output from test can be found here:
http://mesa-ci.01.org/mesa_master_daily/builds/4945/results/601015467
This has been bisected to the following commit:
commit 03a72d96d8dacc32e817089b94bec08ac70b898b
Author: Jason Ekstrand <jason@jlekstrand.net>
Date: Fri Mar 29 22:51:20 2019 -0500
nir/algebraic: Drop some @bool specifiers
Version: git19.3 Release TrackerFaith EkstrandFaith Ekstrandhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1355Steam client has graphical glitches2019-10-07T13:43:34ZBugzilla Migration UserSteam client has graphical glitches## Submitted by leo..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110502)](https://bugs.freedesktop.org/show_bug.cgi?id=110502)**
## Description
The Steam client has graphical bugs, mainly on the ...## Submitted by leo..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110502)](https://bugs.freedesktop.org/show_bug.cgi?id=110502)**
## Description
The Steam client has graphical bugs, mainly on the window borders. While they are minor and does not seem to affect the usability, they are very noticeable. The image from https://i.imgur.com/6eNstFa.png shows the problem on window borders.
Processor: Intel Core i3-6100U;
Video: Intel HD Graphics 520;
Architecture: amd64;
Mesa: 19.1.0-devel (git-21223acf7d);
Kernel version: 4.18.0-17-lowlatency;
Distribution: Xubuntu 18.04.2 amd64.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1354[Runelite GPU plugin] Enabling GPU plugin produces incorrect rendering2021-01-14T17:12:39ZBugzilla Migration User[Runelite GPU plugin] Enabling GPU plugin produces incorrect rendering## Submitted by MIka R
Assigned to **Default DRI bug account**
**[Link to original bug (#109370)](https://bugs.freedesktop.org/show_bug.cgi?id=109370)**
## Description
Created attachment 143135
Garbled polygons and some missing te...## Submitted by MIka R
Assigned to **Default DRI bug account**
**[Link to original bug (#109370)](https://bugs.freedesktop.org/show_bug.cgi?id=109370)**
## Description
Created attachment 143135
Garbled polygons and some missing texture with GPU plugin enabled
More info https://github.com/runelite/runelite/issues/6841
**Attachment 143135**, "Garbled polygons and some missing texture with GPU plugin enabled":
![runelitescreen](/uploads/53b031e431e07e415547b12bbba79ca6/runelitescreen.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1353Luxmark freezes the system2022-11-03T09:08:10ZBugzilla Migration UserLuxmark freezes the system## Submitted by Fabian Maurer
Assigned to **Default DRI bug account**
**[Link to original bug (#109329)](https://bugs.freedesktop.org/show_bug.cgi?id=109329)**
## Description
Created attachment 143077
journalctl log
Running luxma...## Submitted by Fabian Maurer
Assigned to **Default DRI bug account**
**[Link to original bug (#109329)](https://bugs.freedesktop.org/show_bug.cgi?id=109329)**
## Description
Created attachment 143077
journalctl log
Running luxmark (OpenCL) freezes the system.
Only help is to reboot with REISUB command.
dmesg log (from journalctl) attached.
System:
-Arch Linux
-AMD Radeon 285
-AMD Radeon R9 200 Series (TONGA, DRM 3.27.0, 4.20.1-arch1-1-ARCH, LLVM 7.0.0)
-Mesa 18.3.1
**Attachment 143077**, "journalctl log":
[file_109329.txt](/uploads/aa363ead12cd7314b34eabf65a838528/file_109329.txt)
Version: 18.3
### Blocking
* [Bug 99553](https://bugs.freedesktop.org/show_bug.cgi?id=99553)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1352AMD RX 570: Hard reset when playing games2021-02-23T22:07:38ZBugzilla Migration UserAMD RX 570: Hard reset when playing games## Submitted by nol..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#109297)](https://bugs.freedesktop.org/show_bug.cgi?id=109297)**
## Description
I have hard resets, similar to hitting the Reset-Butto...## Submitted by nol..@..il.com
Assigned to **Default DRI bug account**
**[Link to original bug (#109297)](https://bugs.freedesktop.org/show_bug.cgi?id=109297)**
## Description
I have hard resets, similar to hitting the Reset-Button. Which means I get no log or trace of any kind and I am totally clueless where/how to search.
I replaced a Geforce 770 with a MSI RX 570 in the hope of better support for a multi-monitor setup. Turns aut the Card will expose the above issue when gaming (so far played only X-Com2).
xserver-xorg-video-amdgpu is version 18.1.0,
kernel is 4.19.0-1-amd64 (had same issue with 4.18)
- The PSU is a Seasonic Platinum 400 Fanless, more than enough to drive the card and the max ~100W Cpu.
I replaced a Geforce 770, which should have a higher peak without issues.
- Xcom2 crashes after ~5 to 30minutes. I can play longer if I
limit the card to 80 W.
echo 80000000 > /sys/class/drm/card0/device/hwmon/hwmon2/power1_cap
- The system does not cause any troubles with Windows 10,
even if both CPU and GPU are tortured.
- I did sample the temperature berofe the crash, it was below 70degrees GPU and below 60 on GPU. (far from any BIOS triggers)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1351Driver did not suport 8706G Readon PRO WX Vega M in Precision 5530 2-in-12021-01-14T17:26:36ZBugzilla Migration UserDriver did not suport 8706G Readon PRO WX Vega M in Precision 5530 2-in-1## Submitted by Dimitar Atanasov
Assigned to **Default DRI bug account**
**[Link to original bug (#109115)](https://bugs.freedesktop.org/show_bug.cgi?id=109115)**
## Description
lspci
01:00.0 Display controller: Advanced Micro De...## Submitted by Dimitar Atanasov
Assigned to **Default DRI bug account**
**[Link to original bug (#109115)](https://bugs.freedesktop.org/show_bug.cgi?id=109115)**
## Description
lspci
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 694f (rev c0)
last supported ID in driver for Polaris 12 is 694E. I don't know it this is specific to this Dell model is in common.
lshw -C video
*-display UNCLAIMED
description: Display controller
product: Advanced Micro Devices, Inc. [AMD/ATI]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:01:00.0
version: c0
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
configuration: latency=0
resources: memory:a0000000-afffffff memory:b0000000-b01fffff ioport:e000(size=256) memory:ec300000-ec33ffff memory:ec340000-ec35ffff
*-display
description: VGA compatible controller
product: HD Graphics 630
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: iomemory:2f0-2ef irq:133 memory:eb000000-ebffffff memory:2fa0000000-2fafffffff ioport:f000(size=64) memory:c0000-dffffhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1349[amdgpu] [apitrace] Penumbra Overture crash in radeonsi_dri.so on RX5802021-09-09T14:37:35ZBugzilla Migration User[amdgpu] [apitrace] Penumbra Overture crash in radeonsi_dri.so on RX580## Submitted by Henri Valta
Assigned to **Default DRI bug account**
**[Link to original bug (#109048)](https://bugs.freedesktop.org/show_bug.cgi?id=109048)**
## Description
Created attachment 142799
Coredump info
Penumbra Overtur...## Submitted by Henri Valta
Assigned to **Default DRI bug account**
**[Link to original bug (#109048)](https://bugs.freedesktop.org/show_bug.cgi?id=109048)**
## Description
Created attachment 142799
Coredump info
Penumbra Overture game from Steam crashes reliably when trying to detonate the TNT barrel.
The crash seems to happen in radeonsi_dri.so
Stack trace of thread 16178:
#0 0x00000000f44d5dc1 amdgpu_bo_map (radeonsi_dri.so)
#1 0x00000000f448a874 si_texture_transfer_map (radeonsi_dri.so)
#2 0x00000000f4ae24b1 tc_transfer_map (radeonsi_dri.so)
#3 0x00000000f46ee64b pipe_transfer_map_3d (radeonsi_dri.so)
#4 0x00000000f46dfb48 st_MapTextureImage (radeonsi_dri.so)
#5 0x00000000f46b3c85 store_texsubimage (radeonsi_dri.so)
#6 0x00000000f46e2aca st_TexSubImage (radeonsi_dri.so)
#7 0x00000000f46e4650 st_TexImage (radeonsi_dri.so)
#8 0x00000000f46a7085 teximage (radeonsi_dri.so)
#9 0x00000000f46a8a78 _mesa_TexImage1D (radeonsi_dri.so)
#10 0x00000000f7d44236 glTexImage1D (glxtrace.so)
System specification:
AMD Ryzen 7 2700X
MSI X470 Gaming Pro/latest bios
MSI RX580 Armor 8G (1d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/57$
Arch linux 64 bit, but the game is 32 bit
Kernel 4.19.8-arch1-1-ARCH
Mesa 18.3.1-1
**Attachment 142799**, "Coredump info":
[coredump_info.txt](/uploads/734f7d59dd658e3f26895b7d6db3bd0f/coredump_info.txt)
Version: 18.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1348ring gfx timeout during particular shader generation on yuzu emulator2020-09-25T10:15:56ZBugzilla Migration Userring gfx timeout during particular shader generation on yuzu emulator## Submitted by e88z4
Assigned to **Default DRI bug account**
**[Link to original bug (#109022)](https://bugs.freedesktop.org/show_bug.cgi?id=109022)**
## Description
How to reproduce the issue?
1. Using yuzu emualtor latest canar...## Submitted by e88z4
Assigned to **Default DRI bug account**
**[Link to original bug (#109022)](https://bugs.freedesktop.org/show_bug.cgi?id=109022)**
## Description
How to reproduce the issue?
1. Using yuzu emualtor latest canary build.
2. Load Super Mario Odyssey.
3. Create a new game.
4. Wait until Mario jumps for the first time after being woken up by Cappy.
5. Graphic crashes but system is still accessible through SSH
Error message:
[ 540.189992] amdgpu 0000:23:00.0: GPU fault detected: 147 0x09088402 for process glretrace pid 2006 thread glretrace:cs0 pid 2007
[ 540.190000] amdgpu 0000:23:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00001121
[ 540.190004] amdgpu 0000:23:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E084002
[ 540.190010] amdgpu 0000:23:00.0: VM fault (0x02, vmid 7, pasid 32771) at page 4385, read from 'TC7' (0x54433700) (132)
[ 550.275970] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=20845, emitted seq=20848
System specification:
AMD Ryzen 5 2600
ASRock B540M with latest bios update
16 GB DDR4 RAM
MSI RX580 Gaming X
Debian Sid
Kernel 4.20-rc6
Mesa 18.3.1
This bug occurs in all combinations of kernel 4.17, 4.18, 4.19, 4.20, drm-next-4.2.1-wip with mesa 18.2, 18.3, 19.0-development
I am able to get the apitrace result. It can be downloaded from my google drive.
https://drive.google.com/file/d/1MdR1c2g0pQ8ToTCAH53Jc9BUd3WFzbcg/view?usp=sharing
The bug can be easily reproduced by replaying the apitrace result very consistently.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1347Visual Novel "The Fruit of Grisaia" has flickering glitches2022-11-23T22:13:47ZBugzilla Migration UserVisual Novel "The Fruit of Grisaia" has flickering glitches## Submitted by Fabian Maurer
Assigned to **Default DRI bug account**
**[Link to original bug (#108985)](https://bugs.freedesktop.org/show_bug.cgi?id=108985)**
## Description
Created attachment 142757
Screenshot showing a glitch
...## Submitted by Fabian Maurer
Assigned to **Default DRI bug account**
**[Link to original bug (#108985)](https://bugs.freedesktop.org/show_bug.cgi?id=108985)**
## Description
Created attachment 142757
Screenshot showing a glitch
This is a bug about a game run in wine. I've already submitted a wine bug, but after a lot of testing I assume it's more likely a mesa bug.
When played, the game as flickering/glitches where sometimes an old scene is partially shown over the current scene.
What I found out so far:
- apitrace always plays back perfectly fine
- "LIBGL_ALWAYS_SOFTWARE=1 wine grisaia" makes the issue disappear.
- slowing wine down with "WINEDEBUG=+relay" log spam makes the issue disappear
- "vblank_mode=0" makes the issue disappear (when not in fullscreen)
- LIBGL_DRI3_DISABLE=1 makes the issue go away
- usage of gallium nine makes the issue disappear
As I said, not sure where the fault is, but I can provide more information if needed.
There's also a demo if you want to reproduce yourself: http://suezou.dyndns.org/dl2010/frontwing/gurizaia/Grisaia_trial_web.zip (700MB and might take a while to download)
Guide to test:
0) Get the demo
1) Click through the installation. It installs to "C:\frontwing\SomeJapaneseFolder"
2) run wine "Grisaia", it opens a dialog where you should click the right option (windowed mode)
3) in the main menu click the first option, and then any of the scenes you can select.
4) Press left-ctrl to fast-forward or the mouse to advance
5) 5) Screen tearing is pretty obvious (see attachments)
System the bug was tested on:
- Arch Linux 64bit
- Linux 4.19.08, AMDGPU driver
- Mesa 17.2.0-devel (git-ccf9669cc1) / Mesa 17.0.5
- Radeon R9 285
- KDE Plasma 5 with OpenGL compositor and regular X session
**Attachment 142757**, "Screenshot showing a glitch":
![1](/uploads/2828874130b87484c96d34b755052d6a/1.png)
Version: 18.3
### See also
* https://bugs.winehq.org/show_bug.cgi?id=45168https://gitlab.freedesktop.org/mesa/mesa/-/issues/1346Graphical glitch of popupping missing texture on Mesa version >18.0.5 (Padoka...2021-03-11T22:52:05ZBugzilla Migration UserGraphical glitch of popupping missing texture on Mesa version >18.0.5 (Padoka Stable + Unstable/Oibaf/ubuntu-x-swat PPAs)## Submitted by emm..@..il.org
Assigned to **Default DRI bug account**
**[Link to original bug (#108979)](https://bugs.freedesktop.org/show_bug.cgi?id=108979)**
## Description
Trying to upgrade to a more updated Mesa version from ...## Submitted by emm..@..il.org
Assigned to **Default DRI bug account**
**[Link to original bug (#108979)](https://bugs.freedesktop.org/show_bug.cgi?id=108979)**
## Description
Trying to upgrade to a more updated Mesa version from the Mesa 18.0.5 shipped with Ubuntu 18.04.1 as suggested by SCS Software Customer Support to resolve framerate issue on Euro Truck Simulator 2 happened after the 1.33 update of the game (that haven't resolved), I experience graphical glitch of missing texture that appear randomly as popup on every game, not only on ETS2.
I have tried all the PPAs quoted on the summary, but only the 18.0.5 doesn't have this issue.
I will attach a video recording the issue for better comprehension of the bug playing two games to show is not limited to only one game