commit | 6e36587a1f6838d594c7df8382636b71a6044032 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Oct 23 22:00:05 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Oct 23 22:00:05 2020 -0500 |
tree | b2da422d5aa2266f48cb38bb7cc9303e8b873c3b | |
parent | e4f5dbef747fb2a95768ba4fcf6286f559056bd7 [diff] |
Copied FFDCFile and supporting code from phosphor-power Change-Id: Ife659c941c70f66edcb531df2e0d4da8bf158b06
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