[Bug 2097229] Re: Issues with Thunderbolt in initrd: Devices recognized but not working
beMOTION
2097229 at bugs.launchpad.net
Sun Feb 2 23:29:19 UTC 2025
** Description changed:
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:
- When starting the Laptop USB generic drivers are loaded and the Dock is recognized.
+ 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 to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts:
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 assume the power supply to the laptop does
still work, 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
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 loads, Thunderbolt modules are loaded fresh again and from that moment on work properly.
That is why I 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.
I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only.
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
** Description changed:
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
+ 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 to prompt the LUKS passphrase, I recognize the USB generic drivers are dropped and the Thunderbolt module is loaded due to onscreen prompts:
+ 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
+ Dock shut off: Monitors turn blank, Keyboard backlights and Mouse status
indicator LEDs turn off. I assume the power supply to the laptop does
still work, 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
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
+ 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 loads, Thunderbolt modules are loaded fresh again and from that moment on work properly.
That is why I 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.
I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only.
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
** Description changed:
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 assume the power supply to the laptop does
- still work, but do not know for sure.
+ 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
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 loads, Thunderbolt modules are loaded fresh again and from that moment on work properly.
That is why I 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.
I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only.
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
** Description changed:
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
+ 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 loads, Thunderbolt modules are loaded fresh again and from that moment on work properly.
That is why I 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.
I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only.
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
** Description changed:
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 loads, Thunderbolt modules are loaded fresh again and from that moment on work properly.
- That is why I 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.
+ 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 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.
I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only.
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
** Description changed:
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 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.
+ 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.
+ 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
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2097229/+subscriptions
More information about the foundations-bugs
mailing list