commit | 4ed4be5645dbadbe6c251012485a71a75ec9ae82 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 15 17:53:40 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 18 17:20:44 2021 +0000 |
tree | 01dd45fb8009213025d56cec00acf5bec5ef9ca2 | |
parent | 64791cf708574e48182a69e35f39afb40351b1ba [diff] |
Add ServiceData callout list to PEL Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I03b96f48d211c6dc057acc760a0b0eda2ea8fc42
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test