https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #1 from MasterCATZ (mastercatz@xxxxxxxxxxx) --- pm80xx mpi_ssp_completion 1874:sas IO status 0x24 [ 708.424035] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:500605ba00b9cca2 [ 708.424241] sd 1:0:8:0: Power-on or device reset occurred [ 708.712116] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.072865] sas: Enter sas_scsi_recover_host busy: 1 failed: 1 [ 709.073843] sd 1:0:8:0: Power-on or device reset occurred [ 709.074231] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1 [ 709.082924] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083028] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083030] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083032] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083148] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083151] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.083259] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION [ 709.473399] sas: Enter sas_scsi_recover_host busy: 7 failed: 7 [ 709.478894] sd 1:0:8:0: Power-on or device reset occurred [ 709.479203] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 7 tries: 1 [ 709.482057] pm80xx 0000:04:00.0: dev 500605ba00b9cca2 sent sense data, but stat(28) is not CHECK CONDITION -- You are receiving this mail because: You are the assignee for the bug.
