From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Andreas Noever <andreas.noever@gmail.com>,
Mika Westerberg <westeri@kernel.org>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Sanath.S@amd.com, "Lin, Wayne" <Wayne.Lin@amd.com>
Subject: Re: [PATCH] [RFC] thunderbolt: Add delay for Dell U2725QE link width
Date: Tue, 30 Dec 2025 08:30:11 +0100 [thread overview]
Message-ID: <20251230073011.GD2275908@black.igk.intel.com> (raw)
In-Reply-To: <wqc6xvaeebqb5skiba3gpekdpmf3yz2zk3maeqprdtdpglvhww@za2efpacwhzo>
On Mon, Dec 22, 2025 at 09:33:48AM +0800, Chia-Lin Kao (AceLan) wrote:
> On Thu, Dec 18, 2025 at 11:20:21AM +0100, Mika Westerberg wrote:
> > On Thu, Dec 18, 2025 at 03:35:05PM +0800, Chia-Lin Kao (AceLan) wrote:
> > > > Now since USB 2.x has its own wires in Type-C cable this tells me that
> > > > there is some real problem with the connection. Have you tried different
> > > > cables already?
> > > Here is the log I got with another tbt4 cable.
> > > I'm using the kernel with Mario suggests modification.
> > >
> > > https://people.canonical.com/~acelan/bugs/tbt_call_trace/intel/merged_6.18.0-d358e5254674+.patched2.2_new_cable.out
> >
> > Here I see (assuming I read it right) that the USB 2.x enumerates only
> > after the first unplug:
> >
> > [ 28.589861] usb 3-2: New USB device found, idVendor=1d5c, idProduct=5801, bcdDevice= 1.01
> > [ 28.589864] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> > [ 28.589865] usb 3-2: Product: USB2.0 Hub
> > [ 28.589866] usb 3-2: Manufacturer: Fresco Logic, Inc.
> >From the logs, sometimes this hub is enumerated before the call trace
> and then enumerated again after the call trace.
>
> And I also found there are some suspicious USB disconnections while
> plugging in the tbt monitor.
>
> I tried to avoid the USB disconnection by the following modification,
> but still no luck.
Okay but I think this is not a SW issue, rather an issue with that
particular monitor/cable/connection/PD. It is not just the USB4 link that
goes down it's the whole type-C connection therefore something is wrong on
the electrical side of things (well at least it seems so).
Dell also typically validate that their stuff works in Linux so I would
expect to got some report from them if that's not the case (unless you are
doing just that ;-))
Have you tried this same monitor with Windows? Do you see the same issue
there? I would expect so.
next prev parent reply other threads:[~2025-12-30 7:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 5:41 [PATCH] [RFC] thunderbolt: Add delay for Dell U2725QE link width Chia-Lin Kao (AceLan)
2025-12-09 7:06 ` Mika Westerberg
2025-12-09 16:49 ` Mario Limonciello
2025-12-10 5:33 ` Chia-Lin Kao (AceLan)
2025-12-10 3:15 ` Chia-Lin Kao (AceLan)
2025-12-10 7:41 ` Mika Westerberg
2025-12-10 21:42 ` Mario Limonciello
[not found] ` <coxrm5gishdztghznuvzafg2pbdk4qk3ttbkbq7t5whsfv2lk5@3gqepcs6h4uc>
2025-12-12 12:39 ` Mika Westerberg
2025-12-12 14:40 ` Mario Limonciello
2025-12-17 3:06 ` AceLan Kao
2025-12-17 12:55 ` Mika Westerberg
2025-12-17 15:53 ` Mario Limonciello
2025-12-18 1:38 ` AceLan Kao
2025-12-18 7:21 ` Mika Westerberg
[not found] ` <6inne3luvw4ot3wqnsaw3gzhlxtd4756i465oto6so5ox3syxp@kibuv4vhvexx>
2025-12-18 10:20 ` Mika Westerberg
2025-12-22 1:33 ` Chia-Lin Kao (AceLan)
2025-12-30 7:30 ` Mika Westerberg [this message]
2025-12-31 1:33 ` Chia-Lin Kao (AceLan)
2025-12-31 6:03 ` Mika Westerberg
2026-01-02 2:03 ` Chia-Lin Kao (AceLan)
2026-01-05 11:19 ` 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=20251230073011.GD2275908@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Sanath.S@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=acelan.kao@canonical.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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