From: Matt Fleming <matt@readmodwrite.com>
To: Corey Minyard <corey@minyard.net>
Cc: Matt Fleming <mfleming@cloudflare.com>,
openipmi-developer@lists.sourceforge.net,
Tony Camuso <tcamuso@redhat.com>,
linux-kernel@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH 0/1] ipmi: Fix issues with BMCs that report event and message incorrectly
Date: Tue, 21 Apr 2026 23:24:17 +0100 [thread overview]
Message-ID: <aef4rrkhL4xFmh3h@matt-Precision-5490> (raw)
In-Reply-To: <20260421132544.2666174-1-corey@minyard.net>
On Tue, Apr 21, 2026 at 07:42:42AM -0500, Corey Minyard wrote:
> Matt reported that there were issues with the IPMI driver getting wedged
> in some cases. It turns out that the BMC was not reporting an error as
> it should have (per the spec) when the event queue was empty. The IPMI
> driver would then request the next event, and so on, wedging the driver.
Thanks for replying so quickly, Corey. I'll test these out.
One bit of info I pulled out of the stuck machine is that the response
looks properly formed.
I sampled the first 8 entries and they were all identical 19-byte
successful READ_EVENT_MSG_BUFFER responses:
1c 35 00 55 55 c0 41 a7 00 00 00 00 00 3a ff 00 ff ff ff
So on this machine, the event replies do not look short or malformed;
they look like repeated successful event-buffer reads with the same
payload.
Thanks,
Matt
next prev parent reply other threads:[~2026-04-21 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 12:42 [PATCH 0/1] ipmi: Fix issues with BMCs that report event and message incorrectly Corey Minyard
2026-04-21 12:42 ` [PATCH 1/2] ipmi: Check event message buffer response for bad data Corey Minyard
2026-04-21 12:42 ` [PATCH 2/2] ipmi: Add limits to event and receive message requests Corey Minyard
2026-04-25 9:36 ` Matt Fleming
2026-04-25 23:58 ` Corey Minyard
2026-04-28 10:15 ` Matt Fleming
2026-04-28 11:45 ` Corey Minyard
2026-04-28 13:06 ` Corey Minyard
2026-04-21 22:24 ` Matt Fleming [this message]
2026-04-22 4:44 ` [Openipmi-developer] [PATCH 0/1] ipmi: Fix issues with BMCs that report event and message incorrectly Jian Zhang
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=aef4rrkhL4xFmh3h@matt-Precision-5490 \
--to=matt@readmodwrite.com \
--cc=corey@minyard.net \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfleming@cloudflare.com \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=tcamuso@redhat.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