apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2097229/+attachment/5854750/+files/ProcCpuinfoMinimal.txt
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/2097229 Title: Issues with Thunderbolt in initrd: Devices recognized but not working Status in cryptsetup package in Ubuntu: New Status in initrd-tools package in Ubuntu: New Status in plymouth package in Ubuntu: New Status in thunderbolt-tools package in Ubuntu: New Bug description: I'm facing an issue with Thunderbolt in initrd on a Lenovo ThinkPad Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN, Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11. Cross-checking the same Dock and the same SSD within another Laptop (older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt) proofs my suspicion that the hardware works fine but it is some software related issue. Step to Step: Up on starting the Laptop, USB generic drivers are loaded and the Dock is recognized. The Dock works flawlessly in pre-boot environments such as UEFI and GRUB with the loaded USB generic driver. As soon as GRUB is attempting to start the selected system and initrd is loaded for the later prompt of the LUKS passphrase, I recognize the USB generic drivers are loaded once more and the devices are being initialized as USB devices. After that, the USB connection seems to be "dropped" due to the Docks Thunderbolt capability being recognized which causes initrd to load the Thunderbolt module, which is prompted onscreen: thunderbolt 1-0:1.1: new retimer found, vendor ... thunderbolt 1-1: new device found, vendor ... thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock As soon as the Thunderbolt module is loaded the devices connected to the Dock shut off: Monitors turn blank, Keyboard backlights and Mouse status indicator LEDs turn off. I also assume the power supply to the laptop via the same USB connection is dropped, as the Status LED of the Dock is turning off, but do not know for sure. This causes that only Monitors or Keyboards directly connected to the Laptop via USB or HDMI will work for the stage of entering the LUKS passphrase (the internal Monitor and Keyboard obviously do work as intended -> which are directly connected via USB generic and not Thunderbolt). Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my assumption again: The Dock works flawlessly in UEFI, GRUB as well as the initrd/LUKS passphrase/plymouth environment as it is now acting as USB device. I suspect a faulty implementation of the Thunderbolt Module or Security Policies prohibiting its use: As soon as the LUKS passphrase is entered correct and the system starts to load, the Thunderbolt module seem to be loaded new again and from that moment on work properly: The Status LED of the Dock goes on and all devices connected light up again - all while still loading modules (way before the Login screen appears). That is why I first was hoping for the best case of security policies blocking Thunderbolt I/O in the initrd/LUKS passphrase/plymouth stage, but I found no documentation if there is such and how to change that policy which drives me to the conclusion that it is more likely a bug. I also did not find any workaround to drop Thunderbolt for initrd and set USB generic drivers only, which would help a lot until this bug is fixed. Here is some similar report that the issue exists since Kernel 5.4, but they did not have the same conclusion/mentioning of USB-generic drivers vs. Thunderbolt drivers: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215 Previous Stackexchange Ubuntu post by me regarding this behavior: https://askubuntu.com/questions/1534913/issues-with-thunderbolt-and-initramfs-in-ubuntu-24-devices-assume-blocked Another Users similar report: https://askubuntu.com/questions/1516595/lenovo-docks-not-recognized-in-initramfs-after-upgrading-to-ubuntu-24-04 Thanks for your help --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-11-13 (81 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) NonfreeKernelModules: zfs Package: thunderbolt-tools PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.11.0-1013.13-oem 6.11.0 Tags: noble wayland-session Uname: Linux 6.11.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True cmdline: BOOT_IMAGE=/BOOT/ubuntu_n3gtoe@/vmlinuz-6.11.0-1013-oem root=ZFS=rpool/ROOT/ubuntu_n3gtoe ro text crypttab: dm_crypt-0 PARTUUID=dbc7a221-c205-4222-a072-098993c914f7 /dev/urandom swap,initramfs,cipher=aes-xts-plain64:sha256,size=512,plain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2097229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
