| commit | a40a24cd55b7f9510b0f20bb56a5fbfe701d47ae | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 26 13:15:57 2022 -0500 |
| committer | Andrew Geissler <geissonator@yahoo.com> | Mon Sep 26 13:15:57 2022 -0500 |
| tree | 39b3b51c63d02830cb53aedcccf55238c18bc2a8 | |
| parent | 1af14431aab1193c2ec636989aa7db7ef283c8b7 [diff] |
ensure stop-instructions service stopped during istep IBM systems utilize istep to boot a system in a more manual "debug mode". istep does not utilize the host systemd targets to boot the system, and instead directly communicates with the host firmware to boot the system. This results in the obmc-host-* targets not being run as a part of the boot, which results in op-stop-instructions@.service.in not getting it's "Conflicts" operation to run. This means after an istep boot, the op-stop-instruction@.service has not properly stopped, which results in it not properly running during the power off of the next boot. Because op-stop-instruction@.service is now responsible for stopping the attn handler, this is not a good situation. istep boots however do still utilize the obmc-chassis-poweron@.target to power the system on. Add a Conflits for this target to ensure op-stop-instructions@.service is stopped in all scenarios. Leave the Conflits with obmc-host-startmin@.target to ensure the service is still properly stopped on warm reboots. Tested: - Performed an istep boot, and verified during the subsequent power off that op-stop-instructions@0.service was properly run Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I647fae0638468a0c35842d91be8ced2acda59a6b
Contains procedures that interact with the OpenPower nest chipset.
To build this package, do the following steps:
1. meson builddir
2. ninja -C builddir
To build with phal feature:
1. meson builddir -Dphal=enabled -Dopenfsi=enabled
2. ninja -C builddir
To clean the repository run `ninja -C builddir/ clean`.