Thunderbolt Device Activation Failure and DROM Data CRC Mismatch

[Yuwei Sun]

Description: Encountered multiple issues while attempting to connect and activate a Thunderbolt device. Initially, the device was recognized but then disconnected shortly after. System logs indicated a DROM data CRC mismatch, despite which, the system attempted to continue with the device activation. Subsequent log entries indicated failure in the device activation path, as well as a failed attempt to activate the PCIe tunnel, leading to an abort.

Something may be useful: boltctl command can not find this eGPU.

Error Messages:
Device disconnected.
DROM data CRC32 mismatch (expected vs. actual value discrepancy).
New device recognized but subsequent activation path failure.
PCIe tunnel activation failure and aborted attempt.
Kernel warning pointing to the tb_path_activate function.
System and Hardware Information
Operating system version, kernel version (6.5.0-21-generic).

Attempted Resolution Steps:
Reconnecting the Thunderbolt device.
Checking and updating the system kernel and firmware.
Adjusting Thunderbolt-related settings in BIOS/UEFI setup.

Expected Outcome:
Expected the Thunderbolt device to connect successfully and be stably recognized by the system without encountering issues like DROM data mismatch or activation path failures.
Actual Outcome
Faced a series of issues including frequent device disconnections, DROM data checksum mismatches, activation path failures, and failed attempts to activate the PCIe tunnel.
Additional Information
Provide all relevant system log entries and outputs.
Detailed information on any other attempted solutions or relevant setting adjustments should also be included.

Output From: $dmesg | grep thunderbolt
[ 1574.244690] thunderbolt 0-2: device disconnected
[ 1598.743402] thunderbolt 0000:75:00.5: 2: DROM data CRC32 mismatch (expected: 0x97552eeb, got: 0x8dd06782), continuing
[ 1598.754439] thunderbolt 0-2: new device found, vendor=0x215 device=0xb
[ 1598.754443] thunderbolt 0-2: XYJ-LINK XY Dock BX
[ 1598.863476] thunderbolt 0000:75:00.5: 2:1: hop deactivation failed for hop 1, index 8
[ 1598.863485] thunderbolt 0000:75:00.5: path activation failed
[ 1598.863526] WARNING: CPU: 10 PID: 18389 at drivers/thunderbolt/path.c:573 tb_path_activate+0x124/0x500 [thunderbolt]
[ 1598.863643] iwlwifi crypto_simd snd_acp_config usbhid snd drm_kms_helper ecdh_generic cryptd nls_iso8859_1 snd_soc_acpi cfg80211 hid rapl ecc ccp i2c_algo_bit soundcore snd_pci_acp3x sch_fq_codel k10temp wmi_bmof mac_hid acpi_tad msr parport_pc ppdev lp parport drm efi_pstore ip_tables x_tables autofs4 nvme xhci_pci r8169 nvme_core video thunderbolt crc32_pclmul i2c_piix4 xhci_pci_renesas realtek nvme_common wmi
[ 1598.863701] RIP: 0010:tb_path_activate+0x124/0x500 [thunderbolt]
[ 1598.863767] ? tb_path_activate+0x124/0x500 [thunderbolt]
[ 1598.863808] ? tb_path_activate+0x124/0x500 [thunderbolt]
[ 1598.863825] ? tb_path_activate+0x124/0x500 [thunderbolt]
[ 1598.863846] tb_tunnel_restart+0xd6/0x2b0 [thunderbolt]
[ 1598.863864] tb_tunnel_activate+0x141/0x180 [thunderbolt]
[ 1598.863885] tb_tunnel_pci+0xde/0x250 [thunderbolt]
[ 1598.863902] tb_domain_approve_switch+0x3e/0x70 [thunderbolt]
[ 1598.863920] authorized_store+0x250/0x290 [thunderbolt]
[ 1598.864049] thunderbolt 0000:75:00.5: 0:5 <-> 2:6 (PCI): activation failed
[ 1598.864216] thunderbolt 0000:75:00.5: 2:6: PCIe tunnel activation failed, aborting
[ 1598.864418] thunderbolt 0-2: device disconnected