From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Rick <rick@581238.xyz>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Sanath.S@amd.com, christian@heusel.eu, fabian@fstab.de,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: Dell WD19TB Thunderbolt Dock not working with kernel > 6.6.28-1
Date: Tue, 22 Oct 2024 19:10:55 +0300 [thread overview]
Message-ID: <20241022161055.GE275077@black.fi.intel.com> (raw)
In-Reply-To: <22415e85-9397-42db-9030-43fc5f1c7b35@581238.xyz>
Hi,
On Tue, Oct 22, 2024 at 05:44:18PM +0200, Rick wrote:
> Hi Mario,
>
> I apologize. I think I mixed up the versions between linux-lts and linux
> kernel.
>
> linux-6.6.28-1-lts works:
> https://gist.github.com/ricklahaye/610d137b4816370cd6c4062d391e9df5
> linux-6.6.57-1-lts works:
> https://gist.github.com/ricklahaye/48d5a44467fc29abe2b4fd04050309d7
>
> linux-6.11.4-arch2-1 doesn't work:
> https://gist.github.com/ricklahaye/3b13a093e707acd0882203a56e184d3f
> linux-6.11.4-arch2-1 with host_reset on 0 also doesn't work:
> https://gist.github.com/ricklahaye/ea2f4a04f7b9bedcbcce885df09a0388
Looks like some sort of connectivity issue to me.
However, can you first drop the "pcie_aspm=force" from the command line
and see if that has any affect. Probably does not but I suggest not to
keep it unless you really know that you want force ASPM on all PCIe
links (this may cause issues with some devices).
Anyways, even the working -lts ones you see the link goes down and up
which is not expected (unless you unplugged and plugged it back). Some
devices that are not Thunderbolt certified have this kinds of issues.
The cable could make difference too. Is it Thunderbolt 4 cable or
regular one?
next prev parent reply other threads:[~2024-10-22 16:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 12:13 Dell WD19TB Thunderbolt Dock not working with kernel > 6.6.28-1 rick
2024-10-22 12:55 ` Mario Limonciello
2024-10-22 15:44 ` Rick
2024-10-22 16:10 ` Mika Westerberg [this message]
2024-10-22 16:25 ` Mario Limonciello
2024-10-22 17:06 ` Rick
2024-10-23 6:10 ` Mika Westerberg
2024-10-25 10:20 ` Rick
2024-10-28 8:18 ` Mika Westerberg
2024-10-30 7:11 ` Rick
2024-10-30 9:06 ` Mika Westerberg
2024-11-01 12:57 ` Rick
2024-11-04 6:36 ` Mika Westerberg
2024-11-04 18:04 ` Rick
2024-11-05 6:31 ` Mika Westerberg
2024-11-05 8:12 ` Rick
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 6:34 Fabian Stäber
2024-09-23 6:45 ` Greg KH
2024-09-24 6:58 ` Fabian Stäber
2024-10-07 16:49 ` Fabian Stäber
2024-10-07 17:13 ` Linux regression tracking (Thorsten Leemhuis)
2024-10-07 17:21 ` Christian Heusel
2024-10-07 17:33 ` Mario Limonciello
2024-10-08 16:56 ` 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=20241022161055.GE275077@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Sanath.S@amd.com \
--cc=christian@heusel.eu \
--cc=fabian@fstab.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=rick@581238.xyz \
--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;
as well as URLs for NNTP newsgroup(s).