mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2022-06-02T23:21:28Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1749[skl] GPU hang on rsc0 (plasmashell)2022-06-02T23:21:28ZBugzilla Migration User[skl] GPU hang on rsc0 (plasmashell)## Submitted by Simon
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107574)](https://bugs.freedesktop.org/show_bug.cgi?id=107574)**
## Description
My pc hangs from time to time a few seconds and I get this i...## Submitted by Simon
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107574)](https://bugs.freedesktop.org/show_bug.cgi?id=107574)**
## Description
My pc hangs from time to time a few seconds and I get this in my journal:
`
kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in plasmashell [851], reason: Hang on rcs0, action: reset
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
`
here is the crash dump: https://pastebin.com/bCR7bCPQ
I don't have a lot of experience with filing bug reports so if I forgot anything please let me know.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1748[skl] GPU HANG: ecode 9:0:0x85dffffb, in X2022-06-02T23:22:00ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dffffb, in X## Submitted by gag..@..mx.net
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107554)](https://bugs.freedesktop.org/show_bug.cgi?id=107554)**
## Description
Created attachment 141057
DMesg-output, crash-dump,...## Submitted by gag..@..mx.net
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107554)](https://bugs.freedesktop.org/show_bug.cgi?id=107554)**
## Description
Created attachment 141057
DMesg-output, crash-dump, kernelID, SystemID, lspci
This error freezes my Desktop completely.
It occures sometimes, when I work with eagle-4.14 or KiCAD or Libre-Office.
Especially this crash seems to raise when heavy repainting is done (zoom-in/zoom-out).
after some seconds, the desktop restarts and let me log in again - but all unsaved Data in every running application are lost.
Kernel: 4.4.140-62-default
System: openSUSE Leap 42.3
**Attachment 141057**, "DMesg-output, crash-dump, kernelID, SystemID, lspci":
[gpu_hang_crash_files.tar.gz](/uploads/e5b9a893b58f5b7609c4fbb5f6823be7/gpu_hang_crash_files.tar.gz)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1747Segmentation fault in Gnome Shell when resuming from blank screen2022-06-06T08:24:40ZBugzilla Migration UserSegmentation fault in Gnome Shell when resuming from blank screen## Submitted by Peter Bašista `@pbasista`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107520)](https://bugs.freedesktop.org/show_bug.cgi?id=107520)**
## Description
Created attachment 141004
full backtrace...## Submitted by Peter Bašista `@pbasista`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107520)](https://bugs.freedesktop.org/show_bug.cgi?id=107520)**
## Description
Created attachment 141004
full backtrace of gnome-shell crashing on SIGSEGV in image_get_buffers
When resuming from blank screen in Gnome Shell (can be configured in Settings->Power), Gnome Shell process sometimes (around 40% to 50% of cases in my experience) crashes on segmentation fault. The backtraces vary slightly, but mostly they point to intel_update_image_buffers function in the src/mesa/drivers/dri/i965/brw_context.c file.
There is a related bug report on Gnome Bugzilla:
https://bugzilla.gnome.org/show_bug.cgi?id=795537
One person suggested that a crash inside mesa should never happen, so I am reporting it here as well.
One of the backtraces that I have starts like this:
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
```
#0 0x00007f74143eed33 in image_get_buffers (driDrawable=0x56353e8ca4d0, format=4098, stamp=0x56353e8ca500, loaderPrivate=0x56353e8d4510, buffer_mask=1, buffers=0x7ffd94a282c0)
at ../../../src/gbm/backends/dri/gbm_dri.c:132
#1 0x00007f7405c29741 in intel_update_image_buffers (drawable=0x56353e8ca4d0, brw=0x56353e7a9980) at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1751
#2 intel_update_renderbuffers (context=context@entry=0x56353e7c82d0, drawable=drawable@entry=0x56353e8ca4d0) at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1427
#3 0x00007f7405c29dc1 in intel_prepare_render (brw=brw@entry=0x56353e7a9980) at ../../../../../../src/mesa/drivers/dri/i965/brw_context.c:1448
#4 0x00007f7405c2c012 in brw_prepare_drawing (max_index=4294967295, min_index=0, index_bounds_valid=<optimized out>, ib=0x7ffd94a28430, arrays=<optimized out>, ctx=0x56353e7a9980)
at ../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:730
#5 brw_draw_prims (ctx=0x56353e7a9980, prims=0x7ffd94a28450, nr_prims=1, ib=0x7ffd94a28430, index_bounds_valid=<optimized out>, min_index=<optimized out>, max_index=<optimized out>,
gl_xfb_obj=0x0, stream=0, indirect=0x0) at ../../../../../../src/mesa/drivers/dri/i965/brw_draw.c:992
#6 0x00007f74059c1b59 in vbo_validated_drawrangeelements (ctx=<optimized out>, mode=<optimized out>, index_bounds_valid=<optimized out>, start=0, end=<optimized out>,
count=<optimized out>, type=5123, indices=0x0, basevertex=0, numInstances=1, baseInstance=0) at ../../../src/mesa/vbo/vbo_exec_array.c:843
#7 0x00007f74059c252e in vbo_exec_DrawElements (mode=4, count=1302, type=5123, indices=0x0) at ../../../src/mesa/vbo/vbo_exec_array.c:1001
```
The full version is attached.
**Attachment 141004**, "full backtrace of gnome-shell crashing on SIGSEGV in image_get_buffers":
[gnome-shell.backtrace](/uploads/724b50184d023b4983f21f4d2b32701a/gnome-shell.backtrace)
Version: 18.1https://gitlab.freedesktop.org/mesa/mesa/-/issues/1746[lars] dEQP-GLES31.functional.geometry_shading.layered#render_with_default_la...2020-01-29T01:08:49ZBugzilla Migration User[lars] dEQP-GLES31.functional.geometry_shading.layered#render_with_default_layer_3d failure## Submitted by gau..@..el.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107505)](https://bugs.freedesktop.org/show_bug.cgi?id=107505)**
## Description
Created attachment 140989
dEQP Test execution log o...## Submitted by gau..@..el.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107505)](https://bugs.freedesktop.org/show_bug.cgi?id=107505)**
## Description
Created attachment 140989
dEQP Test execution log on lars, it fails on lars
On chrome images, we are seeing a failure of dEQP test case failing on skylake lars.
Steps To reproduce on a lars chromium test image:
cd /usr/local/deqp/modules/gles31/
/usr/local/deqp/modules/gles31/deqp-gles31 --deqp-case=dEQP-GLES31.functional.geometry_shading.layered.render_with_default_layer_3d --deqp-surface-type=pbuffer --deqp-gl-config-name=rgba8888d24s8ms0 --deqp-log-images=disable --deqp-watchdog=disable --deqp-surface-width=256 --deqp-surface-height=256 --deqp-log-filename=/tmp/dEQP-GLES31.log
Test case 'dEQP-GLES31.functional.geometry_shading.layered.render_with_default_layer_3d'..
Vertex shader compile time = 5.480000 ms
Fragment shader compile time = 0.444000 ms
Geometry shader compile time = 0.789000 ms
Link time = 2.192000 ms
Vertex shader compile time = 0.465000 ms
Fragment shader compile time = 0.773000 ms
Link time = 1.593000 ms
Test case duration in microseconds = 21011 us
Fail (Detected invalid layer content)
DONE!
Test run totals:
Passed: 0/1 (0.0%)
Failed: 1/1 (100.0%)
Not supported: 0/1 (0.0%)
Warnings: 0/1 (0.0%)
The same test is passing on skylake chell.
**Attachment 140989**, "dEQP Test execution log on lars, it fails on lars":
[dEQP-GLES31_lars_target_execution_FAILS.log](/uploads/601b43771b0ddd6d779dfa144c7d697f/dEQP-GLES31_lars_target_execution_FAILS.log)
Version: 18.2Lionel LandwerlinLionel Landwerlinhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1745[BYT] Tesselation tests unreliable2019-09-25T19:13:00ZBugzilla Migration User[BYT] Tesselation tests unreliable## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107445)](https://bugs.freedesktop.org/show_bug.cgi?id=107445)**
## Description
BYT intermittently fails tessellation tests ...## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107445)](https://bugs.freedesktop.org/show_bug.cgi?id=107445)**
## Description
BYT intermittently fails tessellation tests in the GLES CTS, for example:
------------------------------------------------------
KHR-GLES31.core.tessellation_shader.tessellation_control_to_tessellation_evaluation.gl_tessLevel
stdout:
Invalid inner/outer tessellation level used in TE stage; expected outer:(16.8, 8.2) rendered outer:(0, 0) vertex spacing mode: equal_spacing
Invalid inner/outer tessellation level used in TE stage at esextcTessellationShaderTCTE.cpp:3671
------------------------------------------------------
These tests are disabled for the platform in CI
KHR-GLESEXT.tessellation_shader.tessellation_shader_tessellation.gl_InvocationID_PatchVerticesIn_PrimitiveID
KHR-GLES31.core.tessellation_shader.tessellation_shader_tessellation.gl_InvocationID_PatchVerticesIn_PrimitiveID
KHR-GLES31.core.tessellation_shader.tessellation_control_to_tessellation_evaluation.gl_tessLevel
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1744[hsw] GPU HANG: ecode 7:0:0x86dffffd in Xorg2022-06-02T23:22:30ZBugzilla Migration User[hsw] GPU HANG: ecode 7:0:0x86dffffd in Xorg## Submitted by Georg
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107420)](https://bugs.freedesktop.org/show_bug.cgi?id=107420)**
## Description
Created attachment 140876
card0 error
My system is a deskto...## Submitted by Georg
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107420)](https://bugs.freedesktop.org/show_bug.cgi?id=107420)**
## Description
Created attachment 140876
card0 error
My system is a desktop with Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz.
This bug happens immediately after installation a debian stretch.
I am able to boot and log in. Using firefox or terminal works as well.
When I start nautilus the system carashes and I'm pushed back to the log in screen.
All data I share are from this situation.
Btw: I see a very similar behavior if I try to install Ubuntu 18.04. I'm not able to run the live system for installation. Neither from USB stick nor from DVD. The same image runs in a virtual box. (so Image seems to be OK.)
**Attachment 140876**, "card0 error":
[sys_class_drm_card0_error](/uploads/972d830f0bda9bfe094b12fa6d03e03e/sys_class_drm_card0_error)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1743[BXT] KHR-GL46.texture_buffer.texture_buffer_atomic_functions intermittent2019-09-25T19:12:52ZBugzilla Migration User[BXT] KHR-GL46.texture_buffer.texture_buffer_atomic_functions intermittent## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107389)](https://bugs.freedesktop.org/show_bug.cgi?id=107389)**
## Description
In Mesa CI, this test fails ~25% of the time...## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107389)](https://bugs.freedesktop.org/show_bug.cgi?id=107389)**
## Description
In Mesa CI, this test fails ~25% of the time on BXT. It passes reliably on all platforms.
stdout:
Result is different than expected at index: 33
Expected value: 664128
Result value: 658538
This test will be disabled for the platform in Mesa CI
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1742GTK Apps severely glitching after updating from 18.1.3 to 18.1.42019-09-25T20:03:18ZBugzilla Migration UserGTK Apps severely glitching after updating from 18.1.3 to 18.1.4## Submitted by Nathan
Assigned to **Dylan Baker `@dbaker`**
**[Link to original bug (#107388)](https://bugs.freedesktop.org/show_bug.cgi?id=107388)**
## Description
On Manjaro linux I upgraded mesa and after restarting saw severe...## Submitted by Nathan
Assigned to **Dylan Baker `@dbaker`**
**[Link to original bug (#107388)](https://bugs.freedesktop.org/show_bug.cgi?id=107388)**
## Description
On Manjaro linux I upgraded mesa and after restarting saw severe glitching:
https://i.imgur.com/4lTkBtv.png
Qt apps did not appear to have this problem, Chrome was fine too. I downgraded mesa after which everything settled down.
Hardware info:
H/W path Device Class Description
===========================================================
system Galago Pro (Not Applicable)
/0 bus Galago Pro
/0/0 memory 64KiB BIOS
/0/13 memory 16GiB System Memory
/0/13/0 memory 8GiB SODIMM DDR4 Synchronous 2133 MHz (0.5 ns)
/0/13/1 memory 8GiB SODIMM DDR4 Synchronous 2133 MHz (0.5 ns)
/0/17 memory 128KiB L1 cache
/0/18 memory 512KiB L2 cache
/0/19 memory 3MiB L3 cache
/0/1a processor Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
/0/100 bridge Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers
/0/100/2 display HD Graphics 620
/0/100/8 generic Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaus
/0/100/14 bus Sunrise Point-LP USB 3.0 xHCI Controller
/0/100/14/0 usb1 bus xHCI Host Controller
/0/100/14/0/1 bus USB2.0 Hub
/0/100/14/0/1/1 multimedia C922 Pro Stream Webcam
/0/100/14/0/1/3 bus Hub
/0/100/14/0/1/3/1 bus USB2.0 Hub
/0/100/14/0/1/3/1/2 input USB Receiver
/0/100/14/0/1/3/1/3 multimedia USB Audio Device
/0/100/14/0/1/4 input USB-HID Gaming Keyboard
/0/100/14/0/4 multimedia BisonCam,NB Pro
/0/100/14/0/5 communication Bluetooth wireless interface
/0/100/14/1 usb2 bus xHCI Host Controller
/0/100/14/1/1 bus USB3.0 Hub
/0/100/14.2 generic Sunrise Point-LP Thermal subsystem
/0/100/17 storage Sunrise Point-LP SATA Controller [AHCI mode]
/0/100/1c bridge Sunrise Point-LP PCI Express Root Port #1
/0/100/1c.4 bridge Sunrise Point-LP PCI Express Root Port #5
/0/100/1c.4/0 generic RTL8411B PCI Express Card Reader
/0/100/1c.4/0.1 enp58s0f1 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/1c.5 bridge Sunrise Point-LP PCI Express Root Port #6
/0/100/1c.5/0 wlp59s0 network Wireless 8265 / 8275
/0/100/1f bridge Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller
/0/100/1f.2 memory Memory controller
/0/100/1f.3 multimedia Sunrise Point-LP HD Audio
/0/100/1f.4 bus Sunrise Point-LP SMBus
/0/1 scsi2 storage
/0/1/0.0.0 /dev/sda disk 250GB WDC WDS250G1B0B-
/0/1/0.0.0/1 /dev/sda1 volume 229GiB EXT4 volume
/0/1/0.0.0/2 /dev/sda2 volume 299MiB Windows FAT volume
/0/1/0.0.0/3 /dev/sda3 volume 3672MiB Linux swap volume
/1 vnet1 network Ethernet interface
/2 virbr1-nic network Ethernet interface
/3 virbr0-nic network Ethernet interface
/4 virbr0 network Ethernet interface
/5 vnet0 network Ethernet interface
/6 virbr1 network Ethernet interface
Version: 18.0Dylan BakerDylan Bakerhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1741[kbl/apl] [drm] GPU hang in Antutu 7.x games with 4.14.52 kernel2022-11-26T16:49:06ZBugzilla Migration User[kbl/apl] [drm] GPU hang in Antutu 7.x games with 4.14.52 kernel## Submitted by Ren Chenglei
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107356)](https://bugs.freedesktop.org/show_bug.cgi?id=107356)**
## Description
Created attachment 140804
DMESG LOG
AnTuTu benchmark...## Submitted by Ren Chenglei
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107356)](https://bugs.freedesktop.org/show_bug.cgi?id=107356)**
## Description
Created attachment 140804
DMESG LOG
AnTuTu benchmark is one popular app for Android smartphone and tablet benchmarking! Recently, when lunched Antutu 7.x version on Android IA and Chrome OS, we encountered GPU hang issue.
```
[ 348.713449] [drm] GPU HANG: ecode 9:0:0x84df9ffc, in Thread-10 [8813], reason: hang on rcs0, action: reset
[ 348.713453] [drm:drm_ioctl] pid=3367, dev=0xe200, auth=1, DRM_IOCTL_WAIT_VBLANK
[ 348.713455] [drm:drm_wait_vblank_ioctl] waiting on vblank count 20853, crtc 0
[ 348.713485] [drm:i915_reset_device] resetting chip
[ 348.713500] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 348.713825] [drm:i915_gem_reset_engine] context Thread-10[8813]/1 marked guilty (score 10) banned? no
[ 348.713827] [drm:i915_gem_reset_engine] resetting rcs0 to restart from tail of request 0x413a
[ 348.713856] [drm] RC6 on
[ 348.714048] [drm:gen8_init_common_ring] Execlists enabled for rcs0
[ 348.714055] [drm:init_workarounds_ring] rcs0: Number of context specific w/a: 15
```
**Attachment 140804**, "DMESG LOG":
[dmesg.txt](/uploads/3dde3735b2f162401acf4f26be4b17a3/dmesg.txt)
Version: 19.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1740Android: i965/miptree null pointer dereference with Google Playstore2022-11-26T16:48:12ZBugzilla Migration UserAndroid: i965/miptree null pointer dereference with Google Playstore## Submitted by maurossi `@issor.oruam`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107352)](https://bugs.freedesktop.org/show_bug.cgi?id=107352)**
## Description
Created attachment 140798
logcat with segf...## Submitted by maurossi `@issor.oruam`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107352)](https://bugs.freedesktop.org/show_bug.cgi?id=107352)**
## Description
Created attachment 140798
logcat with segfault
Hi,
there are segfaults for null pointer dereference happening with Google Playstore.
Logs and patch by Chih-Wei Huang in the attachment
Tested by me and android-x86 users it can resolve the Google Play and other apps crashes.
Mauro Rossi
android-x86 team
**Attachment 140798**, "logcat with segfault":
[logcat_i965_miptree_segfault.txt](/uploads/0e5f7eb166a888419843f5507c3e4d99/logcat_i965_miptree_segfault.txt)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1739[snb] Xorg crashes on Intel, after upgrade to 18.04. The problem is present o...2019-09-25T19:12:21ZBugzilla Migration User[snb] Xorg crashes on Intel, after upgrade to 18.04. The problem is present on several identical machines.## Submitted by Vladimir Skubriev
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107208)](https://bugs.freedesktop.org/show_bug.cgi?id=107208)**
## Description
Created attachment 140608
Intel bug file
We usi...## Submitted by Vladimir Skubriev
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107208)](https://bugs.freedesktop.org/show_bug.cgi?id=107208)**
## Description
Created attachment 140608
Intel bug file
We using ubuntu on desktop. Some desktops are tool old. There is two machines with identical configuration. After installing on it new version of ubuntu (16.04->18.04) users cannot work as early. XServer crashes while increasing the load on the processor (we think so).
Our typical case is using Intel for run Xserver. Nvidia for GPU calculations. We tried upgrade a kernel to latest stable mainline (4.17.4-041704-generic) but unfortunately this does not help.
Running X on nvidia is stable, but gpu memory is used.
**Attachment 140608**, "Intel bug file":
[error_to_report](/uploads/06e7e2408c1841c76c63cb497313e1c4/error_to_report)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1738[skl] ecode 9:0:0x85dffffb, in gnome-shell2022-06-02T23:22:53ZBugzilla Migration User[skl] ecode 9:0:0x85dffffb, in gnome-shell## Submitted by nil..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107178)](https://bugs.freedesktop.org/show_bug.cgi?id=107178)**
## Description
Created attachment 140539
crash dump.
I'm getting ...## Submitted by nil..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107178)](https://bugs.freedesktop.org/show_bug.cgi?id=107178)**
## Description
Created attachment 140539
crash dump.
I'm getting random GPU hangs as well as display corruption (random parts of the screen will show tearing/lines with various colors) quite often. It's very hard to accurately reproduce, but happens pretty consistently when scrolling in Firefox or typing in vim in a terminal.
Running Fedora 28 x86_64 on 4.17.3-200.fc28.x86_64. I'm using a skylake Lenovo p50 with hdmi hooked up to an external 1080p monitor.
Here's the dmesg dump. I get a crash log for the first one. Later ones just show the "Resetting rcs0" message.
[ 4732.361391] [drm] GPU HANG: ecode 9:0:0x85dffffb, in gnome-shell [2235], reason: Hang on rcs0, action: reset
[ 4732.361392] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 4732.361393] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 4732.361393] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 4732.361393] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 4732.361394] [drm] GPU crash dump saved to /sys/class/drm/card1/error
[ 4732.361426] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 4767.361084] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 4846.337555] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 4885.313770] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 4960.322208] i915 0000:00:02.0: Resetting rcs0 after gpu hang
Crash dump attached.
**Attachment 140539**, "crash dump.":
[error.bz2](/uploads/dc1f7c8bcc49c99da6b46072a807d4a1/error.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1737[GLK] GPU HANG in kodi2022-06-02T23:23:37ZBugzilla Migration User[GLK] GPU HANG in kodi## Submitted by Erik Sandlund
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107159)](https://bugs.freedesktop.org/show_bug.cgi?id=107159)**
## Description
Created attachment 140515
/sys/class/drm/card0/error...## Submitted by Erik Sandlund
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107159)](https://bugs.freedesktop.org/show_bug.cgi?id=107159)**
## Description
Created attachment 140515
/sys/class/drm/card0/error
Hi, I'm using a NUC7PJYH for Kodi. It worked fine for a couple of weeks but lately the i915-driver hangs when I stress it. I have tried reinstalling the system (Ubuntu 18.04 Server) and tried various LibreElec-versions. I can reproduce error by running glxgears on openbox. Depending on driver-settings for Xorg Intel-driver the time until crash varies. If I load up Kodi it crashes if I move around in the menus. Videos seems to play ok.
I supply an error-log from a LibreElec "Milhouse build" since I figure it's the least touched by my messing around.
**Attachment 140515**, "/sys/class/drm/card0/error":
[error.log](/uploads/3465f4a5517212f983db5059d2c4e705/error.log)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1736[kbl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg2022-06-02T23:23:52ZBugzilla Migration User[kbl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg## Submitted by sha..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107118)](https://bugs.freedesktop.org/show_bug.cgi?id=107118)**
## Description
Created attachment 140470
/sys/class/drm/card0/erro...## Submitted by sha..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107118)](https://bugs.freedesktop.org/show_bug.cgi?id=107118)**
## Description
Created attachment 140470
/sys/class/drm/card0/error
**Attachment 140470**, "/sys/class/drm/card0/error":
[gpu-hang.txt](/uploads/1bd289fb1653c722d7a6908ca5a62180/gpu-hang.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1735Some miptree maps don't use intel_mipmap_tree::offset2021-08-09T15:21:17ZBugzilla Migration UserSome miptree maps don't use intel_mipmap_tree::offset## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107073)](https://bugs.freedesktop.org/show_bug.cgi?id=107073)**
## Description
Miptree maps for stencil, depth-stencil, an...## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107073)](https://bugs.freedesktop.org/show_bug.cgi?id=107073)**
## Description
Miptree maps for stencil, depth-stencil, and etc-decompressed-workaround miptrees don't use ::offset. This seems wrong.
I think we may run into an issue in the following case:
1. Create a DRI image from a miptree level > 1 via __DRIimageExtensionRec::createImageFromTexture. The level must be in a different tile than the base level. This will set __DRIimage::offset > 0.
2. Create an aformentioned problematic miptree from that image using EGLImageTargetRenderbufferStorage or EGLImageTargetTexture2D (maybe also __DriverAPIRec::MakeCurrent?). These use intel_miptree_create_for_dri_image internally and will set intel_mipmap_tree::offset > 0.
3. Map the miptree for reading. We'll expect data from the level > 1, but we'll instead get data from the base level.
If this is indeed possbile, we need a piglit test to confirm the issue and a Mesa patch to fix it.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1734[SNB][WebGL] conformance/extensions/oes-texture-half-float.html INVALID_FRAME...2019-09-25T19:12:00ZBugzilla Migration User[SNB][WebGL] conformance/extensions/oes-texture-half-float.html INVALID_FRAMEBUFFER_OPERATION error## Submitted by Leonardo
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107026)](https://bugs.freedesktop.org/show_bug.cgi?id=107026)**
## Description
Created attachment 140319
glxinfo
https://www.khronos.or...## Submitted by Leonardo
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#107026)](https://bugs.freedesktop.org/show_bug.cgi?id=107026)**
## Description
Created attachment 140319
glxinfo
https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html
Using the WebGL 1.0.4 conformance test on my Sandybridge laptop.
conformance/extensions/oes-texture-half-float.html (Passed: 107/121 Failed: 14/121 in 683.0 ms)
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_FORMAT should fail for incomplete framebuffers.
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_TYPE should fail for incomplete framebuffers.
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_FORMAT should fail for incomplete framebuffers.
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_TYPE should fail for incomplete framebuffers.
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_FORMAT should fail for incomplete framebuffers.
failed: getError expected: INVALID_OPERATION. Was INVALID_FRAMEBUFFER_OPERATION : IMPLEMENTATION_COLOR_READ_TYPE should fail for incomplete framebuffers.
failed: getError expected: NO_ERROR. Was INVALID_ENUM : readPixels should return NO_ERROR when reading FLOAT data.
failed: Green channel should be 0.25 for FLOAT readPixels. Received: 0
failed: Blue channel should be 0.5 for FLOAT readPixels. Received: 0
failed: Alpha channel should be 0.75 for FLOAT readPixels. Received: 0
failed: getError expected: NO_ERROR. Was INVALID_ENUM : readPixels should return NO_ERROR when reading FLOAT data.
failed: Green channel should be 0.25 for FLOAT readPixels. Received: 0
failed: Blue channel should be 0.5 for FLOAT readPixels. Received: 0
failed: Alpha channel should be 1 for FLOAT readPixels. Received: 0
The other subtests are OK.
I'm using Mesa 1.8.1.1 on Firefox 60.0.2 Manjaro Linux (i've attached a complete glxinfo).
**Attachment 140319**, "glxinfo":
[glxinfo.txt](/uploads/7fc7bce8bedd33abff71adb12165c774/glxinfo.txt)
Version: 18.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1733[snb] GPU hang in Xorg2020-03-16T15:09:02ZBugzilla Migration User[snb] GPU hang in Xorg## Submitted by sem..@..gmx.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106914)](https://bugs.freedesktop.org/show_bug.cgi?id=106914)**
## Description
Created attachment 140150
/sys/class/drm/card/error...## Submitted by sem..@..gmx.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106914)](https://bugs.freedesktop.org/show_bug.cgi?id=106914)**
## Description
Created attachment 140150
/sys/class/drm/card/error
Observed Behaviour:
The KDE Desktop hangs from time to time some seconds.
In some cases the monitors become black afterwards and the system freeze.
Environment:
- MSI Z68MA ED55 + i7-2600
- 2 Monitors driven by graphic signal from MSI board on-board graphic
- Debian Linux/Buster
- KDE Desktop via xorg
**Attachment 140150**, "/sys/class/drm/card/error":
[drm_error.txt](/uploads/4185e1abd236f541055d33208a696694/drm_error.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1732glxinfo and eglinfo reports error on mesa 18.1.x2020-02-28T13:15:59ZBugzilla Migration Userglxinfo and eglinfo reports error on mesa 18.1.x## Submitted by siy..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106882)](https://bugs.freedesktop.org/show_bug.cgi?id=106882)**
## Description
Version: 18.0## Submitted by siy..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106882)](https://bugs.freedesktop.org/show_bug.cgi?id=106882)**
## Description
Version: 18.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1731intel_miptree_map crash2020-01-03T11:04:31ZBugzilla Migration Userintel_miptree_map crash## Submitted by Marc-André Lureau `@elmarco`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106811)](https://bugs.freedesktop.org/show_bug.cgi?id=106811)**
## Description
When taking a screenshot with virt-vi...## Submitted by Marc-André Lureau `@elmarco`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106811)](https://bugs.freedesktop.org/show_bug.cgi?id=106811)**
## Description
When taking a screenshot with virt-viewer (spice with virgl enabled)
```
(gdb) bt
#0 0x00007fffa4f2621d in intel_miptree_map (brw=0x555555f4dc40, mt=0x0, level=0, slice=0, x=0, y=117, w=1024, h=768, mode=1, out_ptr=0x7fffffffbfe0, out_stride=0x7fffffffbfd8) at intel_mipmap_tree.c:3648
#1 0x00007fffa4f1b740 in intel_map_renderbuffer (ctx=0x555555f4dc40, rb=0x555555fe9510, x=0, y=117, w=1024, h=768, mode=1, out_map=0x7fffffffc080, out_stride=0x7fffffffc088) at intel_fbo.c:169
#2 0x00007fffa4b22541 in read_rgba_pixels (ctx=0x555555f4dc40, x=0, y=0, width=1024, height=768, format=6408, type=5121, pixels=0x555556634d80, packing=0x7fffffffc210) at main/readpix.c:464
#3 0x00007fffa4b23463 in _mesa_readpixels (ctx=0x555555f4dc40, x=0, y=0, width=1024, height=768, format=6408, type=5121, packing=0x7fffffffc210, pixels=0x555556634d80) at main/readpix.c:896
#4 0x00007fffa4f29fa1 in intelReadPixels (ctx=0x555555f4dc40, x=0, y=0, width=1024, height=768, format=6408, type=5121, pack=0x7fffffffc210, pixels=0x555556634d80) at intel_pixel_read.c:296
#5 0x00007fffa4b2451f in read_pixels (no_error=false, pixels=0x555556634d80, bufSize=2147483647, type=5121, format=6408, height=768, width=1024, y=0, x=0) at main/readpix.c:1136
#6 0x00007fffa4b2451f in _mesa_ReadnPixelsARB (x=0, y=0, width=1024, height=768, format=6408, type=5121, bufSize=2147483647, pixels=0x555556634d80) at main/readpix.c:1153
#7 0x00007fffa4b245b9 in _mesa_ReadPixels (x=0, y=0, width=1024, height=768, format=6408, type=5121, pixels=0x555556634d80) at main/readpix.c:1168
#8 0x00007ffff7f85521 in spice_display_get_pixbuf (display=<optimized out>) at spice-widget.c:3173
#9 0x0000555555574464 in virt_viewer_window_menu_file_screenshot ()
#10 0x00007ffff4238add in g_closure_invoke () at /lib64/libgobject-2.0.so.0
#11 0x00007ffff424bf43 in () at /lib64/libgobject-2.0.so.0
#12 0x00007ffff425506a in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#13 0x00007ffff4255663 in g_signal_emit () at /lib64/libgobject-2.0.so.0
#14 0x00007ffff6397732 in gtk_widget_activate () at /lib64/libgtk-3.so.0
#15 0x00007ffff6264c76 in gtk_menu_shell_activate_item () at /lib64/libgtk-3.so.0
#16 0x00007ffff6264f13 in gtk_menu_shell_button_release () at /lib64/libgtk-3.so.0
#17 0x00007ffff62477a8 in _gtk_marshal_BOOLEAN__BOXEDv () at /lib64/libgtk-3.so.0
#18 0x00007ffff4238d36 in () at /lib64/libgobject-2.0.so.0
#19 0x00007ffff4254ae4 in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#20 0x00007ffff4255663 in g_signal_emit () at /lib64/libgobject-2.0.so.0
#21 0x00007ffff6395134 in gtk_widget_event_internal () at /lib64/libgtk-3.so.0
#22 0x00007ffff62445d6 in propagate_event () at /lib64/libgtk-3.so.0
#23 0x00007ffff6246793 in gtk_main_do_event () at /lib64/libgtk-3.so.0
#24 0x00007ffff5d4f639 in _gdk_event_emit () at /lib64/libgdk-3.so.0
#25 0x00007ffff5dabac6 in gdk_event_source_dispatch () at /lib64/libgdk-3.so.0
#26 0x00007ffff3f5d8ad in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#27 0x00007ffff3f5dc78 in () at /lib64/libglib-2.0.so.0
#28 0x00007ffff3f5dd10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#29 0x00007ffff4521675 in g_application_run () at /lib64/libgio-2.0.so.0
#30 0x0000555555566980 in main ()
#0 0x00007fffa4f2621d in intel_miptree_map (brw=0x555555f4dc40, mt=0x0, level=0, slice=0, x=0, y=117, w=1024, h=768, mode=1, out_ptr=0x7fffffffbfe0, out_stride=0x7fffffffbfd8) at intel_mipmap_tree.c:3648
3648 assert(mt->surf.samples == 1);
```
mt is NULL
spice-gtk code triggering the crash:
data = g_malloc0(d->area.width * d->area.height * 4);
glReadBuffer(GL_FRONT);
glPixelStorei(GL_UNPACK_ALIGNMENT, 1);
glReadPixels(0, 0, d->area.width, d->area.height,
GL_RGBA, GL_UNSIGNED_BYTE, data);https://gitlab.freedesktop.org/mesa/mesa/-/issues/1730intelReadPixels: fallback to CPU mapping in PBO case for Z24S8 attachments2019-10-03T20:46:23ZBugzilla Migration UserintelReadPixels: fallback to CPU mapping in PBO case for Z24S8 attachments## Submitted by Markus Wick
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106800)](https://bugs.freedesktop.org/show_bug.cgi?id=106800)**
## Description
Created attachment 139997
Apitrace dump of citra showi...## Submitted by Markus Wick
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106800)](https://bugs.freedesktop.org/show_bug.cgi?id=106800)**
## Description
Created attachment 139997
Apitrace dump of citra showing the performance issue
Hi,
calling glReadPixels for the GL_DEPTH24_STENCIL8 attachment and the GL_DEPTH_STENCIL / GL_UNSIGNED_INT_24_8 format seems to stall the GPU, even if a PBO is bound. 92% of my CPU time is spend in intel_miptree_map.
I guess i965 lacks a copy shader for the tiled Z24S8 attachment to the linear TBO buffer.
Tests was done on: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2)
and mesa: 4affeba1e9eb426a1ba13a3e8ced4673c4bb9b34
An apitrace dump which highlights this issue in the last frames is attached.
**Attachment 139997**, "Apitrace dump of citra showing the performance issue":
[citra-qt.trace](/uploads/26b9144dca74e6b77b239276089249fb/citra-qt.trace)
Version: git