| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
If no one else has started this synchronization target before this
service starts then it will run without waiting since there is no Wants
clause. Add the Wants clause to ensure proper synchronization occurs.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I5db6a5800d5456efd97d0f8c2eabd9113d725370
|
|
The removal of these files was moved into the phosphor-state-manager
applications. This is the final commit in that series:
https://github.com/openbmc/phosphor-state-manager/commit/4a4c1a69432dd88a4204e7a15a838aae75ae1d12
Clearing them on the power off paths in this service file caused
complexity with other paths like BMC resets with the host up and
warm reboots.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I33997107a315f888280932fafda1d75d57ba50af
|
|
Recently saw an issue where a system was doing an mpreboot but hit a
processor checkstop as soon as the reboot of the host started. This
caused a full power cycle of the chassis and a normal reboot of the
system. In this scenario, the /run/openbmc/mpreboot@0 file was not
cleared so the normal boot of the system went very haywire as certain
required services do not start when this file is present.
Currently this file is only cleared once we get to the
op-continue-mpreboot@.service. In the scenario listed above, we never
make it to that service, hence the file is never cleared.
This commit ensure anytime the system is having chassis power removed,
the mpreboot file gets cleared.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I9ec2507d56f8d31b034d18ae03f3867e08d1f152
|
|
Currently the op-wait-power-on service is started before power is
actually turned on. Ensure this service does not start until the
obmc-power-on-pre@.target completes.
The bootblock logic prevents the obmc-power-on-pre@.target from
completing when a blocking error or code update is occurring. Without
the fix in this commit, the system will not power on but this service
will fail because it is incorrectly started as a part of the
obmc-power-on-pre@.target.
(From meta-phosphor rev: 7773d935f6bb7680bb92212d0a58cebb097affd1)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib2e339bb93af15ffddacb85d77db7ce22c8a5da1
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This service already has a Before=obmc-power-start@.target which itself
runs before obmc-power-on@.target.
(From meta-phosphor rev: 84de9636c93b8b42f0120c8573586b4829b7600d)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ia51a8030cf7f97b9f9090fa1ec5c7266d8014382
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
A number of corequisites exist so squashing these all into one patch.
meta-ingrasys - refresh master bc513127f4..67bcaf389f
meta-hxt - refresh master 86a4df514f..8fe0d38bbb
meta-phosphor - refresh master 06c09d7cce..df6ddae3d2
meta-quanta - refresh master 4f126361a1..53f3025271
Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The GPIOs have moved out of the system manager's D-Bus object
and the skeleton apps have been updated to get the information
from json
(ref: openbmc/skeleton 0f3fd5aa2d41a1b1bde5df471db74519ec82ef35).
Remove the dependency out of the service files since it's not
needed anymore.
Tested: Verified there were no errors when removing the system
manager app.
(From meta-phosphor rev: 84bd534fb02c6dc5b4cad8a83b5402946c6cb094)
Change-Id: I4cab0ce2f2a93857e9dee0a1b363e859a52108e7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|
