linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216766] USB enumeration lockup
Date: Mon, 05 Dec 2022 15:58:41 +0000	[thread overview]
Message-ID: <bug-216766-208809-0P4nkQSEru@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216766-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216766

Mathias Nyman (mathias.nyman@linux.intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mathias.nyman@linux.intel.c
                   |                            |om

--- Comment #5 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
This could also be related to USB Type-C port setting in resume.

I'm guessing this dock uses DP Alt-mode, with both Display port
and USB 3 over Type-C.

In both resume cases there are some error related to the display:

[drm:dm_late_init [amdgpu]] *ERROR* DM_MST: Failed to start MST
[drm:amdgpu_device_ip_late_init [amdgpu]] *ERROR* late_init of IP block <dm>
failed -5

After this all usb devices on usb4 and usb5 buses disconnect (xHCI
0000:06:00.3:)
There are no xhci errors in the log, just disconnects, as if Type-C port was
muxed away from xHCI.

A bit later we see DP Alt mode entry after first resume, and usb devices are
enumerated again.
[  136.881649] [drm] DP Alt mode state on HPD: 1
[  137.153415] [drm] DM_MST: starting TM on aconnector: 00000000018c53ab [id:
89]

After second resume we don't se this DP Alt mode entry in the log, and usb
devices remain disconnected.

Not that familiar with Type-C settings, could be AMD specific

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-12-05 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 18:54 [Bug 216766] New: USB enumeration lockup bugzilla-daemon
2022-12-02 20:27 ` [Bug 216766] " bugzilla-daemon
2022-12-02 21:09 ` bugzilla-daemon
2022-12-03  2:51 ` bugzilla-daemon
2022-12-03 14:32 ` bugzilla-daemon
2022-12-05 15:58 ` bugzilla-daemon [this message]
2022-12-05 16:06 ` bugzilla-daemon
2022-12-05 18:32 ` bugzilla-daemon
2022-12-05 18:33 ` bugzilla-daemon
2022-12-05 18:34 ` 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-216766-208809-0P4nkQSEru@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 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).