aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/constants.c
diff options
context:
space:
mode:
authorStephen M. Cameron <scameron@beardog.cce.hp.com>2010-08-25 10:44:14 -0500
committerJames Bottomley <James.Bottomley@suse.de>2010-09-02 17:14:44 -0300
commit36ed2176fedaa180b8ea3cdacf68c958e0090a3c (patch)
tree532aae564cb7eae0d737f5101e47a3d605db71f5 /drivers/scsi/constants.c
parentb15d05b0d358cedf9c4d420a60d2ee2d0f530788 (diff)
downloadkernel_samsung_smdk4412-36ed2176fedaa180b8ea3cdacf68c958e0090a3c.zip
kernel_samsung_smdk4412-36ed2176fedaa180b8ea3cdacf68c958e0090a3c.tar.gz
kernel_samsung_smdk4412-36ed2176fedaa180b8ea3cdacf68c958e0090a3c.tar.bz2
[SCSI] hpsa: disable doorbell reset on reset_devices
The doorbell reset initially appears to work correctly, the controller resets, comes up, some i/o can even be done, but on at least some Smart Arrays in some servers, it eventually causes a subsequent controller lockup due to some kind of PCIe error, and kdump can end up leaving the root filesystem in an unbootable state. For this reason, until the problem is fixed, or at least isolated to certain hardware enough to be avoided, the doorbell reset should not be used at all. Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/scsi/constants.c')
0 files changed, 0 insertions, 0 deletions