diff options
| author | Fred Chen <Fred.Chen@quantatw.com> | 2025-08-11 09:10:43 +0300 |
|---|---|---|
| committer | Patrick Williams <patrick@stwcx.xyz> | 2025-08-21 18:20:26 +0300 |
| commit | 2f3c9276612bc3ffcd0d1766cb2149efa73bedb9 (patch) | |
| tree | 3b791c2dd2d9b6e543aefe301babcc94663bfb66 /meta-openembedded/meta-python/recipes-devtools/python/python3-supervisor | |
| parent | 294d3c1028b254d58fe69e9f2ac052cb0c6638b9 (diff) | |
| download | openbmc-2f3c9276612bc3ffcd0d1766cb2149efa73bedb9.tar.xz | |
meta-facebook: santabarbara: Remove chassis-related systemd services
Remove:
- phosphor-reset-chassis-on@.service
- phosphor-reset-chassis-running@.service
- obmc-power-start@.service
- obmc-power-stop@.service
1. These services call mapper-wait@-org-openbmc-control-power* services,
but no corresponding /org/openbmc/control/power1 D-Bus object exists.
Mapper-wait waits indefinitely causing startup hang.
2. On this system PGOOD only indicates chassis standby power good.
phosphor-reset-chassis-running@.service uses PGOOD to create
/run/openbmc/chassis@%i-on, which causes
phosphor-discover-system-state@%i.service to be skipped. We want
discover to always run at BMC boot to evaluate the power-restore policy
and trigger host power-on (always-on).
Removing these services fixes the boot issue.
Change-Id: I87aafd2acf58e2605e010e9aab7ed821387e79d3
Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-supervisor')
0 files changed, 0 insertions, 0 deletions