| commit | c1819379d12c286c8f17175f76e970d14c73d480 | [log] [tgz] |
|---|---|---|
| author | Bonnie Lo <Bonnie_Lo@wiwynn.com> | Thu Oct 27 17:14:55 2022 +0800 |
| committer | Bonnie Lo <Bonnie_Lo@wiwynn.com> | Tue Nov 01 09:00:46 2022 +0800 |
| tree | 3e91a9ac26f6a4f8081dc0acfedabb43a2318468 | |
| parent | a27519e987a8341585e50913930862825c48cd26 [diff] |
Max post code file size per cycle setting Let user could set POST code file size per cycle The default size is 512 counts Reason: BMC may crash caused by nonstop saving POST code when BIOS has some unusual behavior like PXE loop Thus, BMC should set a limit size to prevent this risk Test Case: Manually send POST code to check the POST code file rotation Signed-off-by: Bonnie Lo <Bonnie_Lo@wiwynn.com> Change-Id: Ic7fbafe532a79123e6ae880a8a3506f9c397d933
This phosphor-post-code-manager repository provides an infrastructure to persist the POST codes in BMC filesystem & it also owns the systemd services that are responsible for exposing the BIOS Post Codes to rest of the world via redfish.
To build phosphor-post-code-manager package , do the following steps:
meson <build directory> ninja -C <build directory>
This repository ships xyz.openbmc_project.State.Boot.PostCode.service systemd service along with its template version and a tiny binary that exposes the necessary dbus interfaces & methods to extract the POST codes per boot cycle.
This repository is tightly coupled with phosphor-host-postd OpenBMC respository which is responsible for emitting the dbus signals for every new POST Code.
phosphor-post-code-manager is architected to look for the property changed signals which are being emitted from the service that hosts Value property on xyz.openbmc_project.State.Boot.Raw interface & archive them per boot on the filesystem, so that those can be exposed over redfish