From: Corey Minyard <minyard@acm.org>
To: linux-kernel@vger.kernel.org, akpm@osdl.org
Cc: Matt_Domsch@dell.com, rocky.craig@hp.com
Subject: [PATCH 7/9] ipmi: bt restart reset fixes
Date: Fri, 21 Oct 2005 09:55:58 -0500 [thread overview]
Message-ID: <20051021145558.GG19532@i2.minyard.local> (raw)
The current BT retry/reset mechanism fails to succeed on a PowerEdge
1650, when the controller is wedged with B2H_ATN asserted at
XACTION_START. If this occurs, no further commands will ever succeed
unless the state of the controller is first cleared out.
Furthermore, the soft reset would only occur if the first command
after insmod was the one that timed out, not if a later command timed out.
This patch changes the retry/reset mechanism to be as follows:
Before retrying a command, clear the state of the BT controller such
that the flags represent ready for a new transaction. This increases
the chance of success of the restarted transaction.
After 2 retries, issue a soft reset and retry one more time before
giving up and reporting back a failure.
Signed-off-by: Matt Domsch <Matt_Domsch@dell.com>
Acked-by: Rocky Craig <rocky.craig@hp.com>
Signed-off-by: Corey Minyard <minyard@acm.org>
Index: linux-2.6.ipmi/drivers/char/ipmi/ipmi_bt_sm.c
===================================================================
--- linux-2.6.ipmi.orig/drivers/char/ipmi/ipmi_bt_sm.c 2005-10-10 12:02:10.%N -0500
+++ linux-2.6.ipmi/drivers/char/ipmi/ipmi_bt_sm.c 2005-10-13 14:35:14.%N -0500
@@ -333,8 +333,7 @@
bt->state = BT_STATE_HOSED;
if (!bt->nonzero_status)
printk(KERN_ERR "IPMI: BT stuck, try power cycle\n");
- else if (bt->seq == FIRST_SEQ + BT_RETRY_LIMIT) {
- /* most likely during insmod */
+ else if (bt->error_retries <= BT_RETRY_LIMIT + 1) {
printk(KERN_DEBUG "IPMI: BT reset (takes 5 secs)\n");
bt->state = BT_STATE_RESET1;
}
@@ -475,6 +474,7 @@
break;
case BT_STATE_RESTART: /* don't reset retries! */
+ reset_flags(bt);
bt->write_data[2] = ++bt->seq;
bt->read_count = 0;
bt->nonzero_status = 0;
reply other threads:[~2005-10-21 14:56 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=20051021145558.GG19532@i2.minyard.local \
--to=minyard@acm.org \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rocky.craig@hp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome