From: Corey Minyard <minyard@acm.org>
To: Kunkun Li <likunkun@bytedance.com>
Cc: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipmi: ssif: Add msleep in multipart test
Date: Tue, 26 Oct 2021 11:50:09 -0500 [thread overview]
Message-ID: <20211026165009.GD2744412@minyard.net> (raw)
In-Reply-To: <20211026025834.82766-1-likunkun@bytedance.com>
On Tue, Oct 26, 2021 at 10:58:34AM +0800, Kunkun Li wrote:
> During multipart test, cmd(6,7,8) or cmd(6,7,7) will
> be sent continuously.
This is not useful information, we don't have access to your tests, so
this is meaningless to us.
>
> The pressure test found some BMC systems cannot process
> messages in time, resulting in read_response continues to receive
> error messages from i2c.
> Retry mechanism will takes 10s, and finally set not support
> multipart transmit.
>
> So, to work around this,add msleep after sending cmd 6 and
> cmd 7 respectively. The problem did not appear again in
> pressure test.
No, you can't slow down everyone because you have one dodgy BMC. You
need to detect that this is a BMC that has the problem and only do it
for those BMCs.
-corey
>
> Signed-off-by: Kunkun Li <likunkun@bytedance.com>
> ---
> drivers/char/ipmi/ipmi_ssif.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/char/ipmi/ipmi_ssif.c b/drivers/char/ipmi/ipmi_ssif.c
> index 20d5af92966d..65841798fafe 100644
> --- a/drivers/char/ipmi/ipmi_ssif.c
> +++ b/drivers/char/ipmi/ipmi_ssif.c
> @@ -1453,6 +1453,7 @@ static int start_multipart_test(struct i2c_client *client,
> ret = i2c_smbus_write_block_data(client,
> SSIF_IPMI_MULTI_PART_REQUEST_START,
> 32, msg);
> + msleep(SSIF_MSG_MSEC);
> if (ret) {
> retry_cnt--;
> if (retry_cnt > 0)
> @@ -1467,6 +1468,7 @@ static int start_multipart_test(struct i2c_client *client,
> ret = i2c_smbus_write_block_data(client,
> SSIF_IPMI_MULTI_PART_REQUEST_MIDDLE,
> 32, msg + 32);
> + msleep(SSIF_MSG_MSEC);
> if (ret) {
> dev_err(&client->dev, "Could not write multi-part middle, though the BMC said it could handle it. Just limit sends to one part.\n");
> return ret;
> --
> 2.11.0
>
next prev parent reply other threads:[~2021-10-26 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:58 [PATCH] ipmi: ssif: Add msleep in multipart test Kunkun Li
2021-10-26 16:50 ` Corey Minyard [this message]
2021-10-26 20:48 ` [Openipmi-developer] " Corey Minyard
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=20211026165009.GD2744412@minyard.net \
--to=minyard@acm.org \
--cc=likunkun@bytedance.com \
--cc=linux-kernel@vger.kernel.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