From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.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,
Mario Limonciello <mario.limonciello@amd.com>,
Sanath.S@amd.com
Subject: Re: [PATCH] [RFC] thunderbolt: Add delay for Dell U2725QE link width
Date: Wed, 10 Dec 2025 08:41:33 +0100 [thread overview]
Message-ID: <20251210074133.GE2275908@black.igk.intel.com> (raw)
In-Reply-To: <pjn5d7oz433z4jph6whdalhowf652xknnk2fh5q7elffgb5ogo@7dtpvywxc6nw>
Hi,
On Wed, Dec 10, 2025 at 11:15:25AM +0800, Chia-Lin Kao (AceLan) wrote:
> > We should understand the issue better. This is Intel Goshen Ridge based
> > monitor which I'm pretty sure does not require additional quirks, at least
> > I have not heard any issues like this. I suspect this is combination of the
> > AMD and Intel hardware that is causing the issue.
> Actually, we encountered the same issue on Intel machine, too.
> Here is the log captured by my ex-colleague, and at that time he used
> 6.16-rc4 drmtip kernel and should have reported this issue somewhere.
> https://paste.ubuntu.com/p/bJkBTdYMp6/
>
> The log combines with drm debug log, and becomes too large to be
> pasted on the pastebin, so I removed some unrelated lines between 44s
> ~ 335s.
Okay I see similar unplug there:
[ 337.429646] [374] thunderbolt:tb_handle_dp_bandwidth_request:2752: thunderbolt 0000:00:0d.2: 0:5: handling bandwidth allocation request, retry 0
...
[ 337.430291] [165] thunderbolt:tb_cfg_ack_plug:842: thunderbolt 0000:00:0d.2: acking hot unplug event on 0:1
We had an issue with MST monitors but that resulted unplug of the DP OUT
not link going down. That was fixed with:
9cb15478916e ("drm/i915/dp_mst: Work around Thunderbolt sink disconnect after SINK_COUNT_ESI read")
If you have Intel hardware still there it would be good if you could try
and provide trace from that as well.
next prev parent reply other threads:[~2025-12-10 7:41 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 [this message]
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
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=20251210074133.GE2275908@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Sanath.S@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.