Re: Lacie Rugged USB3-FW does not work with UAS

From: Julian Sikorski <belegdol@gmail.com>
To: Nathan Stratton Treadway <vgerlists@nathanst.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 19:10:21 +0200	[thread overview]
Message-ID: <d11b22f3-3f09-2e3f-dc64-956193f2c5d3@gmail.com> (raw)
In-Reply-To: <20190904155831.GE4337@nathanst.com>

W dniu 04.09.2019 o 17:58, Nathan Stratton Treadway pisze:
> 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
> 
Moreover, does this matter that the two Read Capacity errors only appear 
after the device is disconnected?

Best regards,
Julian