All of lore.kernel.org
 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: Thu, 30 May 2024 18:55:53 +0000	[thread overview]
Message-ID: <bug-218890-208809-BwZNWmeN5j@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 #15 from Alan Stern (stern@rowland.harvard.edu) ---
Here's the relevant part of the usbmon trace:

ffff97af45927780 378815216 S Bo:5:004:2 -115 31 = 55534243 08000000 00020000
80000a28 00000000 00000001 0000000 000000
ffff97af45927780 378815233 C Bo:5:004:2 0 31 >
ffff97af4255c900 378815246 S Bi:5:004:1 -115 512 <
ffff97af4255c900 410624206 C Bi:5:004:1 -104 0

There's still a timeout and cancellation, but at least now the number of bytes
transferred is reported as 0 and not 512.  So the patch did fix this bug, but
it didn't prevent the main problem from occurring.

It looks like the main difference between the working and non-working kernels
is that the non-working one issues a READ(10) command (added by Martin
Petersen's commit) whereas the working one uses only READ(16) commands.  I'll
ask Martin about updating his commit to change this.

-- 
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:[~2024-05-30 18:55 UTC|newest]

Thread overview: 28+ 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
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-06-04 14:45         ` [PATCH] scsi: sd: Use READ(16) when reading block zero on large capacity disks Martin K. Petersen
2024-06-04 14:49           ` Alan Stern
2024-06-04 17:00           ` Bart Van Assche
2024-06-04 17:30             ` Martin K. Petersen
2024-06-05  2:25             ` [PATCH v2] " Martin K. Petersen
2024-06-05 19:15               ` Bart Van Assche
2024-05-30 18:55 ` bugzilla-daemon [this message]
2024-06-20 13:56 ` [Bug 218890] reset SuperSpeed USB device number 2 using xhci_hcd 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-BwZNWmeN5j@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.