I can no longer boot from my Thunderbolt disk

[Roman Steiner]

Description: Ubuntu 24.04.1 LTS
Release: 24.04

Package: linux-image-6.8.0-41-generic

Since the kernel 6.8.0-36 has been updated to a newer version, I can no longer boot from my Thunderbolt disk. Even with the current kernel 6.8.0-41 it does not work.

If I boot with the old kernel 6.8.0-36 it still works, but I don't want to work with it forever.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-41-generic 6.8.0-41.41
ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
Uname: Linux 6.8.0-36-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/seq: roman 2357 F.... pipewire
 /dev/snd/controlC0: roman 2361 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 31 18:34:27 2024
InstallationDate: Installed on 2024-07-07 (55 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Dell Inc. Latitude 5550
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-36-generic root=/dev/mapper/cryptvg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-36-generic N/A
 linux-backports-modules-6.8.0-36-generic N/A
 linux-firmware 20240318.git3b128b60-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2024
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 0314H2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.5
dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd07/18/2024:br1.6:efr1.5:svnDellInc.:pnLatitude5550:pvr:rvnDellInc.:rn0314H2:rvrA00:cvnDellInc.:ct10:cvr:sku0CB9:
dmi.product.family: Latitude
dmi.product.name: Latitude 5550
dmi.product.sku: 0CB9
dmi.sys.vendor: Dell Inc.

[Mario Limonciello (superm1)]

Try adding thunderbolt.host_reset=0 to your kernel command line. Suspect it's the changes that came in https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:

    - thunderbolt: Introduce tb_port_reset()
    - thunderbolt: Introduce tb_path_deactivate_hop()
    - thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4
      routers
    - thunderbolt: Reset topology created by the boot firmware

These changes were done to fix a number of other issues with re-using boot firmware settings. That kernel command line option will align it with old behavior as a workaround.

I feel that a "correct" solution for your issue would be for 'thunderbolt.ko' and boltd to be included in the initramfs so that the reset happens before the rootfs is mounted.

[Roman Steiner (romste)]

It works with thunderbolt.host_reset=0 in the kernel command line.

Thanks

[Mario Limonciello (superm1)]

Thanks for confirming it. You can also try to add thunderbolt to /etc/initramfs-tools/modules to see if that's enough to fix the issue instead of the kernel command line workaround.

I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
* boltd

In any case; I feel the bug is now in initramfs-tools.

[Roman Steiner (romste)]

It doesn't work with adding thunderbolt to /etc/initramfs-tools/modules (and update-initramfs after the add).

[Mario Limonciello (superm1)]

Thanks for checking. I believe what's going on is that it resets the topology, but the policy to re-authorize it doesn't happen because bolt is missing until the rootfs is loaded. So initramfs needs a hook to include bolt.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.