Re: [RFC PATCH] usb: uas: quiesce SCSI before stopping endpoints on driver unbind

[Jiayi Li]

Hi Michal,


> This is actually an anomaly, transfer events should always point
> to valid rings. Device sendig bogus Stream ID would be code 34:
> Invalid Stream ID Error.
>
> Is this an ASMedia host controller? PCI ID doesn't looke like one...


The original controller was not ASMedia.  It was a Zhaoxin xHCI
controller, PCI ID 1d17:9204.


I have now reproduced the same post-rebind failure with the same USB
storage bridge (USB ID 2109:0715) and workload on an Intel xHCI
controller (PCI ID 8086:a2af).  This additional run used
6.14.0-27-generic.


The relevant post-bind log is:


  scsi host7: uas
  scsi 7:0:0:0: tag#4 data cmplt err -75 uas-tag 1 inflight: CMD
  scsi 7:0:0:0: tag#4 CDB: Inquiry 12 00 00 00 24 00
  scsi 7:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
  usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
  scsi host7: uas_eh_device_reset_handler success
  ...
  scsi 7:0:0:0: tag#7 CDB: Test Unit Ready 00 00 00 00 00 00
  scsi host7: uas_eh_device_reset_handler success
  sd 7:0:0:0: Device offlined - not ready after error recovery


There was no "Transfer event 26 for unknown stream ring" message in the
Intel run.  Therefore, I agree that event 26 is anomalous, but it is not
required for the storage failure and appears to be a secondary symptom
specific to the original run.  The first post-bind failure is the
Data-In completion error on INQUIRY, and the same error occurs on both
controllers.


Thanks,
Jiayi