From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Sebastian Loscher <krang@krang.de>
Cc: Mario Limonciello <superm1@kernel.org>,
linux-usb@vger.kernel.org, andreas.noever@gmail.com
Subject: Re: [BUG] thunderbolt: USB4 v2 TBGAA tunnel creation crash in TMU enhanced uni-directional mode
Date: Fri, 29 May 2026 08:34:22 +0200 [thread overview]
Message-ID: <20260529063422.GJ3102@black.igk.intel.com> (raw)
In-Reply-To: <536cc913-8ae8-9000-69f9-02f604b7edfe@krang.de>
Hi,
On Wed, May 27, 2026 at 09:19:56PM +0200, Sebastian Loscher wrote:
> Hey Mika,
>
> Please find attached some more tbtraces (and dmesg however I think they tell
> you less of a story).
>
> I have the previously used cable and repeated the usual boot, plugin. Then I
> dumped the files and rebooted and repeated with a 2nd cable (it's from a three
> months old Lenovo and it charges with 140W, says TB in the package; the
> original cable came with the dock and was only unpacked the day before I
> reached out to you). I attached two different dumps for the 2nd, no reboot in
> between.
> You wondered about the initial couple of disconnects in the logs and blamed the
> cable - rightfully so - but here are some more details, maybe not fully obvious
> from the logs:
> Onbiously there is a GPU in the dock that runs at 100% fan speed, expected of
> course no PC tells it to do otherwise. When I plug the USB cable in there is
> 50% chance that the fans go down in speed for a second during the initial
> handshake (did so with tbtrace_cable1 and cable2_2 | but fails at speed
> negotiation) or it just keeps spinning high (tbtrace_cable2) which seems like,
> at least when I watched dmesg, that it doesn't go beyond the initial handshake
> and disconnects right away. That was, in the previous test, for me the reason
> to plugin it in and out multiple times until I could ‘hear’ something more was
> happening.
>
> A bit adventurous description but maybe the extra info is worth it.
I noticed in your dmesg you have pcie_port_pm=off, can you remove that from
the command line, and add "thunderbolt.dyndbg=+p" instead and try again?
Then provide full dmesg?
next prev parent reply other threads:[~2026-05-29 6:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 16:43 [BUG] thunderbolt: USB4 v2 TBGAA tunnel creation crash in TMU enhanced uni-directional mode Sebastian Loscher
2026-05-25 4:44 ` Mika Westerberg
2026-05-25 22:22 ` Mario Limonciello
2026-05-26 4:07 ` Mika Westerberg
2026-05-26 16:03 ` Sebastian Loscher
2026-05-27 12:26 ` Mika Westerberg
2026-05-27 19:19 ` Sebastian Loscher
2026-05-29 6:34 ` Mika Westerberg [this message]
2026-05-29 20:05 ` Sebastian Loscher
2026-05-28 21:13 ` Mario Limonciello
2026-05-29 6:35 ` Mika Westerberg
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=20260529063422.GJ3102@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=krang@krang.de \
--cc=linux-usb@vger.kernel.org \
--cc=superm1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox