From: Andrew Geissler <geissonator@gmail.com>
To: "Matuszczak, Piotr" <piotr.matuszczak@intel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Critical BMC process failure recovery
Date: Tue, 27 Oct 2020 16:57:36 -0500 [thread overview]
Message-ID: <B24BCA12-F3B1-4DFF-B839-2184D34D0F73@gmail.com> (raw)
In-Reply-To: <CY4PR1101MB2311ABDFBA0EA222BB602B7686190@CY4PR1101MB2311.namprd11.prod.outlook.com>
> On Oct 26, 2020, at 8:19 AM, Matuszczak, Piotr <piotr.matuszczak@intel.com> wrote:
>
> Hi, It's quite interesting discussion. Have you considered some kind of minimal set of features recovery image, to which BMC can switch after N resets during defined amount of time? Such image could hold error log and send periodic event about BMC failure.
That could definitely be useful. Some sort of safe mode. I believe systemd
has rescue/emergency mode options we could look at. I do think as Patrick
pointed out earlier though that most issues are some sort of BMC hardware
failure. Anything that needs the kernel running and even basic services going
is going to be difficult to get running in those scenarios.
>
> Piotr Matuszczak
> ---------------------------------------------------------------------
> Intel Technology Poland sp. z o.o.
> ul. Slowackiego 173, 80-298 Gdansk
> KRS 101882
> NIP 957-07-52-316
>
next prev parent reply other threads:[~2020-10-27 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 19:53 Critical BMC process failure recovery Andrew Geissler
2020-10-19 21:35 ` Neil Bradley
2020-10-22 15:41 ` Andrew Geissler
2020-10-20 2:58 ` Lei Yu
2020-10-20 18:30 ` Bills, Jason M
2020-10-20 14:28 ` Patrick Williams
2020-10-22 16:00 ` Andrew Geissler
2020-10-26 13:19 ` Matuszczak, Piotr
2020-10-27 21:57 ` Andrew Geissler [this message]
2021-09-02 0:29 ` Andrew Geissler
2022-02-21 20:54 ` Andrew Geissler
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=B24BCA12-F3B1-4DFF-B839-2184D34D0F73@gmail.com \
--to=geissonator@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=piotr.matuszczak@intel.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;
as well as URLs for NNTP newsgroup(s).