commit | 60cb2e4277759661f9054d263cc877dc7fa406ed | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Feb 28 16:21:55 2024 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 20 14:44:09 2024 +0000 |
tree | 05eedac734daa36cb4104a3e0e4497c4328b4ee1 | |
parent | 710101c03fee69d998e3596cc02574ee495d19ad [diff] |
Add level 2 callout to TI logs Hostboot requested this just in case any of their log fail to produce a hidden SRC. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ifc7dc862b3f612cfc25d339bf09b40a691c1b464
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