From: Oliver Neukum <oneukum@suse.com>
To: George Cherian <gcherian@caviumnetworks.com>
Cc: hdegoede@redhat.com, stern@rowland.harvard.edu,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: JMS56x not working reliably with uas driver
Date: Wed, 21 Dec 2016 13:12:12 +0100 [thread overview]
Message-ID: <1482322332.7638.12.camel@suse.com> (raw)
In-Reply-To: <585A7073.3060904@caviumnetworks.com>
On Wed, 2016-12-21 at 17:37 +0530, George Cherian wrote:
>
> On 12/21/2016 05:12 PM, Oliver Neukum wrote:
> > On Wed, 2016-12-21 at 17:09 +0530, George Cherian wrote:
> >> Hi Oliver,
> >>
> >> I was working with this JMicron device and using the uas driver.
> >> I am seeing the following 2 issues.
> >>
> >> 1) On connect I see the following messages.
> >
> > Thanks. Do you want to submit it to Greg?
> > The patch is fine.
> Yes please!!!
So you want me to submit it?
It would be your chance to get a patch upstream.
> >> 2) On disconnect I am seeing the following issue
> >>
> >> scsi host4: uas_post_reset: alloc streams error -19 after reset
> >> sd 4:0:0:0: [sdb] Synchronizing SCSI cache
> >>
> >> This is more fatal because after these messages the USB port becomes
> >> unusable. Even an lsusb invocation hangs for ever.
> >
> > Ouch. That points to a logic error. We should not reset if
> > a device is gone.
> > Could you send dmesg of such a case?
> here is the dmesg!!
> [ 203.475382] usb 4-1.3: new SuperSpeed USB device number 3 using xhci_hcd
> [ 203.496172] usb 4-1.3: New USB device found, idVendor=152d,
> idProduct=9561
> [ 203.503037] usb 4-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=5
> [ 203.510352] usb 4-1.3: Product: JMS56x Series
> [ 203.514698] usb 4-1.3: Manufacturer: JMicron
> [ 203.518966] usb 4-1.3: SerialNumber: 00000000000000000000
> [ 203.594383] usbcore: registered new interface driver usb-storage
> [ 203.612425] scsi host4: uas
> [ 203.615418] usbcore: registered new interface driver uas
> [ 203.620979] scsi 4:0:0:0: Direct-Access ST4000NM 0033-9ZM170
> 0001 PQ: 0 ANSI: 6
> [ 203.630240] sd 4:0:0:0: Attached scsi generic sg1 type 0
> [ 203.630382] sd 4:0:0:0: [sdb] 7814037168 512-byte logical blocks:
> (4.00 TB/3.63 TiB)
> [ 203.631338] sd 4:0:0:0: [sdb] Write Protect is off
> [ 203.631342] sd 4:0:0:0: [sdb] Mode Sense: 67 00 10 08
> [ 203.631734] sd 4:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, supports DPO and FUA
> [ 203.631899] xhci_hcd 0000:00:11.0: ERROR Transfer event for disabled
> endpoint or incorrect stream ring
> [ 203.631904] xhci_hcd 0000:00:11.0: @0000001f610a1c10 00000000
> 00000000 1b000000 03078001 state 14 ep_info 9403
> [ 203.631906] xhci_hcd 0000:00:11.0: No epring
> [ 203.674546] sdb: sdb1
> [ 203.676639] sd 4:0:0:0: [sdb] Attached SCSI disk
> [ 213.222913] scsi host4: uas_post_reset: alloc streams error -19 after
> reset
> [ 213.230548] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
>
> Above is the dmesg without the unusual_uas patch applied.
> Do you need me to enable any specific dev_dbg and then the dmesg output?
Damn, that is a strange error. Do you know whether it happens on other
XHCI controllers? Which controller are you using and can you please also
post "lsusb -v"?
Regards
Oliver
next prev parent reply other threads:[~2016-12-21 12:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 11:39 JMS56x not working reliably with uas driver George Cherian
2016-12-21 11:42 ` Oliver Neukum
[not found] ` <1482320547.7638.7.camel-IBi9RG/b67k@public.gmane.org>
2016-12-21 11:54 ` Hans de Goede
2016-12-21 11:54 ` Oliver Neukum
2016-12-21 12:07 ` George Cherian
2016-12-21 12:12 ` Oliver Neukum [this message]
2016-12-21 12:20 ` Hans de Goede
2016-12-21 12:47 ` George Cherian
[not found] ` <585A79F5.7080701-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-12-21 14:39 ` Oliver Neukum
[not found] ` <1482331185.7638.14.camel-IBi9RG/b67k@public.gmane.org>
2016-12-22 2:04 ` George Cherian
[not found] ` <98b66992-826f-7073-2a1d-eee6a2a9590f-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-12-22 10:13 ` George Cherian
2016-12-22 11:25 ` Oliver Neukum
2016-12-21 11:50 ` Hans de Goede
[not found] ` <585A69E6.6040009-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
2016-12-22 22:44 ` Alan Stern
2016-12-23 3:01 ` George Cherian
2016-12-23 14:22 ` Alan Stern
2016-12-27 14:34 ` Oliver Neukum
[not found] ` <1482849255.1731.1.camel-IBi9RG/b67k@public.gmane.org>
2016-12-27 15:20 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1612271015100.21478-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2016-12-27 15:53 ` Oliver Neukum
2016-12-27 18:22 ` George Cherian
2016-12-28 2:19 ` Alan Stern
2016-12-29 8:28 ` Oliver Neukum
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=1482322332.7638.12.camel@suse.com \
--to=oneukum@suse.com \
--cc=gcherian@caviumnetworks.com \
--cc=hdegoede@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).