commit | 276e9813915d608358422e12109faf5dabdbe0d0 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Sep 02 10:48:20 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Sep 02 16:33:19 2021 +0000 |
tree | 170dfd02c48e7b3e0ed899c7434e110e4beb6a86 | |
parent | 2d114321d95e6d49ee152df3a941d0662bd44315 [diff] |
Fix for setting PDBG_DTB environment variable The code for setting PDBG_DTB environment variable conditionally in the service file was not working correctly which resulted in the environment variable not getting set. This was fixed. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: If4f3b97166541b1b3755efc63006371df70a98d5
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