On 30.05.2017 21:32, Nicolas Repentin wrote:
Hi Sure. Using archlinux with 4.11.3-1-ARCH. [ 44.160746] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 53.676266] sd 2:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB) [ 53.676276] sd 2:0:0:0: [sdb] 4096-byte physical blocks [ 53.676589] sd 2:0:0:0: [sdb] Write Protect is off [ 53.676599] sd 2:0:0:0: [sdb] Mode Sense: 53 00 00 08 [ 53.677095] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 53.750540] sdb: sdb1 [ 53.753497] sd 2:0:0:0: [sdb] Attached SCSI disk [ 53.958495] md127: Warning: Device sdb1 is misaligned [ 53.958499] md/raid1:md127: active with 1 out of 2 mirrors [ 53.970042] md127: detected capacity change from 0 to 3000457691136 [ 87.194368] EXT4-fs (md127): recovery complete [ 87.213077] EXT4-fs (md127): mounted filesystem with ordered data mode. Opts: (null) [ 102.786473] xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint or incorrect stream ring [ 102.795395] xhci_hcd 0000:00:14.0: @00000000ffffcb00 00000000 00000000 04000000 05088000 [ 120.207270] xhci_hcd 0000:00:14.0: Cannot set link state. [ 120.207288] usb usb2-port1: cannot disable (err = -32) See debug file (zipped) attached. After timestamp 120, I had to force shutdown the usb drive to avoid kernel freeze.
Thanks, turns out that when using streams (like UAS does) USB transaction errors don't need to have a valid TRB pointer. 102.788970: xhci_handle_event: EVENT: TRB 0000000000000000 status 'USB Transaction Error' len 0 slot 5 ep 8 type 'Transfer Event' flags e:c xhci driver can't handle this, it bails out before handling the error. Transaction error causes endpoint to halt, and driver needs to clear it. So at least one xhci driver issue, but that will only fix how we handle the Transaction error, not the transaction error itself. If I write a patch for this can you try it out? -Mathias -- 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
