mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2022-06-06T08:24:40Zhttps://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/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/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/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/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/1727Upgrade to 18.0 completely breaks gnome-shell2022-06-02T22:12:24ZBugzilla Migration UserUpgrade to 18.0 completely breaks gnome-shell## Submitted by Dustin Phipps
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106556)](https://bugs.freedesktop.org/show_bug.cgi?id=106556)**
## Description
After upgrading to mesa 18.0, gnome-shell crashes im...## Submitted by Dustin Phipps
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106556)](https://bugs.freedesktop.org/show_bug.cgi?id=106556)**
## Description
After upgrading to mesa 18.0, gnome-shell crashes immediately upon starting (before the GDM login prompt). I'm running Arch Linux with Gnome 3.28 on a Lenovo P51 with hybrid graphics. Here are the relevant bits from lspci:
01:00.0 3D controller: NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] (rev a1)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
The following is a stack trace captured from journalctl:
May 17 11:34:07 bubo systemd-coredump[882]: Process 778 (gnome-shell) of user 120 dumped core.
Stack trace of thread 778:
#0 0x00007f627934f860 raise (libc.so.6)
#1 0x00007f6279350ec9 abort (libc.so.6)
#2 0x00007f6279392437 __libc_message (libc.so.6)
#3 0x00007f627939878b malloc_printerr (libc.so.6)
#4 0x00007f6279398c3c munmap_chunk (libc.so.6)
#5 0x00007f625267ee84 n/a (i965_dri.so)
#6 0x00007f62524ecad8 n/a (i965_dri.so)
#7 0x00007f6252595530 n/a (i965_dri.so)
#8 0x00007f6253ddce18 n/a (libEGL_mesa.so.0)
#9 0x00007f6253dd405b eglCreateContext (libEGL_mesa.so.0)
#10 0x00007f6275ba799e n/a (libmutter-cogl-2.so)
#11 0x00007f6275b5dcd6 cogl_display_setup (libmutter-cogl-2.so)
#12 0x00007f6275b5d01b cogl_renderer_check_onscreen_template (libmutter-cogl-2.so)
#13 0x00007f62772af0ff n/a (libmutter-clutter-2.so)
#14 0x00007f62772c8765 n/a (libmutter-clutter-2.so)
#15 0x00007f62772dc6cb n/a (libmutter-clutter-2.so)
#16 0x00007f62772dc898 n/a (libmutter-clutter-2.so)
#17 0x00007f6278622aef g_option_context_parse (libglib-2.0.so.0)
#18 0x00007f62772dd6c5 clutter_init (libmutter-clutter-2.so)
#19 0x00007f6276ac9d78 meta_clutter_init (libmutter-2.so.0)
#20 0x00007f6276b12e2e meta_init (libmutter-2.so.0)
#21 0x000056395e8aecda n/a (gnome-shell)
#22 0x00007f627933bf4a __libc_start_main (libc.so.6)
#23 0x000056395e8af14a n/a (gnome-shell)
Stack trace of thread 806:
#0 0x00007f627940697b __poll (libc.so.6)
#1 0x00007f6278616523 n/a (libglib-2.0.so.0)
#2 0x00007f627861663e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f6278616692 n/a (libglib-2.0.so.0)
#4 0x00007f627863ea2a n/a (libglib-2.0.so.0)
#5 0x00007f62796d908c start_thread (libpthread.so.0)
#6 0x00007f6279410e7f __clone (libc.so.6)
Stack trace of thread 871:
#0 0x00007f627940697b __poll (libc.so.6)
#1 0x00007f6278616523 n/a (libglib-2.0.so.0)
#2 0x00007f627861663e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f6260963f4e n/a (libdconfsettings.so)
#4 0x00007f627863ea2a n/a (libglib-2.0.so.0)
#5 0x00007f62796d908c start_thread (libpthread.so.0)
#6 0x00007f6279410e7f __clone (libc.so.6)
Stack trace of thread 870:
#0 0x00007f627940b879 syscall (libc.so.6)
#1 0x00007f627865d52d g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f62785e8903 n/a (libglib-2.0.so.0)
#3 0x00007f627863f436 n/a (libglib-2.0.so.0)
#4 0x00007f627863ea2a n/a (libglib-2.0.so.0)
#5 0x00007f62796d908c start_thread (libpthread.so.0)
#6 0x00007f6279410e7f __clone (libc.so.6)
Stack trace of thread 807:
#0 0x00007f627940697b __poll (libc.so.6)
#1 0x00007f6278616523 n/a (libglib-2.0.so.0)
#2 0x00007f62786168e2 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f6278c05348 n/a (libgio-2.0.so.0)
#4 0x00007f627863ea2a n/a (libglib-2.0.so.0)
#5 0x00007f62796d908c start_thread (libpthread.so.0)
#6 0x00007f6279410e7f __clone (libc.so.6)
-- Subject: Process 778 (gnome-shell) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 778 (gnome-shell) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Version: 18.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1724[snb] GPU HANG: ecode 6:0:0x85fffffc in ositorWorkQueue2022-06-02T23:24:13ZBugzilla Migration User[snb] GPU HANG: ecode 6:0:0x85fffffc in ositorWorkQueue## Submitted by James
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106495)](https://bugs.freedesktop.org/show_bug.cgi?id=106495)**
## Description
Created attachment 139534
sysfs dump
Watching a video in To...## Submitted by James
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106495)](https://bugs.freedesktop.org/show_bug.cgi?id=106495)**
## Description
Created attachment 139534
sysfs dump
Watching a video in Totem under Gnome 3 in X. Screen froze for a few seconds, then unfroze. Caught the following in dmesg:
[46336.090639] [drm] GPU HANG: ecode 6:0:0x85fffffc, in ositorWorkQueue [8616], reason: Hang on rcs0, action: reset
[46336.090642] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[46336.090642] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[46336.090643] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[46336.090643] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[46336.090644] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[46336.090698] i915 0000:00:02.0: Resetting chip after gpu hang
I was rendering something with Kdenlive at the time, but I didn't see any excessive heat or anything.
**Attachment 139534**, "sysfs dump":
[915dump](/uploads/9de9ce84316741cf153d85238f33b4d3/915dump)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1723No test for Image Load/Store on texture buffer sized greater than MAX_TEXTURE...2022-04-12T23:09:28ZBugzilla Migration UserNo test for Image Load/Store on texture buffer sized greater than MAX_TEXTURE_BUFFER_SIZE_ARB## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106481)](https://bugs.freedesktop.org/show_bug.cgi?id=106481)**
## Description
From the ARB_texture_buffer_object extensio...## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106481)](https://bugs.freedesktop.org/show_bug.cgi?id=106481)**
## Description
From the ARB_texture_buffer_object extension spec:
While buffer textures can be substantially larger than equivalent
one-dimensional textures; the maximum texture size supported for buffer
textures in the initial implementation of this extension is 2^27 texels,
versus 2^13 (8192) texels for otherwise equivalent one-dimensional
textures. [...]
There's a bug in i965, that allows the creation of buffer surface states with sizes greater than 2^27 texels when doing image load/store operations on texture buffers. This patch fixes the issue: https://patchwork.freedesktop.org/patch/211341/
There doesn't seem to be any piglit tests which exercise this path. We should create one to prevent this bug from showing up again.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1722[skl] GPU HANG: ecode 9:0:0x859ffffb, in Xorg2022-06-02T22:12:54ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x859ffffb, in Xorg## Submitted by Simeon Miteff
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106443)](https://bugs.freedesktop.org/show_bug.cgi?id=106443)**
## Description
Created attachment 139429
GPU crash dump
I get GPU ...## Submitted by Simeon Miteff
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106443)](https://bugs.freedesktop.org/show_bug.cgi?id=106443)**
## Description
Created attachment 139429
GPU crash dump
I get GPU hangs on Sky Lake integrated graphics when not booting with either:
i915.modeset=0
or
video=vesafb:off
The hardware is a Dell 7040 with Intel i7-6700 CPU.
Xorg does not crash, but everything except the cursor locks up each time the GPU resets. Here his the drm message:
[ 41.823218] [drm] GPU HANG: ecode 9:0:0x859ffffb, in Xorg [2092], reason: hang on rcs0, action: reset
[ 41.823219] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 41.823220] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 41.823220] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 41.823220] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 41.823221] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Subsequent to this there are frequent repeated resets:
[ 92.731613] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 100.731570] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 108.731500] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 116.731410] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 606.840675] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 617.816522] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 625.816467] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 633.816354] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
Kernel: 4.17.0
Xorg server: 1.19.6
Intel driver: 2.99.917+git20171229-1
Mesa: 18.0.0
GuC firmware: i915/skl_guc_ver9_33.bin
HuC firmware: i915/skl_huc_ver01_07_1398.bin
I started out with a stock Ubuntu Xenial and progressively upgraded bits with no avail. Turning off modeset/vesafb was an acceptable solution until I needed dual display support.
GPU crash dump is attached
**Attachment 139429**, "GPU crash dump":
[gpu_error.txt](/uploads/b5b1a672c924a57aa57f614807a5de9a/gpu_error.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1719[skl] GPU HANG: ecode 9:0:0x86dffffd, in X (libreoffice)2022-06-02T23:26:25ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x86dffffd, in X (libreoffice)## Submitted by adrian.hospodar@gmail.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106214)](https://bugs.freedesktop.org/show_bug.cgi?id=106214)**
## Description
Frequently X crashes when using LibreOff...## Submitted by adrian.hospodar@gmail.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106214)](https://bugs.freedesktop.org/show_bug.cgi?id=106214)**
## Description
Frequently X crashes when using LibreOffice Impress.
Apr 24 17:14:12 linux-bub9 org.a11y.atspi.Registry[4327]: after 429 requests (429 known processed) with 0 events remaining.
Apr 24 17:14:12 linux-bub9 org.a11y.atspi.Registry[4327]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Apr 24 17:14:12 linux-bub9 polkitd[1103]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.58, object path /org/kde/PolicyKit1/Authent
Apr 24 17:14:12 linux-bub9 org.kde.kglobalaccel[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.KScreen[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.kwalletd5[3692]: The X11 connection broke (error 1). Did the X11 server die?
Apr 24 17:14:12 linux-bub9 org.kde.kuiserver[3692]: kuiserver: Fatal IO error: client killed
Apr 24 17:14:12 linux-bub9 bluetoothd[1029]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSink
Apr 24 17:14:12 linux-bub9 bluetoothd[1029]: Endpoint unregistered: sender=:1.65 path=/MediaEndpoint/A2DPSource
Apr 24 17:14:12 linux-bub9 kernel: [drm] GuC firmware load skipped
Apr 24 17:14:12 linux-bub9 kernel: [drm] RC6 on
Apr 24 17:14:12 linux-bub9 kernel: drm/i915: Resetting chip after gpu hang
Apr 24 17:14:02 linux-bub9 kernel: [drm] GuC firmware load skipped
Apr 24 17:14:02 linux-bub9 kernel: [drm] RC6 on
Apr 24 17:14:02 linux-bub9 kernel: drm/i915: Resetting chip after gpu hang
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Apr 24 17:14:02 linux-bub9 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Apr 24 17:14:02 linux-bub9 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Apr 24 17:14:02 linux-bub9 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Apr 24 17:14:02 linux-bub9 kernel: [drm] GPU HANG: ecode 9:0:0x86dffffd, in X [3600], reason: Hang on render ring, action: reset
GPU crash dump is supposedly saved to /sys/class/drm/card0/error, but the file is empty.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1718[CNL-Y] GPU hang2019-09-26T16:57:11ZBugzilla Migration User[CNL-Y] GPU hang## Submitted by Timo Aaltonen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106185)](https://bugs.freedesktop.org/show_bug.cgi?id=106185)**
## Description
Created attachment 138994
gpu dump
I'm seeing hangs...## Submitted by Timo Aaltonen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106185)](https://bugs.freedesktop.org/show_bug.cgi?id=106185)**
## Description
Created attachment 138994
gpu dump
I'm seeing hangs if the GPU is enabled on a CNL-Y SDP (UMCY2SNEP). I've also suspected general HW failure, but after re-seating the CPU and torturing it with stock-ish 4.15 on Ubuntu bionic I'm not able to hang the machine.
Attached is one GPU dump I was able to get with a -nightly kernel from Apr 18. Mesa version is 18.0.0.
**Attachment 138994**, "gpu dump":
[gpu-dump.txt](/uploads/b4442aad000f30c70bee3e1d9ff794e6/gpu-dump.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/17178064px Max OpenGL window resolution i9652019-11-04T16:20:36ZBugzilla Migration User8064px Max OpenGL window resolution i965## Submitted by Inad
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106145)](https://bugs.freedesktop.org/show_bug.cgi?id=106145)**
## Description
Hello,
I have a problem creating an OpenGL window greater th...## Submitted by Inad
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106145)](https://bugs.freedesktop.org/show_bug.cgi?id=106145)**
## Description
Hello,
I have a problem creating an OpenGL window greater than 8064 with DRI / i965
glxgears -geometry 8064x2160 with Intel DRI works fine
glxgears -geometry 8065x2160 with Intel DRI causes corruption in the image
With the classic swrast it works correctly.
I think that with Mesa 13 versions it worked with intel well
Thank you
Version: 18.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1716draw does not work in a simple example2022-06-02T22:13:02ZBugzilla Migration Userdraw does not work in a simple example## Submitted by xinghua
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106123)](https://bugs.freedesktop.org/show_bug.cgi?id=106123)**
## Description
Created attachment 138904
source code of example
I found ...## Submitted by xinghua
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106123)](https://bugs.freedesktop.org/show_bug.cgi?id=106123)**
## Description
Created attachment 138904
source code of example
I found a issue in ANGLE project that draw does not work, and had written a simple example to reproduce this issue, attachment is the source code.
Steps:
1. gcc -o srgb srgb.c -lX11 -lepoxy
2. ./srgb
I had used readPixels to get fbo content and wrote content to files in current directory, the name is "result_1/2/3/4.rgba", These files were all empty, it seems that mesa did draw nothing.
The same case had run on NVIDIA GPU, which draw something normally.
I had spent some time to debug it, but did not find the root cause. Please help me to check it, thank you.
**Attachment 138904**, "source code of example":
[srgb.c](/uploads/ddb15a96a9c630a6251ab73baf3f05bd/srgb.c)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1715Corruption with Firefox after upgrade to 18.0.02022-06-02T22:13:16ZBugzilla Migration UserCorruption with Firefox after upgrade to 18.0.0## Submitted by Timo Aaltonen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106035)](https://bugs.freedesktop.org/show_bug.cgi?id=106035)**
## Description
I've recently upgraded my devel desktop to Ubuntu bi...## Submitted by Timo Aaltonen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106035)](https://bugs.freedesktop.org/show_bug.cgi?id=106035)**
## Description
I've recently upgraded my devel desktop to Ubuntu bionic (~18.04) which comes with Mesa 18.0.0. Now I'm seeing some corruption with Firefox, like the white blobs on this video:
https://www.youtube.com/watch?v=u9EMkuZ9Frk
I also get it sometimes when playing youtube videos, and then the blobs are more colorful..
I didn't have this with 17.2.8 before upgrade. Also, I haven't seen this on my KBL laptop, while this desktop is SKL.. both running same versions of everything.
Version: 18.0