commit | 611b344212fe92f73b74dfe212c9029841549068 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Nov 19 16:02:01 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 07 21:25:46 2021 +0000 |
tree | cf7599d5a9d65ef4b7263ebbdb3640251a259044 | |
parent | a16758b7c34b30083bb403c75d6ddea7841ef1a8 [diff] |
change analyzerHardware() to return PEL PLID is created Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Icee2909e5060c79cb95ead8fc08a5e359df42829
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