All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: David GUENAULT <david.guenault@gmail.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb@vger.kernel.org
Subject: Re: thunderbolt: PCIe tunnel creation fails for USB4 eGPU dock on Titan Ridge host
Date: Fri, 7 Aug 2026 06:37:19 +0200	[thread overview]
Message-ID: <20260807043719.GI235112@black.igk.intel.com> (raw)
In-Reply-To: <CAOFj14_tBEh5eXt_o5ZZme6bMt+Gt1pLS1ARwR2n=29WcjP2Qw@mail.gmail.com>

Hi,

On Thu, Aug 06, 2026 at 11:48:24PM +0200, David GUENAULT wrote:
> PCIe tunneling never succeeds between an Intel Titan Ridge 2C host router
> and a USB4 (Thunderbolt 5) eGPU dock, although the Thunderbolt link itself
> comes up fully bonded at 40 Gb/s and both routers enumerate cleanly.
> tb_tunnel_pci() fails silently -- the only message is "PCIe tunnel creation
> failed", with no path/credit/activation diagnostics even with full dyndbg.

That's because Titan Ridge is using firmware based connection manager so
it's not the TB driver that creates the tunnels.

Can you drop all the non-distro kernel command line options, except
"thunderbolt.dyndbg=+p" and provide full dmesg?

  reply	other threads:[~2026-08-07  4:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 21:48 thunderbolt: PCIe tunnel creation fails for USB4 eGPU dock on Titan Ridge host David GUENAULT
2026-08-07  4:37 ` Mika Westerberg [this message]
2026-08-07  9:55   ` David GUENAULT
2026-08-07 10:18     ` Mika Westerberg
2026-08-07 11:01       ` David GUENAULT
2026-08-07 11:29         ` Mika Westerberg
2026-08-07 11: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=20260807043719.GI235112@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=david.guenault@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=westeri@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.