Hi, On Tue, Jan 03, 2023 at 01:14:09PM +0100, Christian Schaubschläger wrote: > > > > 0. Remove the hack patch if not already. > > > > Steps 1-3 same as before. > > > > 4. Disable runtime PM from the PCIe root ports: > > > > # echo on > /sys/bus/pci/devices/0000:00:07.0/power/control > > # echo on > /sys/bus/pci/devices/0000:00:07.1/power/control > > # echo on > /sys/bus/pci/devices/0000:00:07.2/power/control > > # echo on > /sys/bus/pci/devices/0000:00:07.3/power/control > > > > (or how many Thunderbolt PCIE root ports you have, disable it from all of them). > > > > 5. De-authorize the PCIe tunnel > > > > # echo 0 > /sys/bus/thunderbolt/devices/.../authorized > > > > 6. Soft reboot > > > > Does this change anything or the behavior is the same? > No, that doesn't change anything; though I'm not sure how many > Thunderbolt PCIe root ports I have; I guess only one: 0000:00:07.0 - > please have a look into the attached lspci output. > > dmesg after the above two steps: > > [ 91.655320] pcieport 0000:00:07.0: pciehp: Slot(3): Link Down > [ 91.657353] pcieport 0000:00:07.0: pciehp: Slot(3): Card not present > [ 91.659525] igc 0000:2c:00.0 eth1: PHC removed > [ 91.786204] pcieport 0000:04:03.0: Unable to change power state from D3hot to D0, device inaccessible > [ 91.788645] pcieport 0000:04:03.0: Runtime PM usage count underflow! > [ 91.790766] pcieport 0000:04:02.0: Unable to change power state from D3hot to D0, device inaccessible > [ 91.793156] pcieport 0000:04:02.0: Runtime PM usage count underflow! > [ 91.795341] pcieport 0000:04:01.0: Unable to change power state from D3hot to D0, device inaccessible > [ 91.797797] pcieport 0000:04:01.0: Runtime PM usage count underflow! > [ 91.800031] pcieport 0000:04:00.0: Unable to change power state from D3hot to D0, device inaccessible > [ 91.802671] pci_bus 0000:05: busn_res: [bus 05] is released > [ 91.805004] pci 0000:04:00.0: Removing from iommu group 16 > [ 91.807261] pci_bus 0000:06: busn_res: [bus 06-12] is released > [ 91.809582] pci 0000:04:01.0: Removing from iommu group 17 > [ 91.811925] pci_bus 0000:13: busn_res: [bus 13-1f] is released > [ 91.814303] pci 0000:04:02.0: Removing from iommu group 18 > [ 91.816604] pci_bus 0000:20: busn_res: [bus 20-2b] is released > [ 91.818985] pci 0000:04:03.0: Removing from iommu group 19 > [ 91.821412] pci 0000:2c:00.0: Removing from iommu group 21 > [ 91.823875] pci_bus 0000:2c: busn_res: [bus 2c] is released > [ 91.826241] pci 0000:04:04.0: Removing from iommu group 20 > [ 91.828592] pci_bus 0000:04: busn_res: [bus 04-2c] is released > [ 91.831018] pci 0000:03:00.0: Removing from iommu group 15 > > Still, no network interface after the reboot in the firmware... Okay you have only one Thunderbolt PCIe root port just as you correctly guessed (07.0). At this point I'm running out of ideas what to check or try. We have seen similar but only when there is no battery on the device which is not your case, I suppose. In this case the initial USB4 link state is kind of "open" so it may come up or not.
