PEL:message_registry: add new HostRunning error
The following commit introduced this new error:
https://gerrit.openbmc-project.xyz/c/openbmc/openpower-proc-control/+/44352
This officially defines it within the PEL registry to ensure the
appropriate documentation accompanies it.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I66f4baf40e1e3b14e4b29d9e4f4efe2f1a729686
diff --git a/extensions/openpower-pels/registry/message_registry.json b/extensions/openpower-pels/registry/message_registry.json
index 082ad30..daed092 100644
--- a/extensions/openpower-pels/registry/message_registry.json
+++ b/extensions/openpower-pels/registry/message_registry.json
@@ -472,6 +472,33 @@
},
{
+ "Name": "org.open_power.PHAL.Error.HostRunning",
+ "Subsystem": "cec_sp_hostboot_iface",
+ "ComponentID": "0x3000",
+
+ "SRC":
+ {
+ "ReasonCode": "0x3005",
+ "Words6To9":
+ {
+ }
+ },
+
+ "Documentation":
+ {
+ "Description": "Host did not respond to BMC after a BMC reset",
+ "Message": "Host did not respond to BMC after a BMC reset but hardware indicates it is running",
+ "Notes": [
+ "System will be left in its current state to ensure host ",
+ "is not unexpectedly taken down. There is most likely an ",
+ "issue in the software or hardware communication path ",
+ "between the BMC and the Host firmware.",
+ "A BMC dump will be collected with relevant FFDC."
+ ]
+ }
+ },
+
+ {
"Name": "org.open_power.Processor.Error.SbeChipOpFailure",
"Subsystem": "processor_chip",
"ComponentID": "0x3500",