From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218890] reset SuperSpeed USB device number 2 using xhci_hcd
Date: Tue, 28 May 2024 01:08:41 +0000 [thread overview]
Message-ID: <bug-218890-208809-123KApREiC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218890-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218890
--- Comment #3 from Alan Stern (stern@rowland.harvard.edu) ---
That makes sense; the commit changes the sequence of commands during the early
part of initialization. However, to figure out what's going wrong it would be
a big help to have a usbmon trace for an earlier working kernel, such as
6.6.15, for comparison. Can you do that test and attach the trace to this bug
report?
You don't have to collect a huge amount of information. The first few seconds
would probably be enough -- up to the point where the "Attached SCSI disk"
message appears in the kernel log.
--
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:[~2024-05-28 1:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 10:02 [Bug 218890] New: reset SuperSpeed USB device number 2 using xhci_hcd bugzilla-daemon
2024-05-25 13:54 ` [Bug 218890] " bugzilla-daemon
2024-05-28 0:19 ` bugzilla-daemon
2024-05-28 1:08 ` bugzilla-daemon [this message]
2024-05-28 9:02 ` bugzilla-daemon
2024-05-29 10:40 ` bugzilla-daemon
2024-05-29 11:38 ` bugzilla-daemon
2024-05-29 11:39 ` bugzilla-daemon
2024-05-29 11:46 ` bugzilla-daemon
2024-05-29 15:39 ` bugzilla-daemon
2024-05-29 15:42 ` bugzilla-daemon
2024-05-30 11:44 ` bugzilla-daemon
2024-05-30 15:20 ` bugzilla-daemon
2024-05-30 15:28 ` bugzilla-daemon
2024-05-30 17:08 ` bugzilla-daemon
2024-05-30 19:03 ` Alan Stern
2024-05-31 1:44 ` Martin K. Petersen
2024-05-31 8:39 ` Pierre Tomon
2024-06-04 12:49 ` Mathias Nyman
2024-05-30 18:55 ` bugzilla-daemon
2024-06-20 13:56 ` bugzilla-daemon
2024-06-21 19:53 ` 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-218890-208809-123KApREiC@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).