From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219748] Pluggable UD-4VPD dock appears to continually reset with AMD AI 365
Date: Tue, 04 Mar 2025 08:44:17 +0000 [thread overview]
Message-ID: <bug-219748-208809-GFQ3jKAo4x@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219748-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219748
--- Comment #16 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
Thanks! So we have:
[ 56.773330] thunderbolt 0000:c6:00.6: 0:3: hotplug: scanning
[ 56.773335] thunderbolt 0000:c6:00.6: 0:3: hotplug: no switch found
[ 56.773349] thunderbolt 0000:c6:00.6: acking hot plug event on 0:2
[ 56.773362] thunderbolt 0000:c6:00.6: 0:2: hotplug: scanning
[ 56.773504] thunderbolt 0000:c6:00.6: 0:2: is connected, link is up (state:
2)
[ 56.773515] thunderbolt 0000:c6:00.6: 0:2: waiting for a while
[ 57.371077] thunderbolt 0000:c6:00.6: acking hot unplug event on 0:3
[ 57.371143] thunderbolt 0000:c6:00.6: acking hot unplug event on 0:2
[ 57.692761] thunderbolt 0000:c6:00.6: acking hot plug event on 0:3
[ 57.692828] thunderbolt 0000:c6:00.6: acking hot plug event on 0:2
[ 58.291125] thunderbolt 0000:c6:00.6: acking hot unplug event on 0:2
[ 58.291217] thunderbolt 0000:c6:00.6: acking hot unplug event on 0:3
[ 59.430462] thunderbolt 0000:c6:00.6: 0:2: .. done, trying to enumerate the
router
In other words there is some ~600ms timeout in the pluggable device that
triggers hot-remove and then hot-add if the device is not enumerated. This is
naturally the USB4 spec, as far as I can tell the host does not need to
enumerate the device at all actually.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-03-04 8:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 20:58 [Bug 219748] New: Pluggable UD-4VPD dock appears to continually reset with AMD AI 365 bugzilla-daemon
2025-02-03 20:58 ` [Bug 219748] " bugzilla-daemon
2025-02-04 6:49 ` bugzilla-daemon
2025-02-05 23:14 ` bugzilla-daemon
2025-02-05 23:15 ` bugzilla-daemon
2025-02-05 23:17 ` bugzilla-daemon
2025-02-06 15:51 ` bugzilla-daemon
2025-02-09 19:50 ` bugzilla-daemon
2025-02-10 7:30 ` bugzilla-daemon
2025-02-14 19:46 ` bugzilla-daemon
2025-02-14 19:47 ` bugzilla-daemon
2025-02-14 19:50 ` bugzilla-daemon
2025-02-14 21:31 ` bugzilla-daemon
2025-02-24 6:44 ` bugzilla-daemon
2025-02-24 7:58 ` bugzilla-daemon
2025-03-03 16:06 ` bugzilla-daemon
2025-03-04 8:44 ` bugzilla-daemon [this message]
2025-03-04 8:46 ` bugzilla-daemon
2025-03-04 23:41 ` bugzilla-daemon
2025-03-05 1:30 ` bugzilla-daemon
2025-03-05 9:26 ` bugzilla-daemon
2025-03-05 9:31 ` bugzilla-daemon
2025-03-05 11:52 ` bugzilla-daemon
2025-03-05 12:40 ` bugzilla-daemon
2025-03-05 13:11 ` bugzilla-daemon
2025-03-05 14:34 ` bugzilla-daemon
2025-03-05 23:33 ` bugzilla-daemon
2025-03-05 23:35 ` bugzilla-daemon
2025-03-06 3:53 ` bugzilla-daemon
2025-03-06 7:16 ` bugzilla-daemon
2025-03-06 17:24 ` bugzilla-daemon
2025-03-07 10:39 ` bugzilla-daemon
2025-03-07 20:38 ` bugzilla-daemon
2025-03-07 21:02 ` bugzilla-daemon
2025-03-12 9:33 ` bugzilla-daemon
2025-04-03 2:55 ` bugzilla-daemon
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=bug-219748-208809-GFQ3jKAo4x@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 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.