Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7

From: Gia
Date: Wed May 22 2024 - 10:42:00 EST


Now this is odd...

I've tested another cable - a very short one used with a Gen3 nvme
enclosure that I'm sure it's working - and I got Gen2 20 Gbps. I also
have tested this on Windows 11 and I still just got a Gen2 connection.

I was almost sure it was caused by a bad USB4 implementation by the PC
manufacturer, then I tried to connect a Thunderbolt 3 disk enclosure
via daisy chain to the Caldigit dock and I got the full Gen3 40 Gbps
connection! See the attached picture.

I'll try to connect the dock to a laptop via Thunderbolt 3 as a last
test and I'll report back.



On Tue, May 21, 2024 at 1:26 PM Mika Westerberg
<mika.westerberg@xxxxxxxxxxxxxxx> wrote:
>
> On Tue, May 21, 2024 at 11:12:10AM +0200, Gia wrote:
> > Here you have the output from the dock upstream port:
> >
> > sudo tbdump -r 2 -a 1 -vv -N2 LANE_ADP_CS_0
> >
> > 0x0036 0x003c013e 0b00000000 00111100 00000001 00111110 .... LANE_ADP_CS_0
> > [00:07] 0x3e Next Capability Pointer
> > [08:15] 0x1 Capability ID
> > [16:19] 0xc Supported Link Speeds
> > [20:21] 0x3 Supported Link Widths (SLW)
> > [22:23] 0x0 Gen 4 Asymmetric Support (G4AS)
> > [26:26] 0x0 CL0s Support
> > [27:27] 0x0 CL1 Support
> > [28:28] 0x0 CL2 Support
> > 0x0037 0x0828003c 0b00001000 00101000 00000000 00111100 .... LANE_ADP_CS_1
> > [00:03] 0xc Target Link Speed → Router shall attempt Gen 3 speed
> > [04:05] 0x3 Target Link Width → Establish a Symmetric Link
> > [06:07] 0x0 Target Asymmetric Link → Establish Symmetric Link
> > [10:10] 0x0 CL0s Enable
> > [11:11] 0x0 CL1 Enable
> > [12:12] 0x0 CL2 Enable
> > [14:14] 0x0 Lane Disable (LD)
> > [15:15] 0x0 Lane Bonding (LB)
> > [16:19] 0x8 Current Link Speed → Gen 2
> > [20:25] 0x2 Negotiated Link Width → Symmetric Link (x2)
> > [26:29] 0x2 Adapter State → CL0
> > [30:30] 0x0 PM Secondary (PMS)
>
> Hmm, okay both sides announce support of Gen3 yet the link is Gen2 which
> makes me still suspect the cable, or the connection in general. I
> suggest, if you have, try with another Thunderbolt cable.

Attachment: CaldigitTS3Plus_Win11_link_speed.jpg
Description: JPEG image