commit | 5ec757bfe4d474817304623d0b489e9302f22182 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Feb 09 07:04:58 2021 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Wed Feb 10 04:36:23 2021 +0000 |
tree | 17a441253c9b61e438312acf7426b004e66b684a | |
parent | 29651ef86a9826108393694ddf3484e9665a9104 [diff] |
Attn: Cleanup trace messages 2 Replaced some uses of stringstream with std::string Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I15118d47b8a9ad16dad96494136cbae9b08a6f43
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