How to avoid DisplayLink dock monitors disconnecting intermittently?

## Symptoms Every few minutes/hours the displays connected to the USB3 DisplayLink dock turn off for a few seconds and back on again. ## Hardware - Dell docking station model D6000 - USB3 connection to HP laptop (happens on at least three different models) - DisplayPort connections to two HP monitors ## OS - Arch Linux - Ubuntu 20.04 ## Software - displaylink 5.3.1.34-4 and other versions ## Logs I was lucky to catch only a few log entries in the journal while one of these instances happened. I've included *all* the raw logs around this time, including before the disconnect and after the reconnect:

Dec 04 09:54:25 host gnome-shell: libinput error: event5  -       Das Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow
Dec 04 09:55:43 host kernel: usb 4-1.1: Disable of device-initiated U1 failed.
Dec 04 09:55:43 host kernel: usb 4-1.1: Disable of device-initiated U2 failed.
Dec 04 09:55:43 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: unregister 'cdc_ncm' usb-0000:37:00.0-1.1, CDC NCM
Dec 04 09:55:43 host NetworkManager:   [1607028943.8418] device (ens4u1u1i5): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Dec 04 09:55:43 host dhcpcd: ens4u1u1i5: removing interface
Dec 04 09:55:43 host kernel: usb 4-1.1: Set SEL for device-initiated U1 failed.
Dec 04 09:55:43 host kernel: usb 4-1.1: Set SEL for device-initiated U2 failed.
Dec 04 09:55:44 host kernel: usb 4-1.1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 04 09:55:44 host kernel: usb 4-1.1: Warning! Unlikely big volume range (=767), cval->res is probably wrong.
Dec 04 09:55:44 host kernel: usb 4-1.1:  FU [Mic Capture Volume] ch = 2, val = -4592/7680/16
Dec 04 09:55:44 host kernel: usb 4-1.1: Warning! Unlikely big volume range (=672), cval->res is probably wrong.
Dec 04 09:55:44 host kernel: usb 4-1.1:  FU [Dell USB Audio Playback Volume] ch = 6, val = -10752/0/16
Dec 04 09:55:44 host upowerd: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1.1
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: MAC-Address: 9c:eb:e8:f2:8e:31
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: setting rx_max = 16384
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: setting tx_max = 16384
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 usb0: register 'cdc_ncm' at usb-0000:37:00.0-1.1, CDC NCM, 9c:eb:e8:f2:8e:31
Dec 04 09:55:44 host kernel: usb 4-1.1: usbfs: process 173165 (ActiveCommandQu) did not claim interface 0 before use
Dec 04 09:55:44 host NetworkManager:   [1607028944.2517] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/9)
Dec 04 09:55:44 host systemd-udevd: Using default interface naming scheme 'v245'.
Dec 04 09:55:44 host boltd: probing: started 
Dec 04 09:55:44 host systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: renamed from usb0
Dec 04 09:55:44 host upowerd: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1.1
Dec 04 09:55:44 host NetworkManager:   [1607028944.2787] device (usb0): interface index 8 renamed iface from 'usb0' to 'ens4u1u1i5'
Dec 04 09:55:44 host NetworkManager:   [1607028944.2835] device (ens4u1u1i5): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 04 09:55:44 host NetworkManager:   [1607028944.2859] settings: (ens4u1u1i5): created default wired connection 'Wired connection 1'
Dec 04 09:55:44 host systemd-udevd: Using default interface naming scheme 'v245'.
Dec 04 09:55:44 host systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 04 09:55:44 host dhcpcd: ens4u1u1i5: waiting for carrier
Dec 04 09:55:44 host dhcpcd: ens4u1u1i5: waiting for carrier
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: network connection: disconnected
Dec 04 09:55:47 host boltd: probing: timeout, done:  (2000000)

## Other This has been observed by a bunch of people on similar software and hardware, not just the ones above. It also happens on Windows 10, for example.