On Mon, Feb 05, 2018 at 11:34:40PM +0530, Tushar Nimkar wrote: > Hi , > > I am enabling uas support. And facing the issue as follows. > > I have observed that when ( Transcend StoreJet TS256GESD400K ) > connected to my custom board, it detects first then > uas_eh_abort_handler() get call and then reset and enumerates > properly.When same device is used with 2.0 HUB their is no such issue. > > > logs-->Super-speed > > [ 323.912384] usb 2-1: new SuperSpeed USB device number 3 using xhci-hcd > [ 323.947103] scsi host1: uas > [ 323.948153] scsi 1:0:0:0: Direct-Access StoreJet TS256GESD400K > 0 PQ: 0 ANSI: 6 > [ 323.949825] sd 1:0:0:0: [sda] 500118192 512-byte logical blocks: > (256 GB/238 GiB) > [ 354.092341] sd 1:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 > inflight: CMD IN > [ 354.092380] sd 1:0:0:0: tag#0 CDB: opcode=0x12 12 01 00 00 40 00 > [ 354.098922] scsi host1: uas_eh_device_reset_handler start > [ 354.104963] xhci-hcd xhci-hcd.0.auto: ERROR Transfer event for > disabled endpoint or incorrect stream ring > [ 354.110095] xhci-hcd xhci-hcd.0.auto: @000000007d41f750 00000000 > 00000000 1b000000 01078001 > [ 354.232398] usb 2-1: reset SuperSpeed USB device number 3 using xhci-hcd > [ 354.253844] scsi host1: uas_eh_device_reset_handler success > [ 354.263222] sd 1:0:0:0: [sda] Write Protect is off > [ 354.263461] sd 1:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 354.267036] xhci-hcd xhci-hcd.0.auto: ERROR Transfer event for > disabled endpoint or incorrect stream ring > [ 354.275847] xhci-hcd xhci-hcd.0.auto: @000000007d41fa00 00000000 > 00000000 1b000000 01038001 > [ 354.287566] sda: sda1 sda2 > [ 354.295407] sd 1:0:0:0: [sda] Attached SCSI disk > > logs-->checked with 2.0 hub(same device) > > [ 104.292324] usb 3-1: new high-speed USB device number 2 using xhci-hcd > [ 104.457236] hub 3-1:1.0: USB hub found > [ 104.457305] hub 3-1:1.0: 4 ports detected > [ 105.392323] usb 3-1.4: new high-speed USB device number 3 using xhci-hcd > [ 105.545492] scsi host1: uas > [ 105.546777] scsi 1:0:0:0: Direct-Access StoreJet TS256GESD400K > 0 PQ: 0 ANSI: 6 > [ 105.548876] sd 1:0:0:0: [sda] 500118192 512-byte logical blocks: > (256 GB/238 GiB) > [ 105.556591] sd 1:0:0:0: [sda] Write Protect is off > [ 105.563321] sd 1:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [ 105.570685] sda: sda1 sda2 > [ 105.579182] sd 1:0:0:0: [sda] Attached SCSI disk > > > > Digging into issue I found that blk_rq_timed_out_timer() gets calls > and which calls scsi_time_out() and further uas_eh_abort_handler(). > [ blk_rq_timed_out_timer() --> blk_rq_check_expired()--> > scsi_times_out()-->scsi_abort_command()--> scmd_eh_abort_handler()--> > scsi_try_to_abort_cmd ()-->uas_eh_abort_handler() ] > > Also would like to add whenever we execute read_capacity_16() to read > the capacity of the device suddenly we are receiving > blk_rq_timed_out_timer() and around 30 sec device will reset and > enumerate. > > Also there are errors from xhci driver too. > > > Kernel : 4.4.60 and uas patches cherry-picked from kernel-4.14.13 4.4.60 is _really_ old and obsolete and insecure, and by randomly cherry-picking patches, we really have no idea what you are running. Can you duplicate this on 4.14.14? 4.15? thanks, greg k-h -- 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
