Hi Mika, attached you find two dmesg logs (with tunderbolt.dyndbg=+p), one from power off state were everything is ok (dmesg_ok.txt.xz). The second one (dmesg_nok.txt.xz) is after a reboot when the network interface is in faulty state. Hardware is: Dell Inc. Latitude 7440/0XDRJY, BIOS 1.3.1 04/25/2023 CPU0: 13th Gen Intel(R) Core(TM) i5-1345U (family: 0x6, model: 0xba, stepping: 0x3) thunderbolt 0-1: Dell WD19TB Thunderbolt Dock Best regards, Christian Am 23.05.23 um 10:55 schrieb Mika Westerberg: > Hi, > > On Tue, May 23, 2023 at 10:22:28AM +0200, Christian Schaubschläger wrote: >> Hi Mika, >> >> it seems that I have an issue here which seems similar to the one on the HP earlier this year. >> >> This time the hardware is a Dell Latitude 7440 with a rather new Intel i5-1345U (13th Gen.) and TB4. I have three Docks, one older Dell WD19TB, a newer Dell WD22TB4, and a ThinkPad Universal USB-C Dock. >> With the TB4 dock everything works fine (meaning all hardware is functioning in the UEFI firmware as well as in Windows after booting Linux first). >> >> With the older TB dock, as well as with the USB-C dock the network interface on the dock is dead after Linux. But in contrast to the HP case from earlier this year, this time the network interface remains dead when I boot Linux again. After replugging the dock it becomes alive again. >> >> This can easilsy be reproduced by booting Ubuntu 22.04 from an USB device. Using a newer kernel with the UNSET_INBOUND_SBTX fix does not solve the issue. >> >> I'm not sure if this is a USB or Thunderbolt issue, could be an issue with the network device, too (all three docks have the same Realtek 8153). But I don't see this problem with these docks on other Laptops I have access to, so probably it's not the network device... >> >> Can I provide some logs, etc. to dive deeper into this? > Sure, I suggest also start a new email thread or file a kernel.org > bugzilla ticket. > > Can you add "thunderbolt.dyndbg=+p" in the kernel command line and > reproduce the issue and share the full dmesg?
Attachment:
dmesg_nok.txt.xz
Description: application/xz
Attachment:
dmesg_ok.txt.xz
Description: application/xz
