All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 213081] usb-storage / uas Genesys Logic Card Reader no longer working on 5.12
Date: Wed, 19 May 2021 17:59:31 +0000	[thread overview]
Message-ID: <bug-213081-208809-OnIdFg1Gye@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213081-208809@https.bugzilla.kernel.org/>

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

--- Comment #19 from Alan Stern (stern@rowland.harvard.edu) ---
The usbmon trace shows that the original problem of not reporting the STALL has
been fixed.  But there is a new problem.  Here's where it shows up in the trace
for bus 6:

ffff88810248e0c0 67313744 S Bi:6:004:1 -115 13 <
ffff88810248e0c0 97843800 C Bi:6:004:1 -104 13 = 55534243 04000000 00000000 00

This was the second packet received from ep1in after the halt was cleared.  The
values in the received packet are correct (i.e., what I expect them to be), but
the timestamp and the -104 error code show that the URB timed out after 30
second and was unlinked.  This should not have happened; the URB should have
completed normally in less than one millisecond.

After this error, the device was reset and the same sequence of packets was
exchanged, with the same result as before (apparently -- the trace ends during
the second 30-second timeout window).

This indicates that the patch does not fully fix all the issues.  Evidently
xhci-hcd has trouble seeing when an URB for a formerly halted endpoint has
completed.

-- 
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:[~2021-05-19 17:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 12:43 [Bug 213081] New: usb-storage / uas Genesys Logic Card Reader no longer working on 5.12 bugzilla-daemon
2021-05-15 15:36 ` [Bug 213081] " bugzilla-daemon
2021-05-15 17:44 ` bugzilla-daemon
2021-05-15 17:44 ` bugzilla-daemon
2021-05-15 17:45 ` bugzilla-daemon
2021-05-15 17:51 ` bugzilla-daemon
2021-05-16  1:20 ` bugzilla-daemon
2021-05-16  9:51 ` bugzilla-daemon
2021-05-16 15:01 ` bugzilla-daemon
2021-05-17 19:15 ` bugzilla-daemon
2021-05-18  1:47 ` bugzilla-daemon
2021-05-18 16:59 ` bugzilla-daemon
2021-05-18 17:57 ` bugzilla-daemon
2021-05-18 19:01 ` bugzilla-daemon
2021-05-18 19:48 ` bugzilla-daemon
2021-05-18 21:19 ` bugzilla-daemon
2021-05-19 12:13 ` bugzilla-daemon
2021-05-19 17:31 ` bugzilla-daemon
2021-05-19 17:38 ` bugzilla-daemon
2021-05-19 17:59 ` bugzilla-daemon [this message]
2021-05-19 20:12 ` bugzilla-daemon
2021-05-19 21:24 ` bugzilla-daemon
2021-05-19 21:26 ` bugzilla-daemon
2021-05-20 20:04 ` bugzilla-daemon
2021-05-20 21:04 ` bugzilla-daemon
2021-05-21 16:54 ` bugzilla-daemon
2021-05-21 17:01 ` bugzilla-daemon
2021-05-21 19:25 ` bugzilla-daemon
2021-05-21 20:39 ` bugzilla-daemon
2021-05-21 21:56 ` bugzilla-daemon
2021-06-05  7:29 ` 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-213081-208809-OnIdFg1Gye@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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.