commit | 7d06930a42ac54ee981ede74bd710ed1e02ec43b | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Thu Nov 09 13:25:31 2023 -0600 |
committer | Andrew Geissler <geissonator@yahoo.com> | Thu Nov 09 13:42:51 2023 -0600 |
tree | b778cd3b1210f745c849075e7ff77d1ac35f04d7 | |
parent | e70edac3aaf8528de0b75215fc613b16ce4c8b48 [diff] |
ramoops: generate error log when ramoops detected A ramoops being detected is a critical event for a BMC based system. It indicates the BMC had an unexpected reboot because of a kernel panic. Ensure a log is reported so the user of the system knows to look for a BMC dump with the debug information. Tested: - Manually created some files in /var/lib/systemd/pstore/ and ran the ramoops application and verified the expected log was created. Change-Id: Id1162fa0cca72e5dcc8cf59e75bd298d2ddada2e Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Phosphor Debug Collector provides mechanisms to collect various log files and system parameters. Used to troubleshoot problems in OpenBMC based systems.
One such mechanism is dreport, a script that collects debug data and packages it into an archive file.
To build this package with meson, do the following steps:
1. meson builddir 2. ninja -C builddir
To clean the built files run ninja -C builddir clean
.
Tests can be run in the CI docker container, refer local-ci-build
or with an OpenBMC x86 sdk(see below for x86 steps).
meson -Dtests=enabled build ninja -C build test