mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2022-06-02T21:05:59Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1812[Intel GFX CI] spec@glsl-1.50@execution@texelfetchoffset@gs-sampler2drect - fail2022-06-02T21:05:59ZBugzilla Migration User[Intel GFX CI] spec@glsl-1.50@execution@texelfetchoffset@gs-sampler2drect - fail## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110685)](https://bugs.freedesktop.org/show_bug.cgi?id=110685)**
## Description
https://intel-gfx-ci.01.org/tree/drm-tip/CI_...## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110685)](https://bugs.freedesktop.org/show_bug.cgi?id=110685)**
## Description
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6085/pig-snb-2600/spec@glsl-1.50@execution@texelfetchoffset@gs-sampler2drect.html
Time
0.12 seconds
Out
65x32x1
Probe at (0,30)
Expected: -0.000000 0.967742 0.000000 0.000000
Observed: 0.098039 0.098039 0.098039 1.000000
Environment
PIGLIT_SOURCE_DIR="/opt/igt/piglit" PIGLIT_PLATFORM="gbm"
Command
/opt/igt/piglit/bin/texelFetch offset 140 gs sampler2DRect -auto -fbo
Full piglit results: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6085/pig-snb-2600/results0.json.bz2
Version: 18.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1811i965 miptree tiled_memcpy code uses MAP_RAW without error checks2019-09-25T20:33:18ZBugzilla Migration Useri965 miptree tiled_memcpy code uses MAP_RAW without error checks## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110670)](https://bugs.freedesktop.org/show_bug.cgi?id=110670)**
## Description
Created attachment 144244
Simple workaround/hack to ...## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110670)](https://bugs.freedesktop.org/show_bug.cgi?id=110670)**
## Description
Created attachment 144244
Simple workaround/hack to avoid tiled_memcpy without MMAP_WC
The i965 miptree tiled_memcpy mode, added in 54c823ec790427acbea31212a6ed30a17bd25ff0 ("i965/miptree: Use cpu tiling/detiling when mapping"), calls intel_miptree_map_raw(,,MAP_RAW) from intel_miptree_map_tiled_memcpy() and intel_miptree_unmap_tiled_memcpy(), and does not check return value.
This causes invalid pointer dereferences if the call fails, causing a segfault.
In my case the call fails because pre-4.0 kernel versions do not support I915_MMAP_WC so brw_bo_map_wc() fails (like in bug #110602), but I guess there may be a number of other failure cases where the mmap request may fail.
The code in intel_miptree_map() should select another mapping mode if tiled_memcpy mode is not possible due to missing I915_MMAP_WC. Attached is a quick workaround that avoids the mapping mode in my case.
There seem to be several other non-checked intel_miptree_map_raw() calls in intel_mipmap_tree.c (and several checked ones), but they do not add MAP_RAW flag so they did not fail for me. But maybe error checks should still be added to those as well in case of other failure reasons?
This was observed on a ValleyView Gen7 (8086:0f31) with kernel 3.10.35 with the attached small Qt program with Qt 5.11.2.
**Patch 144244**, "Simple workaround/hack to avoid tiled_memcpy without MMAP_WC":
[i965-tiled_memcpy-workaround.patch](/uploads/911802fc9de9692f8a15a22c5d49edde/i965-tiled_memcpy-workaround.patch)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1810i965 miptree MCS aux_buf allocation failure with old kernels2019-09-25T20:33:13ZBugzilla Migration Useri965 miptree MCS aux_buf allocation failure with old kernels## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110602)](https://bugs.freedesktop.org/show_bug.cgi?id=110602)**
## Description
Created attachment 144147
glxinfo
intel_miptree_cho...## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110602)](https://bugs.freedesktop.org/show_bug.cgi?id=110602)**
## Description
Created attachment 144147
glxinfo
intel_miptree_choose_aux_usage() selects ISL_AUX_USAGE_MCS if intel_miptree_supports_mcs() returns true.
This will cause callchain intel_miptree_alloc_aux() => intel_alloc_aux_buffer() => brw_bo_map(x,y,MAP_RAW|MAP_WRITE) => brw_bo_map_wc(), which checks bufmgr->has_mmap_wc and returns NULL on !bufmgr->has_mmap_wc. There is no fallback in brw_bo_map() for the MAP_RAW case.
This will cause intel_miptree_create() to fail which causes intel_miptree_create_for_renderbuffer() to fail.
I guess either either the miptree creation should be retried without MCS or intel_miptree_supports_mcs() should detect the missing mmap_wc support and return false.
Attached is a quick hack patch that adds mmap_wc check in intel_miptree_supports_mcs(), and it seems to fix the testcase I used (mesa-issue-qt3d.cc).
Without the patch the testcase either crashes (git master) or flashes rapidly (git master + two patches from bug #110601 to workaround the crashes).
The testcase mesa-issue-qt3d.cc is also attached, plus an apitrace and glxinfo with git master.
This was tested on a ValleyView Gen7 (8086:0f31) with kernel 3.10.35.
**Attachment 144147**, "glxinfo":
[glxinfo.txt](/uploads/669419da7a6a4b5ae70a95179dbb946b/glxinfo.txt)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1809i965 renderbuffer miptree creation failure not properly handled2019-09-25T20:33:09ZBugzilla Migration Useri965 renderbuffer miptree creation failure not properly handled## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110601)](https://bugs.freedesktop.org/show_bug.cgi?id=110601)**
## Description
Created attachment 144142
Fix for issue (1), singles...## Submitted by Anssi Hannula
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110601)](https://bugs.freedesktop.org/show_bug.cgi?id=110601)**
## Description
Created attachment 144142
Fix for issue (1), singlesample_mt use after free
In src/mesa/drivers/dri/i965/intel_mipmap_tree.c intel_update_winsys_renderbuffer_miptree() the intel_miptree_create_for_renderbuffer() call can fail and the function is prepared for it.
However, there are several issues with the error handling:
(1) On failure exit from intel_update_winsys_renderbuffer_miptree(), the singlesample_mt received via parameter remains assigned to irb->singlesample_mt. However, in both callsites (brw_context.c intel_process_dri2_buffer() and intel_update_image_buffer()) the miptree is released on failure. This will lead to use-after-free and undefined behavior, including crashes.
Either singlesample_mt should be NULLed or it should not be freed by caller.
I have no idea which one would be correct, but I've attached a patch that does the former that seems to fix the use-after-free issues.
(2) On failure exit from intel_update_winsys_renderbuffer_miptree(), irb->mt remains NULL. However, many functions seem to assume that irb->mt is non-null:
(I) do_single_blorp_clear()
(II) brw_postdraw_set_buffers_need_resolve()
(III) update_renderbuffer_surfaces()
There are probably more, but those are the ones I saw crashes in with the test code.
An example callpath for (I) above is:
brw_clear()
=> intel_prepare_render()
=> intel_update_renderbuffers()
=> intel_process_dri2_buffer()
=> intel_update_winsys_renderbuffer_miptree()
=> fails, irb->mt = NULL
=> brw_blorp_clear_color()
=> do_single_blorp_clear()
=> dereferences irb->mt, segfault
Attached is a hack patch that adds NULL checks to some places, but I imagine a better way would be to somehow remove the renderbuffer altogether or something to avoid having to add mt NULL checks everywhere...
I will open a separate issue for the failure in intel_miptree_create_for_renderbuffer() that triggers this, but I think the error handling should be fixed regardless of the failure reason - at least so that there are no crashes.
I've attached the test application I used as mesa-issue-qt3d.cc. With the patches I still don't see correct graphical output with it (I see the red line as expected but the picture flashes rapidly), but I guess it may be expected with the miptree creation failure - I do see correct output after making miptree creation work.
Also included is an apitrace and glxinfo with mesa master without any patches.
This was tested on a ValleyView Gen7 (8086:0f31) with kernel 3.10.35, git master mesa (2019-05-02). AFAICS the issues can happen with any HW/kernel as long as intel_update_winsys_renderbuffer_miptree() manages to fail.
**Attachment 144142**, "Fix for issue (1), singlesample_mt use after free":
[0001-i965-fix-singlesample_mt-use-after-free.patch](/uploads/6fbe2959a5d68746dfd6a3df6a6d9854/0001-i965-fix-singlesample_mt-use-after-free.patch)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1808Test fails: piglit.spec.ext_packed_float.query-rgba-signed-components2019-09-25T20:33:07ZBugzilla Migration UserTest fails: piglit.spec.ext_packed_float.query-rgba-signed-components## Submitted by Andrii K
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110460)](https://bugs.freedesktop.org/show_bug.cgi?id=110460)**
## Description
Test fails with i965 and passes successfully with Iris.
...## Submitted by Andrii K
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110460)](https://bugs.freedesktop.org/show_bug.cgi?id=110460)**
## Description
Test fails with i965 and passes successfully with Iris.
Test output:
Testing window
Testing GL_RGBA8
Testing GL_R8I
Testing GL_RG8I
Testing GL_R8_SNORM
Testing GL_LUMINANCE8_SNORM
Expected: (1, 1, 1, 0)
Actual: (1, 1, 1, 1)
Testing GL_RGBA8UI
Testing GL_RGBA16F
Testing GL_LUMINANCE16F_ARB
Skipping GL_RGB9_E5: framebuffer not complete
Testing GL_R11F_G11F_B10F
Testing GL_RGBA16F
PIGLIT: {"result": "fail" }https://gitlab.freedesktop.org/mesa/mesa/-/issues/1807[skl] GPU HANG: ecode 9:0:0x85dfffff, in Xorg2022-06-02T22:06:59ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dfffff, in Xorg## Submitted by Jintao Zhang
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110444)](https://bugs.freedesktop.org/show_bug.cgi?id=110444)**
## Description
dmesg output.
```
[ 7003.791337] [drm] GPU HANG: ec...## Submitted by Jintao Zhang
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110444)](https://bugs.freedesktop.org/show_bug.cgi?id=110444)**
## Description
dmesg output.
```
[ 7003.791337] [drm] GPU HANG: ecode 9:0:0x85dfffff, in Xorg [2519], reason: hang on rcs0, action: reset
[ 7003.791342] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 7003.791343] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 7003.791345] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 7003.791347] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 7003.791349] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 7003.792423] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 7011.770307] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 7019.770262] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 7027.770144] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 7035.770234] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 7036.084359] show_signal_msg: 65 callbacks suppressed
[ 7036.084361] electron[12234]: segfault at 968 ip 00007fab9c84d677 sp 00007ffeec2a8920 error 4 in libX11.so.6.3.0[7fab9c81f000+13a000]
```
(MoeLove) ➜ ~ lspci -nn |grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(MoeLove) ➜ ~ uname -rm
5.0.7-100.fc28.x86_64 x86_64
(MoeLove) ➜ ~ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 28 (Twenty Eight)
Release: 28
Codename: TwentyEight
(MoeLove) ➜ ~ rpm -qa |grep -i xorg
xorg-x11-drv-wacom-0.36.1-4.fc28.x86_64
xorg-x11-drv-nouveau-1.0.15-4.fc28.x86_64
xorg-x11-drv-libinput-0.28.1-1.fc28.x86_64
xorg-x11-font-utils-7.5-38.fc28.x86_64
xorg-x11-drv-openchrome-0.6.0-4.fc28.x86_64
xorg-x11-server-utils-7.7-24.fc28.x86_64
xorg-x11-server-common-1.19.6-10.fc28.x86_64
xorg-x11-drv-vesa-2.4.0-2.fc28.x86_64
abrt-addon-xorg-2.10.10-1.fc28.x86_64
xorg-x11-server-Xwayland-1.19.6-10.fc28.x86_64
xorg-x11-drv-fbdev-0.4.3-29.fc28.x86_64
xorg-x11-drv-wacom-serial-support-0.36.1-4.fc28.x86_64
xorg-x11-xauth-1.0.9-11.fc28.x86_64
xorg-x11-drv-qxl-0.1.5-6.fc28.x86_64
xorg-x11-drv-vmware-13.2.1-5.fc28.x86_64
xorg-x11-fonts-ISO8859-1-100dpi-7.5-19.fc28.noarch
xorg-x11-drv-evdev-2.10.6-2.fc28.x86_64
xorg-x11-server-Xorg-1.19.6-10.fc28.x86_64
xorg-x11-fonts-Type1-7.5-19.fc28.noarch
xorg-x11-xkb-utils-7.7-26.fc28.x86_64
xorg-x11-drv-ati-18.1.0-1.fc28.x86_64
xorg-x11-fonts-misc-7.5-19.fc28.noarch
xorg-x11-utils-7.5-28.fc28.x86_64
xorg-x11-drv-intel-2.99.917-32.20171025.fc28.x86_64
xorg-x11-xinit-1.3.4-18.fc28.x86_64
Mcachine: HP ProBook 430G3 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHzhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1806Rendering artifacts created by long switch statement2019-09-25T20:32:58ZBugzilla Migration UserRendering artifacts created by long switch statement## Submitted by Clive McCarthy
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110424)](https://bugs.freedesktop.org/show_bug.cgi?id=110424)**
## Description
Mesa 19.1.0-devel (git b46b661) from Oibaf grabs ar...## Submitted by Clive McCarthy
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110424)](https://bugs.freedesktop.org/show_bug.cgi?id=110424)**
## Description
Mesa 19.1.0-devel (git b46b661) from Oibaf grabs around 1GB of system memory when my application starts. When using Mesa 18.2.8 with the same application and same code, this does not happen.
Hardware: Intel Iris Graphics 655 GT3e (Coffeelake 3x8 GT3)
Linux Mint Kernel 4.15
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1805GPU HANG: ecode 5:0:0xfcefffdf, in chromium [2715], reason: hang on rcs0, act...2022-06-02T22:07:19ZBugzilla Migration UserGPU HANG: ecode 5:0:0xfcefffdf, in chromium [2715], reason: hang on rcs0, action: reset## Submitted by Mike Kuznetsov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110330)](https://bugs.freedesktop.org/show_bug.cgi?id=110330)**
## Description
Created attachment 143873
/sys/class/drm/card0/erro...## Submitted by Mike Kuznetsov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110330)](https://bugs.freedesktop.org/show_bug.cgi?id=110330)**
## Description
Created attachment 143873
/sys/class/drm/card0/error
After opening page with 20+ images in Chromium GPU freezes
/sys/class/drm/card0/error is attached
mike ~$ dmesg | tail
[288438.590783] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288446.586620] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288454.590794] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288462.586720] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288470.586669] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288478.586768] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288486.586821] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288496.570617] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288506.586681] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288514.586677] i915 0000:00:02.0: Resetting chip for hang on rcs0
[288522.586699] i915 0000:00:02.0: Resetting chip for hang on rcs0
mike ~$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Ironlake Mobile (0x46)
Version: 19.0.1
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Mobile
OpenGL version string: 2.1 Mesa 19.0.1
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 19.0.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
mike ~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu Disco Dingo (development branch)"
mike ~$ uname -a
Linux delorean 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
**Attachment 143873**, "/sys/class/drm/card0/error":
[sys_class_drm_card0_error](/uploads/707d5b22bcc1673e17e942032657271f/sys_class_drm_card0_error)
Version: 19.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1804[i965gm] hang in systemd-logind (probably gdm)2022-06-02T23:15:11ZBugzilla Migration User[i965gm] hang in systemd-logind (probably gdm)## Submitted by Filip Bartmann
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110316)](https://bugs.freedesktop.org/show_bug.cgi?id=110316)**
## Description
Created attachment 143852
/sys/class/drm/card0/erro...## Submitted by Filip Bartmann
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110316)](https://bugs.freedesktop.org/show_bug.cgi?id=110316)**
## Description
Created attachment 143852
/sys/class/drm/card0/error dump
When graphics is started, then graphics hangs with message:
--------------------------------------------------------------
[ 65.058293] [drm] GPU HANG: ecode 4:0:0x8645d83f, in systemd-logind [617], reason: hang on rcs0, action: reset
[ 65.058297] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 65.058299] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 65.058300] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 65.058301] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 65.058303] [drm] GPU crash dump saved to /sys/class/drm/card0/error
--------------------------------------------------------------
**Attachment 143852**, "/sys/class/drm/card0/error dump":
[card.txt](/uploads/fb1a129657a471d92332a168c9559d10/card.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1803[i915/hsw] Tropico 6 causes GPU hang2019-09-25T20:32:47ZBugzilla Migration User[i915/hsw] Tropico 6 causes GPU hang## Submitted by Manuel Lauss
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110315)](https://bugs.freedesktop.org/show_bug.cgi?id=110315)**
## Description
Created attachment 143851
GPU crash dump file
The ga...## Submitted by Manuel Lauss
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110315)](https://bugs.freedesktop.org/show_bug.cgi?id=110315)**
## Description
Created attachment 143851
GPU crash dump file
The game Tropico 6 (UE4 4.20-based) causes a GPU hang:
[237980.961658] [drm] GPU HANG: ecode 7:0:0x87d5aef8, in Tropico6-Linux- [105317], reason: hang on rcs0, action: reset
[237980.961660] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[237980.961661] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[237980.961661] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[237980.961661] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[237980.961662] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[237980.961698] i915 0000:00:02.0: Resetting chip for hang on rcs0
[237988.909135] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238002.775684] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238012.802223] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238016.855426] Asynchronous wait on fence i915:rcs0:ede19 timed out (hint:intel_atomic_commit_ready+0x0/0x50)
[238020.908796] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238030.721946] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238038.828601] i915 0000:00:02.0: Resetting chip for hang on rcs0
[238046.725141] i915 0000:00:02.0: Resetting chip for hang on rcs0
The game mostly works, but it has a lot of triangles blinking.
Linux-5.0.5, mesa git @ 43db0632e7dea4339bbfc05caf9f5165ee8329a2
Thanks!
**Attachment 143851**, "GPU crash dump file":
[gpuerror.txt](/uploads/bc3abced0efe3d587c46b02d37da0216/gpuerror.txt)
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=111631https://gitlab.freedesktop.org/mesa/mesa/-/issues/1802[SNB] Test fails piglit.spec.arb_framebuffer_object.fbo-attachments-blit-scal...2019-09-25T20:32:44ZBugzilla Migration User[SNB] Test fails piglit.spec.arb_framebuffer_object.fbo-attachments-blit-scaled-linear## Submitted by Sergii Romantsov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110282)](https://bugs.freedesktop.org/show_bug.cgi?id=110282)**
## Description
Version: git## Submitted by Sergii Romantsov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110282)](https://bugs.freedesktop.org/show_bug.cgi?id=110282)**
## Description
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1801[skl] GPU hang in sway, unknown cause2022-06-02T22:07:39ZBugzilla Migration User[skl] GPU hang in sway, unknown cause## Submitted by Jeff Peeler
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110135)](https://bugs.freedesktop.org/show_bug.cgi?id=110135)**
## Description
Created attachment 143685
crash dump output
[21763.26...## Submitted by Jeff Peeler
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110135)](https://bugs.freedesktop.org/show_bug.cgi?id=110135)**
## Description
Created attachment 143685
crash dump output
[21763.262354] [drm] GPU HANG: ecode 9:0:0x86cdffff, in sway [26607], reason: hang on rcs0, action: reset
[21763.262356] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[21763.262356] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[21763.262357] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[21763.262357] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[21763.262358] [drm] GPU crash dump saved to /sys/class/drm/card1/error
[21763.263378] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
**Attachment 143685**, "crash dump output":
[drm-crash-dump.log.bz2](/uploads/f3d27ebd7a49102a782c05e244885d16/drm-crash-dump.log.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1800[i915 CI][SNB] spec@glsl-1.30@execution@tex-miplevel-selection texture(bias) ...2019-12-27T11:50:31ZBugzilla Migration User[i915 CI][SNB] spec@glsl-1.30@execution@tex-miplevel-selection texture(bias) 2d - fail## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110112)](https://bugs.freedesktop.org/show_bug.cgi?id=110112)**
## Description
After updating mesa from 18.0.5 to 18.2.2, t...## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110112)](https://bugs.freedesktop.org/show_bug.cgi?id=110112)**
## Description
After updating mesa from 18.0.5 to 18.2.2, the test "spec@glsl-1.30@execution@tex-miplevel-selection texture(bias) 2d" started failing consistently on our pig-snb-2600 machine (https://intel-gfx-ci.01.org/hardware.html#pig-snb-2600).
The piglit version is a little old though: fdc5a4ca11124ab8413c7988896eec4c97336694
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 0, maxlod: 5, bias: 5, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 0, maxlod: 5, bias: 5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -5, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -4, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -4, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -3, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -3, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -2, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -2, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -1, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: -1, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 0, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 0, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 1, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 1, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 2, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 2, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 3, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 3, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 4, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 4, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 5, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 1, bias: 5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -5, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -4, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -4, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -3, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -3, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -2, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -2, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -1, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: -1, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 0, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 0, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 1, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 1, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 2, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 2, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 3, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 3, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 4, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 4, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 5, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 2, bias: 5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -5, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -5, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -4, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -4, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -3, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -3, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -2, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -2, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -1, mipfilter: no
Failure:
Expected level: 3
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: -1, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: 0, mipfilter: no
Failure:
Expected level: 4
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: 0, mipfilter: yes
Failure:
Expected level: 2
Observed: unknown value (broken driver?)
Fetch level: 4, baselevel: 2, maxlevel: 4, minlod: 1, maxlod: 3, bias: 1, mipfilter: no
Summary: 58153/58212 passed
Version: 18.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1799[GEN8+] 1-2% perf drop in SynMark2 OglPSPom2022-08-01T11:41:38ZBugzilla Migration User[GEN8+] 1-2% perf drop in SynMark2 OglPSPom## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110029)](https://bugs.freedesktop.org/show_bug.cgi?id=110029)**
## Description
Setup:
* Ubuntu 18.04 with Unity/compiz
* v4.19+ drm...## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#110029)](https://bugs.freedesktop.org/show_bug.cgi?id=110029)**
## Description
Setup:
* Ubuntu 18.04 with Unity/compiz
* v4.19+ drm-tip kernel & git version of Xserver
* Mesa git version
* BSW/BDW/BXT/SKL/KBL/CFL HW
* FullHD monitor
Test-case:
* SynMark2 v7 OglPSPom test in FullHD fullscreen
Performance of that has dropped by 1-2% on all GEN8+ platforms between following Mesa commits:
* 2019-02-01 17:34:02 ab940b0d97: spirv: Support LocalSizeId and LocalSizeHintId execution modes
* 2019-02-02 14:42:14 0aa5a97b03: relnotes: Add VK_EXT_buffer_device_address
There was no perf drop on SNB/HSW, or in other benchmarks I'm running.
Wontfixing this is fine, but I think somebody should bisect it first.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1798[SNB] INTEL_DEBUG=nohiz is likely broken for depth/stencil buffers2020-10-30T23:02:42ZBugzilla Migration User[SNB] INTEL_DEBUG=nohiz is likely broken for depth/stencil buffers## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109985)](https://bugs.freedesktop.org/show_bug.cgi?id=109985)**
## Description
For SNB, INTEL_DEBUG=nohiz seems to be brok...## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109985)](https://bugs.freedesktop.org/show_bug.cgi?id=109985)**
## Description
For SNB, INTEL_DEBUG=nohiz seems to be broken in two places:
1. In miptree_create() in intel_mipmap_tree.c. Trying to create a depth/stencil buffer will cause a depth miptree to be created without stencil.
2. In isl_genX(emit_depth_stencil_hiz_s) in isl_emit_depth_stencil.c. Emitting a depth/stencil buffer instruction will unconditionally force HiZ on.
I haven't tested/verified these observations.
mesa version: ae77f1236862e73c1ac250898924c648d481bda4
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1797[i915 CI][SKL, GLK] spec@ext_framebuffer_multisample_blit_scaled@blit-scaled ...2023-08-09T07:55:41ZBugzilla Migration User[i915 CI][SKL, GLK] spec@ext_framebuffer_multisample_blit_scaled@blit-scaled samples=2* - warn## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109979)](https://bugs.freedesktop.org/show_bug.cgi?id=109979)**
## Description
After updating mesa from 18.0.5 to 18.2.2, o...## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109979)](https://bugs.freedesktop.org/show_bug.cgi?id=109979)**
## Description
After updating mesa from 18.0.5 to 18.2.2, our SKL and GLK piglit machines (https://intel-gfx-ci.01.org/hardware.html#pigs) started consistently failing both "spec@ext_framebuffer_multisample_blit_scaled@blit-scaled samples=2" and "spec@ext_framebuffer_multisample_blit_scaled@blit-scaled samples=2 with gl_texture_2d_multisample_array".
The piglit version is a little old though: fdc5a4ca11124ab8413c7988896eec4c97336694
Here are the logs from the GLK platform when running "spec@ext_framebuffer_multisample_blit_scaled@blit-scaled samples=2":
Testing Intel-specific behavior.
Left Image: multisample scaled blit using extension.
Right Image: multisample scaled blit using shader program.
Probe color at (4,1)
Left: 0.749020 0.749020 0.749020 0.749020
Right: 0.560784 0.560784 0.560784 0.560784
MS attachment = TEXTURE, scale = 0.100000, result = fail
Probe color at (7,0)
Left: 0.000000 0.000000 0.000000 0.000000
Right: 0.658824 0.658824 0.658824 0.658824
MS attachment = TEXTURE, scale = 0.200000, result = fail
Probe color at (4,0)
Left: 0.329412 0.329412 0.329412 0.329412
Right: 0.564706 0.564706 0.564706 0.564706
MS attachment = TEXTURE, scale = 0.300000, result = fail
Probe color at (21,0)
Left: 0.552941 0.552941 0.552941 0.552941
Right: 0.792157 0.792157 0.792157 0.792157
MS attachment = TEXTURE, scale = 0.400000, result = fail
Probe color at (2,0)
Left: 0.403922 0.403922 0.403922 0.403922
Right: 0.890196 0.890196 0.890196 0.890196
MS attachment = TEXTURE, scale = 0.500000, result = fail
Probe color at (2,0)
Left: 1.000000 1.000000 1.000000 1.000000
Right: 0.654902 0.654902 0.654902 0.654902
MS attachment = TEXTURE, scale = 0.600000, result = fail
Probe color at (3,0)
Left: 0.164706 0.164706 0.164706 0.164706
Right: 0.933333 0.933333 0.933333 0.933333
MS attachment = TEXTURE, scale = 0.700000, result = fail
Probe color at (3,0)
Left: 1.000000 1.000000 1.000000 1.000000
Right: 0.219608 0.219608 0.219608 0.219608
MS attachment = TEXTURE, scale = 0.800000, result = fail
Probe color at (4,0)
Left: 0.023529 0.023529 0.023529 0.023529
Right: 0.956863 0.956863 0.956863 0.956863
MS attachment = TEXTURE, scale = 0.900000, result = fail
Probe color at (4,0)
Left: 0.894118 0.894118 0.894118 0.894118
Right: 0.078431 0.078431 0.078431 0.078431
MS attachment = TEXTURE, scale = 1.000000, result = fail
Probe color at (0,0)
Left: 0.956863 0.956863 0.956863 0.956863
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = TEXTURE, scale = 1.100000, result = fail
Probe color at (0,0)
Left: 0.925490 0.925490 0.925490 0.925490
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = TEXTURE, scale = 1.200000, result = fail
Probe color at (0,0)
Left: 0.898039 0.898039 0.898039 0.898039
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = TEXTURE, scale = 1.300000, result = fail
Probe color at (0,0)
Left: 0.866667 0.866667 0.866667 0.866667
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = TEXTURE, scale = 1.400000, result = fail
Probe color at (0,0)
Left: 0.843137 0.843137 0.843137 0.843137
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = TEXTURE, scale = 1.500000, result = fail
Probe color at (0,0)
Left: 0.815686 0.815686 0.815686 0.815686
Right: 0.980392 0.980392 0.980392 0.980392
MS attachment = TEXTURE, scale = 1.600000, result = fail
Probe color at (0,0)
Left: 0.792157 0.792157 0.792157 0.792157
Right: 0.988235 0.988235 0.988235 0.988235
MS attachment = TEXTURE, scale = 1.700000, result = fail
Probe color at (0,0)
Left: 0.768627 0.768627 0.768627 0.768627
Right: 0.992157 0.992157 0.992157 0.992157
MS attachment = TEXTURE, scale = 1.800000, result = fail
Probe color at (0,0)
Left: 0.749020 0.749020 0.749020 0.749020
Right: 1.000000 1.000000 1.000000 1.000000
MS attachment = TEXTURE, scale = 1.900000, result = fail
Probe color at (0,0)
Left: 0.737255 0.737255 0.737255 0.737255
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = TEXTURE, scale = 2.000000, result = fail
Probe color at (0,0)
Left: 0.725490 0.725490 0.725490 0.725490
Right: 0.956863 0.956863 0.956863 0.956863
MS attachment = TEXTURE, scale = 2.100000, result = fail
Probe color at (0,0)
Left: 0.713726 0.713726 0.713726 0.713726
Right: 0.933333 0.933333 0.933333 0.933333
MS attachment = TEXTURE, scale = 2.200000, result = fail
Probe color at (0,0)
Left: 0.705882 0.705882 0.705882 0.705882
Right: 0.913725 0.913725 0.913725 0.913725
MS attachment = TEXTURE, scale = 2.300000, result = fail
Probe color at (0,0)
Left: 0.698039 0.698039 0.698039 0.698039
Right: 0.898039 0.898039 0.898039 0.898039
MS attachment = TEXTURE, scale = 2.400000, result = fail
Probe color at (0,0)
Left: 0.690196 0.690196 0.690196 0.690196
Right: 0.882353 0.882353 0.882353 0.882353
MS attachment = TEXTURE, scale = 2.500000, result = fail
Probe color at (4,1)
Left: 0.749020 0.749020 0.749020 0.749020
Right: 0.560784 0.560784 0.560784 0.560784
MS attachment = RENDERBUFFER, scale = 0.100000, result = fail
Probe color at (7,0)
Left: 0.000000 0.000000 0.000000 0.000000
Right: 0.658824 0.658824 0.658824 0.658824
MS attachment = RENDERBUFFER, scale = 0.200000, result = fail
Probe color at (4,0)
Left: 0.329412 0.329412 0.329412 0.329412
Right: 0.564706 0.564706 0.564706 0.564706
MS attachment = RENDERBUFFER, scale = 0.300000, result = fail
Probe color at (21,0)
Left: 0.552941 0.552941 0.552941 0.552941
Right: 0.792157 0.792157 0.792157 0.792157
MS attachment = RENDERBUFFER, scale = 0.400000, result = fail
Probe color at (2,0)
Left: 0.403922 0.403922 0.403922 0.403922
Right: 0.890196 0.890196 0.890196 0.890196
MS attachment = RENDERBUFFER, scale = 0.500000, result = fail
Probe color at (2,0)
Left: 1.000000 1.000000 1.000000 1.000000
Right: 0.654902 0.654902 0.654902 0.654902
MS attachment = RENDERBUFFER, scale = 0.600000, result = fail
Probe color at (3,0)
Left: 0.164706 0.164706 0.164706 0.164706
Right: 0.933333 0.933333 0.933333 0.933333
MS attachment = RENDERBUFFER, scale = 0.700000, result = fail
Probe color at (3,0)
Left: 1.000000 1.000000 1.000000 1.000000
Right: 0.219608 0.219608 0.219608 0.219608
MS attachment = RENDERBUFFER, scale = 0.800000, result = fail
Probe color at (4,0)
Left: 0.023529 0.023529 0.023529 0.023529
Right: 0.956863 0.956863 0.956863 0.956863
MS attachment = RENDERBUFFER, scale = 0.900000, result = fail
Probe color at (4,0)
Left: 0.894118 0.894118 0.894118 0.894118
Right: 0.078431 0.078431 0.078431 0.078431
MS attachment = RENDERBUFFER, scale = 1.000000, result = fail
Probe color at (0,0)
Left: 0.956863 0.956863 0.956863 0.956863
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = RENDERBUFFER, scale = 1.100000, result = fail
Probe color at (0,0)
Left: 0.925490 0.925490 0.925490 0.925490
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = RENDERBUFFER, scale = 1.200000, result = fail
Probe color at (0,0)
Left: 0.898039 0.898039 0.898039 0.898039
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = RENDERBUFFER, scale = 1.300000, result = fail
Probe color at (0,0)
Left: 0.866667 0.866667 0.866667 0.866667
Right: 0.968627 0.968627 0.968627 0.968627
MS attachment = RENDERBUFFER, scale = 1.400000, result = fail
Probe color at (0,0)
Left: 0.843137 0.843137 0.843137 0.843137
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = RENDERBUFFER, scale = 1.500000, result = fail
Probe color at (0,0)
Left: 0.815686 0.815686 0.815686 0.815686
Right: 0.980392 0.980392 0.980392 0.980392
MS attachment = RENDERBUFFER, scale = 1.600000, result = fail
Probe color at (0,0)
Left: 0.792157 0.792157 0.792157 0.792157
Right: 0.988235 0.988235 0.988235 0.988235
MS attachment = RENDERBUFFER, scale = 1.700000, result = fail
Probe color at (0,0)
Left: 0.768627 0.768627 0.768627 0.768627
Right: 0.992157 0.992157 0.992157 0.992157
MS attachment = RENDERBUFFER, scale = 1.800000, result = fail
Probe color at (0,0)
Left: 0.749020 0.749020 0.749020 0.749020
Right: 1.000000 1.000000 1.000000 1.000000
MS attachment = RENDERBUFFER, scale = 1.900000, result = fail
Probe color at (0,0)
Left: 0.737255 0.737255 0.737255 0.737255
Right: 0.976471 0.976471 0.976471 0.976471
MS attachment = RENDERBUFFER, scale = 2.000000, result = fail
Probe color at (0,0)
Left: 0.725490 0.725490 0.725490 0.725490
Right: 0.956863 0.956863 0.956863 0.956863
MS attachment = RENDERBUFFER, scale = 2.100000, result = fail
Probe color at (0,0)
Left: 0.713726 0.713726 0.713726 0.713726
Right: 0.933333 0.933333 0.933333 0.933333
MS attachment = RENDERBUFFER, scale = 2.200000, result = fail
Probe color at (0,0)
Left: 0.705882 0.705882 0.705882 0.705882
Right: 0.913725 0.913725 0.913725 0.913725
MS attachment = RENDERBUFFER, scale = 2.300000, result = fail
Probe color at (0,0)
Left: 0.698039 0.698039 0.698039 0.698039
Right: 0.898039 0.898039 0.898039 0.898039
MS attachment = RENDERBUFFER, scale = 2.400000, result = fail
Probe color at (0,0)
Left: 0.690196 0.690196 0.690196 0.690196
Right: 0.882353 0.882353 0.882353 0.882353
MS attachment = RENDERBUFFER, scale = 2.500000, result = fail
Version: 18.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1796[ilk] GPU HANG: ecode 5:0:0xfcefffdf, in chromium -- https://www.android.com...2022-06-02T23:16:20ZBugzilla Migration User[ilk] GPU HANG: ecode 5:0:0xfcefffdf, in chromium -- https://www.android.com/versions/go-edition/## Submitted by kbt..@..ree.fr
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109942)](https://bugs.freedesktop.org/show_bug.cgi?id=109942)**
## Description
Created attachment 143588
GPU crash dump saved to /...## Submitted by kbt..@..ree.fr
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109942)](https://bugs.freedesktop.org/show_bug.cgi?id=109942)**
## Description
Created attachment 143588
GPU crash dump saved to /sys/class/drm/card0/error
I have a reproducible bug here. I'm on Arch/Linux, and I use chromium as a Web browser. If I visit https://www.android.com/versions/go-edition/ with it, the screen freezes for many seconds and dmesg gives me this message:
[drm] GPU HANG: ecode 5:0:0xfcefffdf, in chromium [2461], reason: hang on rcs0, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
**Attachment 143588**, "GPU crash dump saved to /sys/class/drm/card0/error":
[error-drm-card0.txt](/uploads/32b638a96331a8beb86f3995f1f19ced/error-drm-card0.txt)
Version: 18.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1794GPU HANG: ecode 7:0:0x85dffffc, in Xorg [739], reason: Hang on render ring, a...2022-06-02T22:07:58ZBugzilla Migration UserGPU HANG: ecode 7:0:0x85dffffc, in Xorg [739], reason: Hang on render ring, action: reset; system freezes and new session is started automatically - GPU issue, i915## Submitted by marco
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109817)](https://bugs.freedesktop.org/show_bug.cgi?id=109817)**
## Description
Created attachment 143514
gpu crash dump from /sys/class/drm...## Submitted by marco
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109817)](https://bugs.freedesktop.org/show_bug.cgi?id=109817)**
## Description
Created attachment 143514
gpu crash dump from /sys/class/drm/card0/error
System freezes and new session is started automatically. Journal entries point to GPU problem (see below). Crash dump in attachment. I´ m facing similar issues (system freezes) also with the RT kernel. Any help is highly appreciated.
thanks & cheers,
marco
Used Kernel: Linux fox 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux
Debian Stretch / XFCE
System:
CPU: Quad core Intel Core i5-4460 (-MCP-) cache: 6144 KB
clock speeds: max: 3400 MHz 1: 3398 MHz 2: 3396 MHz 3: 3395 MHz 4: 3399 MHz
CPU Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2 bts clflush cmov
constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts ept erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht ibpb ibrs ida invpcid invpcid_single kaiser lahf_lm lm mca mce mmx monitor movbe msr
mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts
rdrand rdtscp rep_good sdbg sep smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr
----------------------------
Mär 02 20:56:04 fox kernel: [drm] GPU HANG: ecode 7:0:0x85dffffc, in Xorg [739], reason: Hang on render ring, action: reset
Mär 02 20:56:04 fox kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mär 02 20:56:04 fox kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mär 02 20:56:04 fox kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mär 02 20:56:04 fox kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mär 02 20:56:04 fox kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mär 02 20:56:04 fox kernel: drm/i915: Resetting chip after gpu hang
Mär 02 20:56:15 fox kernel: drm/i915: Resetting chip after gpu hang
Mär 02 20:56:15 fox org.a11y.atspi.Registry[3181]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Mär 02 20:56:15 fox org.a11y.atspi.Registry[3181]: after 82579 requests (82579 known processed) with 0 events remaining.
Mär 02 20:56:15 fox polkitd(authority=local)[529]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.35, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale de_DE.utf8) (disconne
Mär 02 20:56:15 fox lightdm[3048]: pam_unix(lightdm:session): session closed for user marco
Mär 02 20:56:16 fox lightdm[15916]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .servic
Mär 02 20:56:16 fox lightdm[15916]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Mär 02 20:56:16 fox systemd[1]: Created slice User Slice of lightdm.
Mär 02 20:56:16 fox systemd[1]: Starting User Manager for UID 112...
Mär 02 20:56:16 fox systemd-logind[456]: New session c2 of user lightdm.
Mär 02 20:56:16 fox systemd[15919]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Mär 02 20:56:16 fox systemd[1]: Started Session c2 of user lightdm.
**Attachment 143514**, "gpu crash dump from /sys/class/drm/card0/error":
[error_dump.txt](/uploads/c24f983f94e9dc174f9878804001a0d6/error_dump.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1793[hsw] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x112019-12-25T09:06:33ZBugzilla Migration User[hsw] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11## Submitted by amr..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109792)](https://bugs.freedesktop.org/show_bug.cgi?id=109792)**
## Description
Created attachment 143492
The gpu crash dump
From ...## Submitted by amr..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109792)](https://bugs.freedesktop.org/show_bug.cgi?id=109792)**
## Description
Created attachment 143492
The gpu crash dump
From time to time, (once every couple hours approximately), the graphics system hangs for a few seconds, then returns to normal.
The output from dmesg at the time is:
[feb27 19:52] [drm] GPU HANG: ecode 7:0:0x85dffffc, in kwin_x11 [3775], reason: hang on rcs0, action: reset
[ +0,000002] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ +0,000000] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ +0,000000] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ +0,000001] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ +0,000001] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ +0,000043] i915 0000:00:02.0: Resetting chip for hang on rcs0
Thanks a lot.
**Attachment 143492**, "The gpu crash dump":
[graphicsHangError.log](/uploads/9b1520922fe122d045999875b1b0e014/graphicsHangError.log)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1792[SNBGT1] KHR-GL33.transform_feedback.query_geometry_separate_test fails2022-06-02T22:08:43ZBugzilla Migration User[SNBGT1] KHR-GL33.transform_feedback.query_geometry_separate_test fails## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109684)](https://bugs.freedesktop.org/show_bug.cgi?id=109684)**
## Description
In Mesa i965 CI, this test fails on SNBGT1, ...## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109684)](https://bugs.freedesktop.org/show_bug.cgi?id=109684)**
## Description
In Mesa i965 CI, this test fails on SNBGT1, but passes on other skus. Typically, tests pass or fail consistently on all hardware configurations of a particular gen.
Rather than track the GT1 results separately, we will disable this test on SNB.
Version: git