aboutsummaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorStephen M. Cameron <scameron@beardog.cce.hp.com>2010-08-23 11:02:17 +0200
committerJens Axboe <jaxboe@fusionio.com>2010-08-23 11:02:17 +0200
commit75230ff2751e88d594a13a70eae2c146f45e323b (patch)
tree62585cb59ef59e9ec99a3ab7de97cb661b1d0adb /block
parent96aa1b419d47286db446f292cf898bb1a8b27f24 (diff)
downloadmrst-s0i3-test-75230ff2751e88d594a13a70eae2c146f45e323b.tar.gz
mrst-s0i3-test-75230ff2751e88d594a13a70eae2c146f45e323b.tar.xz
mrst-s0i3-test-75230ff2751e88d594a13a70eae2c146f45e323b.zip
cciss: 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: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions