Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Ben <benstaples10@gmail.com>
Cc: linux-usb@vger.kernel.org, andreas.noever@gmail.com,
	westeri@kernel.org, YehezkelShB@gmail.com
Subject: Re: xhci_hcd 0000:0c:00.0 dies with "Abort failed to stop command ring: -110" exactly 24s post-init, tunneled USB4 xHCI behind Goshen Ridge (ASUS ThunderboltEX 4) + CalDigit TS4
Date: Thu, 17 Sep 2026 06:38:47 +0200	[thread overview]
Message-ID: <20260917043847.GV106095@black.igk.intel.com> (raw)
In-Reply-To: <CANcA1gCjSCdXz_3+XA5ZOndm2pAL4ZUs93q_69dzZeq_cmq8Og@mail.gmail.com>

Hi,

On Wed, Sep 16, 2026 at 10:18:59PM -0400, Ben wrote:
> Mika,
> 
> The TCM bit is set.
> I have tried two cables. The cablematters premium 40gbps thunderbolt 4
> cable as well as the apple thunderbolt 5 pro cable. Both the 1m
> version. I believe they should be passive.
> 
> > 0x00a2 0x00003701 0b00000000 00000000 00110111 00000001 ..7. PORT_CS_18
> >   [00:07]        0x1 Cable USB4 Version

This tells that the cable does not support USB4 (should be 0x10)

> >   [08:08]        0x1 Bonding Enabled (BE)
> >   [09:09]        0x1 TBT3-Compatible Mode (TCM)

and because of that the link goes into TB3 mode.

Which is really interesting if you say that these are actual TB4+ cables.
Especially the Apple one should definitely be supporting USB4.

> >   [10:10]        0x1 CLx Protocol Support (CPS)
> >   [11:11]        0x0 RS-FEC Enabled (Gen 2) (RE2)
> >   [12:12]        0x1 RS-FEC Enabled (Gen 3) (RE3)
> >   [13:13]        0x1 Router Detected (RD)
> >   [16:16]        0x0 Wake on Connect Status
> >   [17:17]        0x0 Wake on Disconnect Status
> >   [18:18]        0x0 Wake on USB4 Wake Status
> >   [19:19]        0x0 Wake on Inter-Domain Status
> >   [20:20]        0x0 Cable Gen 3 Support (CG3)
> >   [21:21]        0x0 Cable Gen 4 Support (CG4)
> >   [22:22]        0x0 Cable Asymmetric Support (CSA)
> >   [23:23]        0x0 Cable CLx Support (CSC)
> >   [24:24]        0x0 AsymmetricTransitionInProgress (TIP)
> 
> 
> On the options, noted. I will keep them as standard as possible.
> 
>  And yes, this is a PCIe add-in card. I poked around my BIOS a bit and
> was not able to get it to be recognized on boot. All boot provided to
> you were performed with these options set:
> 
> > USB4 (ASM4242 Controller) Support Disabled (mutually exclusive with Thunderbolt Setting)
> > Thunderbolt/USB4 (Intel JHL8540 controller) Support: Enabled
> > Thunderbolt/USB4 (Intel JHL8540 controller) Security Level: No Security
> > Thunderbolt/USB4 (Intel JHL8540 controller) MMIO Resource: Full Size
> > Thunderbolt/USB4 (Intel JHL8540 controller) Wake Up Command: GO2SX

Okay this tells that it actually has support. However, the BIOS itself
might not support the PCIe resource allocation (well that's pretty much
proven already since you booted with the device connected). For your cases
it should be enough though because the BIOS seems to allocate the minimum
and if you are not planning to expand the chain afterwards with more
devices the one on the dock should be working okay (even the xHCI when the
link is TB3). When the link is USB4 you get the same devices through the
USB3 tunnel and PCIe is not even needed because it just contains PCIe
switch that has nothing behind it.

> I also have IOMMU enabled.

Yes that's expected and should be enabled.

  parent reply	other threads:[~2026-09-17  4:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  4:04 xhci_hcd 0000:0c:00.0 dies with "Abort failed to stop command ring: -110" exactly 24s post-init, tunneled USB4 xHCI behind Goshen Ridge (ASUS ThunderboltEX 4) + CalDigit TS4 Ben
2026-09-15  4:19 ` Mika Westerberg
2026-09-15  4:27   ` Ben
2026-09-15  4:38     ` Mika Westerberg
2026-09-15  4:46       ` Ben
2026-09-15  5:05         ` Mika Westerberg
2026-09-16  3:01           ` Ben
2026-09-16  7:51             ` Mika Westerberg
2026-09-17  2:18               ` Ben
2026-09-17  2:40                 ` Ben
2026-09-17  4:38                 ` Mika Westerberg [this message]
2026-09-19  0:28                   ` Ben
2026-09-21  4:44                     ` Mika Westerberg
2026-09-21 23:25                       ` Ben
2026-09-22  4:26                         ` Mika Westerberg
2026-09-22 11:28                           ` Mathias Nyman
2026-09-24  3:02                           ` Ben
2026-09-24 15:49                             ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mathias Nyman
2026-09-24 22:18                               ` Ben
2026-09-25  8:27                                 ` Michal Pecio
2026-09-25  8:40                                   ` Michal Pecio
2026-09-26  0:28                                     ` Ben
2026-09-26  8:37                                       ` Michal Pecio
2026-09-26 13:59                                         ` Ben
2026-09-26 17:41                                           ` Michal Pecio
2026-09-29 23:50                                             ` Ben

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=20260917043847.GV106095@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=benstaples10@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox