mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2019-09-25T19:11:16Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1725Fractional viewport coordinates shift viewport corner by a whole integer2019-09-25T19:11:16ZBugzilla Migration UserFractional viewport coordinates shift viewport corner by a whole integer## Submitted by Józef Kucia
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106526)](https://bugs.freedesktop.org/show_bug.cgi?id=106526)**
## Description
A piglit test which can be used to reproduce the probl...## Submitted by Józef Kucia
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106526)](https://bugs.freedesktop.org/show_bug.cgi?id=106526)**
## Description
A piglit test which can be used to reproduce the problem: https://lists.freedesktop.org/archives/piglit/2018-May/024378.html
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1721[gm45] Stray GPU writes2019-09-25T19:11:00ZBugzilla Migration User[gm45] Stray GPU writes## Submitted by pis..@..del.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106421)](https://bugs.freedesktop.org/show_bug.cgi?id=106421)**
## Description
Created attachment 139395
/sys/class/drm/card0/erro...## Submitted by pis..@..del.de
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106421)](https://bugs.freedesktop.org/show_bug.cgi?id=106421)**
## Description
Created attachment 139395
/sys/class/drm/card0/error
I just started "git gui", when the notebook froze for a few seconds. Afterwards, I could access most running applications, but chrome only rendered the tab bar, and plasmashell would not start again.
I had only just updated the KDE libraries from 5.44.0 to 5.45.0 when this happened. Not sure if this is related.
from dmesg:
[ 6202.821326] [drm] GPU HANG: ecode 4:0:0xefdcfff7, in chrome [2583], reason: Hang on rcs0, action: reset
[ 6202.821327] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 6202.821328] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 6202.821329] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 6202.821329] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 6202.821330] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 6202.821370] i915 0000:00:02.0: Resetting chip after gpu hang
[ 6207.968047] i915 0000:00:02.0: i915_reset_device timed out, cancelling all in-flight rendering.
[ 6212.288101] i915 0000:00:02.0: Failed to reset chip
**Attachment 139395**, "/sys/class/drm/card0/error":
[card0-error.txt](/uploads/7abc64735149eb76da4ce34f835d28c9/card0-error.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1720[snb] GPU HANG: ecode 6:0:0xf388fff8, in blockGen (VTK)2019-09-25T19:10:58ZBugzilla Migration User[snb] GPU HANG: ecode 6:0:0xf388fff8, in blockGen (VTK)## Submitted by ban..@..mx.net
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106242)](https://bugs.freedesktop.org/show_bug.cgi?id=106242)**
## Description
Created attachment 139110
bzipped /sys/class/drm/ca...## Submitted by ban..@..mx.net
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106242)](https://bugs.freedesktop.org/show_bug.cgi?id=106242)**
## Description
Created attachment 139110
bzipped /sys/class/drm/card0/error gpu crash dump
OS : almost up-to-date openSUSE tumbleweed ( 24th of april 2018)
uname -a: Linux wladimir 4.16.1-1-default #1 SMP PREEMPT Mon Apr 9 06:27:59 UTC 2018 (fc6541a) x86_64 x86_64 x86_64 GNU/Linux
Mesa Version : 18.0.0-193.1
system hangs for 5 seconds while working with homegrown VTK ( OpenGL ) application
dmesg:
[ 3191.906548] [drm] GPU HANG: ecode 6:0:0xf388fff8, in blockGen [7146], reason: Hang on rcs0, action: reset
[ 3191.906551] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 3191.906552] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 3191.906552] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 3191.906553] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 3191.906555] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 3191.906606] i915 0000:00:02.0: Resetting chip after gpu hang
[ 3195.964336] asynchronous wait on fence i915:[global]:161ee timed out
[ 3200.892410] i915 0000:00:02.0: Resetting chip after gpu hang
[ 3209.916414] i915 0000:00:02.0: Resetting chip after gpu hang
Cheers!
**Attachment 139110**, "bzipped /sys/class/drm/card0/error gpu crash dump":
[gpu_crash_dump.bz2](/uploads/4819220db8013eb26c68f11d6fb3a0a6/gpu_crash_dump.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1714KWin shadows occasionally corrupt, only fixed after a full-screen redraw2019-09-25T19:10:32ZBugzilla Migration UserKWin shadows occasionally corrupt, only fixed after a full-screen redraw## Submitted by Nicolas Frattaroli
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106005)](https://bugs.freedesktop.org/show_bug.cgi?id=106005)**
## Description
Created attachment 138800
Screenshot of the bug...## Submitted by Nicolas Frattaroli
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#106005)](https://bugs.freedesktop.org/show_bug.cgi?id=106005)**
## Description
Created attachment 138800
Screenshot of the bug in action, with some sensitive info blacked out to protect the innocent
Occasionally, the window shadows of a window in KWin exhibit a strange corrupted pattern, which flickers depending on (I believe?) cursor movement and disappears when the screen is fully redrawn (e.g. after taking a screenshot in Spectacle, or toggling compositing off and back on)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
Mesa version: 18.0.0
kwin 5.12.4 running on X11
**Attachment 138800**, "Screenshot of the bug in action, with some sensitive info blacked out to protect the innocent":
![please_ignore_the_black_bars](/uploads/e2fa30b3cb1bc1f05b683e342fafc2ad/please_ignore_the_black_bars.png)
Version: 18.0https://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/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/1686GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1317], reason: Hang on rcs0, action:...2019-09-25T19:08:27ZBugzilla Migration UserGPU HANG: ecode 9:0:0x85dffffb, in Xorg [1317], reason: Hang on rcs0, action: reset## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104974)](https://bugs.freedesktop.org/show_bug.cgi?id=104974)**
## Description
+++ This bug report from Alejandro Lorenzo ...## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104974)](https://bugs.freedesktop.org/show_bug.cgi?id=104974)**
## Description
+++ This bug report from Alejandro Lorenzo was salvaged from Bug #104712 +++
While working in eclipse Version: Kepler Service Release 2 the GPU hangs. After 30 seconds the session is reset.
Crash occurs somewhat between 1 to 15 minutes, usually on the early side.
It occurs with kernel 4.14.14 and 4.14.4.
Mesa version in which if crashes are: 17.3.2, 17.3.3 and 17.2.5
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1685[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg2019-09-25T19:08:25ZBugzilla Migration User[skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg## Submitted by PN
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104953)](https://bugs.freedesktop.org/show_bug.cgi?id=104953)**
## Description
Created attachment 137172
Content of /sys/class/drm/card0/error...## Submitted by PN
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104953)](https://bugs.freedesktop.org/show_bug.cgi?id=104953)**
## Description
Created attachment 137172
Content of /sys/class/drm/card0/error
About a week ago, my system froze for the first time with the following syslog entries:
Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [870], reason: Hang on rcs0, action: reset
Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu hang
Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence i915:kwin_x11[1506]/1:bd84 timed out
Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu hang
Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on
Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on
Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on
Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu hang
Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on
Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client killed
The kernel back then was: Linux 4.13.0-32-generic x86_64
This occurred several times a day. I reported this bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746551
I then re-installed kubuntu 17.10, plus a newer 4.15 mainline kernel, but the crash happened again:
Linux kernel:
Linux 4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Dmesg entries:
[16127.462805] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [887], reason: Hang on rcs0, action: reset
[16127.462806] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[16127.462807] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[16127.462807] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[16127.462807] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[16127.462808] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[16127.462813] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16135.453438] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16143.452952] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16157.468290] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[16171.451587] i915 0000:00:02.0: Resetting rcs0 after gpu hang
The content of /sys/class/drm/card0/error is attached as requested
**Attachment 137172**, "Content of /sys/class/drm/card0/error":
[drm_card0_error](/uploads/1aff116c3d1fea5b55738f522d40df13/drm_card0_error)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1681[snb] GPU hang ecode 6:0:0x85fffffc, in gnome-shell [1047]2019-09-25T19:07:59ZBugzilla Migration User[snb] GPU hang ecode 6:0:0x85fffffc, in gnome-shell [1047]## Submitted by Sumit Anantwar
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104822)](https://bugs.freedesktop.org/show_bug.cgi?id=104822)**
## Description
Created attachment 137010
GP Crash Dump
GPU Hang w...## Submitted by Sumit Anantwar
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104822)](https://bugs.freedesktop.org/show_bug.cgi?id=104822)**
## Description
Created attachment 137010
GP Crash Dump
GPU Hang was observed, and the below explanation was found in dmesg.
GPU crash dump is attached.
[Jan28 22:39] [drm] GPU HANG: ecode 6:0:0x85fffffc, in gnome-shell [1047], 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.000001] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ +0.000000] [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.000052] i915 0000:00:02.0: Resetting chip after gpu hang
**Attachment 137010**, "GP Crash Dump":
[GPUCrashDump.txt](/uploads/f1d2280f118976a38216b057ac040e71/GPUCrashDump.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1674Below 60 FPS with XScreenSaver discoball on HiDPI monitor2019-09-25T19:07:22ZBugzilla Migration UserBelow 60 FPS with XScreenSaver discoball on HiDPI monitor## Submitted by Paul Menzel
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104603)](https://bugs.freedesktop.org/show_bug.cgi?id=104603)**
## Description
With Mesa 17.3.1 and XScreenSaver 5.37 testing the dis...## Submitted by Paul Menzel
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104603)](https://bugs.freedesktop.org/show_bug.cgi?id=104603)**
## Description
With Mesa 17.3.1 and XScreenSaver 5.37 testing the discoball in demo, I do not get 60 FPS on the DPI monitor Dell U2718Q.
```
$ lspci -nn -s 0:02.0
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
$ more /proc/version
Linux version 4.14.13.mx64.201 (root@orpheus.molgen.mpg.de) (gcc version 5.3.0 (GCC)) #1 SMP Wed Jan 10 12:14:02 CET 2018
$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-2 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 609mm x 349mm
3840x2160 60.00*+ 29.98
2560x1440 59.95
2048x1280 59.99
1920x1200 59.88
2048x1080 24.00
1920x1080 60.00 60.00 50.00 59.94 24.00 23.98
1920x1080i 60.00 50.00 59.94
1600x1200 60.00
1600x900 60.00
1280x1024 75.02 60.02
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
HDMI-3 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
```
Running the command below, only around 30 FPS are shown and the “animation” stutters, that means, it is not smooth.
```
$ discoball -delay 0 -count 51 -spin -fps
```
Is that a hardware limitation, can the drivers be improved, or is it even XScreenSaver?
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/167110bpc regression2019-09-25T19:07:06ZBugzilla Migration User10bpc regression## Submitted by Tapani Pälli
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104536)](https://bugs.freedesktop.org/show_bug.cgi?id=104536)**
## Description
Created attachment 136608
screenshot
Regression obse...## Submitted by Tapani Pälli
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104536)](https://bugs.freedesktop.org/show_bug.cgi?id=104536)**
## Description
Created attachment 136608
screenshot
Regression observed on Ubuntu, bisected to:
9e63cbacb6bc10b4426fc2af4989fbdc86ec4167
**Attachment 136608**, "screenshot":
![ubuntu](/uploads/034f278aff17953aab0fd9e95972d313/ubuntu.jpg)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1665[i965] Downward causes GPU hangs and misrendering on Haswell2022-06-07T06:42:54ZBugzilla Migration User[i965] Downward causes GPU hangs and misrendering on Haswell## Submitted by Darius Spitznagel `@johndoe7000`
Assigned to **vadym**
**[Link to original bug (#104297)](https://bugs.freedesktop.org/show_bug.cgi?id=104297)**
## Description
Hello Intel devs,
this game behaves very strange.
The...## Submitted by Darius Spitznagel `@johndoe7000`
Assigned to **vadym**
**[Link to original bug (#104297)](https://bugs.freedesktop.org/show_bug.cgi?id=104297)**
## Description
Hello Intel devs,
this game behaves very strange.
The game starts always well to the games menu.
But when you start to play it gets weird.
Sometimes it causes GPU hangs and then crash...
```
[ 690.105553] [drm] GPU HANG: ecode 7:0:0x87d57d10, in Downward [2633], reason: Hang on rcs0, action: reset
[ 690.105557] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 690.105558] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 690.105558] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 690.105559] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 690.105560] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 690.105606] i915 0000:00:02.0: Resetting chip after gpu hang
[ 697.788068] i915 0000:00:02.0: Resetting chip after gpu hang
[ 705.788069] i915 0000:00:02.0: Resetting chip after gpu hang
[ 713.788064] i915 0000:00:02.0: Resetting chip after gpu hang
```
Sometimes it does not hang the GPU, you get into the game and see rendering issues.
The misrendering is always different. Sometimes heavy, sometimes less heavy.
Luckily this game has a free Demo on steam, so you can try this game yourself.
I managed to make an apitrace after some tries but could not see any relevant errors and deleted it. I can do it again if needed.
Setting allow_glsl_cross_stage_interpolation_mismatch=true "seems" not help with this UE4 game.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1663[OpenGL CTS] [SKL] KHR-GL46.compute_shader.resource-texture sometimes fails i...2019-09-25T19:06:19ZBugzilla Migration User[OpenGL CTS] [SKL] KHR-GL46.compute_shader.resource-texture sometimes fails in full run## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104153)](https://bugs.freedesktop.org/show_bug.cgi?id=104153)**
## Description
KHR-GL46.compute_shader.resource-texture ap...## Submitted by Kenneth Graunke `@kwg`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#104153)](https://bugs.freedesktop.org/show_bug.cgi?id=104153)**
## Description
KHR-GL46.compute_shader.resource-texture appears to fail in some configs on Skylake GT4 when run via cts-runner --type=gl46. So far I haven't been able to reproduce this when running a subset of the tests, even with the same config options.
Version: git
### Blocking
* [Bug 102590](https://bugs.freedesktop.org/show_bug.cgi?id=102590)https://gitlab.freedesktop.org/mesa/mesa/-/issues/16584% performance drop in GLB 2.7 Egypt from "Use a 565 format for GL_RGB and GL...2019-09-25T19:06:05ZBugzilla Migration User4% performance drop in GLB 2.7 Egypt from "Use a 565 format for GL_RGB and GL_UNSIGNED_SHORT_5_6_5 textures"## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103939)](https://bugs.freedesktop.org/show_bug.cgi?id=103939)**
## Description
Following commit was bisected (on SKL GT2) to be cau...## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103939)](https://bugs.freedesktop.org/show_bug.cgi?id=103939)**
## Description
Following commit was bisected (on SKL GT2) to be cause for a performance drop in GLB 2.7 Egypt onscreen and offscreen tests:
-------------------------------------------------------------
commit 18bdf73556440ca2eaac2d22e1e3ebe1be7b6c1d
Author: Kenneth Graunke <kenneth@whitecape.org>
AuthorDate: Wed Oct 4 01:08:37 2017 -0700
Commit: Kenneth Graunke <kenneth@whitecape.org>
CommitDate: Thu Oct 5 14:30:47 2017 -0700
mesa: Use a 565 format for GL_RGB and GL_UNSIGNED_SHORT_5_6_5 textures.
Found while trying to optimize an application.
Not observed to help performance on i965, but should at least reduce
the memory usage of such textures a bit.
Reviewed-by: Eric Anholt <eric@anholt.net>
Tested-by: Eero Tamminen <eero.t.tamminen@intel.com>
-------------------------------------------------------------
Egypt performance drop is clearly visible on following platforms:
* 4% on BSW N3050 & SKL GT2 & KBL GT2
* 2% on BXT J4205 & HSW GT2 & SKL GT4e
* 2% on BYT N2820 (only offscreen version)
(BSW & BYT have 1-channel memory, others 2-channel.)
On some other platforms the performance also increases, as was expected:
* 3% on BDW GT3
* 1% on BDW GT2 & SNB GT2 (only offscreen version)
(Sorry for filing this so late. I had been waiting to see whether blorp rework / texture RBC would affect this, but forgot it. That didn't affect Egypt.)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1656[OpenGL CTS] [BDW] KHR-GL45.tessellation_shader.tessellation_shader_tessellat...2019-09-25T19:05:55ZBugzilla Migration User[OpenGL CTS] [BDW] KHR-GL45.tessellation_shader.tessellation_shader_tessellation.gl_InvocationID_PatchVerticesIn_PrimitiveID occasionally fails## Submitted by Neil Roberts `@nroberts`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103837)](https://bugs.freedesktop.org/show_bug.cgi?id=103837)**
## Description
The CTS test KHR-GL45.tessellation_shader...## Submitted by Neil Roberts `@nroberts`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103837)](https://bugs.freedesktop.org/show_bug.cgi?id=103837)**
## Description
The CTS test KHR-GL45.tessellation_shader.tessellation_shader_tessellation.gl_InvocationID_PatchVerticesIn_PrimitiveID seems to occasionally fail at a rate of about 1.4%.
The test emits a bunch of tessellation patches with varying sizes, including the maximum of 32 and does an instanced draw call. There are no vertex buffers bound and all of the vertices have the same position. The tessellation shaders write to 5 integer output varyings which are captured to a transform feedback buffer. The test then scans the buffer to verify that it has the expected values. When it fails, there are one or two vertices in this buffer that get written with all zeroes instead of the expected values. These failed slots are small and in the middle of the buffer so it doesn’t seem likely that this could be a buffer configuration issue. I suspect it might be some hardware quirk but I haven’t been able to find anything relevant in the workarounds in the hardware docs.
The hardware where I can replicate it is a NUC with Intel(R) Iris Pro 6200 (Broadwell GT3e). However I am unable to replicate it on my laptop which has Intel(R) HD Graphics 5500 (Broadwell GT2).
### Blocking
* [Bug 102590](https://bugs.freedesktop.org/show_bug.cgi?id=102590)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1655[SNB] SynMark GSCloth test renders wrong2019-09-25T19:05:52ZBugzilla Migration User[SNB] SynMark GSCloth test renders wrong## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103824)](https://bugs.freedesktop.org/show_bug.cgi?id=103824)**
## Description
Created attachment 135603
Incorrect rendering screen...## Submitted by Eero Tamminen
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#103824)](https://bugs.freedesktop.org/show_bug.cgi?id=103824)**
## Description
Created attachment 135603
Incorrect rendering screenshot
Mesa fails SynMark render validation for OglGSCloth test on SNB:
./synmark2 OglGSCoth
Rendering is obviously incorrect (see the the attachment). Francesco's recent GEN6-7 Transform feedback optimization patch series seems to make this somewhat worse.
I don't know whether Mesa has ever rendered it correctly on SNB, the issue has been there at least a year. Rendering is fine on GEN7+ (also with Francesco's patch series).
Unlike most of the other tests we run regularly (which work fine), GSCloth uses geometry shaders, streamout and transform feedback. GfxBench Manhattan uses also transform feedback, but that at least didn't have obvious rendering issues on SNB like this test.
~~**Attachment 135603**~~, "Incorrect rendering screenshot":
![OglGSCloth_20171120_154952](/uploads/62773221c02ab7d5396b1970dd263563/OglGSCloth_20171120_154952.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1653[BDW BSW SKL KBL] dEQP-GLES31.functional.copy_image regressions2020-05-25T12:24:23ZBugzilla Migration User[BDW BSW SKL KBL] dEQP-GLES31.functional.copy_image regressions## Submitted by Mark Janes `@majanes`
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#103746)](https://bugs.freedesktop.org/show_bug.cgi?id=103746)**
## Description
The following tests fail:
dEQP-GLES31.func...## Submitted by Mark Janes `@majanes`
Assigned to **Jason Ekstrand `@jekstrand`**
**[Link to original bug (#103746)](https://bugs.freedesktop.org/show_bug.cgi?id=103746)**
## Description
The following tests fail:
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_24_bits.srgb8_rgb8_snorm.cubemap_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_24_bits.srgb8_rgb8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_24_bits.srgb8_rgb8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_24_bits.srgb8_rgb8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_24_bits.srgb8_rgb8_snorm.texture2d_to_texture3d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.r11f_g11f_b10f_rgba8_snorm.cubemap_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.r11f_g11f_b10f_rgba8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.r11f_g11f_b10f_rgba8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.r11f_g11f_b10f_rgba8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.r11f_g11f_b10f_rgba8_snorm.texture2d_to_texture3d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2_rgba8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2_rgba8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2_rgba8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2_rgba8_snorm.texture2d_to_texture3d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2ui_rgba8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2ui_rgba8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2ui_rgba8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb10_a2ui_rgba8_snorm.texture2d_to_texture3d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb9_e5_rgba8_snorm.cubemap_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb9_e5_rgba8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb9_e5_rgba8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb9_e5_rgba8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.rgb9_e5_rgba8_snorm.texture2d_to_texture3d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.srgb8_alpha8_rgba8_snorm.texture2d_to_cubemap
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.srgb8_alpha8_rgba8_snorm.texture2d_to_texture2d
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.srgb8_alpha8_rgba8_snorm.texture2d_to_texture2d_array
dEQP-GLES31.functional.copy_image.non_compressed.viewclass_32_bits.srgb8_alpha8_rgba8_snorm.texture2d_to_texture3d
Test output indicates many successful comparisons, along with:
Image comparison failed: max difference = (122, 107, 172, 255), threshold = (2, 2, 2, 2)
These tests were disabled except on daily builds due to test time. Bisection is underway.
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=109655Faith EkstrandFaith Ekstrand