tree e14323f2b5fb597d86522013412a0a812f10adfc
parent 221b79b3b97dac3df73b155f6e24363bb6a9d6f2
author devenrao <devenrao@in.ibm.com> 1712039953 +0530
committer MARRI DEVENDER RAO <devenrao@in.ibm.com> 1713284397 +0000

PEL: Add a new error msg for FFDC collected after SBE chip-op success

SBE enqueues the FFDC (first failure data capture) corresponding
to the internal SBE operations and internal hardware procedure FFDC

After any SBE chip-op request from BMC, if the chip-op is
success BMC needs to check if any FFDC is present and needs
to create PEL based on the severity set in the FFDC packet.

There will be non-fatal errors when executing asynchronous
operations ( e.g auto-boot, MPIPL, DMT or any periodic
background operations in the SBE).

All accumulated non-fatal errors will be regularly reported back
in every chip-op response.

'''
root@rain71bmc:/tmp# peltool -l
{
"0x50006027": {
"SRC":                  "BD204503",
"Message":              "SBE internal FFDC data after chipop request success",
"PLID":                 "0x50006027",
"CreatorID":            "BMC",
"Subsystem":            "Memory",
"Commit Time":          "04/02/2024 12:42:14",
"Sev":                  "Unrecoverable Error",
"CompID":               "bmc POZ PEL parser"
},
"0x50006028": {
"SRC":                  "BD204503",
"Message":              "SBE internal FFDC data after chipop request success",
"PLID":                 "0x50006028",
"CreatorID":            "BMC",
"Subsystem":            "Memory",
"Commit Time":          "04/02/2024 12:42:14",
"Sev":                  "Predictive Error",
"CompID":               "bmc POZ PEL parser"
}
}
'''

Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: Ib488eccfca3df8c68035c78b49661749d7d9889c