segfault in iris_dri.so

Bug #1877879 reported by Lukas Hejtmanek
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL.

This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver.

(gdb) run
Starting program: /usr/bin/glxgears
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff17cf700 (LWP 97070)]
[New Thread 0x7fffebfff700 (LWP 97071)]
[New Thread 0x7ffff0fce700 (LWP 97072)]
[New Thread 0x7fffeb7fe700 (LWP 97073)]

Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
0x00007ffff6a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(gdb) where
#0 0x00007ffff6a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#1 0x00007ffff6c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#2 0x00007ffff6a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007ffff6a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007ffff6099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x000055555555711e in ?? ()
#6 0x0000555555556c88 in ?? ()
#7 0x00007ffff7ace0b3 in __libc_start_main (main=0x555555556410, argc=1, argv=0x7fffffffe698, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe688) at ../csu/libc-start.c:308
#8 0x0000555555556f0a in ?? ()
(gdb)

I believe, this is a bug in mesa tracked here:
https://gitlab.freedesktop.org/mesa/mesa/issues/1358

packages versions:
libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64
xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64
xserver-xorg-core 2:1.20.8-2ubuntu2 amd64

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1876219, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Adamski (danadam) wrote :

AFAICT bug 1876219 is about a newer driver, iris, being used for older cards, gen6. Affected cards from that report:
- "Mine is gen6 so the problem is with the default choice of graphics driver"
- "For me (core m5 6th generation) I noticed that mpv/celluloid is crashing"
- "I have an Intel I7-5600U ... and I'm currently affected by this bug as well."
- "Same problem here (Ubuntu 20.04, i915 driver, Skylake Intel(R) Core(TM) i7-6500U CPU"

Is it still a duplicate if for me the crash happens with a new card, gen8, with which the newer driver is supposed to work? My hardware:
CPU: Intel Core i5-8250U
GPU: Intel UHD Graphics 620 (GT2)

Revision history for this message
Patrick Fasano (kc9jud) wrote :

I have a similar hardware configuration (Intel(R) Core(TM) i5-8265U and Mesa Intel(R) UHD Graphics 620) and see this issue as well. I don't believe it's the same bug as bug 1876219.

Revision history for this message
Oibaf (oibaf) wrote :

Ubuntu 20.04 now has mesa version 21.2.6-0ubuntu0.1~20.04.2, newer than the 20.0.4-2ubuntu1 where you reported the bug.
Can you update and check if the issue is still reproducible?

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mesa (Ubuntu) because there has been no activity for 60 days.]

Changed in mesa (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.