openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Chen (TPI)" <Chris.Chen3@flex.com>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: 回覆: [x86-power-control]: press the power button for a long time that can't force turn off system power
Date: Sat, 24 Jul 2021 03:04:29 +0000	[thread overview]
Message-ID: <DM6PR08MB551464D29CE9BD91FFE1B20ADCE69@DM6PR08MB5514.namprd08.prod.outlook.com> (raw)
In-Reply-To: <8fcc9529-0f7b-df46-aa28-1569d254eb20@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 5854 bytes --]

Hi Jason,

Thanks for your prompt reply.

The system stays on, because I can hear the fan in PSU is still running and CPU heatsink is hot, besides, the log would show "Graceful power-off timer completed" and "Host0: Moving to "On" state" after 5 minutes. Here are all logs of the power-control for your reference. Hope this can provide more details.

=====
root@hudsonbay-obmc:~# journalctl | grep -e "power-control" -e "power control" -e "Power Control"
Jul 24 10:36:06 hudsonbay-obmc systemd[1]: Starting Intel Power Control...
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: Start Chassis power control service...
Jul 24 10:36:09 hudsonbay-obmc systemd[1]: Started Intel Power Control.
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: NMI_OUT set to 0
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: POWER_OUT set to 1
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: RESET_OUT set to 1
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: NMI Source Property Monitor
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: Initializing power state.
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: Host0: Moving to "On" state
Jul 24 10:36:09 hudsonbay-obmc power-control[198]: POH timer started
Jul 24 10:36:38 hudsonbay-obmc power-control[198]: powerStateOn: POST Complete assert event received
Jul 24 10:36:38 hudsonbay-obmc power-control[198]: No action taken.
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: powerStateOn: POST Complete de-assert event received
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: Host0: Moving to "Check for Warm Reset" state
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: Warm reset check timer started
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: RestartCause set to xyz.openbmc_project.State.Host.RestartCause.SoftReset
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: Host system DC power is off
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: POH timer canceled
Jul 24 10:36:41 hudsonbay-obmc power-control[198]: failed to reset ACBoot property
Jul 24 10:36:42 hudsonbay-obmc power-control[198]: Warm reset check timer completed
Jul 24 10:36:42 hudsonbay-obmc power-control[198]: powerStateCheckForWarmReset: warm reset detected event received
Jul 24 10:36:42 hudsonbay-obmc power-control[198]: Host0: Moving to "On" state
Jul 24 10:36:42 hudsonbay-obmc power-control[198]: POH timer started
Jul 24 10:36:42 hudsonbay-obmc power-control[198]: Host system DC power is on
Jul 24 10:38:16 hudsonbay-obmc power-control[198]: powerStateOn: POST Complete assert event received
Jul 24 10:38:16 hudsonbay-obmc power-control[198]: No action taken.
Jul 24 10:38:34 hudsonbay-obmc power-control[198]: PowerControl: power button pressed
Jul 24 10:38:34 hudsonbay-obmc power-control[198]: powerStateOn: power button pressed event received
Jul 24 10:38:34 hudsonbay-obmc power-control[198]: Host0: Moving to "Graceful Transition to Off" state
Jul 24 10:38:34 hudsonbay-obmc power-control[198]: Graceful power-off timer started
Jul 24 10:43:34 hudsonbay-obmc power-control[198]: Graceful power-off timer completed
Jul 24 10:43:34 hudsonbay-obmc power-control[198]: powerStateGracefulTransitionToOff: graceful power-off timer expired event received
Jul 24 10:43:34 hudsonbay-obmc power-control[198]: Host0: Moving to "On" state
=====

Thanks.

Regards,
Chris Chen

________________________________
寄件者: openbmc <openbmc-bounces+chris.chen3=flex.com@lists.ozlabs.org> 代表 Bills, Jason M <jason.m.bills@linux.intel.com>
寄件日期: 2021年7月24日 上午 04:36
收件者: openbmc@lists.ozlabs.org <openbmc@lists.ozlabs.org>
主旨: Re: [x86-power-control]: press the power button for a long time that can't force turn off system power



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[263]: PowerControl: power button pressed
> power-control[263]: powerStateOn: power button pressed event received
> power-control[263]: Host0: Moving to "Graceful Transition to Off" state
> power-control[263]: 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?
Hi Chris,

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?

Thanks,
-Jason
>
>
> Thank you in advance for your help.
>
> Regards,
> Chris Chen
>
> Legal Disclaimer :
> The information contained in this message may be privileged and
> confidential.
> It is intended to be read only by the individual or entity to whom it is
> addressed
> or by their designee. If the reader of this message is not the intended
> recipient,
> 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!

[-- Attachment #2: Type: text/html, Size: 9358 bytes --]

  reply	other threads:[~2021-07-24  3:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 10:28 Chris Chen (TPI)
2021-07-23 20:36 ` Bills, Jason M
2021-07-24  3:04   ` Chris Chen (TPI) [this message]
2021-07-26 16:46     ` 回覆: " Bills, Jason M
2021-08-16  3:52       ` Chris Chen (TPI)
2021-08-16  6:30         ` Andrew Jeffery
2021-08-16 10:45           ` 回覆: " Chris Chen (TPI)
2021-08-17  1:57             ` Andrew Jeffery
2021-08-17 11:17               ` Chris Chen (TPI)
2021-08-17 11:30                 ` Andrew Jeffery
2021-08-17 19:04                   ` Bills, Jason M
2021-08-18 11:07                     ` 回覆: " Chris Chen (TPI)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR08MB551464D29CE9BD91FFE1B20ADCE69@DM6PR08MB5514.namprd08.prod.outlook.com \
    --to=chris.chen3@flex.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --subject='Re: 回覆: [x86-power-control]: press the power button for a long time that can'\''t force turn off system power' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).