summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/mpt3sas/mpt3sas_debug.h
diff options
context:
space:
mode:
authorSreekanth Reddy <sreekanth.reddy@avagotech.com>2015-01-12 11:39:01 +0530
committerChristoph Hellwig <hch@lst.de>2015-01-13 16:27:27 +0100
commitd2227f737404c6a6e7acbd2dec15da9ee57132c3 (patch)
tree5bfbda0d27417a58ffc81061436c5cb195ec2cd1 /drivers/scsi/mpt3sas/mpt3sas_debug.h
parentad666a0f41d98e4420acdbfd0e5f25e10f768e13 (diff)
downloadlinux-stable-d2227f737404c6a6e7acbd2dec15da9ee57132c3.tar.gz
linux-stable-d2227f737404c6a6e7acbd2dec15da9ee57132c3.tar.bz2
linux-stable-d2227f737404c6a6e7acbd2dec15da9ee57132c3.zip
mpt2sas: map log_info value 0x0x32010081 to DID_RESET
For any SCSI command, if the driver receives IOC status = SCSI_IOC_TERMINATED and log info = 0x32010081 then that command will be completed with DID_RESET host status. The definition of this log info value is "Virtual IO has failed and has to be retried". Firmware will provide this log info value with IOC Status "SCSI_IOC_TERMINATED", whenever a drive (with is a part of a volume) is pulled and pushed back within some minimal delay. With this log info value, firmware informs the driver to retry the failed IO command infinite times, so to provide some time for the firmware to discover the reinserted drive successfully instated of just retrying failed command for five times( doesn't giving enough time for firmware to complete the drive discovery) and failing the IO permanently even though drive came back successfully. Signed-off-by: Sreekanth Reddy <Sreekanth.Reddy@avagotech.com> Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/scsi/mpt3sas/mpt3sas_debug.h')
0 files changed, 0 insertions, 0 deletions