commit | fe2757b0883a17d87561ecfc44d5c3a692f1373d | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Jan 14 13:17:50 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Jan 14 21:06:11 2021 +0000 |
tree | d1974a6ad3f95f5914b2bff4950a377c668eea41 | |
parent | a79f6c8fa6bc8fec117f64d14ae7f62fc8b0d48b [diff] |
Attn: Change mpipl target to crash@0 target To start MPIPL we need to start obmc-host-crash@0.target (changed from obmc-host-diagnostic-mode@0.target). Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I41294357a3f08ea41b320a3b892045f6f0c81f78
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