diff options
author | Salyzyn, Mark <mark_salyzyn@adaptec.com> | 2007-03-30 10:30:48 -0400 |
---|---|---|
committer | James Bottomley <jejb@mulgrave.il.steeleye.com> | 2007-04-01 12:44:57 -0500 |
commit | 18a6598f2d3bb7275dadba77df5f06bc996a77d4 (patch) | |
tree | d4dc43a9e7a4fd1391782b090d4f5e20c231f6ac /Documentation/scsi | |
parent | aa2e07b4c2addaa4ad4bd7a6ee205565e83c2a14 (diff) | |
download | op-kernel-dev-18a6598f2d3bb7275dadba77df5f06bc996a77d4.zip op-kernel-dev-18a6598f2d3bb7275dadba77df5f06bc996a77d4.tar.gz |
[SCSI] aacraid: [Fastboot] Panics for AACRAID driver during 'insmod' for kexec test.
Attached is the patch I feel will address this issue. As an added
'perk' I have also added the code to detect if the controller was
previously initialized for interrupted operations by ANY operating
system should the reset_devices kernel parameter not be set and we are
dealing with a naïve kexec without the addition of this kernel
parameter. The reset handler is also improved. Related to reset
operations, but not pertinent specifically to this issue, I have also
altered the handling somewhat so that we reset the adapter if we feel
it is taking too long (three minutes) to start up.
We have not unit tested the reset_devices flag propagation to this
driver code, nor have we unit tested the check for the interrupted
operations under the conditions of a naively issued kexec. We are
submitting this modified driver to our Q/A department for integration
testing in our current programs. I would appreciate an ACK to this
patch should it resolve the issue described in this thread...
Signed-off-by: Mark Salyzyn <aacraid@adaptec.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'Documentation/scsi')
0 files changed, 0 insertions, 0 deletions