*** This bug is a duplicate of bug 1876219 ***
https://bugs.launchpad.net/bugs/1876219
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.
** This bug has been marked a duplicate of bug 1876219
iris driver for old cpu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1877879
Title:
segfault in iris_dri.so
Status in mesa package in Ubuntu:
New
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
