* Thunderbolt call trace occurs on hot-plug
@ 2025-07-11 3:54 En-Wei WU
2025-07-28 6:33 ` Mika Westerberg
0 siblings, 1 reply; 7+ messages in thread
From: En-Wei WU @ 2025-07-11 3:54 UTC (permalink / raw)
To: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb
Hi,
I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
the following call trace. The issue reproduces approximately 60% of
the time.
kern :info : [ 370.181263] usb 5-11: New USB device found,
idVendor=1d5c, idProduct=5801, bcdDevice= 1.01
kern :info : [ 370.181265] usb 5-11: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
kern :info : [ 370.181266] usb 5-11: Product: USB2.0 Hub
kern :info : [ 370.181267] usb 5-11: Manufacturer: Fresco Logic, Inc.
kern :info : [ 370.182473] hub 5-11:1.0: USB hub found
kern :debug : [ 370.182958] i915 0000:00:02.0:
[drm:intel_power_well_disable [i915]] disabling PW_2
kern :info : [ 370.183853] hub 5-11:1.0: 6 ports detected
kern :debug : [ 370.212505] [375]
thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 0:1:
link maximum bandwidth 36000/36000 Mb/s
kern :info : [ 370.215094] usb 5-11: USB disconnect, device number 29
kern :debug : [ 370.218522] [165] thunderbolt:tb_cfg_ack_plug:842:
thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
kern :debug : [ 370.297820] i915 0000:00:02.0: [drm:intel_dpt_create
[i915]] Allocating dpt from smem
kern :debug : [ 370.298136] i915 0000:00:02.0:
[drm:drm_mode_addfb2_ioctl] [FB:263]
kern :debug : [ 370.320677] [375]
thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 1:1:
link maximum bandwidth 36000/36000 Mb/s
kern :debug : [ 370.320810] [375] thunderbolt:tb_tunnel_usb3:952:
thunderbolt 0000:00:0d.2: 1:16: available bandwidth for new USB3
tunnel 36000/36000 Mb/s
kern :warn : [ 370.321640] thunderbolt 0000:00:0d.2: 1: USB3 tunnel
creation failed
kern :debug : [ 370.322322] [3599]
thunderbolt:tb_tunnel_activate:2367: thunderbolt 0000:00:0d.2: 0:8 <->
1:9 (PCI): activating
kern :debug : [ 370.322328] [3599] thunderbolt:tb_path_activate:512:
thunderbolt 0000:00:0d.2: activating PCIe Down path from 0:8 to 1:9
kern :debug : [ 370.322479] [3599] thunderbolt:tb_path_activate:573:
thunderbolt 0000:00:0d.2: 1:1: Writing hop 1
kern :debug : [ 370.322481] [3599] thunderbolt:tb_dump_hop:20:
thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 9 Out HopID: 8
kern :debug : [ 370.322483] [3599] thunderbolt:tb_dump_hop:22:
thunderbolt 0000:00:0d.2: 1:1: Weight: 1 Priority: 3 Credits: 32 Drop:
0 PM: 0
kern :debug : [ 370.322486] [3599] thunderbolt:tb_dump_hop:25:
thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
kern :debug : [ 370.322488] [3599] thunderbolt:tb_dump_hop:27:
thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer
(In/Eg): 0/0
kern :debug : [ 370.322490] [3599] thunderbolt:tb_dump_hop:30:
thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3:
0x0
kern :warn : [ 370.322984] thunderbolt 0000:00:0d.2: 1:1: hop
deactivation failed for hop 1, index 8
kern :warn : [ 370.322986] ------------[ cut here ]------------
kern :warn : [ 370.322987] thunderbolt 0000:00:0d.2: PCIe Down path
activation failed
kern :warn : [ 370.323072] WARNING: CPU: 4 PID: 3599 at
drivers/thunderbolt/path.c:587 tb_path_activate+0x129/0x530
[thunderbolt]
kern :warn : [ 370.323247] CPU: 4 UID: 0 PID: 3599 Comm:
pool-/usr/libex Not tainted 6.16.0-061600rc4drmtip20250702-generic
#202507020208 PREEMPT(voluntary)
kern :warn : [ 370.323250] Hardware name: Dell Inc. Dell Pro Max 16
Plus MB16250/, BIOS 1.0.0 05/23/2025
kern :warn : [ 370.323252] RIP: 0010:tb_path_activate+0x129/0x530 [thunderbolt]
kern :warn : [ 370.323279] Code: 4d 85 e4 0f 84 ee 00 00 00 48 81 c7
c8 00 00 00 e8 fc af d1 d3 4c 89 e9 4c 89 e2 48 c7 c7 78 3e 54 c0 48
89 c6 e8 57 e0 18 d3 <0f> 0b 48 8b 45 d0 65 48 2b 05 b1 4b d2 d5 0f 85
e0 03 00 00 48 8d
kern :warn : [ 370.323281] RSP: 0018:ffffce70a3c2f928 EFLAGS: 00010246
kern :warn : [ 370.323284] RAX: 0000000000000000 RBX: 00000000ffffff95
RCX: 0000000000000000
kern :warn : [ 370.323286] RDX: 0000000000000000 RSI: 0000000000000000
RDI: 0000000000000000
kern :warn : [ 370.323287] RBP: ffffce70a3c2f968 R08: 0000000000000000
R09: 0000000000000000
kern :warn : [ 370.323289] R10: 0000000000000000 R11: 0000000000000000
R12: ffff8bb8033b1380
kern :warn : [ 370.323290] R13: ffffffffc05472fc R14: 0000000000000001
R15: ffffce70a3c2f930
kern :warn : [ 370.323291] FS: 0000747c76bfe6c0(0000)
GS:ffff8bbfe0888000(0000) knlGS:0000000000000000
kern :warn : [ 370.323293] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kern :warn : [ 370.323295] CR2: 000000c000a35000 CR3: 0000000130f59003
CR4: 0000000000f72ef0
kern :warn : [ 370.323296] PKRU: 55555554
kern :warn : [ 370.323298] Call Trace:
kern :warn : [ 370.323299] <TASK>
kern :warn : [ 370.323302] tb_tunnel_activate+0xba/0x2d0 [thunderbolt]
kern :warn : [ 370.323329] ? tb_tunnel_alloc_pci+0xb2/0x110 [thunderbolt]
kern :warn : [ 370.323354] tb_tunnel_pci+0xde/0x170 [thunderbolt]
kern :warn : [ 370.323377] tb_domain_approve_switch+0x3b/0x70 [thunderbolt]
kern :warn : [ 370.323402] authorized_store+0x282/0x2c0 [thunderbolt]
kern :warn : [ 370.323423] dev_attr_store+0x14/0x40
kern :warn : [ 370.323429] sysfs_kf_write+0x6f/0x90
kern :warn : [ 370.323433] kernfs_fop_write_iter+0x151/0x200
kern :warn : [ 370.323437] vfs_write+0x26b/0x490
kern :warn : [ 370.323440] ksys_write+0x6f/0xf0
kern :warn : [ 370.323441] __x64_sys_write+0x19/0x30
kern :warn : [ 370.323443] x64_sys_call+0x29a/0x2320
kern :warn : [ 370.323447] do_syscall_64+0x80/0xe80
kern :warn : [ 370.323450] ? get_signal+0x6da/0x7e0
kern :warn : [ 370.323454] ? vfs_write+0x26b/0x490
kern :warn : [ 370.323456] ? arch_do_signal_or_restart+0x38/0x110
kern :warn : [ 370.323461] ? exit_to_user_mode_loop+0x91/0x170
kern :warn : [ 370.323465] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
kern :warn : [ 370.323468] ? do_syscall_64+0xb6/0xe80
kern :warn : [ 370.323470] ? sysfs_kf_write+0x6f/0x90
kern :warn : [ 370.323472] ? dequeue_signal+0x7e/0x190
kern :warn : [ 370.323474] ? get_signal+0x6da/0x7e0
kern :warn : [ 370.323476] ? vfs_write+0x26b/0x490
kern :warn : [ 370.323478] ? arch_do_signal_or_restart+0x38/0x110
kern :warn : [ 370.323481] ? exit_to_user_mode_loop+0x91/0x170
kern :warn : [ 370.323484] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
kern :warn : [ 370.323487] ? do_syscall_64+0xb6/0xe80
kern :warn : [ 370.323488] ? do_syscall_64+0xb6/0xe80
kern :warn : [ 370.323490] entry_SYSCALL_64_after_hwframe+0x76/0x7e
kern :warn : [ 370.323492] RIP: 0033:0x747c7a51c5ad
kern :warn : [ 370.323495] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75
f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8
b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8
0f c0 f7 ff 48 8b
kern :warn : [ 370.323497] RSP: 002b:0000747c76bfdb70 EFLAGS: 00000293
ORIG_RAX: 0000000000000001
kern :warn : [ 370.323499] RAX: ffffffffffffffda RBX: 00006508223c9860
RCX: 0000747c7a51c5ad
kern :warn : [ 370.323500] RDX: 0000000000000001 RSI: 0000747c76bfdc20
RDI: 000000000000000a
kern :warn : [ 370.323502] RBP: 0000747c76bfdb90 R08: 0000000000000000
R09: 0000747c76bfda80
kern :warn : [ 370.323503] R10: 0000000000000000 R11: 0000000000000293
R12: 0000747c76bfdc20
kern :warn : [ 370.323504] R13: 000000000000000a R14: 0000747c76bfdc18
R15: 0000747c6c00a830
kern :warn : [ 370.323506] </TASK>
kern :warn : [ 370.323507] ---[ end trace 0000000000000000 ]---
kern :warn : [ 370.323509] thunderbolt 0000:00:0d.2: 0:8 <-> 1:9
(PCI): activation failed
kern :debug : [ 370.323512] [3599]
thunderbolt:tb_tunnel_deactivate:2420: thunderbolt 0000:00:0d.2: 0:8
<-> 1:9 (PCI): deactivating
kern :info : [ 370.323831] thunderbolt 0000:00:0d.2: 1:9: PCIe tunnel
activation failed, aborting
kern :debug : [ 370.323843] [375] thunderbolt:tb_handle_hotplug:2496:
thunderbolt 0000:00:0d.2: 0:2: got plug event for connected port,
ignoring
kern :debug : [ 370.323850] [375] thunderbolt:tb_handle_hotplug:2443:
thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
0)
kern :debug : [ 370.323853] [375] thunderbolt:tb_handle_hotplug:2492:
thunderbolt 0000:00:0d.2: 0:2: got unplug event for disconnected port,
ignoring
kern :debug : [ 370.323856] [375] thunderbolt:tb_handle_hotplug:2443:
thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
1)
kern :info : [ 370.323859] thunderbolt 0-0:1.1: retimer disconnected
kern :debug : [ 370.323948] [375] thunderbolt:tb_handle_hotplug:2454:
thunderbolt 0000:00:0d.2: 0:1: switch unplugged
kern :info : [ 370.324578] thunderbolt 0-1: device disconnected
kern :debug : [ 370.324802] [375]
thunderbolt:tb_recalc_estimated_bandwidth:1512: thunderbolt
0000:00:0d.2: bandwidth consumption changed, re-calculating estimated
bandwidth
kern :debug : [ 370.324804] [375]
thunderbolt:tb_recalc_estimated_bandwidth:1521: thunderbolt
0000:00:0d.2: bandwidth re-calculation done
kern :debug : [ 370.324807] [375] thunderbolt:tb_tunnel_dp:2069:
thunderbolt 0000:00:0d.2: looking for DP IN <-> DP OUT pairs:
kern :debug : [ 370.324982] [375] thunderbolt:tb_tunnel_dp:2083:
thunderbolt 0000:00:0d.2: 0:5: DP IN available
kern :debug : [ 370.324985] [375] thunderbolt:tb_tunnel_dp:2089:
thunderbolt 0000:00:0d.2: 0:5: no suitable DP OUT adapter available,
not tunneling
kern :debug : [ 370.325145] [375] thunderbolt:tb_tunnel_dp:2083:
thunderbolt 0000:00:0d.2: 0:6: DP IN available
kern :debug : [ 370.325147] [375] thunderbolt:tb_tunnel_dp:2089:
thunderbolt 0000:00:0d.2: 0:6: no suitable DP OUT adapter available,
not tunneling
I'm not a thunderbolt expert, but it looks like the thunderbolt
controller on the host failed to establish USB3 tunneling with the
screen's internal USB 3 hub, followed by the PCIe link activation
failure.
For more information:
Linux version: vanilla 6.16.0-rc4-drm-tip (commit
4f74a027c8664ae79344bf711acfab9cd2f8edab)
Machine: Dell Pro Max 16 Plus MB16250, BIOS 1.2.0 06/19/2025
CPU model name: Intel(R) Core(TM) Ultra 7 265HX (Arrow Lake)
Lspci-vt:
-+-[0000:00]-+-00.0 Intel Corporation Device 7d2d
| +-01.0-[01]----00.0 Sandisk Corp Device 5049
| +-02.0 Intel Corporation Arrow Lake-U [Intel Graphics]
| +-04.0 Intel Corporation Device ad03
| +-06.0-[02]----00.0 Sandisk Corp Device 5049
|
+-06.1-[03-2f]----00.0-[04-2f]--+-00.0-[05]----00.0 Intel Corporation
Thunderbolt 80/120G NHI [Barlow Ridge Host 80G 2023]
| |
+-01.0-[06-19]----00.0-[07-19]--+-00.0-[08]----00.0 Intel Corporation
Thunderbolt 4 USB Controller [Goshen Ridge 2020]
| | |
+-01.0-[09-0e]----00.0-[0a-0b]----01.0-[0b]----00.0 Samsung
Electronics Co Ltd NVMe SSD Controller 980 (DRAM-less)
| | |
+-02.0-[0f-14]--
| | |
+-03.0-[15-18]--
| | |
\-04.0-[19]--
| |
+-02.0-[1a]----00.0 Intel Corporation Thunderbolt 80/120G USB
Controller [Barlow Ridge Host 80G 2023]
| |
\-03.0-[1b-2f]--
| +-06.3-[30]--+-00.0 NVIDIA Corporation Device 2f38
| | \-00.1 NVIDIA Corporation Device 2f80
| +-07.0-[31-45]--
| +-07.1-[46-5a]--
| +-08.0 Intel Corporation Device ae4c
| +-0a.0 Intel Corporation Device ad0d
| +-0b.0 Intel Corporation Arrow Lake NPU
| +-0d.0 Intel Corporation Meteor Lake-P
Thunderbolt 4 USB Controller
| +-0d.2 Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0
| +-14.0 Intel Corporation Device ae7f
| +-1f.0 Intel Corporation Device ae10
| \-1f.5 Intel Corporation Device ae23
\-[0000:80]-+-12.0 Intel Corporation Device 7f78
+-14.0 Intel Corporation Device 7f6e
+-14.5 Intel Corporation Device 7f2f
+-15.0 Intel Corporation Device 7f4c
+-15.1 Intel Corporation Device 7f4d
+-15.3 Intel Corporation Device 7f4f
+-16.0 Intel Corporation Device 7f68
+-16.3 Intel Corporation Device 7f6b
+-19.0 Intel Corporation Device 7f7a
+-19.1 Intel Corporation Device 7f7b
+-1c.0-[81]----00.0 Intel Corporation Wi-Fi
7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2
+-1c.4-[82-83]----00.0 Realtek Semiconductor Co.,
Ltd. Device 5264
+-1d.0-[84]----00.0 Intel Corporation Ethernet
Controller I226-LM
+-1f.0 Intel Corporation Device 7f12
+-1f.3 Intel Corporation Device 7f50
+-1f.4 Intel Corporation Device 7f23
\-1f.5 Intel Corporation Device 7f24
Thank you for your time.
Best regards,
En-Wei.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-07-11 3:54 Thunderbolt call trace occurs on hot-plug En-Wei WU
@ 2025-07-28 6:33 ` Mika Westerberg
2025-07-30 7:24 ` En-Wei WU
2025-08-08 6:43 ` Mika Westerberg
0 siblings, 2 replies; 7+ messages in thread
From: Mika Westerberg @ 2025-07-28 6:33 UTC (permalink / raw)
To: En-Wei WU; +Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb
Hi,
On Fri, Jul 11, 2025 at 11:54:46AM +0800, En-Wei WU wrote:
> Hi,
>
> I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
> Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
> by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
> the following call trace. The issue reproduces approximately 60% of
> the time.
Could you share the whole dmesg (that is not line wrapped)? With
"thunderbolt.dyndbg=+p" in the kernel command line.
And can you confirm I understand the steps?
1. Boot the system up, nothing connected.
2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
3. Verify that the monitor works (+ run lspci/lsusb)
Expected output: The monitor and the integrated peripherals (PCIe, USB)
work fine.
Actual output: There is error in the log and PCIe peripherals on the
monitor do not show up in lspci output.
> kern :info : [ 370.181263] usb 5-11: New USB device found,
> idVendor=1d5c, idProduct=5801, bcdDevice= 1.01
> kern :info : [ 370.181265] usb 5-11: New USB device strings: Mfr=1,
> Product=2, SerialNumber=0
> kern :info : [ 370.181266] usb 5-11: Product: USB2.0 Hub
> kern :info : [ 370.181267] usb 5-11: Manufacturer: Fresco Logic, Inc.
> kern :info : [ 370.182473] hub 5-11:1.0: USB hub found
> kern :debug : [ 370.182958] i915 0000:00:02.0:
> [drm:intel_power_well_disable [i915]] disabling PW_2
> kern :info : [ 370.183853] hub 5-11:1.0: 6 ports detected
> kern :debug : [ 370.212505] [375]
> thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 0:1:
> link maximum bandwidth 36000/36000 Mb/s
> kern :info : [ 370.215094] usb 5-11: USB disconnect, device number 29
> kern :debug : [ 370.218522] [165] thunderbolt:tb_cfg_ack_plug:842:
> thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
> kern :debug : [ 370.297820] i915 0000:00:02.0: [drm:intel_dpt_create
> [i915]] Allocating dpt from smem
> kern :debug : [ 370.298136] i915 0000:00:02.0:
> [drm:drm_mode_addfb2_ioctl] [FB:263]
> kern :debug : [ 370.320677] [375]
> thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 1:1:
> link maximum bandwidth 36000/36000 Mb/s
> kern :debug : [ 370.320810] [375] thunderbolt:tb_tunnel_usb3:952:
> thunderbolt 0000:00:0d.2: 1:16: available bandwidth for new USB3
> tunnel 36000/36000 Mb/s
> kern :warn : [ 370.321640] thunderbolt 0000:00:0d.2: 1: USB3 tunnel
> creation failed
> kern :debug : [ 370.322322] [3599]
> thunderbolt:tb_tunnel_activate:2367: thunderbolt 0000:00:0d.2: 0:8 <->
> 1:9 (PCI): activating
> kern :debug : [ 370.322328] [3599] thunderbolt:tb_path_activate:512:
> thunderbolt 0000:00:0d.2: activating PCIe Down path from 0:8 to 1:9
> kern :debug : [ 370.322479] [3599] thunderbolt:tb_path_activate:573:
> thunderbolt 0000:00:0d.2: 1:1: Writing hop 1
> kern :debug : [ 370.322481] [3599] thunderbolt:tb_dump_hop:20:
> thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 9 Out HopID: 8
> kern :debug : [ 370.322483] [3599] thunderbolt:tb_dump_hop:22:
> thunderbolt 0000:00:0d.2: 1:1: Weight: 1 Priority: 3 Credits: 32 Drop:
> 0 PM: 0
> kern :debug : [ 370.322486] [3599] thunderbolt:tb_dump_hop:25:
> thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
> kern :debug : [ 370.322488] [3599] thunderbolt:tb_dump_hop:27:
> thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer
> (In/Eg): 0/0
> kern :debug : [ 370.322490] [3599] thunderbolt:tb_dump_hop:30:
> thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3:
> 0x0
> kern :warn : [ 370.322984] thunderbolt 0000:00:0d.2: 1:1: hop
> deactivation failed for hop 1, index 8
> kern :warn : [ 370.322986] ------------[ cut here ]------------
> kern :warn : [ 370.322987] thunderbolt 0000:00:0d.2: PCIe Down path
> activation failed
> kern :warn : [ 370.323072] WARNING: CPU: 4 PID: 3599 at
> drivers/thunderbolt/path.c:587 tb_path_activate+0x129/0x530
> [thunderbolt]
> kern :warn : [ 370.323247] CPU: 4 UID: 0 PID: 3599 Comm:
> pool-/usr/libex Not tainted 6.16.0-061600rc4drmtip20250702-generic
> #202507020208 PREEMPT(voluntary)
> kern :warn : [ 370.323250] Hardware name: Dell Inc. Dell Pro Max 16
> Plus MB16250/, BIOS 1.0.0 05/23/2025
> kern :warn : [ 370.323252] RIP: 0010:tb_path_activate+0x129/0x530 [thunderbolt]
> kern :warn : [ 370.323279] Code: 4d 85 e4 0f 84 ee 00 00 00 48 81 c7
> c8 00 00 00 e8 fc af d1 d3 4c 89 e9 4c 89 e2 48 c7 c7 78 3e 54 c0 48
> 89 c6 e8 57 e0 18 d3 <0f> 0b 48 8b 45 d0 65 48 2b 05 b1 4b d2 d5 0f 85
> e0 03 00 00 48 8d
> kern :warn : [ 370.323281] RSP: 0018:ffffce70a3c2f928 EFLAGS: 00010246
> kern :warn : [ 370.323284] RAX: 0000000000000000 RBX: 00000000ffffff95
> RCX: 0000000000000000
> kern :warn : [ 370.323286] RDX: 0000000000000000 RSI: 0000000000000000
> RDI: 0000000000000000
> kern :warn : [ 370.323287] RBP: ffffce70a3c2f968 R08: 0000000000000000
> R09: 0000000000000000
> kern :warn : [ 370.323289] R10: 0000000000000000 R11: 0000000000000000
> R12: ffff8bb8033b1380
> kern :warn : [ 370.323290] R13: ffffffffc05472fc R14: 0000000000000001
> R15: ffffce70a3c2f930
> kern :warn : [ 370.323291] FS: 0000747c76bfe6c0(0000)
> GS:ffff8bbfe0888000(0000) knlGS:0000000000000000
> kern :warn : [ 370.323293] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> kern :warn : [ 370.323295] CR2: 000000c000a35000 CR3: 0000000130f59003
> CR4: 0000000000f72ef0
> kern :warn : [ 370.323296] PKRU: 55555554
> kern :warn : [ 370.323298] Call Trace:
> kern :warn : [ 370.323299] <TASK>
> kern :warn : [ 370.323302] tb_tunnel_activate+0xba/0x2d0 [thunderbolt]
> kern :warn : [ 370.323329] ? tb_tunnel_alloc_pci+0xb2/0x110 [thunderbolt]
> kern :warn : [ 370.323354] tb_tunnel_pci+0xde/0x170 [thunderbolt]
> kern :warn : [ 370.323377] tb_domain_approve_switch+0x3b/0x70 [thunderbolt]
> kern :warn : [ 370.323402] authorized_store+0x282/0x2c0 [thunderbolt]
> kern :warn : [ 370.323423] dev_attr_store+0x14/0x40
> kern :warn : [ 370.323429] sysfs_kf_write+0x6f/0x90
> kern :warn : [ 370.323433] kernfs_fop_write_iter+0x151/0x200
> kern :warn : [ 370.323437] vfs_write+0x26b/0x490
> kern :warn : [ 370.323440] ksys_write+0x6f/0xf0
> kern :warn : [ 370.323441] __x64_sys_write+0x19/0x30
> kern :warn : [ 370.323443] x64_sys_call+0x29a/0x2320
> kern :warn : [ 370.323447] do_syscall_64+0x80/0xe80
> kern :warn : [ 370.323450] ? get_signal+0x6da/0x7e0
> kern :warn : [ 370.323454] ? vfs_write+0x26b/0x490
> kern :warn : [ 370.323456] ? arch_do_signal_or_restart+0x38/0x110
> kern :warn : [ 370.323461] ? exit_to_user_mode_loop+0x91/0x170
> kern :warn : [ 370.323465] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
> kern :warn : [ 370.323468] ? do_syscall_64+0xb6/0xe80
> kern :warn : [ 370.323470] ? sysfs_kf_write+0x6f/0x90
> kern :warn : [ 370.323472] ? dequeue_signal+0x7e/0x190
> kern :warn : [ 370.323474] ? get_signal+0x6da/0x7e0
> kern :warn : [ 370.323476] ? vfs_write+0x26b/0x490
> kern :warn : [ 370.323478] ? arch_do_signal_or_restart+0x38/0x110
> kern :warn : [ 370.323481] ? exit_to_user_mode_loop+0x91/0x170
> kern :warn : [ 370.323484] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
> kern :warn : [ 370.323487] ? do_syscall_64+0xb6/0xe80
> kern :warn : [ 370.323488] ? do_syscall_64+0xb6/0xe80
> kern :warn : [ 370.323490] entry_SYSCALL_64_after_hwframe+0x76/0x7e
> kern :warn : [ 370.323492] RIP: 0033:0x747c7a51c5ad
> kern :warn : [ 370.323495] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75
> f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8
> b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8
> 0f c0 f7 ff 48 8b
> kern :warn : [ 370.323497] RSP: 002b:0000747c76bfdb70 EFLAGS: 00000293
> ORIG_RAX: 0000000000000001
> kern :warn : [ 370.323499] RAX: ffffffffffffffda RBX: 00006508223c9860
> RCX: 0000747c7a51c5ad
> kern :warn : [ 370.323500] RDX: 0000000000000001 RSI: 0000747c76bfdc20
> RDI: 000000000000000a
> kern :warn : [ 370.323502] RBP: 0000747c76bfdb90 R08: 0000000000000000
> R09: 0000747c76bfda80
> kern :warn : [ 370.323503] R10: 0000000000000000 R11: 0000000000000293
> R12: 0000747c76bfdc20
> kern :warn : [ 370.323504] R13: 000000000000000a R14: 0000747c76bfdc18
> R15: 0000747c6c00a830
> kern :warn : [ 370.323506] </TASK>
> kern :warn : [ 370.323507] ---[ end trace 0000000000000000 ]---
> kern :warn : [ 370.323509] thunderbolt 0000:00:0d.2: 0:8 <-> 1:9
> (PCI): activation failed
> kern :debug : [ 370.323512] [3599]
> thunderbolt:tb_tunnel_deactivate:2420: thunderbolt 0000:00:0d.2: 0:8
> <-> 1:9 (PCI): deactivating
> kern :info : [ 370.323831] thunderbolt 0000:00:0d.2: 1:9: PCIe tunnel
> activation failed, aborting
> kern :debug : [ 370.323843] [375] thunderbolt:tb_handle_hotplug:2496:
> thunderbolt 0000:00:0d.2: 0:2: got plug event for connected port,
> ignoring
> kern :debug : [ 370.323850] [375] thunderbolt:tb_handle_hotplug:2443:
> thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
> 0)
> kern :debug : [ 370.323853] [375] thunderbolt:tb_handle_hotplug:2492:
> thunderbolt 0000:00:0d.2: 0:2: got unplug event for disconnected port,
> ignoring
> kern :debug : [ 370.323856] [375] thunderbolt:tb_handle_hotplug:2443:
> thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
> 1)
> kern :info : [ 370.323859] thunderbolt 0-0:1.1: retimer disconnected
> kern :debug : [ 370.323948] [375] thunderbolt:tb_handle_hotplug:2454:
> thunderbolt 0000:00:0d.2: 0:1: switch unplugged
> kern :info : [ 370.324578] thunderbolt 0-1: device disconnected
> kern :debug : [ 370.324802] [375]
> thunderbolt:tb_recalc_estimated_bandwidth:1512: thunderbolt
> 0000:00:0d.2: bandwidth consumption changed, re-calculating estimated
> bandwidth
> kern :debug : [ 370.324804] [375]
> thunderbolt:tb_recalc_estimated_bandwidth:1521: thunderbolt
> 0000:00:0d.2: bandwidth re-calculation done
> kern :debug : [ 370.324807] [375] thunderbolt:tb_tunnel_dp:2069:
> thunderbolt 0000:00:0d.2: looking for DP IN <-> DP OUT pairs:
> kern :debug : [ 370.324982] [375] thunderbolt:tb_tunnel_dp:2083:
> thunderbolt 0000:00:0d.2: 0:5: DP IN available
> kern :debug : [ 370.324985] [375] thunderbolt:tb_tunnel_dp:2089:
> thunderbolt 0000:00:0d.2: 0:5: no suitable DP OUT adapter available,
> not tunneling
> kern :debug : [ 370.325145] [375] thunderbolt:tb_tunnel_dp:2083:
> thunderbolt 0000:00:0d.2: 0:6: DP IN available
> kern :debug : [ 370.325147] [375] thunderbolt:tb_tunnel_dp:2089:
> thunderbolt 0000:00:0d.2: 0:6: no suitable DP OUT adapter available,
> not tunneling
>
> I'm not a thunderbolt expert, but it looks like the thunderbolt
> controller on the host failed to establish USB3 tunneling with the
> screen's internal USB 3 hub, followed by the PCIe link activation
> failure.
>
> For more information:
> Linux version: vanilla 6.16.0-rc4-drm-tip (commit
> 4f74a027c8664ae79344bf711acfab9cd2f8edab)
>
> Machine: Dell Pro Max 16 Plus MB16250, BIOS 1.2.0 06/19/2025
>
> CPU model name: Intel(R) Core(TM) Ultra 7 265HX (Arrow Lake)
>
> Lspci-vt:
> -+-[0000:00]-+-00.0 Intel Corporation Device 7d2d
> | +-01.0-[01]----00.0 Sandisk Corp Device 5049
> | +-02.0 Intel Corporation Arrow Lake-U [Intel Graphics]
> | +-04.0 Intel Corporation Device ad03
> | +-06.0-[02]----00.0 Sandisk Corp Device 5049
> |
> +-06.1-[03-2f]----00.0-[04-2f]--+-00.0-[05]----00.0 Intel Corporation
> Thunderbolt 80/120G NHI [Barlow Ridge Host 80G 2023]
> | |
> +-01.0-[06-19]----00.0-[07-19]--+-00.0-[08]----00.0 Intel Corporation
> Thunderbolt 4 USB Controller [Goshen Ridge 2020]
> | | |
>
> +-01.0-[09-0e]----00.0-[0a-0b]----01.0-[0b]----00.0 Samsung
> Electronics Co Ltd NVMe SSD Controller 980 (DRAM-less)
> | | |
> +-02.0-[0f-14]--
> | | |
> +-03.0-[15-18]--
> | | |
> \-04.0-[19]--
> | |
> +-02.0-[1a]----00.0 Intel Corporation Thunderbolt 80/120G USB
> Controller [Barlow Ridge Host 80G 2023]
> | |
> \-03.0-[1b-2f]--
> | +-06.3-[30]--+-00.0 NVIDIA Corporation Device 2f38
> | | \-00.1 NVIDIA Corporation Device 2f80
> | +-07.0-[31-45]--
> | +-07.1-[46-5a]--
> | +-08.0 Intel Corporation Device ae4c
> | +-0a.0 Intel Corporation Device ad0d
> | +-0b.0 Intel Corporation Arrow Lake NPU
> | +-0d.0 Intel Corporation Meteor Lake-P
> Thunderbolt 4 USB Controller
> | +-0d.2 Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0
> | +-14.0 Intel Corporation Device ae7f
> | +-1f.0 Intel Corporation Device ae10
> | \-1f.5 Intel Corporation Device ae23
> \-[0000:80]-+-12.0 Intel Corporation Device 7f78
> +-14.0 Intel Corporation Device 7f6e
> +-14.5 Intel Corporation Device 7f2f
> +-15.0 Intel Corporation Device 7f4c
> +-15.1 Intel Corporation Device 7f4d
> +-15.3 Intel Corporation Device 7f4f
> +-16.0 Intel Corporation Device 7f68
> +-16.3 Intel Corporation Device 7f6b
> +-19.0 Intel Corporation Device 7f7a
> +-19.1 Intel Corporation Device 7f7b
> +-1c.0-[81]----00.0 Intel Corporation Wi-Fi
> 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2
> +-1c.4-[82-83]----00.0 Realtek Semiconductor Co.,
> Ltd. Device 5264
> +-1d.0-[84]----00.0 Intel Corporation Ethernet
> Controller I226-LM
> +-1f.0 Intel Corporation Device 7f12
> +-1f.3 Intel Corporation Device 7f50
> +-1f.4 Intel Corporation Device 7f23
> \-1f.5 Intel Corporation Device 7f24
>
> Thank you for your time.
>
> Best regards,
> En-Wei.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-07-28 6:33 ` Mika Westerberg
@ 2025-07-30 7:24 ` En-Wei WU
2025-08-08 6:43 ` Mika Westerberg
1 sibling, 0 replies; 7+ messages in thread
From: En-Wei WU @ 2025-07-30 7:24 UTC (permalink / raw)
To: Mika Westerberg
Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb
> And can you confirm I understand the steps?
>
> 1. Boot the system up, nothing connected.
> 2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
> 3. Verify that the monitor works (+ run lspci/lsusb)
> Expected output: The monitor and the integrated peripherals (PCIe, USB)
> work fine.
>
> Actual output: There is error in the log and PCIe peripherals on the
> monitor do not show up in lspci output.
Yes, the laptop wasn't connected to anything at boot. Once booted up,
we connected Thunderbolt cable to Dell U2725QE monitor.
After hot-plugging the Thunderbolt cable, a call trace might happen
with the possibility of 60%. However, the monitor works in either
case.
> Could you share the whole dmesg (that is not line wrapped)? With
> "thunderbolt.dyndbg=+p" in the kernel command line.
Please disregard the logs I sent before and find the newly captured
logs here: https://gist.github.com/rickywu0421/316bede16ea7a91f6f67691845c47d57
One should see five logs there:
1. dmesg-hot-plug-thunderbolt.log : the whole dmesg from boot. There
are two pairs of hot-plug and unplug involved (one without call trace
and the other with):
1.1. The first hot-plug, started from [ 84.817039] ======= Hotplug
Thunderbolt Cable =======
1.2. No call trace, until the first unplug [ 103.601869] =======
Unplug Thunderbolt Cable =======
1.3. The second hot-plug, started from [ 113.907760] ======= Hotplug
Thunderbolt Cable =======
1.4. There are two call traces, until the second unplug [ 132.421579]
======= Unplug Thunderbolt Cable =======
2. lspci-after-plugging.log (captured after a call trace happened)
3. lspci-before-plugging.log
4. lsusb-after-plugging.log (captured after a call trace happened)
5. lsusb-before-plugging.log
Best,
En-Wei.
On Mon, 28 Jul 2025 at 14:33, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
>
> Hi,
>
> On Fri, Jul 11, 2025 at 11:54:46AM +0800, En-Wei WU wrote:
> > Hi,
> >
> > I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
> > Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
> > by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
> > the following call trace. The issue reproduces approximately 60% of
> > the time.
>
> Could you share the whole dmesg (that is not line wrapped)? With
> "thunderbolt.dyndbg=+p" in the kernel command line.
>
> And can you confirm I understand the steps?
>
> 1. Boot the system up, nothing connected.
> 2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
> 3. Verify that the monitor works (+ run lspci/lsusb)
>
> Expected output: The monitor and the integrated peripherals (PCIe, USB)
> work fine.
>
> Actual output: There is error in the log and PCIe peripherals on the
> monitor do not show up in lspci output.
>
> > kern :info : [ 370.181263] usb 5-11: New USB device found,
> > idVendor=1d5c, idProduct=5801, bcdDevice= 1.01
> > kern :info : [ 370.181265] usb 5-11: New USB device strings: Mfr=1,
> > Product=2, SerialNumber=0
> > kern :info : [ 370.181266] usb 5-11: Product: USB2.0 Hub
> > kern :info : [ 370.181267] usb 5-11: Manufacturer: Fresco Logic, Inc.
> > kern :info : [ 370.182473] hub 5-11:1.0: USB hub found
> > kern :debug : [ 370.182958] i915 0000:00:02.0:
> > [drm:intel_power_well_disable [i915]] disabling PW_2
> > kern :info : [ 370.183853] hub 5-11:1.0: 6 ports detected
> > kern :debug : [ 370.212505] [375]
> > thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 0:1:
> > link maximum bandwidth 36000/36000 Mb/s
> > kern :info : [ 370.215094] usb 5-11: USB disconnect, device number 29
> > kern :debug : [ 370.218522] [165] thunderbolt:tb_cfg_ack_plug:842:
> > thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
> > kern :debug : [ 370.297820] i915 0000:00:02.0: [drm:intel_dpt_create
> > [i915]] Allocating dpt from smem
> > kern :debug : [ 370.298136] i915 0000:00:02.0:
> > [drm:drm_mode_addfb2_ioctl] [FB:263]
> > kern :debug : [ 370.320677] [375]
> > thunderbolt:tb_maximum_bandwidth:788: thunderbolt 0000:00:0d.2: 1:1:
> > link maximum bandwidth 36000/36000 Mb/s
> > kern :debug : [ 370.320810] [375] thunderbolt:tb_tunnel_usb3:952:
> > thunderbolt 0000:00:0d.2: 1:16: available bandwidth for new USB3
> > tunnel 36000/36000 Mb/s
> > kern :warn : [ 370.321640] thunderbolt 0000:00:0d.2: 1: USB3 tunnel
> > creation failed
> > kern :debug : [ 370.322322] [3599]
> > thunderbolt:tb_tunnel_activate:2367: thunderbolt 0000:00:0d.2: 0:8 <->
> > 1:9 (PCI): activating
> > kern :debug : [ 370.322328] [3599] thunderbolt:tb_path_activate:512:
> > thunderbolt 0000:00:0d.2: activating PCIe Down path from 0:8 to 1:9
> > kern :debug : [ 370.322479] [3599] thunderbolt:tb_path_activate:573:
> > thunderbolt 0000:00:0d.2: 1:1: Writing hop 1
> > kern :debug : [ 370.322481] [3599] thunderbolt:tb_dump_hop:20:
> > thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 9 Out HopID: 8
> > kern :debug : [ 370.322483] [3599] thunderbolt:tb_dump_hop:22:
> > thunderbolt 0000:00:0d.2: 1:1: Weight: 1 Priority: 3 Credits: 32 Drop:
> > 0 PM: 0
> > kern :debug : [ 370.322486] [3599] thunderbolt:tb_dump_hop:25:
> > thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
> > kern :debug : [ 370.322488] [3599] thunderbolt:tb_dump_hop:27:
> > thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer
> > (In/Eg): 0/0
> > kern :debug : [ 370.322490] [3599] thunderbolt:tb_dump_hop:30:
> > thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3:
> > 0x0
> > kern :warn : [ 370.322984] thunderbolt 0000:00:0d.2: 1:1: hop
> > deactivation failed for hop 1, index 8
> > kern :warn : [ 370.322986] ------------[ cut here ]------------
> > kern :warn : [ 370.322987] thunderbolt 0000:00:0d.2: PCIe Down path
> > activation failed
> > kern :warn : [ 370.323072] WARNING: CPU: 4 PID: 3599 at
> > drivers/thunderbolt/path.c:587 tb_path_activate+0x129/0x530
> > [thunderbolt]
> > kern :warn : [ 370.323247] CPU: 4 UID: 0 PID: 3599 Comm:
> > pool-/usr/libex Not tainted 6.16.0-061600rc4drmtip20250702-generic
> > #202507020208 PREEMPT(voluntary)
> > kern :warn : [ 370.323250] Hardware name: Dell Inc. Dell Pro Max 16
> > Plus MB16250/, BIOS 1.0.0 05/23/2025
> > kern :warn : [ 370.323252] RIP: 0010:tb_path_activate+0x129/0x530 [thunderbolt]
> > kern :warn : [ 370.323279] Code: 4d 85 e4 0f 84 ee 00 00 00 48 81 c7
> > c8 00 00 00 e8 fc af d1 d3 4c 89 e9 4c 89 e2 48 c7 c7 78 3e 54 c0 48
> > 89 c6 e8 57 e0 18 d3 <0f> 0b 48 8b 45 d0 65 48 2b 05 b1 4b d2 d5 0f 85
> > e0 03 00 00 48 8d
> > kern :warn : [ 370.323281] RSP: 0018:ffffce70a3c2f928 EFLAGS: 00010246
> > kern :warn : [ 370.323284] RAX: 0000000000000000 RBX: 00000000ffffff95
> > RCX: 0000000000000000
> > kern :warn : [ 370.323286] RDX: 0000000000000000 RSI: 0000000000000000
> > RDI: 0000000000000000
> > kern :warn : [ 370.323287] RBP: ffffce70a3c2f968 R08: 0000000000000000
> > R09: 0000000000000000
> > kern :warn : [ 370.323289] R10: 0000000000000000 R11: 0000000000000000
> > R12: ffff8bb8033b1380
> > kern :warn : [ 370.323290] R13: ffffffffc05472fc R14: 0000000000000001
> > R15: ffffce70a3c2f930
> > kern :warn : [ 370.323291] FS: 0000747c76bfe6c0(0000)
> > GS:ffff8bbfe0888000(0000) knlGS:0000000000000000
> > kern :warn : [ 370.323293] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > kern :warn : [ 370.323295] CR2: 000000c000a35000 CR3: 0000000130f59003
> > CR4: 0000000000f72ef0
> > kern :warn : [ 370.323296] PKRU: 55555554
> > kern :warn : [ 370.323298] Call Trace:
> > kern :warn : [ 370.323299] <TASK>
> > kern :warn : [ 370.323302] tb_tunnel_activate+0xba/0x2d0 [thunderbolt]
> > kern :warn : [ 370.323329] ? tb_tunnel_alloc_pci+0xb2/0x110 [thunderbolt]
> > kern :warn : [ 370.323354] tb_tunnel_pci+0xde/0x170 [thunderbolt]
> > kern :warn : [ 370.323377] tb_domain_approve_switch+0x3b/0x70 [thunderbolt]
> > kern :warn : [ 370.323402] authorized_store+0x282/0x2c0 [thunderbolt]
> > kern :warn : [ 370.323423] dev_attr_store+0x14/0x40
> > kern :warn : [ 370.323429] sysfs_kf_write+0x6f/0x90
> > kern :warn : [ 370.323433] kernfs_fop_write_iter+0x151/0x200
> > kern :warn : [ 370.323437] vfs_write+0x26b/0x490
> > kern :warn : [ 370.323440] ksys_write+0x6f/0xf0
> > kern :warn : [ 370.323441] __x64_sys_write+0x19/0x30
> > kern :warn : [ 370.323443] x64_sys_call+0x29a/0x2320
> > kern :warn : [ 370.323447] do_syscall_64+0x80/0xe80
> > kern :warn : [ 370.323450] ? get_signal+0x6da/0x7e0
> > kern :warn : [ 370.323454] ? vfs_write+0x26b/0x490
> > kern :warn : [ 370.323456] ? arch_do_signal_or_restart+0x38/0x110
> > kern :warn : [ 370.323461] ? exit_to_user_mode_loop+0x91/0x170
> > kern :warn : [ 370.323465] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
> > kern :warn : [ 370.323468] ? do_syscall_64+0xb6/0xe80
> > kern :warn : [ 370.323470] ? sysfs_kf_write+0x6f/0x90
> > kern :warn : [ 370.323472] ? dequeue_signal+0x7e/0x190
> > kern :warn : [ 370.323474] ? get_signal+0x6da/0x7e0
> > kern :warn : [ 370.323476] ? vfs_write+0x26b/0x490
> > kern :warn : [ 370.323478] ? arch_do_signal_or_restart+0x38/0x110
> > kern :warn : [ 370.323481] ? exit_to_user_mode_loop+0x91/0x170
> > kern :warn : [ 370.323484] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xc0
> > kern :warn : [ 370.323487] ? do_syscall_64+0xb6/0xe80
> > kern :warn : [ 370.323488] ? do_syscall_64+0xb6/0xe80
> > kern :warn : [ 370.323490] entry_SYSCALL_64_after_hwframe+0x76/0x7e
> > kern :warn : [ 370.323492] RIP: 0033:0x747c7a51c5ad
> > kern :warn : [ 370.323495] Code: e5 48 83 ec 20 48 89 55 e8 48 89 75
> > f0 89 7d f8 e8 b8 bf f7 ff 48 8b 55 e8 48 8b 75 f0 41 89 c0 8b 7d f8
> > b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8
> > 0f c0 f7 ff 48 8b
> > kern :warn : [ 370.323497] RSP: 002b:0000747c76bfdb70 EFLAGS: 00000293
> > ORIG_RAX: 0000000000000001
> > kern :warn : [ 370.323499] RAX: ffffffffffffffda RBX: 00006508223c9860
> > RCX: 0000747c7a51c5ad
> > kern :warn : [ 370.323500] RDX: 0000000000000001 RSI: 0000747c76bfdc20
> > RDI: 000000000000000a
> > kern :warn : [ 370.323502] RBP: 0000747c76bfdb90 R08: 0000000000000000
> > R09: 0000747c76bfda80
> > kern :warn : [ 370.323503] R10: 0000000000000000 R11: 0000000000000293
> > R12: 0000747c76bfdc20
> > kern :warn : [ 370.323504] R13: 000000000000000a R14: 0000747c76bfdc18
> > R15: 0000747c6c00a830
> > kern :warn : [ 370.323506] </TASK>
> > kern :warn : [ 370.323507] ---[ end trace 0000000000000000 ]---
> > kern :warn : [ 370.323509] thunderbolt 0000:00:0d.2: 0:8 <-> 1:9
> > (PCI): activation failed
> > kern :debug : [ 370.323512] [3599]
> > thunderbolt:tb_tunnel_deactivate:2420: thunderbolt 0000:00:0d.2: 0:8
> > <-> 1:9 (PCI): deactivating
> > kern :info : [ 370.323831] thunderbolt 0000:00:0d.2: 1:9: PCIe tunnel
> > activation failed, aborting
> > kern :debug : [ 370.323843] [375] thunderbolt:tb_handle_hotplug:2496:
> > thunderbolt 0000:00:0d.2: 0:2: got plug event for connected port,
> > ignoring
> > kern :debug : [ 370.323850] [375] thunderbolt:tb_handle_hotplug:2443:
> > thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
> > 0)
> > kern :debug : [ 370.323853] [375] thunderbolt:tb_handle_hotplug:2492:
> > thunderbolt 0000:00:0d.2: 0:2: got unplug event for disconnected port,
> > ignoring
> > kern :debug : [ 370.323856] [375] thunderbolt:tb_handle_hotplug:2443:
> > thunderbolt 0000:00:0d.2: hotplug event for upstream port 1:2 (unplug:
> > 1)
> > kern :info : [ 370.323859] thunderbolt 0-0:1.1: retimer disconnected
> > kern :debug : [ 370.323948] [375] thunderbolt:tb_handle_hotplug:2454:
> > thunderbolt 0000:00:0d.2: 0:1: switch unplugged
> > kern :info : [ 370.324578] thunderbolt 0-1: device disconnected
> > kern :debug : [ 370.324802] [375]
> > thunderbolt:tb_recalc_estimated_bandwidth:1512: thunderbolt
> > 0000:00:0d.2: bandwidth consumption changed, re-calculating estimated
> > bandwidth
> > kern :debug : [ 370.324804] [375]
> > thunderbolt:tb_recalc_estimated_bandwidth:1521: thunderbolt
> > 0000:00:0d.2: bandwidth re-calculation done
> > kern :debug : [ 370.324807] [375] thunderbolt:tb_tunnel_dp:2069:
> > thunderbolt 0000:00:0d.2: looking for DP IN <-> DP OUT pairs:
> > kern :debug : [ 370.324982] [375] thunderbolt:tb_tunnel_dp:2083:
> > thunderbolt 0000:00:0d.2: 0:5: DP IN available
> > kern :debug : [ 370.324985] [375] thunderbolt:tb_tunnel_dp:2089:
> > thunderbolt 0000:00:0d.2: 0:5: no suitable DP OUT adapter available,
> > not tunneling
> > kern :debug : [ 370.325145] [375] thunderbolt:tb_tunnel_dp:2083:
> > thunderbolt 0000:00:0d.2: 0:6: DP IN available
> > kern :debug : [ 370.325147] [375] thunderbolt:tb_tunnel_dp:2089:
> > thunderbolt 0000:00:0d.2: 0:6: no suitable DP OUT adapter available,
> > not tunneling
> >
> > I'm not a thunderbolt expert, but it looks like the thunderbolt
> > controller on the host failed to establish USB3 tunneling with the
> > screen's internal USB 3 hub, followed by the PCIe link activation
> > failure.
> >
> > For more information:
> > Linux version: vanilla 6.16.0-rc4-drm-tip (commit
> > 4f74a027c8664ae79344bf711acfab9cd2f8edab)
> >
> > Machine: Dell Pro Max 16 Plus MB16250, BIOS 1.2.0 06/19/2025
> >
> > CPU model name: Intel(R) Core(TM) Ultra 7 265HX (Arrow Lake)
> >
> > Lspci-vt:
> > -+-[0000:00]-+-00.0 Intel Corporation Device 7d2d
> > | +-01.0-[01]----00.0 Sandisk Corp Device 5049
> > | +-02.0 Intel Corporation Arrow Lake-U [Intel Graphics]
> > | +-04.0 Intel Corporation Device ad03
> > | +-06.0-[02]----00.0 Sandisk Corp Device 5049
> > |
> > +-06.1-[03-2f]----00.0-[04-2f]--+-00.0-[05]----00.0 Intel Corporation
> > Thunderbolt 80/120G NHI [Barlow Ridge Host 80G 2023]
> > | |
> > +-01.0-[06-19]----00.0-[07-19]--+-00.0-[08]----00.0 Intel Corporation
> > Thunderbolt 4 USB Controller [Goshen Ridge 2020]
> > | | |
> >
> > +-01.0-[09-0e]----00.0-[0a-0b]----01.0-[0b]----00.0 Samsung
> > Electronics Co Ltd NVMe SSD Controller 980 (DRAM-less)
> > | | |
> > +-02.0-[0f-14]--
> > | | |
> > +-03.0-[15-18]--
> > | | |
> > \-04.0-[19]--
> > | |
> > +-02.0-[1a]----00.0 Intel Corporation Thunderbolt 80/120G USB
> > Controller [Barlow Ridge Host 80G 2023]
> > | |
> > \-03.0-[1b-2f]--
> > | +-06.3-[30]--+-00.0 NVIDIA Corporation Device 2f38
> > | | \-00.1 NVIDIA Corporation Device 2f80
> > | +-07.0-[31-45]--
> > | +-07.1-[46-5a]--
> > | +-08.0 Intel Corporation Device ae4c
> > | +-0a.0 Intel Corporation Device ad0d
> > | +-0b.0 Intel Corporation Arrow Lake NPU
> > | +-0d.0 Intel Corporation Meteor Lake-P
> > Thunderbolt 4 USB Controller
> > | +-0d.2 Intel Corporation Meteor Lake-P Thunderbolt 4 NHI #0
> > | +-14.0 Intel Corporation Device ae7f
> > | +-1f.0 Intel Corporation Device ae10
> > | \-1f.5 Intel Corporation Device ae23
> > \-[0000:80]-+-12.0 Intel Corporation Device 7f78
> > +-14.0 Intel Corporation Device 7f6e
> > +-14.5 Intel Corporation Device 7f2f
> > +-15.0 Intel Corporation Device 7f4c
> > +-15.1 Intel Corporation Device 7f4d
> > +-15.3 Intel Corporation Device 7f4f
> > +-16.0 Intel Corporation Device 7f68
> > +-16.3 Intel Corporation Device 7f6b
> > +-19.0 Intel Corporation Device 7f7a
> > +-19.1 Intel Corporation Device 7f7b
> > +-1c.0-[81]----00.0 Intel Corporation Wi-Fi
> > 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2
> > +-1c.4-[82-83]----00.0 Realtek Semiconductor Co.,
> > Ltd. Device 5264
> > +-1d.0-[84]----00.0 Intel Corporation Ethernet
> > Controller I226-LM
> > +-1f.0 Intel Corporation Device 7f12
> > +-1f.3 Intel Corporation Device 7f50
> > +-1f.4 Intel Corporation Device 7f23
> > \-1f.5 Intel Corporation Device 7f24
> >
> > Thank you for your time.
> >
> > Best regards,
> > En-Wei.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-07-28 6:33 ` Mika Westerberg
2025-07-30 7:24 ` En-Wei WU
@ 2025-08-08 6:43 ` Mika Westerberg
2025-08-11 8:04 ` En-Wei WU
1 sibling, 1 reply; 7+ messages in thread
From: Mika Westerberg @ 2025-08-08 6:43 UTC (permalink / raw)
To: En-Wei WU
Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb,
Alan Borzeszkowski
Hi,
On Mon, Jul 28, 2025 at 09:33:29AM +0300, Mika Westerberg wrote:
> Hi,
>
> On Fri, Jul 11, 2025 at 11:54:46AM +0800, En-Wei WU wrote:
> > Hi,
> >
> > I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
> > Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
> > by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
> > the following call trace. The issue reproduces approximately 60% of
> > the time.
>
> Could you share the whole dmesg (that is not line wrapped)? With
> "thunderbolt.dyndbg=+p" in the kernel command line.
>
> And can you confirm I understand the steps?
>
> 1. Boot the system up, nothing connected.
> 2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
> 3. Verify that the monitor works (+ run lspci/lsusb)
>
> Expected output: The monitor and the integrated peripherals (PCIe, USB)
> work fine.
>
> Actual output: There is error in the log and PCIe peripherals on the
> monitor do not show up in lspci output.
For some reason I never got the reply from you although I can see it on
lore.kernel.org. Thanks to Alan (Cc'd) who notified me about your reply :)
Anyways, I looked your first full dmesg and what stands out there is that:
[ 113.907760] ======= Hotplug Thunderbolt Cable =======
[ 116.091653] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot plug event on 0:1
...
[ 116.134083] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc050
[ 116.134092] thunderbolt 0-1: DELL U2725QE
...
[ 116.862460] [185] thunderbolt:tb_dump_hop:20: thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 16 Out HopID: 8
[ 116.862463] [185] thunderbolt:tb_dump_hop:22: thunderbolt 0000:00:0d.2: 1:1: Weight: 2 Priority: 3 Credits: 14 Drop: 0 PM: 0
[ 116.862466] [185] thunderbolt:tb_dump_hop:25: thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
[ 116.862469] [185] thunderbolt:tb_dump_hop:27: thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer (In/Eg): 0/0
[ 116.862472] [185] thunderbolt:tb_dump_hop:30: thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
[ 116.865613] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
This last one is unplug to the host router downstream port while we are
just setting up a PCIe tunnel, so it is expected that we cannot configure
the router (Dell device) from that point forward. That WARN() should be
changed to dev_warn() or so as this is really expected if the user unplugs
the device while we are configuring it (this is nature of USB4 as user can
unplug devices at any time).
In other words that calltrace is fine.
However, why the link goes down is another thing. If you did not
deliberately unplug the cable it suggest some sort of cable/PD issue to me.
Sometimes I have seen the plug gets bit loose and that makes the cable to
unplug itself quite easily. The other thing might be the cable itself may
be bad (I wonder if you have another Thunderbolt 4 cable that you could
try?).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-08-08 6:43 ` Mika Westerberg
@ 2025-08-11 8:04 ` En-Wei WU
2025-08-14 8:21 ` En-Wei WU
0 siblings, 1 reply; 7+ messages in thread
From: En-Wei WU @ 2025-08-11 8:04 UTC (permalink / raw)
To: Mika Westerberg
Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb,
Alan Borzeszkowski
Hi Mika,
Thanks for the update.
I didn't deliberately unplug the cable while the "acking hot unplug
event on 0:1" happened, suggesting that there might be an issue on our
cable as you said.
I'll perform other tests and get back to you.
Thanks,
En-Wei.
On Fri, 8 Aug 2025 at 14:43, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
>
> Hi,
>
> On Mon, Jul 28, 2025 at 09:33:29AM +0300, Mika Westerberg wrote:
> > Hi,
> >
> > On Fri, Jul 11, 2025 at 11:54:46AM +0800, En-Wei WU wrote:
> > > Hi,
> > >
> > > I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
> > > Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
> > > by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
> > > the following call trace. The issue reproduces approximately 60% of
> > > the time.
> >
> > Could you share the whole dmesg (that is not line wrapped)? With
> > "thunderbolt.dyndbg=+p" in the kernel command line.
> >
> > And can you confirm I understand the steps?
> >
> > 1. Boot the system up, nothing connected.
> > 2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
> > 3. Verify that the monitor works (+ run lspci/lsusb)
> >
> > Expected output: The monitor and the integrated peripherals (PCIe, USB)
> > work fine.
> >
> > Actual output: There is error in the log and PCIe peripherals on the
> > monitor do not show up in lspci output.
>
> For some reason I never got the reply from you although I can see it on
> lore.kernel.org. Thanks to Alan (Cc'd) who notified me about your reply :)
>
> Anyways, I looked your first full dmesg and what stands out there is that:
>
> [ 113.907760] ======= Hotplug Thunderbolt Cable =======
> [ 116.091653] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot plug event on 0:1
> ...
> [ 116.134083] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc050
> [ 116.134092] thunderbolt 0-1: DELL U2725QE
> ...
> [ 116.862460] [185] thunderbolt:tb_dump_hop:20: thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 16 Out HopID: 8
> [ 116.862463] [185] thunderbolt:tb_dump_hop:22: thunderbolt 0000:00:0d.2: 1:1: Weight: 2 Priority: 3 Credits: 14 Drop: 0 PM: 0
> [ 116.862466] [185] thunderbolt:tb_dump_hop:25: thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
> [ 116.862469] [185] thunderbolt:tb_dump_hop:27: thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer (In/Eg): 0/0
> [ 116.862472] [185] thunderbolt:tb_dump_hop:30: thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
> [ 116.865613] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
>
> This last one is unplug to the host router downstream port while we are
> just setting up a PCIe tunnel, so it is expected that we cannot configure
> the router (Dell device) from that point forward. That WARN() should be
> changed to dev_warn() or so as this is really expected if the user unplugs
> the device while we are configuring it (this is nature of USB4 as user can
> unplug devices at any time).
>
> In other words that calltrace is fine.
>
> However, why the link goes down is another thing. If you did not
> deliberately unplug the cable it suggest some sort of cable/PD issue to me.
> Sometimes I have seen the plug gets bit loose and that makes the cable to
> unplug itself quite easily. The other thing might be the cable itself may
> be bad (I wonder if you have another Thunderbolt 4 cable that you could
> try?).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-08-11 8:04 ` En-Wei WU
@ 2025-08-14 8:21 ` En-Wei WU
2025-08-14 8:32 ` Mika Westerberg
0 siblings, 1 reply; 7+ messages in thread
From: En-Wei WU @ 2025-08-14 8:21 UTC (permalink / raw)
To: Mika Westerberg
Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb,
Alan Borzeszkowski
I just ran a test using a different cable, and the issue remains.
One thing I've noticed is that no matter which cable and whether there
is a call trace on that hot-plug event, there is always the message:
thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot
unplug event on 0:1
On Mon, 11 Aug 2025 at 16:04, En-Wei WU <en-wei.wu@canonical.com> wrote:
>
> Hi Mika,
>
> Thanks for the update.
>
> I didn't deliberately unplug the cable while the "acking hot unplug
> event on 0:1" happened, suggesting that there might be an issue on our
> cable as you said.
>
> I'll perform other tests and get back to you.
>
> Thanks,
> En-Wei.
>
> On Fri, 8 Aug 2025 at 14:43, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> >
> > Hi,
> >
> > On Mon, Jul 28, 2025 at 09:33:29AM +0300, Mika Westerberg wrote:
> > > Hi,
> > >
> > > On Fri, Jul 11, 2025 at 11:54:46AM +0800, En-Wei WU wrote:
> > > > Hi,
> > > >
> > > > I'm seeing an issue on a Dell Pro Max 16 with Intel Arrow Lake CPU --
> > > > Hot-plugging a thunderbolt 4 cable into a thunderbolt 4 port (backed
> > > > by Intel iGPU) and connecting it to a Dell U2725QE monitor triggers
> > > > the following call trace. The issue reproduces approximately 60% of
> > > > the time.
> > >
> > > Could you share the whole dmesg (that is not line wrapped)? With
> > > "thunderbolt.dyndbg=+p" in the kernel command line.
> > >
> > > And can you confirm I understand the steps?
> > >
> > > 1. Boot the system up, nothing connected.
> > > 2. Once booted up, connect Thunderbolt cable to Dell U2725QE monitor.
> > > 3. Verify that the monitor works (+ run lspci/lsusb)
> > >
> > > Expected output: The monitor and the integrated peripherals (PCIe, USB)
> > > work fine.
> > >
> > > Actual output: There is error in the log and PCIe peripherals on the
> > > monitor do not show up in lspci output.
> >
> > For some reason I never got the reply from you although I can see it on
> > lore.kernel.org. Thanks to Alan (Cc'd) who notified me about your reply :)
> >
> > Anyways, I looked your first full dmesg and what stands out there is that:
> >
> > [ 113.907760] ======= Hotplug Thunderbolt Cable =======
> > [ 116.091653] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot plug event on 0:1
> > ...
> > [ 116.134083] thunderbolt 0-1: new device found, vendor=0xd4 device=0xc050
> > [ 116.134092] thunderbolt 0-1: DELL U2725QE
> > ...
> > [ 116.862460] [185] thunderbolt:tb_dump_hop:20: thunderbolt 0000:00:0d.2: 1:1: In HopID: 8 => Out port: 16 Out HopID: 8
> > [ 116.862463] [185] thunderbolt:tb_dump_hop:22: thunderbolt 0000:00:0d.2: 1:1: Weight: 2 Priority: 3 Credits: 14 Drop: 0 PM: 0
> > [ 116.862466] [185] thunderbolt:tb_dump_hop:25: thunderbolt 0000:00:0d.2: 1:1: Counter enabled: 0 Counter index: 2047
> > [ 116.862469] [185] thunderbolt:tb_dump_hop:27: thunderbolt 0000:00:0d.2: 1:1: Flow Control (In/Eg): 1/0 Shared Buffer (In/Eg): 0/0
> > [ 116.862472] [185] thunderbolt:tb_dump_hop:30: thunderbolt 0000:00:0d.2: 1:1: Unknown1: 0x0 Unknown2: 0x0 Unknown3: 0x0
> > [ 116.865613] [504] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
> >
> > This last one is unplug to the host router downstream port while we are
> > just setting up a PCIe tunnel, so it is expected that we cannot configure
> > the router (Dell device) from that point forward. That WARN() should be
> > changed to dev_warn() or so as this is really expected if the user unplugs
> > the device while we are configuring it (this is nature of USB4 as user can
> > unplug devices at any time).
> >
> > In other words that calltrace is fine.
> >
> > However, why the link goes down is another thing. If you did not
> > deliberately unplug the cable it suggest some sort of cable/PD issue to me.
> > Sometimes I have seen the plug gets bit loose and that makes the cable to
> > unplug itself quite easily. The other thing might be the cable itself may
> > be bad (I wonder if you have another Thunderbolt 4 cable that you could
> > try?).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Thunderbolt call trace occurs on hot-plug
2025-08-14 8:21 ` En-Wei WU
@ 2025-08-14 8:32 ` Mika Westerberg
0 siblings, 0 replies; 7+ messages in thread
From: Mika Westerberg @ 2025-08-14 8:32 UTC (permalink / raw)
To: En-Wei WU
Cc: westeri, michael.jamet, andreas.noever, YehezkelShB, linux-usb,
Alan Borzeszkowski
Hi,
On Thu, Aug 14, 2025 at 04:21:36PM +0800, En-Wei WU wrote:
> I just ran a test using a different cable, and the issue remains.
>
> One thing I've noticed is that no matter which cable and whether there
> is a call trace on that hot-plug event, there is always the message:
>
> thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot
> unplug event on 0:1
That means the USB4 link went down at that point and the driver cannot do
anything else except start tearing down the devices from that point.
We could try to look bit deeper what is happening there. However, if this
is PD/cable issue then there is little we can do on software side. Anyways,
I wonder if you can repro with tracing enabled?
There is info how to do that (let me know if any questions):
https://github.com/intel/tbtools/wiki/Useful-Commands#tracing
Can you then provide me either the merged log or dmesg and trace
separately? I can try to see if there is something suspicious happening
prior that unplug.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2025-08-14 8:33 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-11 3:54 Thunderbolt call trace occurs on hot-plug En-Wei WU
2025-07-28 6:33 ` Mika Westerberg
2025-07-30 7:24 ` En-Wei WU
2025-08-08 6:43 ` Mika Westerberg
2025-08-11 8:04 ` En-Wei WU
2025-08-14 8:21 ` En-Wei WU
2025-08-14 8:32 ` Mika Westerberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).