tree bafeb5f205db9c20d68f108fdc6fbf8f859b254a
parent 71a14131f1f9b41e75873c69e8f7d8d9a6d8490f
author Adriana Kobylak <anoo@us.ibm.com> 1643230290 +0000
committer Shawn McCarney <shawnmm@us.ibm.com> 1643825799 +0000

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>