mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2022-06-02T22:06:59Zhttps://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/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/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/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/1795src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1970: intel_miptree_has_color_u...2022-06-06T08:10:55ZBugzilla Migration Usersrc/mesa/drivers/dri/i965/intel_mipmap_tree.c:1970: intel_miptree_has_color_unresolved: Assertion `aux_state != ISL_AUX_STATE_AUX_INVALID' failed.## Submitted by Sergey Alirzaev
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109826)](https://bugs.freedesktop.org/show_bug.cgi?id=109826)**
## Description
Occurs in compton on my Kaby Lake R laptop when i ...## Submitted by Sergey Alirzaev
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109826)](https://bugs.freedesktop.org/show_bug.cgi?id=109826)**
## Description
Occurs in compton on my Kaby Lake R laptop when i run compton and then i3lock-color --composite. Backtrace:
```
#0 0x00007f30d068c45b in raise () from /lib64/libc.so.6
#1 0x00007f30d0675535 in abort () from /lib64/libc.so.6
#2 0x00007f30d067540f in __assert_fail_base.cold.0 () from /lib64/libc.so.6
#3 0x00007f30d0683d92 in __assert_fail () from /lib64/libc.so.6
#4 0x00007f30cecdb2f4 in intel_miptree_has_color_unresolved (mt=mt@entry=0x55f8b1925cd0, start_level=start_level@entry=0, num_levels=num_levels@entry=4294967295, start_layer=start_layer@entry=0, num_layers=num_layers@entry=4294967295)
at ../mesa-9999/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1942
#5 0x00007f30cecdd259 in intel_miptree_texture_aux_usage (brw=brw@entry=0x55f8b1666570, mt=mt@entry=0x55f8b1925cd0, view_format=view_format@entry=ISL_FORMAT_B8G8R8A8_UNORM,
astc5x5_wa_bits=astc5x5_wa_bits@entry=GEN9_ASTC5X5_WA_TEX_TYPE_AUX) at ../mesa-9999/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:2587
#6 0x00007f30cecdd2f5 in intel_miptree_prepare_texture (brw=brw@entry=0x55f8b1666570, mt=0x55f8b1925cd0, view_format=view_format@entry=ISL_FORMAT_B8G8R8A8_UNORM, start_level=start_level@entry=0, num_levels=num_levels@entry=1,
start_layer=start_layer@entry=0, num_layers=4294967295, astc5x5_wa_bits=GEN9_ASTC5X5_WA_TEX_TYPE_AUX) at ../mesa-9999/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:2627
#7 0x00007f30ceca9085 in brw_predraw_resolve_inputs (brw=brw@entry=0x55f8b1666570, rendering=rendering@entry=true, draw_aux_buffer_disabled=draw_aux_buffer_disabled@entry=0x7fff1c907040)
at ../mesa-9999/src/mesa/drivers/dri/i965/brw_draw.c:537
#8 0x00007f30ceca94d6 in brw_prepare_drawing (ctx=ctx@entry=0x55f8b1666570, ib=ib@entry=0x0, index_bounds_valid=index_bounds_valid@entry=true, min_index=0, max_index=3) at ../mesa-9999/src/mesa/drivers/dri/i965/brw_draw.c:846
#9 0x00007f30ceca96d2 in brw_draw_prims (ctx=0x55f8b1666570, prims=0x55f8b169c368, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=<optimized out>, max_index=<optimized out>, gl_xfb_obj=0x0, stream=0, indirect=0x0)
at ../mesa-9999/src/mesa/drivers/dri/i965/brw_draw.c:1138
#10 0x00007f30cedf5986 in vbo_exec_vtx_flush (exec=exec@entry=0x55f8b169bb70, keepUnmapped=keepUnmapped@entry=1 '\001') at ../mesa-9999/src/mesa/vbo/vbo_exec_draw.c:388
#11 0x00007f30cedd510c in vbo_exec_FlushVertices_internal (exec=0x55f8b169bb70, unmap=unmap@entry=1 '\001') at ../mesa-9999/src/mesa/vbo/vbo_exec_api.c:638
#12 0x00007f30cedf4bab in vbo_exec_FlushVertices (ctx=ctx@entry=0x55f8b1666570, flags=flags@entry=1) at ../mesa-9999/src/mesa/vbo/vbo_exec_api.c:1256
#13 0x00007f30cedb00e3 in bind_texture_object (ctx=ctx@entry=0x55f8b1666570, unit=0, texObj=texObj@entry=0x55f8b151ebb0) at ../mesa-9999/src/mesa/main/texobj.c:1674
#14 0x00007f30cedb1856 in bind_texture (no_error=false, texName=0, target=3553, ctx=0x55f8b1666570) at ../mesa-9999/src/mesa/main/texobj.c:1787
#15 _mesa_BindTexture (target=3553, texName=0) at ../mesa-9999/src/mesa/main/texobj.c:1807
#16 0x000055f8b106dd57 in glx_render_ ()
#17 0x000055f8b105cfa0 in render_ ()
#18 0x000055f8b1064c2f in paint_all ()
#19 0x000055f8b10599d9 in main ()
```
Version: githttps://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: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1789[CI] spec@arb_texture_float@multisample-formats [48] (gl_arb_texture_float|gl...2023-07-27T10:29:12ZBugzilla Migration User[CI] spec@arb_texture_float@multisample-formats [48] (gl_arb_texture_float|gl_ext_packed_float) - fail## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109643)](https://bugs.freedesktop.org/show_bug.cgi?id=109643)**
## Description
The following tests failed on the same run o...## Submitted by Martin Peres `@mupuf`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109643)](https://bugs.freedesktop.org/show_bug.cgi?id=109643)**
## Description
The following tests failed on the same run on our pig-hsw-4770r machine:
spec@ext_packed_float@multisample-formats 4 gl_ext_packed_float
Using test set: GL_EXT_packed_float
Testing GL_R11F_G11F_B10F
Probe at (156,226)
Expected: 0.000000 0.000000 0.000000
Observed: 0.275000 0.005566 0.712500
spec@arb_texture_float@multisample-formats 8 gl_arb_texture_float
Using test set: GL_ARB_texture_float
Testing GL_RGB16F
Probe at (156,226)
Expected: 0.000000 0.000000 0.000000
Observed: 0.275195 0.005859 0.719141
Testing GL_RGBA16F
Testing GL_ALPHA16F_ARB
Unsupported framebuffer combination
Testing GL_LUMINANCE16F_ARB
Testing GL_LUMINANCE_ALPHA16F_ARB
Unsupported framebuffer combination
Testing GL_INTENSITY16F_ARB
Testing GL_RGB32F
Unsupported framebuffer combination
Testing GL_RGBA32F
Unsupported framebuffer combination
Testing GL_ALPHA32F_ARB
Unsupported framebuffer combination
Testing GL_LUMINANCE32F_ARB
Testing GL_LUMINANCE_ALPHA32F_ARB
Unsupported framebuffer combination
Testing GL_INTENSITY32F_ARB
More info about the machine: https://intel-gfx-ci.01.org/hardware/pig-hsw-4770r/
Version: 18.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1788[ICL] piglit.spec.arb_compute_shader.render-and-compute GPU hang under load2022-06-02T23:18:22ZBugzilla Migration User[ICL] piglit.spec.arb_compute_shader.render-and-compute GPU hang under load## Submitted by Mark Janes `@majanes`
Assigned to **Anuj Phogat `@aphogat`**
**[Link to original bug (#109549)](https://bugs.freedesktop.org/show_bug.cgi?id=109549)**
## Description
This test passes reliably by itself.
However, i...## Submitted by Mark Janes `@majanes`
Assigned to **Anuj Phogat `@aphogat`**
**[Link to original bug (#109549)](https://bugs.freedesktop.org/show_bug.cgi?id=109549)**
## Description
This test passes reliably by itself.
However, if you run the test while the piglit suite is running, it will quickly generate a gpu hang.
To reproduce: in one window, execute the test in a loop:
$ for ((;;)) do arb_compute_shader-render-and-compute -auto -fbo; done
Run `dmesg -w` to watch for gpu hangs
In a second window, run piglit. GPU Hang will be produced within a few tests.Anuj PhogatAnuj Phogathttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1787GPU HANG: ecode 9:0:0x84dffefc, in WizardOfLegend.2020-02-28T14:28:29ZBugzilla Migration UserGPU HANG: ecode 9:0:0x84dffefc, in WizardOfLegend.## Submitted by lor..@..rts.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109547)](https://bugs.freedesktop.org/show_bug.cgi?id=109547)**
## Description
Created attachment 143289
error log of gpu
gpu han...## Submitted by lor..@..rts.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109547)](https://bugs.freedesktop.org/show_bug.cgi?id=109547)**
## Description
Created attachment 143289
error log of gpu
gpu hangs wile playing
system architecture: Linux bartimaeus 4.20.6-arch1-1-ARCH #1 SMP PREEMPT Thu Jan 31 08:22:01 UTC 2019 x86_64 GNU/Linux
kernel version: 4.20.6-arch1-1-ARCH
Display connector: eDP1
**Attachment 143289**, "error log of gpu":
[gpu_hang](/uploads/364c9d1d0c35aaf600521a6fa3ad3a82/gpu_hang)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1786[GEN9+] 14-24% perf drop in SynMark2 v7 CSDof2022-08-01T11:46:14ZBugzilla Migration User[GEN9+] 14-24% perf drop in SynMark2 v7 CSDof## Submitted by Eero Tamminen
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#109517)](https://bugs.freedesktop.org/show_bug.cgi?id=109517)**
## Description
Mesa performance in SynMark2 v7 CSDof test dropped ...## Submitted by Eero Tamminen
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#109517)](https://bugs.freedesktop.org/show_bug.cgi?id=109517)**
## Description
Mesa performance in SynMark2 v7 CSDof test dropped 24% on SKL GT4e and 14-20% on other GEN9+ platforms.
Setup:
- Ubuntu 18.04
- Unity / compiz desktop
- Mesa from git
- X server and drm-tip kernel from git within last 1-2 months, with modifier support enabled
- FullHD monitor
Test-case:
- synmark2 OglCSDof
(configured to run in fullscreen FullHD resolution.)
Regression happened between following commits:
* 2019-01-28 17:50:08 41a0acd6a1: Switch imx to kmsro and remove the imx winsys
* 2019-01-30 17:49:45 f4eb746ef7: r600: add -Wstrict-overflow=0 to meson to silence the warning
CSDof compute shaders register spill, so a change to register usage (e.g. SENDS support which is GEN9+ specific) is likely cause for the perf regression.
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=110745Faith EkstrandFaith Ekstrandhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1784[skl] GPU HANG: ecode 9:0:0x86dffffd, in Xorg2022-06-02T23:20:07ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x86dffffd, in Xorg## Submitted by sin..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109510)](https://bugs.freedesktop.org/show_bug.cgi?id=109510)**
## Description
Created attachment 143258
This is /sys/class/drm/ca...## Submitted by sin..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109510)](https://bugs.freedesktop.org/show_bug.cgi?id=109510)**
## Description
Created attachment 143258
This is /sys/class/drm/card0/error
I was using Xilinx ISE 10.1 SP3 (x86_64) on my Arch Linux machine. I was drawing a wire while the user interface suddenly froze. I tried switching tabs (I'm using i3 as windows manager) but nothing happened. Then after a few seconds everything is back to normal. I checked the kernel log by typing dmesg, and discovered the following message. I thought it might be good to file a bug report.
[24917.579505] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [669], reason: hang on rcs0, action: reset
[24917.579506] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[24917.579507] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[24917.579507] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[24917.579508] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[24917.579508] [drm] GPU crash dump saved to /sys/class/drm/card0/error
**Attachment 143258**, "This is /sys/class/drm/card0/error":
[drm-error](/uploads/671e0d401349ca79b3ae23e77c8b1f8d/drm-error)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1783[snb] GPU HANG: ecode 6:0:0x85fffffc, in Civ4BeyondSword [1257]2022-06-02T22:08:59ZBugzilla Migration User[snb] GPU HANG: ecode 6:0:0x85fffffc, in Civ4BeyondSword [1257]## Submitted by kom..@..oho.eu
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109464)](https://bugs.freedesktop.org/show_bug.cgi?id=109464)**
## Description
Created attachment 143235
[drm] GPU crash dump save...## Submitted by kom..@..oho.eu
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109464)](https://bugs.freedesktop.org/show_bug.cgi?id=109464)**
## Description
Created attachment 143235
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 668.446232] [drm] GPU HANG: ecode 6:0:0x85fffffc, in Civ4BeyondSword [1257], reason: hang on rcs0, action: reset
[ 668.446235] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 668.446236] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 668.446236] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 668.446237] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 668.446238] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 668.446287] i915 0000:00:02.0: Resetting chip for hang on rcs0
**Attachment 143235**, "[drm] GPU crash dump saved to /sys/class/drm/card0/error":
[error20190127](/uploads/326d8fe95da7617115d6f197ffef4c56/error20190127)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1782[kbl] GPU hang in gnome-shell2022-06-02T23:18:59ZBugzilla Migration User[kbl] GPU hang in gnome-shell## Submitted by Nikola
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109250)](https://bugs.freedesktop.org/show_bug.cgi?id=109250)**
## Description
Created attachment 143021
dmesg error log with debugging en...## Submitted by Nikola
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109250)](https://bugs.freedesktop.org/show_bug.cgi?id=109250)**
## Description
Created attachment 143021
dmesg error log with debugging enabled
System works fine until I log in via GDM and try to do anything in the desktop environment. Then it freezes, it may seem to work after a few minutes but again if I try to open anything it will stop working. Weird small rectangles may show up on the screen.
dmesg shows that GPU is hanging.
It works fine without a UI, and also works fairly well in Windows.
Hardware: Thinkpad X1 Carbon 5th Gen
Distro: ArchLinux (build 01.01.2019) but same issue on other distros (Ubuntu,Mate,CentOS,etc)
Kernel: 4.20.0, but same issue on any kernel since 4.14 (haven't tried the older ones)
The only thing that makes it work, barely, is nomodeset. But that's not really a solution.
The attached error log is from ArchLinux running kernel 4.20.0.
The GPU in question:
0:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at eb000000 (64-bit, non-prefetchable) [size=16M]
Memory at 60000000 (64-bit, prefetchable) [size=256M]
I/O ports at e000 [size=64]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Kernel modules: i915
I've spent countless hours trying to figure out where the issue is and have made zero progress. Would really appreciate some help on this as it renders my laptop unusable.
**Attachment 143021**, "dmesg error log with debugging enabled":
[dmesg.log](/uploads/577abb556cf9a7196e6799ee8100fc2f/dmesg.log)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1780[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2087], reason: hang on rcs0, a...2022-06-02T22:09:21ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2087], reason: hang on rcs0, action: reset## Submitted by John M.
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109208)](https://bugs.freedesktop.org/show_bug.cgi?id=109208)**
## Description
Created attachment 142939
/sys/class/drm/card0/error
dmes...## Submitted by John M.
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109208)](https://bugs.freedesktop.org/show_bug.cgi?id=109208)**
## Description
Created attachment 142939
/sys/class/drm/card0/error
dmesg:
GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2087], reason: hang on rcs0, action: reset
GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
drm/i915 developers can then reassign to the right component if it's not a kernel issue.
...
exe[10465]: segfault at 968 ip 00007f227bb2c1d3 sp 00007ffe2fe8e020 error 4 in libX11.so.6.3.0[7f227bb03000+133000]
...
i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
Chrome_~dThread[13012]: segfault at 0 ip 00007fc6ec59f33d sp 00007fc6fe1ccae0 error 6 in libxul.so[7fc6eb854000+65d3000]
...
My kernel: 4.19.12-gnu
**Attachment 142939**, "/sys/class/drm/card0/error":
[drm-card0-error.txt](/uploads/5e4c077ed3aa8e90d6d934745c0bd7dc/drm-card0-error.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1779GPU HANG: ecode 9:0:0x85dffffb (esp. chrome with hardware-acceleration, also ...2021-09-08T07:55:01ZBugzilla Migration UserGPU HANG: ecode 9:0:0x85dffffb (esp. chrome with hardware-acceleration, also elsewhere) - UHD Graphics 620## Submitted by Christian Lohmaier `@cloph`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109170)](https://bugs.freedesktop.org/show_bug.cgi?id=109170)**
## Description
Created attachment 142908
/sys/class/d...## Submitted by Christian Lohmaier `@cloph`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#109170)](https://bugs.freedesktop.org/show_bug.cgi?id=109170)**
## Description
Created attachment 142908
/sys/class/drm/card0/error , hang triggered by chrome w/hw-accel on youtube
On a laptop with Intel Core i7-8550U and integrated UHD Graphics 620, I experience frequent hangs when using chrome browser watching youtube or using mpv to playback video.
If I disable use of hardware acceleration in chromium browser or force software decoding/rendering in mpv, the crashes are way less frequent.
With hardware-acceleration enabled I almost immediately get a gpu hang in chromebrowser when visiting youtube (starting a video is guaranteed to trigger)
Symptoms of hang differ from frozen image for a few seconds after which it recovers (although next error then only is a few minutes away, until it reaches a point where it cannot recover anymore), to complete freezes (still image shown, audio loops the last couple seconds, no reaction to keyboard whatsoever, cannot even use magic sysRq anymore) to crashes of Gnome3/wayland (can switch to virtual console and login/trigger reboot)
Distro: Mageia (Cauldron/development)
kernel: 4.19.12
mesa: 18.3.1
chromium-browsser: 70.0.3538.77
**Attachment 142908**, "/sys/class/drm/card0/error , hang triggered by chrome w/hw-accel on youtube":
[hw_accel_yt.error](/uploads/86a4900fa1724a31f910d10584d08b3a/hw_accel_yt.error)