From: Matthew Garrett <mjg@redhat.com>
To: minyard@acm.org
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gcase@redhat.com
Subject: Re: [PATCH] ipmi: Increase KCS timeouts
Date: Wed, 14 Dec 2011 21:12:28 +0000 [thread overview]
Message-ID: <20111214211228.GA28019@srcf.ucam.org> (raw)
In-Reply-To: <1322680347-25743-1-git-send-email-mjg@redhat.com>
Ping?
On Wed, Nov 30, 2011 at 02:12:27PM -0500, Matthew Garrett wrote:
> We currently time out and retry KCS transactions after 1 second of waiting
> for IBF or OBF. This appears to be too short for some hardware. The IPMI
> spec says "All system software wait loops should include error timeouts. For
> simplicity, such timeouts are not shown explicitly in the flow diagrams. A
> five-second timeout or greater is recommended". Change the timeout to five
> seconds to satisfy the slow hardware.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
> ---
> drivers/char/ipmi/ipmi_kcs_sm.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/ipmi/ipmi_kcs_sm.c b/drivers/char/ipmi/ipmi_kcs_sm.c
> index cf82fed..e53fc24 100644
> --- a/drivers/char/ipmi/ipmi_kcs_sm.c
> +++ b/drivers/char/ipmi/ipmi_kcs_sm.c
> @@ -118,8 +118,8 @@ enum kcs_states {
> #define MAX_KCS_WRITE_SIZE IPMI_MAX_MSG_LENGTH
>
> /* Timeouts in microseconds. */
> -#define IBF_RETRY_TIMEOUT 1000000
> -#define OBF_RETRY_TIMEOUT 1000000
> +#define IBF_RETRY_TIMEOUT 5000000
> +#define OBF_RETRY_TIMEOUT 5000000
> #define MAX_ERROR_RETRIES 10
> #define ERROR0_OBF_WAIT_JIFFIES (2*HZ)
>
> --
> 1.7.7.1
>
>
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-12-14 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 19:12 Matthew Garrett
2011-12-14 21:12 ` Matthew Garrett [this message]
2011-12-15 14:35 ` Corey Minyard
2011-12-15 14:45 ` Matthew Garrett
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=20111214211228.GA28019@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=gcase@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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