linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Stratton Treadway <vgerlists@nathanst.com>
To: Julian Sikorski <belegdol@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>, linux-usb@vger.kernel.org
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Wed, 4 Sep 2019 11:58:31 -0400	[thread overview]
Message-ID: <20190904155831.GE4337@nathanst.com> (raw)
In-Reply-To: <2a06a5dd-3fc9-0aac-a7e2-67be35e2d6bb@gmail.com>

On Mon, Sep 02, 2019 at 22:10:01 +0200, Julian Sikorski wrote:
> thanks for the patch! It appears that we got the drives confused, the 
> one needing quirks is 059f:1061. Unfortunately, even after hand-editing 
> the patch to match (attached for confirmation), uas is still not 
> working. The dmesg log is unchanged:
> 
> [   67.925435] usb 2-4: new SuperSpeed Gen 1 USB device number 2 using 
> xhci_hcd
> [   67.947738] usb 2-4: New USB device found, idVendor=059f, 
> idProduct=1061, bcdDevice= 0.01
> [   67.947739] usb 2-4: New USB device strings: Mfr=2, Product=3, 
> SerialNumber=1
> [   67.947740] usb 2-4: Product: Rugged USB3-FW
> [   67.947741] usb 2-4: Manufacturer: LaCie
> [   67.947742] usb 2-4: SerialNumber: 00000000157f928920fa
> [   67.978140] usbcore: registered new interface driver usb-storage
> [   68.007356] scsi host12: uas
> [   68.007520] usbcore: registered new interface driver uas
> [   68.007781] scsi 12:0:0:0: Direct-Access     LaCie    Rugged FW USB3 
>  051E PQ: 0 ANSI: 6
[...] 
> [  280.017821] usb 2-4: USB disconnect, device number 2
> [  280.017869] scsi host12: uas_eh_device_reset_handler FAILED err -22
> [  280.017876] sd 12:0:0:0: Device offlined - not ready after error recovery
> [  280.043423] sd 12:0:0:0: [sdb] Optimal transfer size 33553920 bytes
> [  280.204419] sd 12:0:0:0: [sdb] Read Capacity(16) failed: Result: 
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  280.204422] sd 12:0:0:0: [sdb] Sense not available.
> [  280.324417] sd 12:0:0:0: [sdb] Read Capacity(10) failed: Result: 
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  280.324420] sd 12:0:0:0: [sdb] Sense not available.


Oliver, does the presence of the "Read Capacity(16)" message here
indicate that either the quirk was not applied to the device or that
the patch didn't have the expected effect?

(Is there any way to check what quirks flags are actually in effect for
a device attached to the UAS driver?  For the usb-storage driver there's
both a "Quirks match for vid..." dmesg line and the Quirks: line in the 
/proc/scsi/usb-storage/* file -- but neither of those seem to exist for
the UAS driver....)

							Nathan


  reply	other threads:[~2019-09-04 16:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 13:31 Lacie Rugged USB3-FW does not work with UAS Julian Sikorski
2019-08-23 13:39 ` Oliver Neukum
2019-08-23 13:43   ` Julian Sikorski
2019-08-23 14:21     ` Julian Sikorski
2019-08-23 21:23       ` Oliver Neukum
2019-08-24  7:08         ` Julian Sikorski
2019-08-29 18:33           ` Julian Sikorski
2019-09-02 11:42             ` Oliver Neukum
2019-09-02 20:10               ` Julian Sikorski
2019-09-04 15:58                 ` Nathan Stratton Treadway [this message]
2019-09-04 17:10                   ` Julian Sikorski
2019-09-09 12:45                     ` Oliver Neukum
2019-09-09 16:18                       ` Julian Sikorski
2021-07-17  8:28                         ` Julian Sikorski
2021-07-19 12:47                           ` Oliver Neukum
2021-07-19 16:10                             ` Julian Sikorski
2021-07-20  7:43                               ` Greg KH
2021-07-20  9:35                               ` Oliver Neukum
2021-07-27 21:19                               ` Hans de Goede
     [not found]                                 ` <CA+xVL_QEgzb1tu-tzqYPxJF-G_a8czCp=uyZ1JJ9+5xmCcNp2Q@mail.gmail.com>
     [not found]                                   ` <CA+xVL_QrJ9f8-BwVRq1oG_yo2Cd=yQH9=TCm5g=MUO9MmdvRVA@mail.gmail.com>
2021-07-29  8:43                                     ` Oliver Neukum
2021-07-29  9:08                                     ` Hans de Goede
2021-08-01  7:36                                       ` Julian Sikorski
2021-08-01  8:46                                         ` Hans de Goede
     [not found]                                       ` <a645c513-794f-5171-d383-7b40fbb1ba18@gmail.com>
2021-08-01  7:47                                         ` Julian Sikorski
2021-09-12 20:13                                       ` Julian Sikorski
2021-09-13  7:38                                         ` Hans de Goede
     [not found]                                           ` <1f6c3026-143a-2004-24da-1da56e6305be@suse.com>
2021-09-13 11:50                                             ` Hans de Goede

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=20190904155831.GE4337@nathanst.com \
    --to=vgerlists@nathanst.com \
    --cc=belegdol@gmail.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).