[x86-power-control]: press the power button for a long time that can't force turn off system power
Bills, Jason M
jason.m.bills at linux.intel.com
Sat Jul 24 06:36:52 AEST 2021
On 7/23/2021 4:28 AM, Chris Chen (TPI) wrote:
> Hi all,
> I am working on an ast2600 with Intel CPU.
> The system power currently is able to turn on during Phosphor OpenBMC
> boot up after I completed works following:
> 1. enable ACPI in u-boot
> 2. set GPIOP0 ~ P3 pass-through in u-boot
> 3. porting ESPI driver from AST SDK v6.01 to linux-aspeed repository
> 4. add "&gpio0" with gpio-line-names which has POWER_BUTTON, POWER_OUT,
> SIO_S3, SIO_S5, etc. defintion in the dts, I think the
> "x86-power-control" repository required these.
> 5. append "x86-power-control" and "intel-ipmi-oem" repositories to image
> However, I always only got the following logs when I pressed the power
> button for a long time (> 4s).
> power-control: PowerControl: power button pressed
> power-control: powerStateOn: power button pressed event received
> power-control: Host0: Moving to "Graceful Transition to Off" state
> power-control: Graceful power-off timer started
> It doesn't occur "SIO_ONCONTROL value changed: 1 -> SIO power good
> de-assert event received", etc. operations and then to turn off the power.
> Can anyone do me a favor to give me some clues for what I was wrong?
Holding the power button should force a hardware shutdown. The BMC only
monitors this flow and doesn't participate.
Did your system shut down correctly and you just not see the logs in
BMC? Or, did the system stay on?
> Thank you in advance for your help.
> Chris Chen
> Legal Disclaimer :
> The information contained in this message may be privileged and
> It is intended to be read only by the individual or entity to whom it is
> or by their designee. If the reader of this message is not the intended
> you are on notice that any distribution of this message, in any form,
> is strictly prohibited. If you have received this message in error,
> please immediately notify the sender and delete or destroy any copy of
> this message!
More information about the openbmc