commit | 3e8f295821993f04bb03f3ef62195519b223a09b | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 18 13:29:30 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Jan 18 21:06:37 2022 +0000 |
tree | f14e7bfbab41cdf0c8d8b9104db361e369079996 | |
parent | a4134770850077cbe7171b8852a1fa1b3c1c6525 [diff] |
fixed unit path in RasDataParser::parseBus() This function was not properly converting the unit name into the device tree path as designed. This will result in an exception thrown by pdbg because we are using an unsupported device tree path. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I966abb043988866ef22cc5dd85ee1b55c9a07d3b
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