Crash with SIGABRT in _iris_batch_flush from iris_fence_flush()

[Mc]

https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

---

nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.7-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 10 00:50:52 2020
DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
DistroCodename: focal
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
InstallationDate: Installed on 2019-11-27 (134 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD
 Bus 001 Device 003: ID 8087:0029 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5500
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
Title: Xorg crashed with SIGABRT in __GI_raise()
UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
UserGroups:

dmi.bios.date: 08/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0M14W7
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5500
dmi.product.sku: 08B9
dmi.sys.vendor: Dell Inc.
separator:

version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Apport retracing service (apport)]

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 _iris_batch_flush.cold () from /tmp/apport_sandbox_wp79yx1l/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 iris_fence_flush () from /tmp/apport_sandbox_wp79yx1l/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 st_glFlush () from /tmp/apport_sandbox_wp79yx1l/usr/lib/x86_64-linux-gnu/dri/iris_dri.so

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Tracking in:

https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a

[Sebastien Bacher (seb128)]

The recent duplicates refers to https://gitlab.freedesktop.org/mesa/mesa/issues/1358

[Daniel van Vugt (vanvugt)]

Re comment #9, I don't think mesa#1358 is the same as this. It's crashing with a different signal, in a different function :)

[Daniel van Vugt (vanvugt)]

Anyone affected by this crash, please report it to the Mesa developers at:

  https://gitlab.freedesktop.org/mesa/mesa/-/issues

and then tell us the new issue ID.

[Daniel van Vugt (vanvugt)]

Weird: The debug symbols for iris_dri.so don't seem to have worked on this bug. They didn't work in comments #4 and #5 above and they didn't work in duplicate bug reports even when the debug symbols were definitely installed before the crash was reproduced.

[paquin pierre (castrogne)]

Hi,

I created an account on mesa forum. I don't really know what to tell, and which file send them. Can you help me and tell me what to say and send?

Thanks,

[Daniel van Vugt (vanvugt)]

Some line number info from bug 1915375:

 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 _iris_batch_flush (batch=batch@entry=0x557db808c938, file=<optimized out>, file@entry=0x7fbec72f6d68 "../src/gallium/drivers/iris/iris_fence.c", line=line@entry=248) at ../src/gallium/drivers/iris/iris_batch.c:750
 iris_fence_flush (ctx=0x557db808c4b0, out_fence=0x0, flags=<optimized out>) at ../src/gallium/drivers/iris/iris_fence.c:248
 st_flush (flags=0, fence=0x0, st=0x557db80a9900) at ../src/mesa/state_tracker/st_cb_flush.c:60

[Daniel van Vugt (vanvugt)]

I've logged it for you:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275

[Daniel van Vugt (vanvugt)]

Good news: This is only happening in kernel 5.4-5.6. No reports from kernel 5.8.

[Daniel van Vugt (vanvugt)]

Please try this:

  sudo apt update
  sudo apt install linux-generic-hwe-20.04

and then reboot.

[paquin pierre (castrogne)]

Hello,

Well I tried... and have some troubles :). After reboot, displaylink didn't work anymore. I tried to uninstall but when I try to reinstall, here what I get :
ERROR (dkms apport): binary package for evdi: 1.7.0 not found
Error! Bad return status for module build on kernel: 5.8.0-43-generic (x86_64)
Consult /var/lib/dkms/evdi/1.7.0/build/make.log for more information.
ERROR: Failed to install evdi/5.3.1.34 to the kernel tree.

I know this is ubuntu, not displaylink, but if you have any idea that would be great.

Notice : If i run install twice, I got only 1 error : "Error! DKMS tree already contains: evdi-1.7.0" and installation continue. But don't work... Uninstall / reinstall will do same thing (1st fatal error that stop installer, then this one)

[paquin pierre (castrogne)]

Hello,

This is why you have no report from kernel 5.8+ :
"The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg version is 1.16 and minimum supported Mutter (Wayland) is 3.32."

https://support.displaylink.com/knowledgebase/articles/684649

Some people seems to have kernel 5.9 working, but I tried without success, still have the above message. Here's an entry on DisplayLink forum with the same problem :
https://displaylink.org/forum/showthread.php?t=67561

I can't create an account on this forum, don't know why... The mail with code never arrive. If anyone has my problem, he can reply on displaylink forum to get help with kernel 5.8+

Here's a tuto for kernel 5.9, don't work for me, but seemed to help sometimes :
https://displaylink.org/forum/showpost.php?p=90853&postcount=2

[Daniel van Vugt (vanvugt)]

Sorry to hear that. To remove the 5.8 kernel packages, first run this command to find their names:

  dpkg -l | grep 5.8.0 | grep linux | awk '{print $2;}'

Then you can remove them with:

  sudo dpkg -P PACKAGENAMES

[paquin pierre (castrogne)]

Hi, thanks,

can't I just do a sudo apt purge linux-generic-hwe-20.04 ?

For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the subject you opened on https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have some news. That's very technical, can you put here informations when you have a piece of solution ?

Many thanks

[paquin pierre (castrogne)]

Hello,

I sent a mail to DisplayLink, here is their answer...
"
Thank you for bringing it to our attention but based on the log files and errors over there the best way would be to discuss it with Xorg engineers as the majority of problems comes from the OS itself and not from our driver here.
"

Do you have any news about the bug?

Thanks

[paquin pierre (castrogne)]

Hi,

Last message seems to indicate that a fix is found, good news! Anything to do to get the fix?

Thanks,

[Daniel van Vugt (vanvugt)]

We are waiting for either:

* A Mesa developer to cherry pick the fix into 20.2; or

* Mesa 22.0 to reach a future version of Ubuntu.

[Timo Aaltonen (tjaalton)]

20.2.x is dead, next upstream version is 21.0.0 which we'll get in hirsute once released

[Daniel van Vugt (vanvugt)]

The fix isn't in the 21.0 branch yet. Only on master (22).

[Daniel van Vugt (vanvugt)]

Upstream are not totally sure that fix also addresses this crash so reopened for now.

[paquin pierre (castrogne)]

Hello,

Any news on when it will be solved ? No update solved it on my ubuntu with officials updates.

Thanks,

[Daniel van Vugt (vanvugt)]

The Mesa developers won't be monitoring this bug. For more current information please subscribe to https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 instead.

[Daniel van Vugt (vanvugt)]

Fixed in bug 1918855?

[paquin pierre (castrogne)]

Well, maybe or not but I don't understand how to install the patch

[paquin pierre (castrogne)]

Hello Daniel,

So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if the patch will be in next 22.04 LTS ? Or maybe there's a way to patch 20.04?

Thanks,

[Daniel van Vugt (vanvugt)]

I don't see any fix on the way. If you're affected by this bug then please also subscribe to https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

[paquin pierre (castrogne)]

Hello,

You spoke about a fixed in your comment on 2021-06-22 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30 . Is that to say that no fix will be part of Ubuntu next LTS version 22.04?

I see your link on mesa. No reponse since 8 months. In your comment on 2021-03-05 you sid "The fix isn't in the 21.0 branch yet. Only on master (22)." => is that to say that Ubuntu 22.04 will have the fix ?

Thanks

[Timo Aaltonen (tjaalton)]

Bug 1918855 is fixed in focal and up, so if you still have crashes then that was not your bug/fix.

[Daniel van Vugt (vanvugt)]

Comment #30 was only a question, not a statement :)

[paquin pierre (castrogne)]

Hello,

Thanks for your answers. I did a full update/upgrade and install latest displaylink driver. I'll let you know if crash still here.

"X server crash in iris driver" subject is still open, no news since 8 months. Any way to know if it's still in progress or if it's on pause? I just try to know if this problem will be still there in next Ubuntu LTS release.

Thanks,

[paquin pierre (castrogne)]

I can confirm crash on latest 20.04 is still there.

[Daniel van Vugt (vanvugt)]

No crashes after 20.10 so consider it fixed.

[udippel (udippel)]

Yep. here, on 20.04 it crashed a few days ago, for the last time. With 22.04.1 it doesn't crash any longer.
Though that's not a big help: there is simply no second display. I installed the most recent driver from DisplayLink, 5.6.1. There was no error or warning message, just that I had to reboot. Did so, and just nothing. Not recognized in System settings, and xrandr states:
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

Fortunately, I can exclude Dock, cables and so forth, since it is a dual-boot to W10. And just rebooting, choosing W10, works flawlessly.

Here it also used to work, before this bug, on a daily basis. I usually work on a laptop, with lid closed, and all screen content on an external monitor. Then this bug appeared, and now the bug is gone, the screen stays black.

Any idea appreciated, what I could do.

[udippel (udippel)]

Update/edit: On the Display-Link forum I have found in the meantime, that I'm not the only one.
It seems that it doesn't work with 22.04, x11, due to a gdm3 problem. It only works on Wayland, but the selection gear doesn't work. There are some 'askubuntu' items available, confirming this.

(What the heck, 22.04 seems to have quite some problems; for an update of LTS! - No x11 Displaylink, no WiFi, no usrmerge. And nobody stopped it?)

[Daniel van Vugt (vanvugt)]

Yes we know 20.04 is still crashing, but Fix Released is still the correct status if it's fixed in any later release.

[Daniel van Vugt (vanvugt)]

If you encounter any issues in 22.04 then please be sure to report separate bugs for each.