| commit | 9a967ec383a6f0d0a7e3d7a61d48b35c8aaf8f1c | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Mon Jun 22 15:14:30 2020 -0500 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Jun 25 19:38:40 2020 +0000 |
| tree | 35358a8a22166b604fe43662354dea31761d6799 | |
| parent | fdc02f7c022f8ea5a8143310562b79aefe2d9522 [diff] |
clear host volatile section on chassis poweron When using istep to boot a openpower based system, the flow is to issue a "obmcutil chassison" and then boot the system using the istep tool. istep does not use the host-start targets so therefore the host volatile data is not cleared. To ensure the data is always cleared, add the services to the chassis-poweron target. The services need to remain within the host start targets to handle warm reboot scenarios. A normal "obmcutil poweron" will run both the host and chassis targets but due to them being started at the same time (and letting systemd figure out the ordering), the volatiles services will each only be run once so there is no extra execution due to this commit. If a user were to just issue a "obmcutil chassison" and then follow that with a "obmcutil poweron" then the services would be run a second time. This scenario is a debug only type situation and the extra second to re-run the services would have very minimal impact. There is a desire to move services from requires to wants relationships. That was not done here because of the undefined behavior seen by the host when this data is not cleared. The required behaviors is to fail the power on or host start if these services fail. Tested: - Verified services were in obmc-chassis-poweron@0.target.requires - Verified services were run as expected issuing a chassison - Verified boot of system worked as expected and services were only executed once during "obmcutil poweron" Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I1f51be27d5b9e22f9395a53c537a03133457718b
This layer provides support for the BMC firmware on OpenPOWER reference platforms, and/or a base upon which to create a BMC firmware implementation on any POWER system.
This layer depends on: URI: git://git.openembedded.org/openembedded-core layers: meta branch: master revision: HEAD URI: https://github.com/openbmc/meta-phosphor branch: master revision: HEAD URI: https://github.com/openbmc/meta-aspeed branch: master revision: HEAD
More information on OpenPOWER can be found here.
meta-openpower patches are reviewed using the Gerrit instance at https://gerrit.openbmc-project.xyz.
Please submit patches to Gerrit. More information on using Gerrit can be found here. https://github.com/openbmc/meta-openpower is a hosting mirror only and GitHub pull requests are not monitored and will not be accepted.
Patch checklist. Please ensure patches adhere to the following guidelines:
For questions or help please come join us on the mailing list or in IRC.