Age | Commit message (Collapse) | Author | Files | Lines |
|
Kudo uses GPIO for checking the host status and does not use IPMI
SMS. Therefore, this will remove the host-check feature as some of
the recent recipe changes create stalls between host-state-manager
and IPMI host control. Reference changes made in,
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/45312
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I76b246dd003f94c95f194592647c4291014abf0b
|
|
Instead of a host or chassis restart for a Chassis PowerCycle,
have both the BMC and host perform a hard reset. This requires
changes to phosphor-state-manager to add the handling of
xyz.openbmc_project.State.Chassis.Transition.PowerCycle. Currently,
there is handling for On and Off, but not PowerCycle.
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: I3d934c47a68899b2fd8fcba966f8d92c97554a77
|
|
Summary of changes:
1. Adjust start time of xyz.openbmc_project.State.Chassis.service
to fix initial chassis state
2. Add shutdown ack service
3. Remove reset ack service
4. Remove heartbeat mode
5. Remove sysreset pin control from power_control.exe
6. Remove all phosphor-fan services that caused power off during
a system reset
7. Adjustments to ampere_power_util.sh (See below)
ampere_power_util.sh:
1. Use GPIO instead of dbus for host state
2. Wait 3 seconds before checking power status for power on
3. Wait 6 seconds before checking power status for power off
4. Have force_off act GPIO while power_off sets Chassis state
5. Graceful shutdown acts GPIO
6. Check host status before issuing system reset
7. Set Watchdog Expire Action to None before power off and reset
Signed-off-by: Charles Boyer <Charles.Boyer@fii-usa.com>
Change-Id: Ie2720ee60d489c4160165c6827a78a400ae4d30b
|