public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216766] USB enumeration lockup
Date: Sat, 03 Dec 2022 02:51:25 +0000	[thread overview]
Message-ID: <bug-216766-208809-t6IcfGuMaD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216766-208809@https.bugzilla.kernel.org/>

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

--- Comment #3 from Alan Stern (stern@rowland.harvard.edu) ---
Judging from the log, it looks like the problem is related to the xHCI
controller at 0000:06:00.3 (although another possibility is PCI, since the log
includes several PCI error messages).  The problem seems to begin when all the
USB devices connected to that controller disappear during the second system
resume and never show up again.

I suggest you send an email describing the problem (include a pointer to this
Bugzilla entry) to the linux-usb@vger.kernel.org mailing list and CC: the xHCI
maintainer: Mathias Nyman <mathias.nyman@intel.com>.  He'll probably have some
requests for more tests you can run.

-- 
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-03  2:51 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 [this message]
2022-12-03 14:32 ` bugzilla-daemon
2022-12-05 15:58 ` bugzilla-daemon
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-t6IcfGuMaD@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