commit | 6764d70eea47a83adc98c1266dd2f7eb5b7456c8 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 12 09:17:23 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 22 16:50:28 2021 +0000 |
tree | 86c7c5ccb27c57deedf7090725b560834370980d | |
parent | 4ed4be5645dbadbe6c251012485a71a75ec9ae82 [diff] |
Attn: Limit trace length messages Limit trace length messages specifically for exception messages which tend to be long. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I50360121541c92b732ffe4502c5084497ebb0357
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