From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Christian Schaubschläger" <christian.schaubschlaeger@gmx.at>
Cc: linux-usb@vger.kernel.org
Subject: Re: Possible problem with thunderbolt 4
Date: Tue, 23 May 2023 11:55:23 +0300 [thread overview]
Message-ID: <20230523085523.GN45886@black.fi.intel.com> (raw)
In-Reply-To: <c5193a7f-53c4-34da-f3b4-128356f9a6a0@gmx.at>
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?
prev parent reply other threads:[~2023-05-23 8:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:24 Possible problem with thunderbolt 4 Christian Schaubschläger
2022-12-27 14:28 ` Mika Westerberg
2022-12-30 7:57 ` Christian Schaubschläger
2022-12-30 9:28 ` Mika Westerberg
2022-12-30 11:38 ` Christian Schaubschläger
2022-12-30 11:55 ` Mika Westerberg
2022-12-30 12:08 ` Christian Schaubschläger
2022-12-30 12:21 ` Mika Westerberg
2023-01-02 8:56 ` Christian Schaubschläger
2023-01-02 11:11 ` Mika Westerberg
2023-01-02 11:45 ` Christian Schaubschläger
2023-01-02 16:23 ` Mika Westerberg
2023-01-03 9:08 ` Christian Schaubschläger
2023-01-03 11:08 ` Mika Westerberg
2023-01-03 12:14 ` Christian Schaubschläger
2023-01-03 16:07 ` Mika Westerberg
2023-01-03 17:50 ` Christian Schaubschläger
2023-01-04 8:04 ` Mika Westerberg
2023-01-09 12:17 ` Christian Schaubschläger
2023-01-09 12:50 ` Mika Westerberg
2023-01-09 14:21 ` Christian Schaubschläger
2023-01-10 15:12 ` Mika Westerberg
2023-01-11 10:38 ` Christian Schaubschläger
2023-01-11 10:45 ` Mika Westerberg
2023-01-19 9:41 ` Christian Schaubschläger
2023-01-19 10:10 ` Mika Westerberg
2023-01-19 14:37 ` Christian Schaubschläger
2023-01-20 10:14 ` Mika Westerberg
2023-01-20 11:19 ` Christian Schaubschläger
2023-01-20 11:36 ` Mika Westerberg
2023-01-27 12:07 ` Christian Schaubschläger
2023-01-27 12:27 ` Mika Westerberg
2023-01-30 10:52 ` Christian Schaubschläger
2023-01-30 14:10 ` Mika Westerberg
2023-03-06 11:52 ` Mika Westerberg
2023-03-06 12:27 ` Christian Schaubschläger
2023-05-23 8:22 ` Christian Schaubschläger
2023-05-23 8:55 ` Mika Westerberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230523085523.GN45886@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=christian.schaubschlaeger@gmx.at \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.