mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2019-09-25T18:54:07Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1488[BDW] Incorrect rendering in CS:GO2019-09-25T18:54:07ZBugzilla Migration User[BDW] Incorrect rendering in CS:GO## Submitted by Matthieu Bouron
Assigned to **Ian Romanick**
**[Link to original bug (#91617)](https://bugs.freedesktop.org/show_bug.cgi?id=91617)**
## Description
Hello,
CS:GO is not rendered correctly on an intel HD5500 (Intel(...## Submitted by Matthieu Bouron
Assigned to **Ian Romanick**
**[Link to original bug (#91617)](https://bugs.freedesktop.org/show_bug.cgi?id=91617)**
## Description
Hello,
CS:GO is not rendered correctly on an intel HD5500 (Intel(R) Core(TM) i7-5600U) using mesa git (as of 02a4fe22b137d4bc8378bedd8319109fd23a50e3). The issue was present in mesa 10.6 and mesa 10.6.1. I haven't tested with older versions.
libdrm version is 2.4.62
kernel version is 4.1.4
xf86-video-intel version is 1:2.99.917+381+g5772556
Here are some screenshots comparing the output from an intel hd4000 (mesa 10.6.1) on the left of the screnshots and the hd5500 on the right.
It looks like the hdr/bloom postprocessing filters are missing, causing the game to render darker in a lot of areas which makes it unplayable in those.
http://0x5c.me/intel/01.png
http://0x5c.me/intel/02.png
http://0x5c.me/intel/03.png
http://0x5c.me/intel/04.png
The issue is more visible on screenshot 01.png and 03.png.
Let me know if you need more debug information.
Version: git
### Blocking
* [Bug 93185](https://bugs.freedesktop.org/show_bug.cgi?id=93185)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1489[snb blorp] GPU HANG in Terraria2022-06-02T22:33:32ZBugzilla Migration User[snb blorp] GPU HANG in Terraria## Submitted by Nelson A. de Oliveira
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#91650)](https://bugs.freedesktop.org/show_bug.cgi?id=91650)**
## Description
Created attachment 117710
full dmesg
Was tryi...## Submitted by Nelson A. de Oliveira
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#91650)](https://bugs.freedesktop.org/show_bug.cgi?id=91650)**
## Description
Created attachment 117710
full dmesg
Was trying to play Terraria and saw this:
[ 5959.279079] [drm] stuck on render ring
[ 5959.279509] [drm] GPU HANG: ecode 6:0:0x84feeffc, in Terraria.bin.x8 [6369], reason: Ring hung, action: reset
[ 5959.279510] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 5959.279511] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 5959.279512] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 5959.279512] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 5959.279513] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5959.287045] drm/i915: Resetting chip after gpu hang
[ 5965.320467] [drm] stuck on render ring
[ 5965.320916] [drm] GPU HANG: ecode 6:0:0x84fefffc, in Terraria.bin.x8 [6369], reason: Ring hung, action: reset
[ 5965.328419] drm/i915: Resetting chip after gpu hang
[ 5971.241939] [drm] stuck on render ring
[ 5971.242571] [drm] GPU HANG: ecode 6:0:0x84fefffc, in steam [1348], reason: Ring hung, action: reset
[ 5971.249927] drm/i915: Resetting chip after gpu hang
[ 5977.283335] [drm] stuck on render ring
[ 5977.283942] [drm] GPU HANG: ecode 6:0:0x84fefffc, in steam [1348], reason: Ring hung, action: reset
[ 5977.291271] drm/i915: Resetting chip after gpu hang
[ 5984.026748] CIPCServer::Thr[1384]: segfault at c ip 00000000efc2d9be sp 00000000eec39910 error 4 in steamclient.so[ef15a000+10e1000]
dmseg and /sys/class/drm/card0/error are attached
**Attachment 117710**, "full dmesg":
[dmseg.txt.bz2](/uploads/ff0c3dd189e8c2a272d66849906ab95b/dmseg.txt.bz2)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1490Textures are blocky in Crusader Kings 22020-03-19T14:22:13ZBugzilla Migration UserTextures are blocky in Crusader Kings 2## Submitted by Pavel Ondračka
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#91683)](https://bugs.freedesktop.org/show_bug.cgi?id=91683)**
## Description
Created attachment 117772
screenshot with bad and exp...## Submitted by Pavel Ondračka
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#91683)](https://bugs.freedesktop.org/show_bug.cgi?id=91683)**
## Description
Created attachment 117772
screenshot with bad and expected rendering
Textures are blocky in Crusader Kings 2, on my Broadwell GT2. My guess is the texture filtering isn't working properly (or maybe antialiasing, dunno).
Attached is a screenshot of rendering with i965 and compared to expected rendering (obtained with radeonsi driver).
apitrace here: http://pavel.ondracka.cz/ck2.trace
My system:
GPU: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)
mesa: 8f7ebcb6fad53ea6d2f80fc5b7a046db07690032
libdrm: ab2fadabde3829b1ec56bd4756165dd9bd281488
xf86-video-intel: 18e484502727f2e2e16138a3de5b6727f3879a2b (dri3 + sna)
kernel: 4.1.4-200.fc22.x86_64
**Attachment 117772**, "screenshot with bad and expected rendering":
![ck2-screenshot](/uploads/5065cd7a937483f8deeb73984c1da44f/ck2-screenshot.jpg)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1491[ivb blorp?] GPU hang in witcher.EXE2019-10-25T10:23:56ZBugzilla Migration User[ivb blorp?] GPU hang in witcher.EXE## Submitted by Tim Allen
Assigned to **Ian Romanick**
**[Link to original bug (#91730)](https://bugs.freedesktop.org/show_bug.cgi?id=91730)**
## Description
Created attachment 117869
Contents of /sys/class/drm/card0/error as requ...## Submitted by Tim Allen
Assigned to **Ian Romanick**
**[Link to original bug (#91730)](https://bugs.freedesktop.org/show_bug.cgi?id=91730)**
## Description
Created attachment 117869
Contents of /sys/class/drm/card0/error as requested
I wish I had some easy way to reproduce this with some widely-available software, but I'm not sure what would count.
The setup:
- I'm trying to play The Witcher Enhanced Edition
- Running under Wine 1.7.49
- Mesa 10.6.3
- Xorg 2.99.917
- Linux 4.1.0
- Debian Testing
- Intel Ivy Bridge i5-3570K CPU, with HD4000 graphics
Steps to reproduce (on my machine):
- Start the game
- Load my usual saved game
- Sometimes, once the initial loading screen's progress bar gets to the 99% mark, the hard-drive light stops flickering and the progress will pause for 10 seconds or so and then crash to desktop
- Sometimes the game loads properly, but later I'll be moving from one zone to another and *that* loading screen will pause and crash.
- Generally, I can't play the game for more than 5-10 minutes before a crash occurs.
- This same problem also occurs with another game called Path of Exile, in a similar fashion: every loading screen has some percentage chance to pause and crash.
Effects:
- When I start the game from a terminal, after a crash it displays the following message:
intel_do_flush_locked failed: Input/output error
- /var/log/messages receives this message:
[ 807.367059] [drm] stuck on render ring
[ 807.367363] [drm] GPU HANG: ecode 7:0:0x85fffff8, in witcher.EXE [4865], reason: Ring hung, action: reset
[ 807.367364] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 807.367364] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 807.367365] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 807.367365] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 807.367366] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 807.369412] drm/i915: Resetting chip after gpu hang
[ 813.363894] [drm] stuck on render ring
[ 813.364243] [drm] GPU HANG: ecode 7:0:0x85ffbff8, in witcher.EXE [4865], reason: Ring hung, action: reset
[ 813.366337] drm/i915: Resetting chip after gpu hang
- If I restart the game and try again, it'll crash again (usually faster), and after a few iterations eventually the console stops responding to anything but the Alt-SysRq keys (although I can SSH in from another computer and everything seems to be running fine) and I have to reboot.
Because I'm using Debian Testing, it's a bit difficult to say when this started. My recollection is that everything worked fine under Mesa 10.4, but these errors started appearing after Debian upgraded to Mesa 10.5. Of course, Debian was changing all kinds of stuff around that time, so it might have been anything.
**Attachment 117869**, "Contents of /sys/class/drm/card0/error as requested":
[my-gpu-crash.txt](/uploads/0d87eeb5b658893edb2ffb584a8692fb/my-gpu-crash.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1492gsraytrace fails with Input/Output error intel_do_flush_locked2019-09-25T18:54:32ZBugzilla Migration Usergsraytrace fails with Input/Output error intel_do_flush_locked## Submitted by Jonas Wielicki
Assigned to **Ian Romanick**
**[Link to original bug (#91827)](https://bugs.freedesktop.org/show_bug.cgi?id=91827)**
## Description
The gsraytrace demo from mesademos 8.2 fails with the following out...## Submitted by Jonas Wielicki
Assigned to **Ian Romanick**
**[Link to original bug (#91827)](https://bugs.freedesktop.org/show_bug.cgi?id=91827)**
## Description
The gsraytrace demo from mesademos 8.2 fails with the following output on mesa-11.0.0-rc2 on Intel Sandybridge:
$ LD_LIBRARY_PATH=/usr/local/lib /usr/lib64/mesa/gsraytrace
GL_RENDERER = Mesa DRI Intel(R) Sandybridge Mobile
ESC = exit demo
left mouse + drag = rotate camera
intel_do_flush_locked failed: Input/output error
intel_do_flush_locked failed: Input/output error
No special input is required, the demo crashes right away. The same also happens with the system mesa which is at version 10.6.3.
intel GPU:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1493[ILK] GPU hang (and multiple fails) in piglit shader tests if spilling is for...2019-09-25T18:54:35ZBugzilla Migration User[ILK] GPU hang (and multiple fails) in piglit shader tests if spilling is forced in the vec4 backend## Submitted by Iago Toral `@itoral`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92100)](https://bugs.freedesktop.org/show_bug.cgi?id=92100)**
## Description
Running piglit's shader tests (~14000 tests) wh...## Submitted by Iago Toral `@itoral`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92100)](https://bugs.freedesktop.org/show_bug.cgi?id=92100)**
## Description
Running piglit's shader tests (~14000 tests) while forcing spilling on the vec4 backend (INTEL_DEBUG=spill_vec4) produces at least one GPU hang (for me this happens consistently around test 10400). Also, I see a lot of tests that stop passing, even before the GPU hang, which points at something seriously broken. The FS backend is not affected, even if INTEL_DEBUG=spill_fs is used to force spilling.
All this is with current master (1614c39a8fc205)
To reproduce:
INTEL_DEBUG=spill_vec4 ./piglit-run.py tests/shader results/shader
I'll see if I can add more info, at least the specific test triggering the hang.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1494[G45] Segmentation fault in get_stencil_miptree2019-09-25T18:54:38ZBugzilla Migration User[G45] Segmentation fault in get_stencil_miptree## Submitted by Giulio Bernardi
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92103)](https://bugs.freedesktop.org/show_bug.cgi?id=92103)**
## Description
Created attachment 118428
Stack trace
This bug was ...## Submitted by Giulio Bernardi
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92103)](https://bugs.freedesktop.org/show_bug.cgi?id=92103)**
## Description
Created attachment 118428
Stack trace
This bug was originally reported on RedHat's bugzilla for Fedora 22:
https://bugzilla.redhat.com/show_bug.cgi?id=1266025
Description of problem:
On the machine I use at work sometimes plasma crashes after the login, before showing the KDE desktop. Investigation with gdb might have shown the cause of the problem.
Version-Release number of selected component (if applicable):
mesa-dri-drivers-10.6.3-3.20150729.fc22.x86_64
How reproducible:
Sometimes
Steps to Reproduce:
1. In KDM, perform the login
Actual results:
Sometimes plasma crashes before showing the desktop
Expected results:
Plasma should start and show the desktop
Additional info:
I Launched gdb from the KDE crash handler (drkonqi?), see attached stack trace. The crash happened at brw_misc_state.c:215, that is:
(gdb) list
210 static struct intel_mipmap_tree *
211 get_stencil_miptree(struct intel_renderbuffer *irb)
212 {
213 if (!irb)
214 return NULL;
215 if (irb->mt->stencil_mt)
216 return irb->mt->stencil_mt;
217 return irb->mt;
218 }
219
It turns out that irb->mt was null:
(gdb) print irb->mt
$3 = (struct intel_mipmap_tree *) 0x0
I modified the line to read
if (irb->mt && irb->mt->stencil_mt)
(see the attached patch) and so far (a couple of restarts, a shutdown, and a tenth of logouts/logins) no crash happened.
However, since the crash is not always reproducible, I cannot be 100% sure.
The video card is
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
I am using the intel driver with UXA acceleration method (not SNA).
Glxinfo says:
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) G45/G43
OpenGL version string: 2.1 Mesa 10.6.3 (git-ccef890)
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 10.6.3 (git-ccef890)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
I think this is not a duplicate of bugs like this:
https://bugs.freedesktop.org/show_bug.cgi?id=77402
because it was fixed long ago.
**Attachment 118428**, "Stack trace":
[file_92103.txt](/uploads/485c6038abb40e84553371ef658db165/file_92103.txt)
Version: 10.6https://gitlab.freedesktop.org/mesa/mesa/-/issues/1495[g965] intermittent gpu hang on piglit.spec.ext_framebuffer_object.fbo-maxsize2019-09-25T18:54:43ZBugzilla Migration User[g965] intermittent gpu hang on piglit.spec.ext_framebuffer_object.fbo-maxsize## Submitted by Mark Janes `@majanes`
Assigned to **Ian Romanick**
**[Link to original bug (#92108)](https://bugs.freedesktop.org/show_bug.cgi?id=92108)**
## Description
one of Mesa's g965 continuous integration systems encounters...## Submitted by Mark Janes `@majanes`
Assigned to **Ian Romanick**
**[Link to original bug (#92108)](https://bugs.freedesktop.org/show_bug.cgi?id=92108)**
## Description
one of Mesa's g965 continuous integration systems encounters occasional GPU hang on this piglit test.
[drm] stuck on render ring
[drm] GPU HANG: ecode 4:0:0xfde5fafd, in fbo-maxsize [8834], reason: Ring hung, action: reset
Running the test suite with i915.reset=0, this test was found to be running in several of the hang cases.
Strangely, otc-gfxtest-g965-02 encounters the hang, but otc-gfxtest-g965-01 does not. The failing system is a mobile:
jenkins@otc-gfxtest-g965-02:/$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
in contrast, the working system is a desktop:
jenkins@otc-gfxtest-g965-01:/$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1496[BDW] ES3-CTS.shaders.uniform_block.random.nested_structs_arrays.9 Fails2019-09-25T18:54:45ZBugzilla Migration User[BDW] ES3-CTS.shaders.uniform_block.random.nested_structs_arrays.9 Fails## Submitted by Marta Löfstedt `@marta`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92196)](https://bugs.freedesktop.org/show_bug.cgi?id=92196)**
## Description
The OpenGL ES 3.0 CTS: ES3-CTS.shaders.unifo...## Submitted by Marta Löfstedt `@marta`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92196)](https://bugs.freedesktop.org/show_bug.cgi?id=92196)**
## Description
The OpenGL ES 3.0 CTS: ES3-CTS.shaders.uniform_block.random.nested_structs_arrays.9 fails for BDW with Mesa 11.0.2 (git-51e0b06).
I have bisected the first problematic commit to:
commit 18e73bf7f8b12022e02db3230ee109657581900b
Author: Connor Abbott <cwabbott0@gmail.com>
Date: Tue Jun 30 13:38:20 2015 -0700
i965/fs: remove special case in setup_payload_interference()
regs_read() will handle LINTERP for us since the previous commit. In
addition, we were being too conservative, since it will only read 2
registers on SIMD8.
instructions in affected programs: 9061 -> 8893 (-1.85%)
helped: 10
HURT: 0
GAINED: 0
LOST: 0
All of the changes were due to spills being eliminated, mostly in KSP
shaders.
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Signed-off-by: Connor Abbott <connor.w.abbott@intel.com>
With a revert of above commit the test pass. However, the revert cause regressions for other CTS tests. Also, the commit appear to be part of a cooperative patch-set from Jordan and Connor.
Potential relation to https://bugs.freedesktop.org/show_bug.cgi?id=92113 has not yet been proven.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1497[BSW] piglit tests intermittently/randomly fail when running concurrently2020-04-24T21:31:29ZBugzilla Migration User[BSW] piglit tests intermittently/randomly fail when running concurrently## Submitted by Mark Janes `@majanes`
Assigned to **Mark Janes `@majanes`**
**[Link to original bug (#92320)](https://bugs.freedesktop.org/show_bug.cgi?id=92320)**
## Description
On linux 4.2.0, random piglit failures occur when r...## Submitted by Mark Janes `@majanes`
Assigned to **Mark Janes `@majanes`**
**[Link to original bug (#92320)](https://bugs.freedesktop.org/show_bug.cgi?id=92320)**
## Description
On linux 4.2.0, random piglit failures occur when running concurrently.
Changing to serial execution eliminates the failures, leaving aside the occasional gpu hang.
This behavior needs more investigation to verify that
* the list of failures is indeed unstable/random
* disabling tests has no effect on the failures.
Version: git
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=108787https://gitlab.freedesktop.org/mesa/mesa/-/issues/1498[BSW/BDW] ogles1conform Gets test fails2019-09-25T18:54:50ZBugzilla Migration User[BSW/BDW] ogles1conform Gets test fails## Submitted by cprigent
Assigned to **Ian Romanick**
**[Link to original bug (#92363)](https://bugs.freedesktop.org/show_bug.cgi?id=92363)**
## Description
Platform: Braswell M
CPU : Intel(R) Celeron N3060 1.60GHz @ 1.6 GHz (fam...## Submitted by cprigent
Assigned to **Ian Romanick**
**[Link to original bug (#92363)](https://bugs.freedesktop.org/show_bug.cgi?id=92363)**
## Description
Platform: Braswell M
CPU : Intel(R) Celeron N3060 1.60GHz @ 1.6 GHz (family: 6, model: 76 stepping: 4)
SoC : BSW D0
QDF : K6XC
CRB : BRASWELL RVP Fab2
Mandatory Reworks : All
Feature Reworks: F28, F32, F33, F35, F37
Optional reworks : O-01a; O-02, O-03
Software
Linux distribution: Ubuntu 14.04 LTS 64 bits
BIOS : BRAS.X64.B084.R00.1508310642
TXE FW : 2.0.0.2073
Ksc : 1.08
kernel drm-intel-nightly 4.3.0-rc3 eb69e51 from anongit.freedesktop.org/drm-intel
mesa: (HEAD, tag: mesa-11.0.2) 51e0b06d9916e126060c0d218de1aaa4e5a4ce26 from
git://git.freedesktop.org/git/mesa/mesa
cairo: (HEAD, tag: 1.14.2) 93422b3cb5e0ef8104b8194c8873124ce2f5ea2d from
git://git.freedesktop.org/git/cairo
drm: (HEAD, tag: libdrm-2.4.64, tag: 2.4.64)
ab2fadabde3829b1ec56bd4756165dd9bd281488 from
git://git.freedesktop.org/git/mesa/drm
intel-driver: (HEAD, origin/master, origin/HEAD, master)
2a72f99d24714f2a58f400ef63b913d4cf9080b3 from
git://git.freedesktop.org/git/vaapi/intel-driver
libva: (HEAD, tag: libva-1.6.1, origin/v1.6-branch)
613eb962b45fbbd1526d751e88e0d8897af6c0e0 from
git://git.freedesktop.org/git/vaapi/libva
xf86-video-intel: (HEAD, origin/master, origin/HEAD, master)
f0fd4d500de03c30c7ce19915f85acadd1ca4e5d from
git://git.freedesktop.org/git/xorg/driver/xf86-video-intel
xserver: (HEAD, tag: xorg-server-1.17.2)
2123f7682d522619f101b05fb75efa75dabbe371 from
git://git.freedesktop.org/git/xorg/xserver
intel-gpu-tools: (HEAD, origin/master, origin/HEAD, master)
1b492e311ce13fe4bc42f1edd5479441662d4855 from
git://git.freedesktop.org/git/xorg/app/intel-gpu-tools
Steps:
------
Execute command:
./conform
Actual result:
---------------
"Gets test" is fail
Expected result:
-----------------
"Gets test" is Pass
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1499GPU hang in chromium on BDW2022-06-02T23:28:57ZBugzilla Migration UserGPU hang in chromium on BDW## Submitted by Vasily Khoruzhick `@anarsoul`
Assigned to **Ian Romanick**
**[Link to original bug (#92559)](https://bugs.freedesktop.org/show_bug.cgi?id=92559)**
## Description
Created attachment 119017
i915_error_state.gz
No sp...## Submitted by Vasily Khoruzhick `@anarsoul`
Assigned to **Ian Romanick**
**[Link to original bug (#92559)](https://bugs.freedesktop.org/show_bug.cgi?id=92559)**
## Description
Created attachment 119017
i915_error_state.gz
No specific steps to reproduce, happens randomly. Quite often happens while opening a new tab.
mesa 11.0.3, xf86-video-intel-2.99.917+478+gdf72bc5, linux-4.2.3, chromium-46.0.2490.71
**Attachment 119017**, "i915_error_state.gz":
[i915_error_state.gz](/uploads/5b1bc71479da5c0b714281b76f534e50/i915_error_state.gz)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1500[g965] Implement dependency workaround in vec4 backend2019-09-25T18:54:56ZBugzilla Migration User[g965] Implement dependency workaround in vec4 backend## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92696)](https://bugs.freedesktop.org/show_bug.cgi?id=92696)**
## Description
commit 2458ea95c5676807a064f24ec720f1250697540...## Submitted by Mark Janes `@majanes`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92696)](https://bugs.freedesktop.org/show_bug.cgi?id=92696)**
## Description
commit 2458ea95c5676807a064f24ec720f12506975402 regressed 8 GL conformance tests on g965:
Author: Jason Ekstrand <jason.ekstrand@intel.com>
AuthorDate: Wed Sep 9 14:40:06 2015 -0700
Commit: Jason Ekstrand <jason.ekstrand@intel.com>
CommitDate: Tue Sep 15 12:38:07 2015 -0700
nir/lower_vec_to_movs: Coalesce movs on-the-fly when possible
The old pass blindly inserted a bunch of moves into the shader with no
concern for whether or not it was really needed. This adds code to try and
coalesce into the destination of the instruction providing the value.
Shader-db results for vec4 shaders on Haswell:
total instructions in shared programs: 1754420 -> 1747753 (-0.38%)
instructions in affected programs: 231230 -> 224563 (-2.88%)
helped: 1017
HURT: 2
This approach is heavily based on a different patch by Eduardo Lima Mitev
<elima@igalia.com>. Eduardo's patch did this in a separate pass as opposed
to integrating it into nir_lower_vec_to_movs.
Reviewed-by: Eduardo Lima Mitev <elima@igalia.com>
Intel never submitted conformance results for g965, so I'm not sure if this bug is a blocker.
Regressions:
es2-cts.gtf.gl.cross.cross_vec3_vert_xvaryyconst
es2-cts.gtf.gl.exp.exp_float_vert_xvaryneg
es2-cts.gtf.gl.exp.exp_vec2_vert_xvaryneg
es2-cts.gtf.gl.exp2.exp2_float_vert_xvaryneg
es2-cts.gtf.gl.exp2.exp2_vec2_vert_xvaryneg
es2-cts.gtf.gl.faceforward.faceforward_vec3_vert_nvaryiconst
es2-cts.gtf.gl.reflect.reflect_vec3_vert_ivarynconst
es2-cts.gtf.gl.refract.refract_vec3_vert_ivarynconst
Sample Standard Output:
/tmp/build_root/m64/bin/cts/glcts --deqp-case=ES2-CTS.gtf.GL.exp.exp_float_vert_xvaryneg
dEQP Core GL-CTS-2.0 (0x0052484b) starting..
target implementation = 'intel-gbm'
Test case 'ES2-CTS.gtf.GL.exp.exp_float_vert_xvaryneg'..
#+ GTF/GL/exp/exp_float_vert_xvaryneg.shader1.ppm and GTF/GL/exp/exp_float_vert_xvaryneg.shader2.ppm are different
Fail (Fail)
DONE!
Test run totals:
Passed: 0/1 (0.00%)
Failed: 1/1 (100.00%)
Not supported: 0/1 (0.00%)
Warnings: 0/1 (0.00%)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1501Visuals without alpha bits are not sRGB-capable2021-04-23T04:49:49ZBugzilla Migration UserVisuals without alpha bits are not sRGB-capable## Submitted by Deve
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92759)](https://bugs.freedesktop.org/show_bug.cgi?id=92759)**
## Description
Created attachment 119319
intel_mesa_10_3.png
Look at the scre...## Submitted by Deve
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92759)](https://bugs.freedesktop.org/show_bug.cgi?id=92759)**
## Description
Created attachment 119319
intel_mesa_10_3.png
Look at the screenshots.
- intel_mesa_10_3.png file shows what is expected. It is working with intel using mesa 10.3.2 and also with proprietary nvidia/amd graphics drivers.
- intel_mesa_current-git.png shows how it looks now with intel in current mesa git 0ef8c5cb96f6b1fea7c18c25fbff2adb6d7d0736
It looks like a regression in mesa. I can bisect it if I'll find a time.
My system information:
Intel HD4000 (Ivybridge)
Ubuntu 15.10 + Gnome 3.16
mesa 11.0.2
libdrm 2.4.64
xserver 1.17.2
xserver-xorg-video-intel 2.99.917~git20150808
supertuxkart 0.9.1
Note that you need at least SuperTuxKart 0.9 to reproduce this issue because we are using new OpenGL 3.x based renderer since this version.
**Attachment 119319**, "intel_mesa_10_3.png":
![intel_mesa_10_3](/uploads/1d14973231feb4de29ceff2eae940360/intel_mesa_10_3.png)
Version: git
### Blocking
* [Bug 93185](https://bugs.freedesktop.org/show_bug.cgi?id=93185)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1502Feature request: Implement __DRIimageExtension's blitImage2022-11-23T21:26:33ZBugzilla Migration UserFeature request: Implement __DRIimageExtension's blitImage## Submitted by Axel Davy `@axeldavy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92970)](https://bugs.freedesktop.org/show_bug.cgi?id=92970)**
## Description
blitImage is part of __DRIimageExtension Mesa ...## Submitted by Axel Davy `@axeldavy`
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#92970)](https://bugs.freedesktop.org/show_bug.cgi?id=92970)**
## Description
blitImage is part of __DRIimageExtension Mesa internal API.
It is used to blit from a surface to another (I don't expect it would be difficult to implement for an intel dev).
The extension is required for the secondary card for DRI_PRIME on egl/wayland, glx dri3 (and soon egl/x11 dri3).
While if you are on a dedicated card it doesn't make a lot of sense to use DRI_PRIME to render on the integrated gpu (thus explaining the current low interest to implement the function), we could imagine it be used by future wayland compositors when enabling the use of several displays connected to different cards (one of the big things wayland is supposed to solve).
As Wayland compositors begin to be more and more ready, I suggest to implement that function soon, so that when wayland compositors become ready enough to begin to implement advanced functionnalities, blitImage would be ready for intel as well for Mesa stable.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1503[PATCH] i965 fails to load miserably on musl libc due to underlinking2020-03-11T02:34:50ZBugzilla Migration User[PATCH] i965 fails to load miserably on musl libc due to underlinking## Submitted by Kylie McClain
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#93059)](https://bugs.freedesktop.org/show_bug.cgi?id=93059)**
## Description
Created attachment 120007
[PATCH] i965: don't underlin...## Submitted by Kylie McClain
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#93059)](https://bugs.freedesktop.org/show_bug.cgi?id=93059)**
## Description
Created attachment 120007
[PATCH] i965: don't underlink i965_dri.so, causes miserable failure on musl libc
musl libc doesn't like lazy binding, which i965_dri.so depends on to load correctly in Xorg. As such, it is underlinked and doesn't load because of linking issues on musl libc.
More information: http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc#Lazy_bindings
**Attachment 120007**, "[PATCH] i965: don't underlink i965_dri.so, causes miserable failure on musl libc":
[file_93059.txt](/uploads/ffad15f00967e781ee26dd87d1118b9e/file_93059.txt)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1504More verbose errors for dmabuf creation.2019-09-25T18:55:13ZBugzilla Migration UserMore verbose errors for dmabuf creation.## Submitted by Lubosz Sarnecki
Assigned to **Ian Romanick**
**[Link to original bug (#93138)](https://bugs.freedesktop.org/show_bug.cgi?id=93138)**
## Description
Created attachment 120173
More verbose errors for dmabuf creation....## Submitted by Lubosz Sarnecki
Assigned to **Ian Romanick**
**[Link to original bug (#93138)](https://bugs.freedesktop.org/show_bug.cgi?id=93138)**
## Description
Created attachment 120173
More verbose errors for dmabuf creation.
Using EXT_image_dma_buf_import on i965 can be confusing if you don't look in the code.
The driver always outputs EGL_BAD_MATCH for using multi planar formats. The practice here is to use multiple EGL images per plane and do the color conversion in GLSL.
The same error is given when the fourcc format is unsupported.
This patch gives the application programmer more information about what he is doing wrong, by putting out this information with _mesa_warning().
**Attachment 120173**, "More verbose errors for dmabuf creation.":
[0001-i965-More-verbose-errors-for-dmabuf-creation.patch](/uploads/1f6c8490e8b289469c5ad704a4bb8255/0001-i965-More-verbose-errors-for-dmabuf-creation.patch)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1505[BDW] GPU HANG: ecode 8:0:0x85dffffb, in steam [3539], reason: Ring hung, act...2019-10-20T13:46:25ZBugzilla Migration User[BDW] GPU HANG: ecode 8:0:0x85dffffb, in steam [3539], reason: Ring hung, action: reset## Submitted by Sören Beye
Assigned to **Sören Beye**
**[Link to original bug (#93166)](https://bugs.freedesktop.org/show_bug.cgi?id=93166)**
## Description
[ 66.756009] [drm] stuck on render ring
[ 66.757070] [drm] GPU HANG: ...## Submitted by Sören Beye
Assigned to **Sören Beye**
**[Link to original bug (#93166)](https://bugs.freedesktop.org/show_bug.cgi?id=93166)**
## Description
[ 66.756009] [drm] stuck on render ring
[ 66.757070] [drm] GPU HANG: ecode 8:0:0x85dffffb, in steam [3539], reason: Ring hung, action: reset
[ 66.757072] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 66.757073] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 66.757075] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 66.757076] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 66.757077] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 66.759234] drm/i915: Resetting chip after gpu hang
[ 66.928689] ------------[ cut here ]------------
[ 66.928715] WARNING: CPU: 3 PID: 0 at drivers/gpu/drm/i915/intel_uncore.c:620 hsw_unclaimed_reg_debug.isra.11+0x62/0x78 [i915]()
[ 66.928717] Unclaimed register detected before reading register 0x223a0
[ 66.928719] Modules linked in: md4 nls_utf8 cifs nfsv3 vmnet(O) binfmt_misc cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats vsock(O) vmci(O) vmmon(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc ch341 usbserial joydev hid_generic usbhid hid usb_storage arc4 brcmsmac cordic brcmutil x86_pkg_temp_thermal kvm_intel b43 kvm mac80211 cfg80211 ssb mmc_core jitterentropy_rng rfkill rng_core pcmcia pcmcia_core sha256_generic hmac snd_hda_codec_hdmi drbg iTCO_wdt iTCO_vendor_support ansi_cprng evdev snd_hda_codec_realtek snd_hda_codec_generic aesni_intel zram lz4_compress aes_x86_64 zsmalloc ablk_helper cryptd lrw snd_hda_intel gf128mul glue_helper i915 snd_hda_codec snd_hda_core snd_hwdep bcma snd_pcm snd_timer pcspkr drm_kms_helper i2c_i801 snd drm soundcore
[ 66.928766] lpc_ich mfd_core shpchp i2c_algo_bit i2c_core battery video acpi_cpufreq acpi_pad button processor coretemp loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 jbd2 mbcache microcode sg sd_mod ahci libahci crc32c_intel libata xhci_pci ehci_pci xhci_hcd ehci_hcd scsi_mod r8169 mii usbcore usb_common thermal fan thermal_sys
[ 66.928792] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G O 4.2.6 #1
[ 66.928793] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CRESCENTBAY, BIOS 5.6.5 08/29/2015
[ 66.928795] 0000000000000000 0000000000000009 ffffffff813c8003 ffff88021ed83d78
[ 66.928798] ffffffff81042ce2 0000000000000004 ffffffffa03dda2e 0000000000000002
[ 66.928800] ffff880215790078 00000000000223a0 00000000000223a0 ffff880215790078
[ 66.928803] Call Trace:
[ 66.928805] `<IRQ>` [`<ffffffff813c8003>`] ? dump_stack+0x40/0x50
[ 66.928812] [`<ffffffff81042ce2>`] ? warn_slowpath_common+0x98/0xb0
[ 66.928828] [`<ffffffffa03dda2e>`] ? hsw_unclaimed_reg_debug.isra.11+0x62/0x78 [i915]
[ 66.928831] [`<ffffffff81042d92>`] ? warn_slowpath_fmt+0x45/0x4a
[ 66.928847] [`<ffffffffa03dda2e>`] ? hsw_unclaimed_reg_debug.isra.11+0x62/0x78 [i915]
[ 66.928858] [`<ffffffffa03de3a4>`] ? gen6_read32+0x43/0xae [i915]
[ 66.928871] [`<ffffffffa03d6e7c>`] ? intel_lrc_irq_handler+0x30/0x186 [i915]
[ 66.928875] [`<ffffffff8105f2ad>`] ? check_preempt_curr+0x25/0x65
[ 66.928887] [`<ffffffffa03d0824>`] ? gen8_gt_irq_handler+0x69/0x1bd [i915]
[ 66.928898] [`<ffffffffa03d09e2>`] ? gen8_irq_handler+0x6a/0x3e5 [i915]
[ 66.928902] [`<ffffffff8107b151>`] ? handle_irq_event_percpu+0x4f/0x179
[ 66.928904] [`<ffffffff8107b2aa>`] ? handle_irq_event+0x2f/0x55
[ 66.928907] [`<ffffffff8107da36>`] ? handle_edge_irq+0xb1/0xd0
[ 66.928909] [`<ffffffff810050a4>`] ? handle_irq+0x18/0x20
[ 66.928911] [`<ffffffff81004ae5>`] ? do_IRQ+0x41/0xb1
[ 66.928915] [`<ffffffff813ccba8>`] ? common_interrupt+0x68/0x68
[ 66.928916] `<EOI>` [`<ffffffff812e98ed>`] ? cpuidle_enter_state+0x103/0x170
[ 66.928920] [`<ffffffff812e98af>`] ? cpuidle_enter_state+0xc5/0x170
[ 66.928923] [`<ffffffff8106c5e8>`] ? cpu_startup_entry+0x182/0x226
[ 66.928925] ---[ end trace d5720282c5d9890b ]---
This is a cheap Chinese passiively cooled NUC like computer with an i5-5257U and Intel Iris Pro 6200.
The OS is Debian jessie with xserver-xorg-video-intel from the backports (2:2.99.917-2~bpo8+1).
Kernel Linux ishimura 4.2.6 #1 SMP Wed Nov 18 20:21:58 CET 2015 x86_64 GNU/Linux
build from the kernel.org sources.
The Kernel parameter intel_iommu=igfx_off is set but doesn't help. The crashes are very frequent.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1506GPU HANG: ecode 7:0:0x86f29ff9, in MatQueue0 [7002], reason: Ring hung, actio...2022-06-02T22:33:27ZBugzilla Migration UserGPU HANG: ecode 7:0:0x86f29ff9, in MatQueue0 [7002], reason: Ring hung, action: reset## Submitted by Eugenio
Assigned to **Ian Romanick**
**[Link to original bug (#93181)](https://bugs.freedesktop.org/show_bug.cgi?id=93181)**
## Description
Created attachment 120220
Crash dump
Fedora 23 with all updates
dmesg:
[...## Submitted by Eugenio
Assigned to **Ian Romanick**
**[Link to original bug (#93181)](https://bugs.freedesktop.org/show_bug.cgi?id=93181)**
## Description
Created attachment 120220
Crash dump
Fedora 23 with all updates
dmesg:
[drm] stuck on render ring
[drm] GPU HANG: ecode 7:0:0x86f29ff9, in MatQueue0 [7002], reason: Ring hung, 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
drm/i915: Resetting chip after gpu hang
This happened while playing on steam, the computer didn't need a reboot however.
**Attachment 120220**, "Crash dump":
[dump](/uploads/9f432ebcbb7899d9ae975f33ca70c7ca/dump)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1507[snb] GPU hang in Chrome2022-06-02T22:33:20ZBugzilla Migration User[snb] GPU hang in Chrome## Submitted by Ard Biesheuvel
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#93402)](https://bugs.freedesktop.org/show_bug.cgi?id=93402)**
## Description
Created attachment 120542
lspci -v output
[ 7580.121...## Submitted by Ard Biesheuvel
Assigned to **Intel 3D Bugs Mailing List**
**[Link to original bug (#93402)](https://bugs.freedesktop.org/show_bug.cgi?id=93402)**
## Description
Created attachment 120542
lspci -v output
[ 7580.121408] [drm] stuck on render ring
[ 7580.121838] [drm] GPU HANG: ecode 6:0:0x85fffffc, in chrome [1549], reason: Ring hung, action: reset
[ 7580.121840] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 7580.121841] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 7580.121842] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 7580.121842] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 7580.121843] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 7580.123937] drm/i915: Resetting chip after gpu hang
Running Ubuntu 15.10 and Gnome Shell + Chrome Version 47.0.2526.106 (64-bit)
Manufacturer: Apple Inc.
Product Name: Macmini5,3
**Attachment 120542**, "lspci -v output":
[lspci](/uploads/5de92c82408f358be4c6f4292258f31f/lspci)