linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Vipin K Parashar <vipin@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: stewart@linux.vnet.ibm.com,
	Vipin K Parashar <vipin@linux.vnet.ibm.com>,
	joel@jms.id.au, vaibhav@linux.vnet.ibm.com
Subject: Re: [v6] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform
Date: Fri,  5 Jun 2015 08:01:02 +1000 (AEST)	[thread overview]
Message-ID: <20150604220102.6BCFE140281@ozlabs.org> (raw)
In-Reply-To: <1433419397-3119-2-git-send-email-vipin@linux.vnet.ibm.com>

On Thu, 2015-04-06 at 12:03:17 UTC, Vipin K Parashar wrote:
> This patch adds support for FSP (Flexible Service Processor)
> EPOW (Early Power Off Warning) and DPO (Delayed Power Off) events for
> the PowerNV platform. EPOW events are generated by FSP due to various
> critical system conditions that require system shutdown. A few examples
> of these conditions are high ambient temperature or system running on
> UPS power with low UPS battery. DPO event is generated in response to
> admin initiated system shutdown request. Upon receipt of EPOW and DPO
> events the host kernel invokes orderly_poweroff() for performing
> graceful system shutdown.
> 
> Reviewed-by: Joel Stanley <joel@jms.id.au>
> Reviewed-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
> Reviewed-by: Michael Ellerman <mpe@ellerman.id.au>
> Signed-off-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>

Hi Vipin,

One issue, on mambo I'm seeing:

  [666973573,3] OPAL: Called with bad token 105 !
  opal-power: Existing DPO event detected.
  reboot: Failed to start orderly shutdown: forcing the issue
  reboot: Power down
  [684431322,5] OPAL: Shutdown request type 0x0...


ie. at boot it shuts down immediately.

The problem is in here I think:

> +	/* Check for DPO event */
> +	rc = opal_get_dpo_status(&opal_dpo_timeout);
> +	if (rc != OPAL_WRONG_STATE) {
> +		pr_info("Existing DPO event detected.\n");
> +		return true;
> +	}


This also makes me think you probably haven't tested this on a BMC machine?

cheers

  reply	other threads:[~2015-06-04 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 12:03 [PATCH v6] powerpc/powernv: Poweroff (EPOW, DPO) events support for PowerNV platform Vipin K Parashar
2015-06-04 12:03 ` [PATCH v6] powerpc/powernv: Add poweroff " Vipin K Parashar
2015-06-04 22:01   ` Michael Ellerman [this message]
2015-06-04 22:33     ` [v6] " Michael Ellerman
2015-06-08 14:19     ` Vipin K Parashar

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=20150604220102.6BCFE140281@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=vaibhav@linux.vnet.ibm.com \
    --cc=vipin@linux.vnet.ibm.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).