| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
By default phosphor-reboot-host@.service sleeps for 5 seconds between
power off and power on.
Make the sleep time as configurable parameter in environment, so
different machines could use different sleep time.
Tested: Verify the sleep time is from the config file.
Change-Id: I81d17e56010fe595dd46295923746f8678678209
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
On startup, the service attempts to read the PGOOD property
to know if the system is already on. For that to work, the
org.openbmc.Control.Power service must already be running,
so ensure that is the case.
Having this check working right allows the code to know if
there was an AC loss while booted.
Resolves openbmc/openbmc#3266
Tested: Check that the service knows power is on when rebooted
at runtime.
Change-Id: I1314865609ecdf3765603f8bd8ed1add6888e558
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
This TODO was properly addressed but the comment
was not deleted
Part-of openbmc/openbmc#2207
Change-Id: I410e2a95707c1c14c3d0699af00c7dcb874cef23
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The dependency on the legacy system service is obsolete and so it
is removed. The dependency on the mapper is added.
Change-Id: I6afd2020f73829df7c5a53342087a3051939928d
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
|
|
The host reboot attempts counter is used to ensure
the host is only allowed a certain amount of retries to
boot for any given boot request. The count should be reset,
and the host should be given it's full amount of tries, on
any fresh boot request.
This commit puts a service into the host-start target which
is only called on a fresh boot request.
Tested: Verified this new service is run on fresh boot requests
and is not run on host reboot requests.
Resolves openbmc/openbmc#3035
Change-Id: I4be327e57d6f835b19e47272ceaad796196b68c5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Requirements have arisen for OpenBMC firmware to run
certain services only during fresh power on operations.
To achieve that, break the obmc-host-start action target into
two targets. The existing obmc-host-start target will now
call the new obmc-host-startmin target. The startmin target
will be the minimum services required to start the host.
The obmc-host-start target is where services that should
only be called during a fresh power on can be placed.
The initial use case for this is the obmc-host-reboot target.
It will call this new obmc-host-startmin target to do the bare
minimum on a reboot operation.
This then allows the use case for OpenBMC to only reset the host
reboot count on a fresh power on operation. A new service will
be added to the obmc-host-start target to do this. If a reboot
operation is issued, or a host watchdog is triggered to cause a
reboot, this service would not be started, ensuring the reboot
count is properly decremented.
Tested: Verified on/off/reboot and ran CT regression suite.
https://gerrit.openbmc-project.xyz/#/c/9821/ is required
for reboots to work properly.
Change-Id: I86df03e6d671178c1525f852e196c4102bb73cb6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Reset boot progress and OS status sensors if host is not
running
Resolves openbmc/openbmc#2804
Change-Id: I1fee2bf7776ae957e87452d9cfa7a4fca647b46f
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
|
All the fan services associated with controlling, monitoring and
presence detection of fans need to remain active until a poweroff
completes. This helps ensure thermal safety while a system is in
transition to a powered off state.
With the introduction of this new target (which runs last in
the power off path), need to move the host reset service to
running after it to ensure the power on in the reboot path
does not start until the last power off target runs.
Resolves openbmc/openbmc#2762
Change-Id: I4ca671d2c7de66e8bfa4bba607b06c88c0a6e7f9
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
If the BMC was rebooted while the chassis power was on
then we want the BMC to update it's targets to reflect
this and leave the system as-is. This also applies if
the host is running.
Resolves openbmc/openbmc#2180
Change-Id: Ib9c067d79368db749fd65d050132d15ad793fdbf
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This commit enables patches from the /usr/local path by replacing
absolute paths to /usr/sbin or /usr/bin in every service file with
"/usr/bin/env ". Additionally, SyslogIdentifier is added to each
file to ensure that journal entries are still distinct.
In two cases, service files also had to change due to references
to ${{PATH}}, which doesn't work with /usr/bin/env. These
references - and the corresponding definitions - were changed to
${{DEVPATH}}.
Resolves openbmc/openbmc#2149
Change-Id: I12c5c6e5101eef6820b985a563313836250ff2c7
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
When a BMC reboot occurs with the host running, need
to ensure the reset targets and services run before
we start other application that depend on whether
the host is running
Specifically, don't start phosphor-host-state-manager until
it's been determined if the host is up. Don't start
phosphor-discover-system-state until the state of the
chassis is known.
Change-Id: I458fa78802cd9ecca99c54834512bfebf04b5012
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
The state management code on the BMC is designed to
utilize systemd targets as much as possible. The host
reboot was always the odd duck that had some special
code written to support it. This special code would
basically issue a power off, look for it to complete
and then issue a power on. This is very error prone
code and has resulted in a few issues.
Moving to a single systemd target (the new reboot target)
defined here will allow the host reboots to occur
solely through a single systemd target now.
openbmc/openbmc#2032 is one of those bugs being
addressed with this change.
Change-Id: If33454aa4f15580e45f888a9b1602dec24a46fca
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Change-Id: I0e7e84f191f6a466b0f84c6d4f490816331f141f
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
|
|
The obmc-host-stop@.target will always be called on host shutdowns
but the inverse is not always true. This commit ensures everything
conflicts with the target that is always called in this path.
Change-Id: Ic680ef96b1d6e2aec844a9c619928b7014fe7450
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This application and services will be used by the host reset service
to determine if the host is running after a BMC has been rebooted
Change-Id: I8299546b0f275ebbb46aa775ab7b0633cc3fd5e0
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This recipe will add the new program phosphor-discover-system-state
to new builds. Additionally, the old Python state manager is
removed from the build since discover_system_state.py was the last
thing in it.
Resolves openbmc/openbmc#773
Change-Id: I99ba0f1f0264cedebc5a9a7e5fa5dbaba0b79502
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
Change-Id: I4c013d98e03703b1328d85ae00cebb8500ffa205
Signed-off-by: Josh King <jdking@us.ibm.com>
|
|
The phosphor-state-manager repository builds [at least] two executables:
* phosphor-host-state-manager
* phosphor-chassis-state-manager
phosphor-host-state-manager.bb and phosphor-chassis-state-manager.bb
were effectively the exact same file and had no assignment of
executables to files. The result was that both packages installed both
daemons and caused an installation collision.
Combine the two recipes into a single recipe with the correct package
relationship for each executable.
Change-Id: I76a1e598bebc5090ae374271bbd5e8e32967cb43
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
