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 218890] reset SuperSpeed USB device number 2 using xhci_hcd
Date: Sat, 25 May 2024 13:54:01 +0000	[thread overview]
Message-ID: <bug-218890-208809-PqTq1EYsm7@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 #1 from Alan Stern (stern@rowland.harvard.edu) ---
There are at least two very suspicious-looking things in the usbmon trace:

ffff9244d6cf5000 1301812804 S Ci:6:004:0 s 80 06 0301 0409 00ff 255 <
ffff9244d6cf5000 1306956154 C Ci:6:004:0 -2 255 = 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
ffff9244d6cf5000 1306956185 S Ci:6:004:0 s 80 06 0301 0409 0002 2 <
ffff9244d6cf5000 1310626032 C Ci:6:004:0 0 2 = 2a03

The first two lines show the computer asking the drive to send one of its
string descriptors and the transfer timing out after 5 seconds.  The trace says
that the device sent 255 bytes of zeros, which seems unlikely, but if it is
true it should have caused the transfer to end right away.  The second two
lines show the computer asking for just the first two bytes of the string
descriptor and the response arriving correctly, but not until an additional 3.7
seconds have passed.

ffff9244d6cf5300 1311630806 S Bo:6:004:2 -115 31 = 55534243 05000000 00020000
80000a28 00000000 00000001 00000000 000000
ffff9244d6cf5300 1311630823 C Bo:6:004:2 0 31 >
ffff9244ea669300 1311630835 S Bi:6:004:1 -115 512 <
ffff9244ea669300 1342568184 C Bi:6:004:1 -104 512 = 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000

This shows the computer trying to read the first sector of the drive.  The
transfer times out after 30 seconds (again after 512 bytes of zeros are
apparently received), and this error is what causes the reset.

It's possible that the problem is in the device, but more likely the problem is
in the kernel.  You've made a good start by finding that the 6.6.1 kernel works
properly and the 6.7.7 kernel doesn't.  You should try doing a git bisection to
find out which commit in the interval between those kernels caused the problem
to appear.

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

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

  reply	other threads:[~2024-05-25 13:54 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 ` bugzilla-daemon [this message]
2024-05-28  0:19 ` [Bug 218890] " bugzilla-daemon
2024-05-28  1:08 ` bugzilla-daemon
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-PqTq1EYsm7@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).