PEL: new info log for when chassis power on is started
This new informational error is being defined for a couple of reasons:
- An easy eye catcher when reviewing logs to easily distinguish between
major boots of the system (ones including a chassis power cycle)
- A mechanism for other OpenBMC software which utilizes the log to
report back to the user when errors from the current boot need
attention
This log will be created by an optional opt-in service within
phosphor-state-manager as a part of the obmc-chassis-poweron@.target.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Idd39680091c6e915997d69370e988e4d0bd29912
diff --git a/extensions/openpower-pels/registry/message_registry.json b/extensions/openpower-pels/registry/message_registry.json
index 4cfa1f0..aa4d41a 100644
--- a/extensions/openpower-pels/registry/message_registry.json
+++ b/extensions/openpower-pels/registry/message_registry.json
@@ -1362,6 +1362,25 @@
},
{
+ "Name": "xyz.openbmc_project.State.Info.ChassisPowerOnStarted",
+ "Subsystem": "bmc_firmware",
+ "ComponentID": "0x3400",
+ "Severity": "non_error",
+ "SRC": {
+ "ReasonCode": "0x3416",
+ "Words6To9": {}
+ },
+ "Documentation": {
+ "Description": "A power on of the chassis has been started",
+ "Message": "The chassis is powering on.",
+ "Notes": [
+ "This informational error is logged each time the chassis",
+ "is powered on."
+ ]
+ }
+ },
+
+ {
"Name": "org.open_power.Processor.Error.SbeChipOpFailure",
"Subsystem": "processor_chip",
"ComponentID": "0x3500",