| commit | 75230ff2751e88d594a13a70eae2c146f45e323b | |
| author | Stephen M. Cameron <scameron@beardog.cce.hp.com> | |
| Mon, 23 Aug 2010 09:02:17 +0000 (23 11:02 +0200) | ||
| committer | Jens Axboe <jaxboe@fusionio.com> | |
| Mon, 23 Aug 2010 09:02:17 +0000 (23 11:02 +0200) | ||
| tree | 62585cb59ef59e9ec99a3ab7de97cb661b1d0adb | treesnapshot (tar.gz zip) |
| parent | 96aa1b419d47286db446f292cf898bb1a8b27f24 | commitdiff |
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>
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>
| drivers/block/cciss.c | diffblobblamehistory |