From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Gia <giacomo.gio@gmail.com>, "S, Sanath" <Sanath.S@amd.com>,
"Benjamin Böhmke" <benjamin@boehmke.net>,
"Christian Heusel" <christian@heusel.eu>,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"kernel@micha.zone" <kernel@micha.zone>,
"Andreas Noever" <andreas.noever@gmail.com>,
"Michael Jamet" <michael.jamet@intel.com>,
"Yehezkel Bernat" <YehezkelShB@gmail.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7
Date: Thu, 23 May 2024 07:45:07 +0300 [thread overview]
Message-ID: <20240523044507.GX1421138@black.fi.intel.com> (raw)
In-Reply-To: <79dfc0b9-94d4-4046-a3b9-185e53b4a192@amd.com>
On Wed, May 22, 2024 at 10:19:51AM -0500, Mario Limonciello wrote:
> On 5/22/2024 09:41, Gia wrote:
> > 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 suspect you can't actually get Gen 3 performance in this configuration.
> IIUC you should still be limited by the uplink to the host.
One "explanation" could be that the distance from the SoC to the Type-C
connector is relatively long which would require a retimer to get the
Gen3 speeds.
next prev parent reply other threads:[~2024-05-23 4:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHe5sWavQcUTg2zTYaryRsMywSBgBgETG=R1jRexg4qDqwCfdw@mail.gmail.com>
2024-05-06 12:53 ` [REGRESSION] Thunderbolt Host Reset Change Causes eGPU Disconnection from 6.8.7=>6.8.8 Linux regression tracking (Thorsten Leemhuis)
2024-05-20 9:19 ` Gia
2024-05-20 13:43 ` Mario Limonciello
2024-05-20 14:39 ` [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7 Christian Heusel
2024-05-20 14:41 ` Mario Limonciello
2024-05-20 15:12 ` Benjamin Böhmke
2024-05-20 16:21 ` Mika Westerberg
2024-05-20 16:53 ` Benjamin Böhmke
2024-05-20 17:30 ` Gia
2024-05-21 5:11 ` Mika Westerberg
2024-05-21 8:15 ` Gia
2024-05-21 8:59 ` Mika Westerberg
2024-05-21 9:12 ` Gia
2024-05-21 11:26 ` Mika Westerberg
2024-05-22 14:41 ` Gia
2024-05-22 15:19 ` Mario Limonciello
2024-05-23 4:45 ` Mika Westerberg [this message]
2024-05-21 4:59 ` Mika Westerberg
2024-05-21 10:52 ` Limonciello, Mario
2024-05-20 15:57 ` Gia
2024-05-21 5:15 ` Mika Westerberg
2024-05-21 8:07 ` Gia
2024-05-21 8:55 ` Mika Westerberg
2024-05-21 9:24 ` Gia
2024-05-21 11:29 ` Mika Westerberg
2024-05-21 10:50 ` Limonciello, Mario
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=20240523044507.GX1421138@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=benjamin@boehmke.net \
--cc=christian@heusel.eu \
--cc=giacomo.gio@gmail.com \
--cc=kernel@micha.zone \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox