commit | 35171d900255ab799dfb18290d7da39f8e0ff1e4 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 03 13:31:13 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 09 02:33:06 2020 +0000 |
tree | 7e15860c55ceb0c945b8ef095f05cb2a6d57b41a | |
parent | 5183af300eca2e241c7d9bea10f4c0ee102838b9 [diff] |
Get chip ID/EC from hardware if not synced in attributes Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I988fd16c1514d9fe2058f8becdfcf3a39abf8b85
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