Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-power / 2549d79233802e39e21f4d142f89eb6b8841a8c6
commit2549d79233802e39e21f4d142f89eb6b8841a8c6[log] [tgz]
authorAdriana Kobylak <anoo@us.ibm.com>Wed Jan 26 20:51:30 2022 +0000
committerShawn McCarney <shawnmm@us.ibm.com>Wed Feb 02 18:16:39 2022 +0000
treebafeb5f205db9c20d68f108fdc6fbf8f859b254a
parent71a14131f1f9b41e75873c69e8f7d8d9a6d8490f [diff]
psu-ng: Log error on brownout condition

Per design document:
https://github.com/openbmc/docs/blob/master/designs/power-recovery.md#brownout

The BMC must log an error indicating the brownout event has occurred.

Check for a brownout condition where all PSUs are either not present or
report an AC loss VIN fault. The error log would be the same as a
Blackout condition. Keep track if the error was created via a variable
so that the error is not created multiple times. Clear the variable once
the brownout condition is no longer detected or when then system is
powered off so that it gets logged on the next power on.

Tested: On Rainier 2S2U simulation where there are 4 PSUs slots but only
two power supplies connected, inject a VIN fault on the two present PSUs
and verify an error log for AC loss 110000AC is created:

Jan 31 16:57:37 p10bmc phosphor-psu-monitor[963]: INPUT fault:
STATUS_WORD = 0x2848, STATUS_MFR_SPECIFIC = 0x0, STATUS_INPUT = 0x38
Jan 31 16:57:37 p10bmc phosphor-psu-monitor[963]: VIN_UV fault:
STATUS_WORD = 0x2848, STATUS_MFR_SPECIFIC = 0x0, STATUS_INPUT = 0x38
Jan 31 16:57:38 p10bmc phosphor-psu-monitor[963]: INPUT fault:
STATUS_WORD = 0x2848, STATUS_MFR_SPECIFIC = 0x0, STATUS_INPUT = 0x38
Jan 31 16:57:38 p10bmc phosphor-psu-monitor[963]: VIN_UV fault:
STATUS_WORD = 0x2848, STATUS_MFR_SPECIFIC = 0x0, STATUS_INPUT = 0x38
Jan 31 16:57:38 p10bmc phosphor-log-manager[305]: Created PEL 0x50000007
(BMC ID 7) with SRC 110000AC

Change-Id: I7760b59a02ef2afc81bd7807c7896183d99a66ec
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2 files changed
tree: bafeb5f205db9c20d68f108fdc6fbf8f859b254a
  1. cold-redundancy/
  2. example/
  3. org/
  4. phosphor-power-sequencer/
  5. phosphor-power-supply/
  6. phosphor-regulators/
  7. power-sequencer/
  8. power-supply/
  9. services/
  10. test/
  11. tools/
  12. .clang-format
  13. .gitignore
  14. .shellcheck
  15. argument.hpp
  16. device.hpp
  17. device_monitor.hpp
  18. elog-errors.hpp
  19. file_descriptor.hpp
  20. gpio.cpp
  21. gpio.hpp
  22. LICENSE
  23. MAINTAINERS
  24. meson.build
  25. meson_options.txt
  26. names_values.hpp
  27. OWNERS
  28. pmbus.cpp
  29. pmbus.hpp
  30. README.md
  31. types.hpp
  32. utility.cpp
  33. utility.hpp
README.md

Overview

This repository contains applications for configuring and monitoring devices that deliver power to the system.

  • cold-redundancy: Application that makes power supplies work in Cold Redundancy mode and rotates them at intervals.
  • phosphor-power-sequencer: Applications for configuring and monitoring power sequencer and related devices that support JSON-driven configuration.
  • phosphor-power-supply: Next generation power supply monitoring application.
  • phosphor-regulators: JSON-driven application that configures and monitors voltage regulators.
  • power-sequencer: A power sequencer monitoring application.
  • power-supply: Original power supply monitoring application.
  • tools/power-utils: Power supply utilities.

Build

To build all applications in this repository:

  meson build
  ninja -C build

To clean the repository and remove all build output:

  rm -rf build

You can specify meson options to customize the build process. For example, you can specify:

  • Which applications to build and install.
  • Application-specific configuration data, such as power sequencer type.
  • Whether to build tests.

Power Supply Monitor and Util JSON config

Several applications in this repository require a PSU JSON config to run. The JSON config file provides information for:

  • Where to access the pmbus attributes
  • Which attribute file in pmbus maps to which property and interface in D-Bus
  • Which kernel device directory is used on which PSU

There is an example psu.json to describe the necessary configurations.

  • inventoryPMBusAccessType defines the pmbus access type, which tells the service which sysfs type to use to read the attributes. The possible values are:
    • Base: The base dir, e.g. /sys/bus/i2c/devices/3-0069/
    • Hwmon: The hwmon dir, e.g. /sys/bus/i2c/devices/3-0069/hwmon/hwmonX/
    • Debug: The pmbus debug dir, e.g. /sys/kernel/debug/pmbus/hwmonX/
    • DeviceDebug: The device debug dir, e.g. '/sys/kernel/debug/./`
    • HwmonDeviceDebug: The hwmon device debug dir, e.g. /sys/kernel/debug/pmbus/hwmonX/cffps1/
  • fruConfigs defines the mapping between the attribute file and the FRU inventory interface and property. The configuration example below indicates that the service will read part_number attribute file from a directory specified by the above pmbus access type, and assign to PartNumber property in xyz.openbmc_project.Inventory.Decorator.Asset interface.
      "fruConfigs": [
    {
      "propertyName": "PartNumber",
      "fileName": "part_number",
      "interface": "xyz.openbmc_project.Inventory.Decorator.Asset"
    }
  ]
  • psuDevices defines the kernel device dir for each PSU in inventory. The configuration example below indicates that powersupply0's device is located in /sys/bus/i2c/devices/3-0069.
      "psuDevices": {
    "/xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply0" : "/sys/bus/i2c/devices/3-0069",
  }