On 2018-04-17 12:03, Tushar Nimkar wrote:
On 2018-04-16 20:03, Oliver Neukum wrote:
Am Montag, den 16.04.2018, 10:23 -0400 schrieb Alan Stern:
> > > > [57246.701096] sd 1:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1
> > > > inflight: CMD IN
> > > > [57246.701130] sd 1:0:0:0: tag#0 CDB: opcode=0x1a 1a 00 3f 00 04 00
>
> URB is canceled, maybe that URB never finished?
No doubt. Perhaps the device doesn't support this particular
command.
Then we should expect the enumeration to always fail.
Possibly the lower layers swallow the transfer.
Note not every time abort with 0x1a command ..sometimes it is with
0x9e, 0x12, 0xa0.
As my observation issue is observed during read_capacity_16/REPORT_LUN
or INQUIRY.
Regards
Oliver
Oliver,
I have doubt that sequential scan(scsi_sequential_lun_scan) work well
for uas device(SCSI>3)..
Why? As I have seen in most cases failed to enumerate during REPORT_LUN
command...and there is older way to scan disk is also present,
so I was thinking to try that.. did following things
starget->no_report_luns = 1 ---> for my target while uas_target_alloc
(for try)
Found it is doing sequential scan but popuating 256 entries in cat
proc/partiction
for one disk
root@OpenWrt:/# cat proc/partitions
major minor #blocks name
8 0 488386584 sda
8 1 488384032 sda1
8 48 488386584 sdd
8 49 488384032 sdd1
8 64 488386584 sde
8 65 488384032 sde1
8 80 488386584 sdf
8 81 488384032 sdf1
8 96 488386584 sdg
8 97 488384032 sdg1
8 112 488386584 sdh
8 113 488384032 sdh1
........256 total.
...though it is SCSI>3 device ,it should support both sequential as well
as REPORT_LUN?
refering bellow commit ..no idea how this Seagate device is using
Sequential scan
commit 1363074667a6b7d0507527742ccd7bbed5e3ceaa
Author: Hans de Goede <hdegoede@xxxxxxxxxx>
Date: Tue Apr 12 12:27:09 2016 +0200
USB: uas: Add a new NO_REPORT_LUNS quirk
Add a new NO_REPORT_LUNS quirk and set it for Seagate drives with
an usb-id of: 0bc2:331a, as these will fail to respond to a
REPORT_LUNS command.
Cc: stable@xxxxxxxxxxxxxxx
Reported-and-tested-by: David Webb <djw@xxxxxxxxx>
Signed-off-by: Hans de Goede <hdegoede@xxxxxxxxxx>
Acked-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Do not know weather this is the cause for the issue or not ...but if so
need to think on this too :)
--
To unsubscribe from this list: send the line "unsubscribe linux-usb"
in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best Regards,
Tushar R Nimkar
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of Code Aurora Forum, hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
