aboutsummaryrefslogtreecommitdiffstats
path: root/lib/locking-selftest-rlock-hardirq.h
diff options
context:
space:
mode:
authorKashyap, Desai <kashyap.desai@lsi.com>2009-09-23 17:26:58 +0530
committerJames Bottomley <James.Bottomley@suse.de>2009-10-29 13:03:10 -0400
commitfa7f31673583a6e0876f8bb420735cdd8a3ffa57 (patch)
tree5b547d903081571bc2cc5950de513beba4895ed0 /lib/locking-selftest-rlock-hardirq.h
parent9fec5f9fc2fbe7c6e39db01ae296528d9a20a5b1 (diff)
downloadkernel_samsung_smdk4412-fa7f31673583a6e0876f8bb420735cdd8a3ffa57.zip
kernel_samsung_smdk4412-fa7f31673583a6e0876f8bb420735cdd8a3ffa57.tar.gz
kernel_samsung_smdk4412-fa7f31673583a6e0876f8bb420735cdd8a3ffa57.tar.bz2
[SCSI] mpt2sas: Support for stopping driver when Firmware encounters
Added command line option and shost sysfs attribute called mpt2sas_fwfault_debug. When enduser writes a "1" to this parameter, this will enable support in the driver for debugging firmware timeout related issues. This handling was added in three areas (a) scsi error handling callback called task_abort, (b) IOCTL interface, and (c) other timeouts that result in diag resets, such as manufacturing config pages. When this support is enabled, the driver will provide dump_stack to console, halt controller firmware, and panic driver. The end user probably would want to setup serial console redirection so the dump stack can be seen. Here are the three methods for enable this support: (a) # insmod mpt2sas.ko mpt2sas_fwfault_debug=1 (b) # echo 1 > /sys/module/mpt2sas/parameters/mpt2sas_fwfault_debug (c) # echo 1 > /sys/class/scsi_host/host#/fwfault_debug (where # is the host number) Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com> Signed-off-by: Eric Moore <Eric.moore@lsi.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'lib/locking-selftest-rlock-hardirq.h')
0 files changed, 0 insertions, 0 deletions