mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2019-09-25T19:10:29Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1713µtox text rendering broken with glamor on gen52019-09-25T19:10:29ZBugzilla Migration Userµtox text rendering broken with glamor on gen5## Submitted by Clemens Eisserer
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105948)](https://bugs.freedesktop.org/show_bug.cgi?id=105948)**
## Description
Created attachment 138694
screenshot - no text vi...## Submitted by Clemens Eisserer
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105948)](https://bugs.freedesktop.org/show_bug.cgi?id=105948)**
## Description
Created attachment 138694
screenshot - no text visible
When running Xorg with glamor acceleration (this is what most distributions are shipping by default currently) text rendering within the utox application is broken.
The same application works fine when using the SNA backend as well as with glamor on top of radeonsi.
**Attachment 138694**, "screenshot - no text visible":
![utox_glamor](/uploads/b37d944f0cf98ab6f947e6f3088264b8/utox_glamor.png)
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1712[Gen9] ASTC texture downloads and CopyImage can fail2019-09-25T19:10:27ZBugzilla Migration User[Gen9] ASTC texture downloads and CopyImage can fail## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105853)](https://bugs.freedesktop.org/show_bug.cgi?id=105853)**
## Description
When uploading ASTC textures on gen9, we pe...## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105853)](https://bugs.freedesktop.org/show_bug.cgi?id=105853)**
## Description
When uploading ASTC textures on gen9, we perform a workaround that involves modifying the compressed blocks.
If these blocks are subsequently read via a texture download or CopyImage operation, the result would not match what the user uploaded.
Another reason that CopyImage can fail is that the needed workaround is not applied for CopyImage calls that have ASTC textures as the target. When the ASTC texture is later read, we may encounter a rendering issue.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1711[Gen7-8] Integer and snorm texture views can be incorrect2022-07-07T16:05:56ZBugzilla Migration User[Gen7-8] Integer and snorm texture views can be incorrect## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105826)](https://bugs.freedesktop.org/show_bug.cgi?id=105826)**
## Description
On BDW and earlier, fast-clear colors are l...## Submitted by Nanley Chery `@nchery`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105826)](https://bugs.freedesktop.org/show_bug.cgi?id=105826)**
## Description
On BDW and earlier, fast-clear colors are limited to 0 and a format-dependent 1 per-channel. For integer textures, the 1 equals 0x1 and for float textures the 1 equals 1.0f (0x3f80000). Due to the clear color value of 1 being interpreted differently for different formats, it should not be possible to use it without introducing resolves.
i965 currently allows fast-clearing a float texture to 1 but doesn't introduce a resolve when accessing the texture as an integer.
We can demonstrate the problem this causes by doing the following:
1. Fast clear an R32F texture to 1.0. For the purpose of this example, we make it 64x64px.
2. Create an R32UINT texture view from the R32F.
3. Render to the first row of the R32UINT. This will cause the HW to write out the fast clear color in the parts of the cacheline pairs not written to. Each CL Pair has a dimension of 8x4px.
4. Read back the texture as R32UINT.
5. Observe that the following 3 rows are equal to 1 instead of the 0x3f800000 it was cleared to in step 1.
We need write a bug to exercise this issue, and then fix it. The piglit test at:
tests/spec/arb_texture_view/rendering-r32ui.c looks like a good place to start.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1710[cfl] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg2022-06-02T22:13:27ZBugzilla Migration User[cfl] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg## Submitted by dr...@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105815)](https://bugs.freedesktop.org/show_bug.cgi?id=105815)**
## Description
Created attachment 138441
GPU crash dump
This GPU ...## Submitted by dr...@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105815)](https://bugs.freedesktop.org/show_bug.cgi?id=105815)**
## Description
Created attachment 138441
GPU crash dump
This GPU crash happened when I opened a new project in the IDEA IntelliJ application (https://www.jetbrains.com/idea/) which runs as a java process.
Java version on this machine:
ava(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
Here's the output of dmesg just before the crash
-------------------------------------------------
Mar 30 07:34:08 xxx.xxx.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostn
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [2225], reason: Hang on rcs0, action: reset
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU crash dump saved to /sys/class/drm/card1/error
Please find attached the crash report.
**Attachment 138441**, "GPU crash dump":
[drm_intel_crash.bz2](/uploads/9d3be626251ad0c955a0d30e07702e3b/drm_intel_crash.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1709[chv] GPU hangs/resets, sometimes locks completely, in kwin_x112020-06-15T16:37:38ZBugzilla Migration User[chv] GPU hangs/resets, sometimes locks completely, in kwin_x11## Submitted by Alex
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105810)](https://bugs.freedesktop.org/show_bug.cgi?id=105810)**
## Description
Created attachment 138429
dmesg
A laptop sometimes hangs wit...## Submitted by Alex
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105810)](https://bugs.freedesktop.org/show_bug.cgi?id=105810)**
## Description
Created attachment 138429
dmesg
A laptop sometimes hangs with GPU reset or might lock completely especially if I leave it turned on in sleep state over night. I'm not sure if it is the same issue because can't read dmesg output, the system doesn't react neither on sysrq nor ctrl-alt-f2, simply a blank screen.
I tried to add "intel_iommu=igfx_off" to kernel options without any luck, the issue still persists.
**Attachment 138429**, "dmesg":
[dmesg.crash.txt](/uploads/74313af7a86a0136863b62338698c39a/dmesg.crash.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1708[g33] piglit intermittent failure on spec.apple_object_purgeable.object_purge...2019-09-25T19:10:17ZBugzilla Migration User[g33] piglit intermittent failure on spec.apple_object_purgeable.object_purgeable-api-vbo## Submitted by clayton craft `@craftyguy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105721)](https://bugs.freedesktop.org/show_bug.cgi?id=105721)**
## Description
stdout from failing test:
Mesa: User e...## Submitted by clayton craft `@craftyguy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105721)](https://bugs.freedesktop.org/show_bug.cgi?id=105721)**
## Description
stdout from failing test:
Mesa: User error: GL_INVALID_VALUE in glObjectPurgeable(name = 0x0)
Mesa: User error: GL_INVALID_VALUE in glObjectUnpurgeable(name = 0x0)
Mesa: User error: GL_INVALID_VALUE in glGetObjectParameteriv(name = 0x0)
Mesa: User error: GL_INVALID_OPERATION in glObjectPurgeable(name = 0x1) is already purgeable
Mesa: User error: GL_INVALID_OPERATION in glObjectUnpurgeable(name = 0x1) object is already "unpurged"
Mesa: User error: GL_INVALID_OPERATION in glObjectPurgeable(name = 0x1) is already purgeable
glObjectUnpurgeableAPPLE:GL_UNDEFINED_APPLE: expected 0x8a1c (GL_UNDEFINED_APPLE), got 0x8a1b (GL_RETAINED_APPLE).Mesa: User error: GL_INVALID_OPERATION in glObjectUnpurgeable(name = 0x1) object is already "unpurged"
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1707[kbl] U HANG: ecode 9:0:0x00775757, in Worklog Assista2022-06-02T22:14:05ZBugzilla Migration User[kbl] U HANG: ecode 9:0:0x00775757, in Worklog Assista## Submitted by era..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105550)](https://bugs.freedesktop.org/show_bug.cgi?id=105550)**
## Description
Created attachment 138153
dump of gpu error state
...## Submitted by era..@..il.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105550)](https://bugs.freedesktop.org/show_bug.cgi?id=105550)**
## Description
Created attachment 138153
dump of gpu error state
Just seen this GPU-hanger once, will report back if it occurs again. The application was in the system tray and when I tried to open the window, the system seemed frozen for several seconds.
$ uname -a
Linux ch10dd405 4.9.76-realtime-1-rt61 #1 SMP PREEMPT RT Wed Jan 17 14:36:24 CET 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
$ lspci -v | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Device 5912 (rev 04) (prog-if 00 [VGA controller])
$ cat /proc/cpuinfo | grep "model name" -m 1
model name : Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
[145347.575536] [drm] GPU HANG: ecode 9:0:0x00775757, in Worklog Assista [18034], reason: Hang on render ring, action: reset
[145347.575540] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[145347.575540] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[145347.575540] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[145347.575541] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[145347.575543] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[145347.575581] drm/i915: Resetting chip after gpu hang
[145347.575621] [drm] RC6 on
[145347.593831] [drm] GuC firmware load skipped
[145359.543380] drm/i915: Resetting chip after gpu hang
[145359.543422] [drm] RC6 on
[145359.561485] [drm] GuC firmware load skipped
**Attachment 138153**, "dump of gpu error state":
[error.bz2](/uploads/9aaa0eab7810b1f3383c36a2d7428ffb/error.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1706[IVB] [Mesa 17.3.6] GPU HANG: ecode 7:0:0x86edbff1, in Fallout4.exe, reason: ...2022-06-02T22:14:27ZBugzilla Migration User[IVB] [Mesa 17.3.6] GPU HANG: ecode 7:0:0x86edbff1, in Fallout4.exe, reason: Hang on rcs0, action: reset## Submitted by Andrew Agafonov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105491)](https://bugs.freedesktop.org/show_bug.cgi?id=105491)**
## Description
Fallout 4 in wine-staging 3.3.
Crash in random pl...## Submitted by Andrew Agafonov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105491)](https://bugs.freedesktop.org/show_bug.cgi?id=105491)**
## Description
Fallout 4 in wine-staging 3.3.
Crash in random places with "[drm] GPU HANG: ecode 7:0:0x86edbff1, in Fallout4.exe [12513], reason: Hang on rcs0, action: reset" in dmesg and "i965: Failed to submit batchbuffer: Input/output error" in konsole.
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1705GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1068], reason: Hang on rcs0, action:...2022-06-02T22:14:52ZBugzilla Migration UserGPU HANG: ecode 9:0:0x85dffffb, in Xorg [1068], reason: Hang on rcs0, action: reset## Submitted by bru..@..ys.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105486)](https://bugs.freedesktop.org/show_bug.cgi?id=105486)**
## Description
My X server crashes occasionally, with no reproduci...## Submitted by bru..@..ys.com
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105486)](https://bugs.freedesktop.org/show_bug.cgi?id=105486)**
## Description
My X server crashes occasionally, with no reproducible activities. Here is what I found in the /var/log/messages:
Mar 13 11:44:00 cannes kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1068], reason: Hang on rcs0, action: reset
Mar 13 11:44:00 cannes kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 13 11:44:00 cannes kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 13 11:44:00 cannes kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 13 11:44:00 cannes kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar 13 11:44:00 cannes kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar 13 11:44:00 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:08 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:16 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:24 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:32 cannes kernel: i915 0000:00:02.0: Resetting rcs0 after gpu hang
Mar 13 11:44:33 cannes journal[5403]: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 13 11:44:33 cannes at-spi-bus-launcher[2217]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Mar 13 11:44:33 cannes at-spi-bus-launcher[2217]: after 134897 requests (134897 known processed) with 0 events remaining.
Mar 13 11:44:34 cannes journal[2514]: cinnamon-screensaver-main.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 13 11:44:34 cannes kdm[1049]: X server for display :0 terminated unexpectedly
Mar 13 11:44:34 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 13 11:44:34 cannes kernel: show_signal_msg: 3 callbacks suppressed
Mar 13 11:44:34 cannes kernel: SHCLIP[6438]: segfault at 5815b590 ip 00007fe21fa46f05 sp 00007fe116022a30 error 4 in libc-2.25.so[7fe21fa0c000+1cb000]
Mar 13 11:44:34 cannes audit[6088]: ANOM_ABEND auid=2053 uid=2053 gid=2001 ses=1 pid=6088 comm="SHCLIP" exe="/usr/lib64/virtualbox/VirtualBox" sig=11 res=1
Mar 13 11:44:35 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Unit entered failed state.
Mar 13 11:44:35 cannes systemd[1799]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Mar 13 11:44:35 cannes python3[20342]: The X11 connection broke (error 1). Did the X11 server die?https://gitlab.freedesktop.org/mesa/mesa/-/issues/1704Save/restore gen program for ARB_get_program_binary2019-09-25T21:19:56ZBugzilla Migration UserSave/restore gen program for ARB_get_program_binary## Submitted by Jordan Justen `@jljusten`
Assigned to **Jordan Justen `@jljusten`**
**[Link to original bug (#105445)](https://bugs.freedesktop.org/show_bug.cgi?id=105445)**
## Description
Currently we only save/restore the NIR pr...## Submitted by Jordan Justen `@jljusten`
Assigned to **Jordan Justen `@jljusten`**
**[Link to original bug (#105445)](https://bugs.freedesktop.org/show_bug.cgi?id=105445)**
## Description
Currently we only save/restore the NIR program when GetProgramBinary
and ProgramBinary are called. We should also save the gen program
for the default key/program.
I have started working on this in this branch:
git://people.freedesktop.org/~jljusten/mesa i965-get-program-binary-gen
Version: gitJordan JustenJordan Justenhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1703[hsw] GPU HANG in paraview2022-06-02T22:15:04ZBugzilla Migration User[hsw] GPU HANG in paraview## Submitted by Giuseppe Bilotta `@bilog`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105397)](https://bugs.freedesktop.org/show_bug.cgi?id=105397)**
## Description
Created attachment 137889
/sys/class/drm...## Submitted by Giuseppe Bilotta `@bilog`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105397)](https://bugs.freedesktop.org/show_bug.cgi?id=105397)**
## Description
Created attachment 137889
/sys/class/drm/card0/error contents
I just experienced this while using Paraview to visualize a largish dataset (some time after the hang and reset, PV crashed).
This is a Dell XPS 15 9530 featuring an i7-4712HQ CPU @ 2.30GHz, running Debian unstable
uname -a: Linux oblomov 4.15.0-1-amd64 #1 SMP Debian 4.15.4-1 (2018-02-18) x86_64 GNU/Linux
* paraview 5.4.1+dfsg3-1+b2
* xorg 1:7.7+19
* mesa 17.3.6-1
* libdrm-intel1 2.4.90-1
The crash dump is attached.
**Attachment 137889**, "/sys/class/drm/card0/error contents":
[drm-card0-error.log](/uploads/865f5e629a4a1dd270c6ab6bb6fbe20f/drm-card0-error.log)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1702[snb] GPU HANG: ecode 6:0:0x86f2fffe, in chrome2022-06-02T22:15:28ZBugzilla Migration User[snb] GPU HANG: ecode 6:0:0x86f2fffe, in chrome## Submitted by Steve Newcomb
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105331)](https://bugs.freedesktop.org/show_bug.cgi?id=105331)**
## Description
Created attachment 137761
GPU crash dump
Mar 2 13:...## Submitted by Steve Newcomb
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105331)](https://bugs.freedesktop.org/show_bug.cgi?id=105331)**
## Description
Created attachment 137761
GPU crash dump
Mar 2 13:17:50 carp kernel: [156478.322197] [drm] stuck on render ring
Mar 2 13:17:50 carp kernel: [156478.323481] [drm] GPU HANG: ecode 6:0:0x86f2fffe, in chrome [5756], reason: Ring hung, action: reset
Mar 2 13:17:50 carp kernel: [156478.323484] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 2 13:17:50 carp kernel: [156478.323486] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 2 13:17:50 carp kernel: [156478.323488] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 2 13:17:50 carp kernel: [156478.323490] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar 2 13:17:50 carp kernel: [156478.323493] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar 2 13:17:50 carp kernel: [156478.325705] drm/i915: Resetting chip after gpu hang
**Attachment 137761**, "GPU crash dump":
[carp-graphics-error](/uploads/6e2c308acf8115e390dadb3d6cd18a21/carp-graphics-error)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1701[snb] hanging in Shadow Warrior Classic Redux2022-06-02T22:15:38ZBugzilla Migration User[snb] hanging in Shadow Warrior Classic Redux## Submitted by gwaewion
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105288)](https://bugs.freedesktop.org/show_bug.cgi?id=105288)**
## Description
Created attachment 137685
from /sys/class/drm/card0/error...## Submitted by gwaewion
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105288)](https://bugs.freedesktop.org/show_bug.cgi?id=105288)**
## Description
Created attachment 137685
from /sys/class/drm/card0/error
random hanging in SW. laptop lenovo x220. os - arch linux.
dmesg output:
[ 1494.760722] [drm] GPU HANG: ecode 6:0:0x85fffffc, in sw [3344], reason: Hang on rcs0, action: reset
[ 1494.760725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1494.760725] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1494.760726] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1494.760726] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1494.760727] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1494.760770] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1502.755940] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1510.755941] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1518.755951] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1708.771958] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1716.771942] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1724.771935] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1732.707964] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1747.982140] perf: interrupt took too long (2541 > 2500), lowering kernel.perf_event_max_sample_rate to 78000
[ 1756.044265] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 1756.329393] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 1756.407757] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 1758.755945] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1766.755957] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1774.755935] i915 0000:00:02.0: Resetting chip after gpu hang
[ 1782.755940] i915 0000:00:02.0: Resetting chip after gpu hang
**Attachment 137685**, "from /sys/class/drm/card0/error":
[error](/uploads/4647a003cd3bd748c1ab72017c0990e2/error)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1700[ivb] Possibly nvidia/primus-induced GPU hang on rcs0, ecode 7:0:0x85fffff8 i...2022-06-02T22:15:48ZBugzilla Migration User[ivb] Possibly nvidia/primus-induced GPU hang on rcs0, ecode 7:0:0x85fffff8 in chromium## Submitted by Dorian Wouters
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105278)](https://bugs.freedesktop.org/show_bug.cgi?id=105278)**
## Description
Created attachment 137665
/sys/class/drm/card0/erro...## Submitted by Dorian Wouters
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105278)](https://bugs.freedesktop.org/show_bug.cgi?id=105278)**
## Description
Created attachment 137665
/sys/class/drm/card0/error contents
Bug description: My entire display froze while switching between windows in X11. Nothing else seems to have hanged, as music was still playing and everything came back to normal after SIGKILLing Blender which was running on the nVidia GPU.
Details / Reproducing steps:
- Blender 2.79 was running on the nVidia GPU through primus with primusrun. CUDA was used to render Blender Cycles images. The Blender window was inactive for a while and did not render any other image since at least 10 minutes.
- I (accidentally) switched to the Blender window by clicking below the other window icon I tried to click on in (a vertical) xfce4-panel, then used the mouse wheel to get to another window above it in the list, scrolling through 4 other windows before reaching Chromium's, where the hang happened
- Xorg did not visually respond to VT switch requests in the minute or so following the freeze, but it turned out later switching itself worked; I left tty2 active (still without visual feedback; X11 on tty1)
- I suspended then resumed the laptop, same display before and after
- I ssh'd into my machine, where I ran:
* `htop`, which did not show any CPU usage other than itself, sshd, firefox and pulseaudio (which were playing music in the background)
* `perf top` showed no graphics-related perf event samples
* `killall -9 blender`
- At this point the display did not update but was on tty2 (expected killing blender would unclog the graphics stack and make the console render)
- Alt+F1, and X11 resumes
- Ctrl+Alt+F2 and tty2 displays properly
- Back to X11, read dmesg and report this bug
System environment (package versions as reported by `pacman`):
-- chipset: HD4000 (part of an Intel i5-3317U; Ivy Bridge)
-- system architecture: 64-bit
-- xf86-video-intel: 1:2.99.917+812+g75795523-1
-- xserver: 1.19.6+13+gd0d1a694f-1
-- mesa: 17.3.5-1
-- libdrm: 2.4.90-3
-- kernel: 4.15.5-1-ARCH #1 SMP PREEMPT Thu Feb 22 22:15:20 UTC 2018 x86_64
-- Linux distribution: Arch Linux
-- Machine or mobo model: ASUS K56CB
-- Display connector: LVDS panel
-- nvidia: 390.25-13
-- nvidia GPU: GeForce 740M
-- primus: 20151110-7
-- bumblebee: 3.2.1-16
-- bbswitch: 0.8-113
-- blender: 17:2.79-9
-- compton (X11 compositor in use): 0.1_beta2.5-10
-- chromium: 64.0.3282.167-1
Additional info:
In the process of resetting the i915, a fence wait timed out:
[95008.506693] i915 0000:00:02.0: Resetting chip after gpu hang
[95010.549217] asynchronous wait on fence i915:[global]:6fd684 timed out
[95016.501277] i915 0000:00:02.0: Resetting chip after gpu hang
Starting up or using primus-forwarded software sometimes creates graphics corruption on some windows, which is fixed when a redraw happens but that also seems to happen all types of graphics buffers on the i915 like font cache/atlases, some applications like Steam are particularly affected by this problem. It is not unexpected that more than just buffer content gets corrupted.
Booting with intel_iommu enabled prevents graphical output as soon as the kernel switches away from efifb to inteldrmfb (that is, early in boot); maybe it could have a beneficial impact on the graphics corruption problem if it worked...
**Attachment 137665**, "/sys/class/drm/card0/error contents":
[card0err](/uploads/cafdb8be1935a47cffdd1bf84061bd38/card0err)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1699[SKL] Aztec Ruins benchmark (GL version) causes intermittent GPU hangs2022-06-02T22:16:03ZBugzilla Migration User[SKL] Aztec Ruins benchmark (GL version) causes intermittent GPU hangs## Submitted by clayton craft `@craftyguy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105276)](https://bugs.freedesktop.org/show_bug.cgi?id=105276)**
## Description
Created attachment 137663
output in /sy...## Submitted by clayton craft `@craftyguy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105276)](https://bugs.freedesktop.org/show_bug.cgi?id=105276)**
## Description
Created attachment 137663
output in /sys/class/drm/card0/error
Attached error file from /sys/class/drm/card0. This may be related to other gpu hangs in aztec ruins (e.g. 104636), I just don't know enough about this error file to come to any definitive conclusion.
**Attachment 137663**, "output in /sys/class/drm/card0/error":
[skl_card0_error](/uploads/d1761966392f48cab1f33e95775e3e21/skl_card0_error)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1698[HSW] Intermittent failures on KHR-GLES31.core.tessellation_shader.tessellati...2023-02-01T08:31:10ZBugzilla Migration User[HSW] Intermittent failures on KHR-GLES31.core.tessellation_shader.tessellation_control_to_tessellation_evaluation.gl_tessLevel## Submitted by clayton craft `@craftyguy`
Assigned to **Kenneth Graunke `@kwg`**
**[Link to original bug (#105261)](https://bugs.freedesktop.org/show_bug.cgi?id=105261)**
## Description
In mesa CI, there are intermittent (~90%) f...## Submitted by clayton craft `@craftyguy`
Assigned to **Kenneth Graunke `@kwg`**
**[Link to original bug (#105261)](https://bugs.freedesktop.org/show_bug.cgi?id=105261)**
## Description
In mesa CI, there are intermittent (~90%) failures on this test:
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
I wasn't able to reproduce this after looping glcts on this one test (with multiple instanced running), but it does fail if looping the full glcts.
Version: gitKenneth Graunkekenneth@whitecape.orgKenneth Graunkekenneth@whitecape.orghttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1697GPU HANG: ecode 7:0:0x87f57ff8, in navigation application - Baytrail2022-06-02T22:16:19ZBugzilla Migration UserGPU HANG: ecode 7:0:0x87f57ff8, in navigation application - Baytrail## Submitted by James Thomas
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105252)](https://bugs.freedesktop.org/show_bug.cgi?id=105252)**
## Description
Created attachment 137604
Card error
Anywhere betwee...## Submitted by James Thomas
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105252)](https://bugs.freedesktop.org/show_bug.cgi?id=105252)**
## Description
Created attachment 137604
Card error
Anywhere between 1-2 hours of running a driving simulation using a proprietary Qt5 based navigation application we're observing the attached GPU hang.
Kernel: 4.14.19
CPU: Intel(R) Atom(TM) CPU E3840 (Baytrail)
Other: Weston 1.0.6 (proprietary DRM rendering backend)
Mesa 13.0.6 (stock i965 driver from this)
The issue wasn't previously seen on our 4.4.x based released, however we were using a mesa 9.x based proprietary user-space driver, and a similar driver in the kernel (though it was essentially a wrapper around i915)
Unfortunately due to the version of Weston we're using we won't be able to easily upgrade mesa from 13.0.6 (it's a binary blob)
**Attachment 137604**, "Card error":
[card_error.log](/uploads/e421cffaf39a98812622eb8d95ba3ecc/card_error.log)
Version: 13.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1696[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg2022-06-02T22:16:34ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg## Submitted by Peter van Hooft
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105236)](https://bugs.freedesktop.org/show_bug.cgi?id=105236)**
## Description
Created attachment 137585
/sys/class/drm/card0/err...## Submitted by Peter van Hooft
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105236)](https://bugs.freedesktop.org/show_bug.cgi?id=105236)**
## Description
Created attachment 137585
/sys/class/drm/card0/error
Platform: HP Elitebook 840 G3, Fedora 27, kernel 4.15.4-300.fc27.x86_64.
mesa-dri-drivers-17.3.5-1.fc27.x86_64
xorg-x11-drv-intel-2.99.917-31.20171025.fc27.x86_64
After starting a graphical Java program the X server becomes unresponsive and eventually I'm logged out:
[Sun Feb 25 08:40:41 2018] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [3413], reason: Hang on rcs0, action: reset
[Sun Feb 25 08:40:41 2018] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[Sun Feb 25 08:40:41 2018] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[Sun Feb 25 08:40:41 2018] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[Sun Feb 25 08:40:41 2018] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[Sun Feb 25 08:40:41 2018] [drm] GPU crash dump saved to /sys/class/drm/card0/error
**Attachment 137585**, "/sys/class/drm/card0/error":
[gpu-crash-dump](/uploads/ebf54c00f84594e34f141c1b7b9c0a32/gpu-crash-dump)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1695[snb] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell2020-03-16T15:15:01ZBugzilla Migration User[snb] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell## Submitted by Mikhail Gavrilov `@Mikhail`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105219)](https://bugs.freedesktop.org/show_bug.cgi?id=105219)**
## Description
Created attachment 137547
dmesg
[ 426...## Submitted by Mikhail Gavrilov `@Mikhail`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105219)](https://bugs.freedesktop.org/show_bug.cgi?id=105219)**
## Description
Created attachment 137547
dmesg
[ 4264.490623] [drm] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell [1514], reason: Hang on rcs0, action: reset
[ 4264.490625] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 4264.490626] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 4264.490626] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 4264.490626] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 4264.490627] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 4264.490693] i915 0000:00:02.0: Resetting chip after gpu hang
[ 5202.670808] perf: interrupt took too long (6361 > 6315), lowering kernel.perf_event_max_sample_rate to 31000
[ 9323.092160] perf: interrupt took too long (8025 > 7951), lowering kernel.perf_event_max_sample_rate to 24000
**Attachment 137547**, "dmesg":
[dmesg.txt](/uploads/ee2e880eac2abb390787ed44ee3657b0/dmesg.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1694[skl] GPU HANG: ecode 9:0:0x85dffffb, in X2022-06-02T22:16:46ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dffffb, in X## Submitted by rob..@..nl.gov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105182)](https://bugs.freedesktop.org/show_bug.cgi?id=105182)**
## Description
Created attachment 137489
Intel GPU Crash Dump
Whe...## Submitted by rob..@..nl.gov
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#105182)](https://bugs.freedesktop.org/show_bug.cgi?id=105182)**
## Description
Created attachment 137489
Intel GPU Crash Dump
When this issue happens, the X server and gdm process terminates and you end up back at the login screen. The system itself is not hung, but you lose your desktop session.
Kernel: 3.10.0-693.11.1.el7.x86_64
Linux Distro: RHEL 7.4
Hardware: Dell XPS 13 9350
Display Connector: Just the laptop display
I have attached a GPU crash dump.
In addition, here are the relevant log entries from /var/log/messsages for the last 2 times the GPU hung.
=====================
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455912] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [1636], reason: Hang on render ring, action: reset
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455916] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455917] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455918] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455918] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Feb 20 16:35:12 xecho kernel: [kern.info][250168.455919] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Feb 20 16:35:12 xecho kernel: [kern.notice][250168.455963] drm/i915: Resetting chip after gpu hang
Feb 20 16:35:12 xecho kernel: [kern.info][250168.456024] [drm] RC6 on
Feb 20 16:35:12 xecho kernel: [kern.info][250168.467483] [drm] GuC firmware load skipped
Feb 20 16:35:24 xecho kernel: [kern.notice][250180.401159] drm/i915: Resetting chip after gpu hang
Feb 20 16:35:24 xecho kernel: [kern.info][250180.401251] [drm] RC6 on
Feb 20 16:35:24 xecho kernel: [kern.info][250180.417580] [drm] GuC firmware load skipped
Feb 20 16:35:25 xecho gdm: [user.notice] Child process 1636 was already dead.
=====================
Feb 20 17:04:01 xecho kernel: [kern.notice][251897.385910] drm/i915: Resetting chip after gpu hang
Feb 20 17:04:01 xecho kernel: [kern.info][251897.386001] [drm] RC6 on
Feb 20 17:04:01 xecho kernel: [kern.info][251897.402075] [drm] GuC firmware load skipped
Feb 20 17:04:17 xecho kernel: [kern.notice][251913.380806] drm/i915: Resetting chip after gpu hang
Feb 20 17:04:17 xecho kernel: [kern.info][251913.380882] [drm] RC6 on
Feb 20 17:04:17 xecho kernel: [kern.info][251913.396346] [drm] GuC firmware load skipped
Feb 20 17:04:29 xecho kernel: [kern.notice][251925.384639] drm/i915: Resetting chip after gpu hang
Feb 20 17:04:29 xecho kernel: [kern.info][251925.384717] [drm] RC6 on
Feb 20 17:04:29 xecho kernel: [kern.info][251925.400945] [drm] GuC firmware load skipped
Feb 20 17:04:31 xecho gdm: [user.notice] Child process 16301 was already dead.
=====================
**Attachment 137489**, "Intel GPU Crash Dump":
[xecho_gpu_crash_dump](/uploads/a4c5eaf0bbf6b5f1b7f601805b0440fe/xecho_gpu_crash_dump)