[Bug 2085945] Re: Unreadable thunderbolt nvm_version under sysfs

** Tags added: jira-cpl-46 oem-priority

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2085945

Title:
Unreadable thunderbolt nvm_version under sysfs

Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.11 source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Status in linux-oem-6.11 source package in Oracular:
Invalid

Bug description:
[Impact]
Upgrading the TBT firmware through fwupdmgr and encounter the error.
It was working well with 6.8 kernel.

ubuntu@localhost:~$ sudo fwupdtool get-updates
Loading… [****************** ]02:20:03.374 FuEngine failed to add device /sys/devices/pci0000:00/0000:00:0d.3/domain1/1-0/1-1/usb4_port1/1-1:1.1: failed to read NVM
Loading… [********************* ]02:20:03.479 FuPluginIntelMe failed to get public key using file-id 0x40002300: generic failure [0xb]
Loading… [************************************** ]

[Fix]
Mika helps to fix the issue
https://patchwork.kernel.org/project/linux-usb/patch/20241028105121.894978-1-mika.westerberg@linux.intel.com/

The issue is introduced by below commit in v6.11-rc1, so 6.8 is not affected.
ff6ab055e070 thunderbolt: Add receiver lane margining support for retimers

[Test]
Plug TBT dock and run `sudo fwupdtool get-updates`, there should be no "failed to read NVM" error.

[Where problems could occur]
The retimer node should not be exposed to the system, the patch fixes the max index to elimite the nodes. It should be safe and not seems to introduce regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2085945/+subscriptions