| 2024-10-30 11:46:32 |
AceLan Kao |
bug |
|
|
added bug |
| 2024-10-30 11:48:01 |
AceLan Kao |
nominated for series |
|
Ubuntu Noble |
|
| 2024-10-30 11:48:01 |
AceLan Kao |
bug task added |
|
linux-oem-6.11 (Ubuntu Noble) |
|
| 2024-10-30 11:48:01 |
AceLan Kao |
nominated for series |
|
Ubuntu Oracular |
|
| 2024-10-30 11:48:01 |
AceLan Kao |
bug task added |
|
linux-oem-6.11 (Ubuntu Oracular) |
|
| 2024-10-30 11:48:14 |
AceLan Kao |
bug task added |
|
linux (Ubuntu) |
|
| 2024-10-30 11:48:35 |
AceLan Kao |
linux (Ubuntu Noble): status |
New |
Invalid |
|
| 2024-10-30 11:48:40 |
AceLan Kao |
linux (Ubuntu Oracular): status |
New |
In Progress |
|
| 2024-10-30 11:48:43 |
AceLan Kao |
linux (Ubuntu Oracular): assignee |
|
AceLan Kao (acelankao) |
|
| 2024-10-30 11:48:49 |
AceLan Kao |
linux-oem-6.11 (Ubuntu Noble): status |
New |
In Progress |
|
| 2024-10-30 11:48:54 |
AceLan Kao |
linux-oem-6.11 (Ubuntu Noble): assignee |
|
AceLan Kao (acelankao) |
|
| 2024-10-30 11:48:58 |
AceLan Kao |
linux-oem-6.11 (Ubuntu Oracular): status |
New |
Invalid |
|
| 2024-10-30 11:50:20 |
AceLan Kao |
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/
[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. |
[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. |
|
| 2024-10-30 14:51:11 |
AceLan Kao |
tags |
|
jira-cpl-46 oem-priority |
|
| 2024-11-13 09:29:20 |
LEE KUAN-YING |
linux-oem-6.11 (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-11-14 10:57:47 |
Ubuntu Kernel Bot |
tags |
jira-cpl-46 oem-priority |
jira-cpl-46 kernel-spammed-noble-linux-oem-6.11-v2 oem-priority verification-needed-noble-linux-oem-6.11 |
|
| 2024-11-15 02:55:54 |
AceLan Kao |
tags |
jira-cpl-46 kernel-spammed-noble-linux-oem-6.11-v2 oem-priority verification-needed-noble-linux-oem-6.11 |
jira-cpl-46 kernel-spammed-noble-linux-oem-6.11-v2 oem-priority verification-done-noble-linux-oem-6.11 |
|
| 2024-11-18 21:33:25 |
Launchpad Janitor |
linux-oem-6.11 (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
