From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Cyril Roelandt <cyril@redhat.com>
Cc: linux-usb@vger.kernel.org, Oliver Neukum <oneukum@suse.com>
Subject: [Regression] xhci: some hard drives cannot be seen using a JMicron JMS56x enclosure
Date: Wed, 7 Mar 2018 17:16:45 +0200 [thread overview]
Message-ID: <b94137b3-b882-82a4-f4e2-d3d8f162e343@linux.intel.com> (raw)
On 06.03.2018 04:24, Cyril Roelandt wrote:
> Hi,
>
> On 02/28/18 15:55, Mathias Nyman wrote:
>>
>> I have a series of even more custom debugging patches.
>> attached patches apply on 4.13, but seris for both 4.13 and 4.15 can be found in the
>> streams-debug-4.13 and streams-debug-4.15 branches at
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git
>> https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git
>>
>> Can I ask you to do take logs with these?
>> no need for the previous diff, it's included
>
> I applied your three patches on top of v4.13 and got the followings logs:
>
> dmesg:
>
...
151.747272: xhci_get_hw_deq: ep_index 6 stream_id 1 deq 00000001bd377133
...
151.747288: xhci_queue_trb: CMD: Set TR Dequeue Pointer Command: deq 00000001bd377143 stream 1 slot 2 ep 7 flags C
...
151.747351: xhci_get_hw_deq: ep_index 6 stream_id 2 deq 00000001bd377143
>
> I hope this helps,
> Cyril Roelandt.
>
Thanks, It does
To me it looks like there is a issue with setting the dequeue pointer of a stream if
another stream was active while the endpoint stopped.
Basically if we want to cancel a URB on Stream 1, meaning stop entire endpoint with all its streams,
and then move stream 1 dequeue pointer forward, we end up setting the dequeue pointer of stream 2
as well. Probably because stream 2 was the active stream when the endpoint was stopped.
I can try to write a workaround that sets dequeue pointers for both the stream we want, and
the current active stream for each URB canceling.
Thanks
Mathias
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-03-07 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 15:16 Mathias Nyman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-26 12:27 [Regression] xhci: some hard drives cannot be seen using a JMicron JMS56x enclosure Mathias Nyman
2018-03-24 4:37 Cyril Roelandt
2018-02-28 13:55 Mathias Nyman
2018-02-21 15:04 Mathias Nyman
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=b94137b3-b882-82a4-f4e2-d3d8f162e343@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=cyril@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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).