USB, display and ethernet ports in HP Thunderbolt dock don't work

When connecting dock to laptop following lines appear to dmesg:
[ 407.217872] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
[ 407.217885] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
[ 407.217893] pcieport 0000:00:1c.4: device [8086:a114] error status/mask=00000001/00002000
[ 407.217899] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
[ 407.750868] hp_wmi: Unknown event_id - 131073 - 0x1
[ 407.863552] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20160422/dswload2-330)
[ 407.863564] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20160422/psobject-227)
[ 407.863569] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff903add0f92f8), AE_ALREADY_EXISTS (20160422/psparse-542)
[ 407.863581] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff903add0f92f8), AE_ALREADY_EXISTS (20160422/psparse-542)
[ 407.863594] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E4C] (20160422/evgpe-592)
[ 408.175164] pci 0000:04:00.0: [8086:1578] type 01 class 0x060400
[ 408.175332] pci 0000:04:00.0: supports D1 D2
[ 408.175335] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.175565] pci 0000:04:00.0: System wakeup disabled by ACPI
[ 408.187146] pci 0000:05:00.0: [8086:1578] type 01 class 0x060400
[ 408.187340] pci 0000:05:00.0: supports D1 D2
[ 408.187343] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.187507] pci 0000:05:01.0: [8086:1578] type 01 class 0x060400
[ 408.187679] pci 0000:05:01.0: supports D1 D2
[ 408.187681] pci 0000:05:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.187825] pci 0000:05:02.0: [8086:1578] type 01 class 0x060400
[ 408.187995] pci 0000:05:02.0: supports D1 D2
[ 408.187997] pci 0000:05:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.188152] pci 0000:05:04.0: [8086:1578] type 01 class 0x060400
[ 408.188314] pci 0000:05:04.0: supports D1 D2
[ 408.188317] pci 0000:05:04.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.188478] pci 0000:04:00.0: PCI bridge to [bus 05-6e]
[ 408.188491] pci 0000:04:00.0: bridge window [mem 0xb4000000-0xe20fffff]
[ 408.188500] pci 0000:04:00.0: bridge window [mem 0x50000000-0x99ffffff 64bit pref]
[ 408.188619] pci 0000:06:00.0: [8086:1577] type 00 class 0x088000
[ 408.188645] pci 0000:06:00.0: reg 0x10: [mem 0xe2000000-0xe203ffff]
[ 408.188662] pci 0000:06:00.0: reg 0x14: [mem 0xe2040000-0xe2040fff]
[ 408.188855] pci 0000:06:00.0: supports D1 D2
[ 408.188857] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 408.189037] pci 0000:05:00.0: PCI bridge to [bus 06]
[ 408.189050] pci 0000:05:00.0: bridge window [mem 0xe2000000-0xe20fffff]
[ 408.189149] pci 0000:05:01.0: PCI bridge to [bus 07-39]
[ 408.189161] pci 0000:05:01.0: bridge window [mem 0xb4000000-0xcbefffff]
[ 408.189170] pci 0000:05:01.0: bridge window [mem 0x50000000-0x6fffffff 64bit pref]
[ 408.189292] pci 0000:05:02.0: PCI bridge to [bus 3a]
[ 408.189307] pci 0000:05:02.0: bridge window [mem 0xcbf00000-0xcbffffff]
[ 408.189436] pci 0000:05:04.0: PCI bridge to [bus 3b-6e]
[ 408.189...

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1696325

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc4

I got my laptop and installed Ubuntu a month ago. This issue has been active from the beginning.

I tried today mainline kernel v4.12-rc4 but it doesn't help.
Following lines appear to dmesg when connecting the dock into laptop with kernel v4.12-rc4 in use:
[ 2482.713699] hp_wmi: Unknown event_id - 131073 - 0x1
[ 2483.284641] ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20170303/dswload2-330)
[ 2483.284656] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20170303/psobject-241)
[ 2483.284664] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff8b739d18d528), AE_ALREADY_EXISTS (20170303/psparse-543)
[ 2483.284676] ACPI Error: Method parse/execution failed [\_GPE._E4C] (Node ffff8b739d18d528), AE_ALREADY_EXISTS (20170303/psparse-543)
[ 2483.284690] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E4C] (20170303/evgpe-646)
[ 2483.600163] pci 0000:04:00.0: [8086:1578] type 01 class 0x060400
[ 2483.600317] pci 0000:04:00.0: supports D1 D2
[ 2483.600319] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.600495] pci 0000:04:00.0: System wakeup disabled by ACPI
[ 2483.600696] pci 0000:05:00.0: [8086:1578] type 01 class 0x060400
[ 2483.600847] pci 0000:05:00.0: supports D1 D2
[ 2483.600848] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.600968] pci 0000:05:01.0: [8086:1578] type 01 class 0x060400
[ 2483.601117] pci 0000:05:01.0: supports D1 D2
[ 2483.601118] pci 0000:05:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.601230] pci 0000:05:02.0: [8086:1578] type 01 class 0x060400
[ 2483.601376] pci 0000:05:02.0: supports D1 D2
[ 2483.601378] pci 0000:05:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.601494] pci 0000:05:04.0: [8086:1578] type 01 class 0x060400
[ 2483.601642] pci 0000:05:04.0: supports D1 D2
[ 2483.601643] pci 0000:05:04.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.601784] pci 0000:04:00.0: PCI bridge to [bus 05-6e]
[ 2483.601796] pci 0000:04:00.0: bridge window [mem 0xb4000000-0xe20fffff]
[ 2483.601803] pci 0000:04:00.0: bridge window [mem 0x50000000-0x99ffffff 64bit pref]
[ 2483.601894] pci 0000:06:00.0: [8086:1577] type 00 class 0x088000
[ 2483.601925] pci 0000:06:00.0: reg 0x10: [mem 0xe2000000-0xe203ffff]
[ 2483.601938] pci 0000:06:00.0: reg 0x14: [mem 0xe2040000-0xe2040fff]
[ 2483.602113] pci 0000:06:00.0: supports D1 D2
[ 2483.602115] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2483.602285] pci 0000:05:00.0: PCI bridge to [bus 06]
[ 2483.602296] pci 0000:05:00.0: bridge window [mem 0xe2000000-0xe20fffff]
[ 2483.602372] pci 0000:05:01.0: PCI bridge to [bus 07-39]
[ 2483.602383] pci 0000:05:01.0: bridge window [mem 0xb4000000-0xcbefffff]
[ 2483.602390] pci 0000:05:01.0: bridge window [mem 0x50000000-0x6fffffff 64bit pref]
[ 2483.602459] pci 0000:05:02.0: PCI bridge to [bus 3a]
[ 2483.602470] pci 0000:05:02.0: bridge window [mem 0xcbf00000-0xcbffffff]
[ 2483.602543] pci 0000:05:04.0: PCI bridge to [bus 3b-6e]
[ 2483.602553] pci 0000:05:04.0: bridge window [mem 0xcc000000-0xe1ffffff]
[ 2483.602560] pci 0000:05:04.0: bridge window [mem 0x70000000-0x99ffffff 64bit pref]
[ 2483.602596] p...

Thunderbolt support for PCs is included in v4.13-rc1 and later kernels. Do you have a possibility to try the latest mainline kernel?

Note the userspace support is not yet ready so you need to authorize device manually. See for example:https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html how it can be done.

Unfortunately I don't have that laptop anymore. Currently I have Dell
Precision M5520 with Ubuntu 16.04 pre-installed and almost everything is
working excellently with its TB16 dock.

(3440x1440 resolution through HDMI is not always working at first try, but
after disabling and enabling few times the external display from System
Settings > Display, it starts to work. But that might be some hardware or
cable issue.)

I am using mainline kernel v4.12.5 installed with Ukuu.

18.8.2017 22.41 "Mika Westerberg" <email address hidden> kirjoitti:

Thunderbolt support for PCs is included in v4.13-rc1 and later kernels.
Do you have a possibility to try the latest mainline kernel?

Note the userspace support is not yet ready so you need to authorize
device manually. See for example:https://www.kernel.org/doc/html/latest
/admin-guide/thunderbolt.html how it can be done.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1696325

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  $ lsb_release -rd
  Description: Ubuntu 16.04.2 LTS
  Release: 16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
    Installed: 4.8.0.54.25
    Candidate: 4.8.0.54.25
    Version table:
   *** 4.8.0.54.25 500
          500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
          500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
          100 /var/lib/dpkg/status
  ---
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1: markus 3304 F.... pulseaudio
   /dev/snd/controlC0: markus 3304 F.... pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600
(model 1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8....

Hi guys, I have indirect comment, but related to thuderbold support. I have Dell xps 13 and by running on 4.12.12 kernel I get same messages on Dell DA200 UCB-C adapter (provides HDMI and Ethernet and VGA and USB). In didn't get it working yet, but just testing it with latest available kernel on Gentoo system =4.15.7 (release 1).

I found in my case information that it might help if I upgrade the thunderbolt firmware in the laptop, which dell made open source: https://github.com/dell/thunderbolt-nvm-linux

Not sure if HP provides you with Thunderbolt firmware update for Linux (although in case of Dell the files are extractable from Windows CAB files, but I am studying it at the moment)

I confirm that after upgrade to latest 4.15.7 and few changes to kernel config my adapter DA200 works via USB-C as expected.

I've got the same setup as the original report and the problem still exists on a fully upgrade BIOS and dock firmware (under certain circumstances).

1. the setup works with Thunderbolt 3 security disable (set to NONE) in the BIOS

2. with TB3 security set to "secure", cold plugging the dock leads to a non working setup, even replugging the dock can not make it work

during boot a error and a some kernel oops are logged (I'll attach the log file):

error message:

[ 5.194097] thunderbolt 0000:07:00.0: unexpected hop count: 1023
[ 5.195229] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 5.195250] ipmi device interface
[ 5.195679] thunderbolt 0000:07:00.0: NHI initialized, starting thunderbolt
[ 5.195682] thunderbolt 0000:07:00.0: allocating TX ring 0 of size 10
[ 5.195695] thunderbolt 0000:07:00.0: allocating RX ring 0 of size 10
[ 5.195706] thunderbolt 0000:07:00.0: control channel created
[ 5.195707] thunderbolt 0000:07:00.0: control channel starting...
[ 5.195709] thunderbolt 0000:07:00.0: starting TX ring 0
[ 5.195715] thunderbolt 0000:07:00.0: enabling interrupt at register 0x38200 bit 0 (0xffffffff -> 0xffffffff)

oops:

[ 5.195716] ------------[ cut here ]------------
[ 5.195717] thunderbolt 0000:07:00.0: interrupt for TX ring 0 is already enabled
[ 5.195739] WARNING: CPU: 6 PID: 203 at drivers/thunderbolt/nhi.c:106 ring_interrupt_active+0x20b/0x250 [thunderbolt]
[ 5.195739] Modules linked in: ipmi_devintf(+) thunderbolt(+) intel_lpss_pci(+) i2c_hid nvme_core(+) rtsx_pci(+) ipmi_msghandler intel_lpss hid pinctrl_sunrisepoint pinctrl_intel fjes(-)
[ 5.195747] CPU: 6 PID: 203 Comm: systemd-udevd Not tainted 4.19.0-13-generic #14-Ubuntu
[ 5.195748] Hardware name: HP HP ZBook Studio G3/80D4, BIOS N82 Ver. 01.37 01/03/2019
[ 5.195753] RIP: 0010:ring_interrupt_active+0x20b/0x250 [thunderbolt]
[ 5.195754] Code: 48 89 55 c8 4c 89 4d d0 e8 22 72 bd f6 4c 8b 4d d0 48 8b 55 c8 45 89 f0 4c 89 e1 48 89 c6 48 c7 c7 60 bb 0c c0 e8 17 ab 5d f6 <0f> 0b e9 38 ff ff ff 44 03 6a 60 e9 54 fe ff ff 41 0f b6 47 78 d3
[ 5.195755] RSP: 0018:ffffb0d681f7f9a0 EFLAGS: 00010086
[ 5.195757] RAX: 0000000000000000 RBX: 00000000ffffffff RCX: ffff9391618d8000
[ 5.195757] RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000002
[ 5.195758] RBP: ffffb0d681f7f9d8 R08: 0000000000000000 R09: 0000000000022600
[ 5.195759] R10: 00000011cc6c3e93 R11: 000000000002cd30 R12: ffffffffc00cb1e9
[ 5.195760] R13: 0000000000038200 R14: 0000000000000000 R15: ffff9391615cb9c0
[ 5.195762] FS: 00007ff380e628c0(0000) GS:ffff93916f780000(0000) knlGS:0000000000000000
[ 5.195763] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.195763] CR2: 00007ff380e5f767 CR3: 00000004a0c60001 CR4: 00000000003606e0
[ 5.195765] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 5.195765] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 5.195766] Call Trace:
[ 5.195772] tb_ring_start+0xf4/0x190 [thunderbolt]
[ 5.195777] tb_ctl_start+0x3c/0x90 [thunderbolt]
[ 5.195783] tb_domain_add+0x60/0x150 [thunderbolt]
[ 5.195787] nhi_probe+0x2c6/0x560 [thunde...

Forgot to add, this is with Disco,

kernel 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Hi, the BIOS is expected to configure the PCI bridges leading to the TBT controller but it does not seem to do that:

[ 3.725792] pci 0000:06:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.725799] pci 0000:06:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.725807] pci 0000:06:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 3.725814] pci 0000:06:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring

to me this looks like a BIOS issue.

I'm not sure how the bridge initialization is supposed to work with TB3 security. But, I would guess that the dock needs to be authorized first before the PCIE bridges can be initialized.

Since the BIOS is not handling the TB3 authorization, it might not be able to access the bridges. So the task of bringing them up would fall to the OS.

On "legacy enumeration" systems, such as this one the BIOS SMI handler enumerates the PCI bridges before handing off to the OS. The bridges here are the TBT host router bridges so no need for any authorization.