Hi Bills,

I have added the case psPowerOKDeAssert to powerStateCheckForWarmReset, in addition to avoiding the loss of DC power, it can also prevent the inconsistency between the power state in the log and the actual power state after a soft shutdown without the SIO_S5 GPIO monitoring.

Currently in review here:
https://gerrit.openbmc-project.xyz/c/openbmc/x86-power-control/+/27607

Regards,
P.K.

On Nov 27, 2019, at 15:09, P. K. Lee (李柏寬) <P.K.Lee@quantatw.com<mailto:P.K.Lee@quantatw.com>> wrote:

Hi Bills,

Sorry I found that I said the wrong event, not the powerButtonPressed event, but the soft shutdown.

In the absence of SIO_S5 monitoring, when there was no case of postCompleteDeAssert in the state of powerStateOn, the beep function will be called because the soft shutdown in the OS and it was switched to psPowerOKDeAssert.

Now the soft shutdown in the OS will switch to postCompleteDeAssert but it will trigger a soft reset, and finally the host shutdown and the power state is on.

Regards,
P.K.

On Nov 27, 2019, at 11:46, P. K. Lee (李柏寬) <P.K.Lee@quantatw.com<mailto:P.K.Lee@quantatw.com>> wrote:

Hi Bills,

I observed that the beep sound was triggered by receiving the psPpowerOKDeAssert event in the state of powerStateOn,
but my machine does not have the SIO_S5 GPIO events, so I need to add a judgment when a beep sound is needed.

The question is, is the forced shutdown (pressing the power button for more than 4 seconds) included in "DC power is unexpectedly lost" mentioned in the comment?

Thanks,
P.K.