WD19 dock stops working in Ubuntu 21.04

Bug #1926809 reported by Daniel Mulholland
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This morning I upgraded to Kubuntu 21.04.

I use two external monitors connected to my Dell XPS laptop via a Dell WD19 dock.

Post-upgrade the monitors and also network functionality through the dock appear to have completely stopped functioning.

When the dock is plugged in and the computer is booted the monitors do not enable.
When the dock is not plugged in the computer boots normally.

When I look at the dmesg output there appears to be some notable errors when I plug the dock in:

[ 516.173451] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ 516.207480] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 521.313422] pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[ 555.140320] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ 555.140343] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 560.291086] pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[ 850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 851.717630] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 851.815190] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 856.320487] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 856.343208] i915 0000:00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
[ 856.382831] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 860.704920] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 860.765138] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 860.894454] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 860.965337] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 861.115198] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 861.182111] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 866.351715] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 866.473097] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 866.534697] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

With the dock plugged in:

* neither monitor displays although they are present under display configuration
* since my laptop screen is not usually on if both monitors are present on the dock the immediate result was no display at all under the dock was detached
* network connectivity is not established although the network device appears under networks

Unfortunately I lack the skills to diagnose this further without assistance or to install a more recent kernel to see if it is resolved there.

It appears that communications between the laptop and the Dock are not going well to my eyes (is this what link training is on Thunderbolt)

I'm happy to provide further information... although in a few days the lack of Dock and monitors will be a bit of an issue and I may have to roll something back.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: mulhollandd 1940 F.... pulseaudio
 /dev/snd/controlC1: mulhollandd 1940 F.... pulseaudio
 /dev/snd/controlC0: mulhollandd 1940 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat May 1 08:57:26 2021
InstallationDate: Installed on 2020-06-13 (321 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-16-generic N/A
 linux-backports-modules-5.11.0-16-generic N/A
 linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-04-30 (0 days ago)
dmi.bios.date: 03/09/2021
dmi.bios.release: 2.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.15.1
dmi.board.name: 0115N5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:br2.15:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0115N5:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.

Revision history for this message
Daniel Mulholland (dan-mulholland) wrote :
Revision history for this message
Daniel Mulholland (dan-mulholland) wrote :

Some functionality still appears to work correctly -- headphones plugged into the Dock appear to function.

Revision history for this message
Daniel Mulholland (dan-mulholland) wrote :

When I boot to use an older kernel, initially things appear no better -- no monitors except the laptop and after logging into Kubuntu no monitors at all.

After removing the USB-C connection and plugging it back in again both monitors come back, headphones work but the wired network connection does not work.

Here's some dmesg output for this:

mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err
[ 95.459529] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ 95.459573] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 100.553294] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 100.553301] pcieport 0000:00:1c.0: AER: device [8086:9d10] error status/mask=00000001/00002000
[ 100.553306] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 100.630562] pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
mulhollandd@mulhollandd-XPS-13-9360:~$ # no monitors but when I unplug and replug both monitors come back
mulhollandd@mulhollandd-XPS-13-9360:~$ # now a new dmesg output
mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err
[ 95.459529] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ 95.459573] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 100.553294] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 100.553301] pcieport 0000:00:1c.0: AER: device [8086:9d10] error status/mask=00000001/00002000
[ 100.553306] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 100.630562] pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[ 158.228726] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[ 158.228734] pcieport 0000:00:1c.4: AER: device [8086:9d14] error status/mask=00001000/00002000
[ 158.228739] pcieport 0000:00:1c.4: AER: [12] Timeout
mulhollandd@mulhollandd-XPS-13-9360:~$ # we are on an older kernel now
mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a
Linux mulhollandd-XPS-13-9360 5.8.0-50-generic #56-Ubuntu SMP Mon Apr 12 17:18:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
mulhollandd@mulhollandd-XPS-13-9360:~$

I should note that the AER PCIe Bus Errors have been present I think for many years and versions of Ubuntu so I think they are unrelated. However the power state transition from "D3cold to D0 (config space inaccessible)" is I think new.

Happy to provide further information.

Revision history for this message
Daniel Mulholland (dan-mulholland) wrote :

It may be that this (fixed) bug is related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903969

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
description: updated
Revision history for this message
Daniel Mulholland (dan-mulholland) wrote :

I used the mainline tool to install kernel 5.12.

The dock is back again and everything appears to work.

```
mulhollandd@mulhollandd-XPS-13-9360:~$ uname -a
Linux mulhollandd-XPS-13-9360 5.12.0-051200-generic #202104252130 SMP Sun Apr 25 21:33:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
mulhollandd@mulhollandd-XPS-13-9360:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
mulhollandd@mulhollandd-XPS-13-9360:~$ sudo dmesg --level=err
[sudo] password for mulhollandd:
[ 0.011338] efi: Failed to lookup EFI memory descriptor for 0x000000007b014000
[ 14.615560] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ 14.615574] xhci_hcd 0000:39:00.0: HC died; cleaning up
[ 15.030088] usb 4-1.3: device not accepting address 3, error -108
[ 15.030150] usb 4-1-port3: couldn't allocate usb_device
[ 15.030198] usb 3-1-port5: couldn't allocate usb_device
[ 112.758908] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 00000000b3a810eb port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
mulhollandd@mulhollandd-XPS-13-9360:~$
```

Revision history for this message
Harald (hschmitt) wrote :
Revision history for this message
Jeroen (c0p3rn1c) wrote :

What exact version of the mainland kernel would you recommend?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ubuntu 21.04 is no longer supported but we are tracking the same issue in bug 1970495 still.

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.