All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Milton Miller II" <miltonm@us.ibm.com>
To: Mike Jones <proclivis@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re:  Power Supplies are Turned off after boot
Date: Fri, 7 Aug 2020 02:32:27 +0000	[thread overview]
Message-ID: <OF66E559B6.C704B66F-ON002585BD.000DF51B-002585BD.000DF524@notes.na.collabserv.com> (raw)
In-Reply-To: <F6868B82-B239-44DE-B90A-BD808FEA4C5B@gmail.com>

On August 5, 2020 Mike Jones wrote:

>Now that I have webui displaying telemetry for multiple PMBus
>devices, I want to solve a power supply problem.
>
>After boot, all PMBus devices have their power turned off via an
>OPERATION command. This happens about 10-20 seconds after boot
>completes. There is a message printed saying it is disabling them,
>and one line per action. Like:
>
>VOUT 1: disabling
>
>Where VOUT 1 does not match the name of the rails in the config files
>with the name and limits. It seems like a more generic term
>indicating voltage.
>
>These devices are in the device tree and have hwmon running.
>
>What service would be capable of shutting off the supplies? It would
>have to be able to discover them, perhaps by device tree, then issue
>standard PMBus commands.

I'm guessing the host watchdog was not shutdown when your HOST 
completed boot and the watchdog requesed the system power off.
Normally an IPMI message from the host will disable the watchdog.

You should be able to see the transition files run in the systemd 
journal if this is the case.

if not try watching for activity by using journalctl to follow 
events live in a shell.

>>Note: the Phosphor System Manager service fails at start up. I don’t
>know if this matters, I was going to figure out what it does later.
>
>Mike
>

  reply	other threads:[~2020-08-07  2:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 22:28 Power Supplies are Turned off after boot Mike Jones
2020-08-07  2:32 ` Milton Miller II [this message]
2020-08-07  3:34   ` Mike
2020-08-07 23:00   ` Mike Jones

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=OF66E559B6.C704B66F-ON002585BD.000DF51B-002585BD.000DF524@notes.na.collabserv.com \
    --to=miltonm@us.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=proclivis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.