commit | 063f6bdc3957d65e127a4616a3d04c9f054c0e5f | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Mar 26 07:45:56 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Mar 26 16:23:03 2021 +0000 |
tree | 4ca50818dfe641885a65e3ad3ffbd1700a14bb54 | |
parent | 3a85108f9fdf27ca1e7e70469d4c327e0b19a00c [diff] |
Attn: Submit event logs before transitioning host For terminating events we will generate and submit the events logs before we request to transition the host. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ie600bbdbb34eb18154ea080fe1ac7d1861691e04
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