[DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

[udippel]

Since my upgrade from 18.04 to 20.04 I experience rather frequent crashes of the X server. Nothing specific of applications running, presumably at videos (VLC, Youtube in a browser tab ...).

If not yet attached, I'll attach the *.old log with the most recent trace.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Dec 7 22:15:34 2020
DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
InstallationDate: Installed on 2019-02-16 (660 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20CHS10P02
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
dmi.bios.date: 03/24/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ETB2W (2.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CHS10P02
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
dmi.product.family: ThinkPad Helix 2nd
dmi.product.name: 20CHS10P02
dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
dmi.product.version: ThinkPad Helix 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

Looks like the issue is:

[ 15285.452] (EE) Backtrace:
[ 15285.453] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55b0f2a4952c]
[ 15285.455] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f1c35a1241f]
[ 15285.458] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f1c3584f18b]
[ 15285.462] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f1c3582e859]
[ 15285.465] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.465] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f1c33a4d3a9]
[ 15285.466] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x2038c7) [0x7f1c346405f7]
[ 15285.468] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x24f35) [0x7f1c33a9d6a5]
[ 15285.470] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x24fa4) [0x7f1c33a9d7a4]
[ 15285.472] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.472] (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f1c36368c90]
[ 15285.474] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 15285.474] (EE) 9: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f1c3636b8f0]
[ 15285.474] (EE) 10: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x55b0f28ec995]
[ 15285.475] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x55b0f2a42ba2]
[ 15285.475] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b0f28e7cf7]
[ 15285.476] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55b0f28ebfc4]
[ 15285.479] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f1c358300b3]
[ 15285.479] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2e) [0x55b0f28d5a2e]

[Daniel van Vugt (vanvugt)]

This appears to be the same as bug 1906642.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

The DisplayLink engineer I asked no longer works for DisplayLink :(

The next step for anyone affected would be to try and get a better quality stack trace because we need to find out what part of iris_dri.so is really crashing. If you're on Ubuntu 20.04 then please install:

  https://launchpad.net/ubuntu/+archive/primary/+files/libgl1-mesa-dri-dbgsym_20.2.6-0ubuntu0.20.04.1_amd64.ddeb

and then send us the system logs (journalctl output) from the crash next time it happens.

[Daniel van Vugt (vanvugt)]

Alternatively, you might like to try using 'Ubuntu on Wayland' instead. If you then encounter any crashes in gnome-shell, please report them as new bugs and mention the bug IDs here.

[paquin pierre (castrogne)]

Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time

[Daniel van Vugt (vanvugt)]

Thanks, but it looks the same :(

(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x557db676a59c]
(EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fbec831b41f]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fbec815818b]
(EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fbec8137859]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fbec62a8aec]
(EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fbec6ffac9c]
(EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d)

If you already have libgl1-mesa-dri-dbgsym_20.2.6-0ubuntu0.20.04.1_amd64.ddeb installed then it seems the problem right now is that Xorg doesn't know how to load debug symbols.

https://errors.ubuntu.com/ is also not showing me any Xorg crashes from your system since January. So I think we need to do one of two things:

* Attach a debugger to the Xorg process before it crashes; or

* Configure Xorg to dump core properly and not try to catch its own crashes.

[paquin pierre (castrogne)]

Hi,

Ok, if there's nothing here about xorg crash, how may I provide you more information about that :
ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt
.....
-rw-r----- 1 username whoopsie 17322105 févr. 10 14:15 _usr_lib_xorg_Xorg.1000.crash

It seems I have some informations on my system about crash. but the following command doesn't work. I have a message with some "internal error" :
sudo ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

Thanks,

[paquin pierre (castrogne)]

Oh I forgot, Yes, i have installed dbgsym :

$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for xserver-xorg-core

[paquin pierre (castrogne)]

Well if I couldn't use ubuntu bug, I could use that, hope it'll help :
apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash

It then create this bug entry :
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375

[Daniel van Vugt (vanvugt)]

Great, thanks! That's a duplicate of bug 1871959 which has useful debug symbols. Unless/until any evidence can be found that this bug is not the same, I will mark it as a duplicate of bug 1871959.

[paquin pierre (castrogne)]

Hi,

Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I don't think I have installed myself this. If it cause the bug, is it possible to remove it?

Thanks,

[Daniel van Vugt (vanvugt)]

Mesa is the core graphics library. Everything uses it and you can't remove it.