From: Shyam Iyer <shyam_iyer@dell.com>
To: linux-scsi@vger.kernel.org
Cc: DL-MPTFusionLinux@lsi.com
Subject: [PATCH] Wait for 15s on doorbell ACK before checking IOC READY state
Date: Tue, 13 Jul 2010 13:04:07 -0400 [thread overview]
Message-ID: <4C3C9C87.9050904@dell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
Wait for 15 seconds for Doorbell ACK.
Not waiting 15s results in a few resets and kernel panics.
https://bugzilla.redhat.com/show_bug.cgi?id=594505
This is also logical since we wait for 15 seconds to compare if the
state really changed.
Signed-off-by: Shyam Iyer<shyam_iyer@dell.com>
[-- Attachment #2: 0001-Wait-for-15s-on-doorbell-ACK-before-checking-IOC-REA.patch --]
[-- Type: text/plain, Size: 1217 bytes --]
>From a2cfe7cad6c22849d3561a5466760917c1d3b02a Mon Sep 17 00:00:00 2001
From: Shyam Iyer <shyam_iyer@dell.com>
Date: Thu, 8 Jul 2010 15:47:53 -0400
Subject: [PATCH] Wait for 15s on doorbell ACK before checking IOC READY state
Not waiting 15s results in a few resets and kernel panics.
https://bugzilla.redhat.com/show_bug.cgi?id=594505
This is also logical since we wait for 15 seconds to compare if the state really changed.
Signed-off-by: Shyam Iyer <shyam_iyer@dell.com>
---
drivers/message/fusion/mptbase.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/message/fusion/mptbase.c b/drivers/message/fusion/mptbase.c
index a6a5701..e658a53 100644
--- a/drivers/message/fusion/mptbase.c
+++ b/drivers/message/fusion/mptbase.c
@@ -4208,7 +4208,7 @@ SendIocReset(MPT_ADAPTER *ioc, u8 reset_type, int sleepFlag)
drsprintk(ioc, printk(MYIOC_s_DEBUG_FMT "Sending IOC reset(0x%02x)!\n",
ioc->name, reset_type));
CHIPREG_WRITE32(&ioc->chip->Doorbell, reset_type<<MPI_DOORBELL_FUNCTION_SHIFT);
- if ((r = WaitForDoorbellAck(ioc, 5, sleepFlag)) < 0)
+ if ((r = WaitForDoorbellAck(ioc, 15, sleepFlag)) < 0)
return r;
/* FW ACK'd request, wait for READY state
--
1.6.6.1
reply other threads:[~2010-07-13 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3C9C87.9050904@dell.com \
--to=shyam_iyer@dell.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.