commit | 535a8d4aaa059e48f9650142e4db3d4ea41ca5db | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Mar 08 18:07:14 2022 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Tue Mar 08 18:07:14 2022 -0600 |
tree | 9e81a55ce835c8471b04c38afc9920e64b40d807 | |
parent | 5d835ec9e80934bb998f85c4f495b16553d3d6bd [diff] |
attn: Fix incorrect trace message formatting Some of the TI info data being traced for logging was incorrectly formatted when trace support was changed to using the util functions. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I289bbed7f61c2f5d34f21e84d6e77a605aad4324
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