PEL: Add firmware error for VPD

The commit adds new error to call out procedure in case there is any
std::runtime exception in the VPD Manager.

Change-Id: Id2a567fb7bc4cc2335e08b4695a5ff5e405c5aa2

PEL: Add firmware error for VPD

The commit adds new error to call out procedure in case there is any
std::runtime exception in the VPD Manager.

Change-Id: Id2a567fb7bc4cc2335e08b4695a5ff5e405c5aa2
Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com>

show more ...

Update new error message for single FAB feature

Two new error messages are added in the message registry for creating
PEL in case invalid system configuration found and need PE’s
intervention to upd

Update new error message for single FAB feature

Two new error messages are added in the message registry for creating
PEL in case invalid system configuration found and need PE’s
intervention to update IM value manually to support single FAB feature.

Change-Id: Ifbc4d9eea44877db07542efc351364d133394ad4
Signed-off-by: Anupama B R <anupama.b.r1@ibm.com>

show more ...

PEL: Add PSU firmware update PELs

Add PEL entries for PSU firmware update and firmware file issues

- Added PEL for successful PSU firmware update (PEL 0x15F8)
- Added PEL for PSU firmware update fa

PEL: Add PSU firmware update PELs

Add PEL entries for PSU firmware update and firmware file issues

- Added PEL for successful PSU firmware update (PEL 0x15F8)
- Added PEL for PSU firmware update failure, callout of PSU and BMC (PEL
0x15F9)
- Added PEL for PSU firmware file issues, referencing procedure BMC001
(PEL 0x15FA)

Test:
Tested all new PEL message in simulation and verified the output.

Change-Id: I4e26a9c4a3764429931f3a509e63c5c9d0638851
Signed-off-by: Faisal Awada <faisal@us.ibm.com>

show more ...

PEL: Removed severity from OCC OpenFailure PEL

The OpenFailure PEL was being set to predictive severity.
These errors can happen when a system hits a processor checkpoint. There
should already be an

PEL: Removed severity from OCC OpenFailure PEL

The OpenFailure PEL was being set to predictive severity.
These errors can happen when a system hits a processor checkpoint. There
should already be another error logged for the checkstop, so if the code
hits this condition it will be logged as Notice/Informational.
Also made some changes to add journal traces to other occ-control PELs.

Tested on Rainier.

Change-Id: I320a0758344718e8d1fff478c9c561063ec070e6
Signed-off-by: Chris Cain <cjcain@us.ibm.com>

show more ...

PEL: Add a new error message for Dump Offload

We log the same error for Dump Delete and Offload right now. Adding a
new error to distinguish between a dump delete and a dump offload.

Change-Id: I1c

PEL: Add a new error message for Dump Offload

We log the same error for Dump Delete and Offload right now. Adding a
new error to distinguish between a dump delete and a dump offload.

Change-Id: I1c74906fb170d883447a021c59199baaa4f6dc97
Signed-off-by: SwethaParasa <parasa.swetha1@ibm.com>

show more ...

openpower-pels: Add BMC0005 callout to pgood error

Add the procedure BMC0005 as a high priority callout for pgood errors on
the 3V3IO voltage rail. Reduce first VRM callout to medium priority.

Whe

openpower-pels: Add BMC0005 callout to pgood error

Add the procedure BMC0005 as a high priority callout for pgood errors on
the 3V3IO voltage rail. Reduce first VRM callout to medium priority.

When the lid (cover) is removed on Everest/Fuji systems, main power is
automatically shut off for safety reasons. Due to the hardware design
and UCD configuration, the resulting pgood error is incorrectly isolated
to the 3V3IO voltage rail. Add the BMC0005 procedure as the first
callout for this error so the lid will be checked as a possible cause.

Tested:
* Created 11002620 error for the 3V3IO rail using busctl.
* Verified all callouts in the resulting error log were correct.

Change-Id: I3af8ce6ae146ff8c6816602a2bfa47e679268387
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

manager: use new Logging.Cleared event

Modify the internal manager support for creating internal events
to be able to support the sdbusplus generated events. Transition
from the local Logging.Error

manager: use new Logging.Cleared event

Modify the internal manager support for creating internal events
to be able to support the sdbusplus generated events. Transition
from the local Logging.Error.LogsCleared to the global Logging.Cleared
event. Clean up references to the old event.

Tested:
```
$ busctl --user call xyz.openbmc_project.Logging /xyz/openbmc_project/logging xyz.openbmc_project.Collection.DeleteAll DeleteAll
$ busctl --user introspect xyz.openbmc_project.Logging /xyz/openbmc_project/logging/entry/1 -l | cat
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
xyz.openbmc_project.Logging.Entry interface - - -
.GetEntry method - h -
.AdditionalData property as 5 "NUMBER_OF_LOGS=210" "_CODE_FILE=../log_manager.hpp" "_CODE_FUNC=virtual void phosphor::logging::Manager::deleteAll()" "_CODE_LINE=361" "_PID=3318436" emits-change writable
.EventId property s "" emits-change writable
.Id property u 1 emits-change writable
.Message property s "xyz.openbmc_project.Logging.Cleared" emits-change writable
.Resolution property s "" emits-change writable
.Resolved property b false emits-change writable
.ServiceProviderNotify property s "xyz.openbmc_project.Logging.Entry.Notify.NotSupported" emits-change writable
.Severity property s "xyz.openbmc_project.Logging.Entry.Level.Informational" emits-change writable
.Timestamp property t 1730408674348 emits-change writable
.UpdateTimestamp property t 1730408674348 emits-change writable
```

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I470f33ae2f5bfae6bf6d6a80ac2c5f028e41da95

show more ...

PEL: Add heartbeat action flag to power-on log

The informational PEL for a chassis power on starting is also considered
a heartbeat error log.

Change-Id: I7befa66997bcd17fd310304ae76516cfeea7a3e6
S

PEL: Add heartbeat action flag to power-on log

The informational PEL for a chassis power on starting is also considered
a heartbeat error log.

Change-Id: I7befa66997bcd17fd310304ae76516cfeea7a3e6
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

show more ...

PEL: Updated PEL spec error action flag bit#10

- This will help to indicate which SRCs need to be collected and
regularly called home.
- Defined new entry in message registry schema action flags fie

PEL: Updated PEL spec error action flag bit#10

- This will help to indicate which SRCs need to be collected and
regularly called home.
- Defined new entry in message registry schema action flags field
- Set this action flag in the registry for the daily clock PEL
and the voltage regulator N+1 phase fault PEL

Tested:
Sample output:
```bash
$ peltool -af
...
"Action Flags": [
"Report Externally",
"Heartbeat Call Home Event"
...
"Action Flags": [
"Report Externally",
"HMC Call Home",
"Heartbeat Call Home Event"
...
$ peltool -afx
...
00000030 55 48 00 18 01 00 20 00 60 03 00 01 00 00 00 00 |
00000040 00 00 20 20 00 00 00 00 50 53 00 50 01 01 27 00 |
...
00000030 55 48 00 18 01 00 20 00 58 03 00 01 00 00 00 00 |
00000040 00 00 28 20 00 00 00 00 50 53 00 50 01 01 30 00 |
...

```
Change-Id: Ifa181374692013dfadc0dd744f6db61baad3d42e
Signed-off-by: Harsh Agarwal <Harsh.Agarwal@ibm.com>

show more ...

PEL: Adding BMC PEL for PLDM error

This commit adds BMC pels for PLDM error so as to report resource dump
failure.

Change-Id: I1f4f742900f69dbd38c8dbbdba67549c7862a3b2
Signed-off-by: Riya Dixit <ri

PEL: Adding BMC PEL for PLDM error

This commit adds BMC pels for PLDM error so as to report resource dump
failure.

Change-Id: I1f4f742900f69dbd38c8dbbdba67549c7862a3b2
Signed-off-by: Riya Dixit <riyadixitagra@gmail.com>

show more ...

PEL: Update msg reg name for perf loss threshold

The commit openbmc/phosphor-fan-presence@99914e5 changed the Message
property of the performance loss threshold alert from
TemperaturePerfLossHigh an

PEL: Update msg reg name for perf loss threshold

The commit openbmc/phosphor-fan-presence@99914e5 changed the Message
property of the performance loss threshold alert from
TemperaturePerfLossHigh and TemperaturePerfLossHighClear to
TemperaturePerformanceLossHigh and TemperaturePerformanceLossHighClear.

Update the value in the PEL message registry to match.

Change-Id: If85160782092f6da0fe846e545142e49e5cac9f3
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

show more ...

PEL: Remove deprecated power sequencer callouts

Remove callouts for GPIO and voltage rail names that have been
deprecated by the phosphor-power-sequencer application.

Tested:
* Ran message registry

PEL: Remove deprecated power sequencer callouts

Remove callouts for GPIO and voltage rail names that have been
deprecated by the phosphor-power-sequencer application.

Tested:
* Ran message registry validation tool
* Verified error logged with removed GPIO name has no callouts
* Verified error logged with removed rail name has no callouts
* Verified error logged with valid rail name has correct callouts

Change-Id: I0c7c91aaea87d235952509a713c92011149114ed
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

PEL: Adding a new BMC PEL for PDR Exchange Failure

This commit adds a new PEL when BMC fails to collect PDR from host.
GetPDR returns no response because of BMC PDR exchange failure as three
tries g

PEL: Adding a new BMC PEL for PDR Exchange Failure

This commit adds a new PEL when BMC fails to collect PDR from host.
GetPDR returns no response because of BMC PDR exchange failure as three
tries get exhausted and timeouts.

Change-Id: I6b928c53ca75f6b55dc124cc01eaba025ec9252a
Signed-off-by: Riya Dixit <riyadixitagra@gmail.com>

show more ...

PEL: Updating sev for set host effecter failure

This commit updates the severity of PEL
'xyz.openbmc_project.PLDM.Error.SetHostEffecterFailed' from
UNRECOVERABLE ERROR to INFORMATIONAL.

Change-Id:

PEL: Updating sev for set host effecter failure

This commit updates the severity of PEL
'xyz.openbmc_project.PLDM.Error.SetHostEffecterFailed' from
UNRECOVERABLE ERROR to INFORMATIONAL.

Change-Id: I196e858b9ac71554f6dce6dfb70c6d29b3aa9caa
Signed-off-by: Riya Dixit <riyadixitagra@gmail.com>

show more ...

PEL: Fixing procedure name in callout details

In the newly introduced PEL in the callout details
we had procedure name as "next_level_support" but
recently made a change to expose the procedure
call

PEL: Fixing procedure name in callout details

In the newly introduced PEL in the callout details
we had procedure name as "next_level_support" but
recently made a change to expose the procedure
callouts in the RCDL because service said they needed
them. This changes fixes this missing actual procedure
name from next_level_support to BMC0002.

Signed-off-by: Swarnendu Roy Chowdhury <swarnendu.roy.chowdhury@ibm.com>
Change-Id: I7f49ca37cef3c6f49fc08808b68fdd9f72549b25

show more ...

PEL: Add a new error when occ-control can't find PDRs

The occ-control app needs the PDRs for the OCCs in order to know when
the OCCs are available. If those PDRs are not able to be found for a
perio

PEL: Add a new error when occ-control can't find PDRs

The occ-control app needs the PDRs for the OCCs in order to know when
the OCCs are available. If those PDRs are not able to be found for a
period of time, this PEL will be created for further investigation.

'''
"0x500813BD": {
"SRC": "BD8D2685",
"Message": "BMC firmware was not able to find the OCC sensor ID records",
"PLID": "0x500813BD",
"CreatorID": "BMC",
"Subsystem": "BMC Firmware",
"Commit Time": "04/22/2024 17:05:58",
"Sev": "Predictive Error",
"CompID": "bmc occ control"
},
'''

Change-Id: Ic8167f6d06a346c6bdaa59058fcbbf4b5a63ec38
Signed-off-by: Chris Cain <cjcain@us.ibm.com>

show more ...

PEL: fix the subsystem type for proc sbe internal data msg

Modified to fix the subsystem value used for SBEInternalData
error message for processor.

Signed-off-by: Marri Devender Rao <devenrao@in.i

PEL: fix the subsystem type for proc sbe internal data msg

Modified to fix the subsystem value used for SBEInternalData
error message for processor.

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

show more ...

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

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

show more ...

PEL: Message_registry: System name as per new compatible interface

As part of the migration from IBMCompatible interface to the new
Compatible interface the PEL code is changed to use the new system

PEL: Message_registry: System name as per new compatible interface

As part of the migration from IBMCompatible interface to the new
Compatible interface the PEL code is changed to use the new system name
format as 'com.ibm.Hardware.Chassis.Model.<system_name>'.

The message registry file still uses the old system name format
'ibm,<system_name>' which results parsing error of PEL message registry
callout JSON.

Hence modifies the message registry file to use the new system name
format.

Tested:
The dev_callouts file in /usr/share/phosphor-logging/pels/ have the new
system name format.
```
com.ibm.Hardware.Chassis.Model.Rainier1S4U_dev_callouts.json
com.ibm.Hardware.Chassis.Model.Rainier2U_dev_callouts.json
com.ibm.Hardware.Chassis.Model.Rainier4U_dev_callouts.json
```

Creating a PEL for SbeTimeout which leads to the PEL callouts as
expected:
```
"Callout Section": {
"Callout Count": "2",
"Callouts": [{
"FRU Type": "Normal Hardware FRU",
"Priority": "Lowest priority replacement",
"Location Code": "U78DA.ND0.WZS004A-P0",
"Part Number": "02WG676",
"CCIN": "2E2D",
"Serial Number": "Y131UF07302J"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Lowest priority replacement",
"Location Code": "U78DA.ND0.WZS004A-P0-C22",
"Part Number": "02WF429",
"CCIN": "6B59",
"Serial Number": "YL101314Y002"
}]
}
```

Signed-off-by: Arya K Padman <aryakpadman@gmail.com>
Change-Id: I438bb3de5014edd6a510e5334c8b1981d5ac512c

show more ...

PEL: Fix PEL to callout PGDPART symbolic FRU

Tested:
Injected a error and verified the output
busctl call xyz.openbmc_project.Logging /xyz/openbmc_project/logging \
xyz.openbmc_project.Logging

PEL: Fix PEL to callout PGDPART symbolic FRU

Tested:
Injected a error and verified the output
busctl call xyz.openbmc_project.Logging /xyz/openbmc_project/logging \
xyz.openbmc_project.Logging.Create Create ssa{ss} \
xyz.openbmc_project.State.Shutdown.Power.Error.Regulator \
xyz.openbmc_project.Logging.Entry.Level.Critical 0

'''
peltool -l
{
"0x5000012C": {
"SRC": "11002602",
"Message": "A power off was issued because a regulator for standby power faulted",
"PLID": "0x5000012C",
"CreatorID": "BMC",
"Subsystem": "Power Control Hardware",
"Commit Time": "03/28/2024 02:49:10",
"Sev": "Critical Error, System Termination",
"CompID": "bmc power and thermal"
}
}
'''

peltool -i 0x5000012C
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "bmc power and thermal",
"Created at": "03/28/2024 02:49:10",
"Committed at": "03/28/2024 02:49:10",
"Creator Subsystem": "BMC",
"CSSVER": "",
"Platform Log Id": "0x5000012C",
"Entry Id": "0x5000012C",
"BMC Event Log Id": "32"
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "bmc error logging",
"Subsystem": "Power Control Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Critical Error, System Termination",
"Event Type": "Not Applicable",
"Action Flags": [
"Service Action Required",
"Report Externally",
"HMC Call Home"
],
"Host Transmission": "Not Sent",
"HMC Transmission": "Acked"
},
'''
"Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "bmc power and thermal",
"SRC Version": "0x02",
"SRC Format": "0x55",
"Virtual Progress SRC": "False",
"I5/OS Service Event Bit": "False",
"Hypervisor Dump Initiated":"False",
"Backplane CCIN": "2E44",
"Terminate FW Error": "True",
"Deconfigured": "False",
"Guarded": "False",
"Error Details": {
"Message": "A power off was issued because a regulator for standby power faulted"
},
"Valid Word Count": "0x09",
"Reference Code": "11002602",
"Hex Word 2": "00000055",
"Hex Word 3": "2E440010",
"Hex Word 4": "11002602",
"Hex Word 5": "20000000",
"Hex Word 6": "00000000",
"Hex Word 7": "00000000",
"Hex Word 8": "00000000",
"Hex Word 9": "00000000",
"Callout Section": {
"Callout Count": "1",
"Callouts": [{
"FRU Type": "Symbolic FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Part Number": "PGDPART"
}]
}
},
'''
"Extended User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "bmc error logging",
"Reporting Machine Type": "9028-21B",
"Reporting Serial Number": "788C451",
"FW Released Ver": "NL1060_034",
"FW SubSys Version": "fw1060.00-4.36",
"Common Ref Time": "00/00/0000 00:00:00",
"Symptom Id Len": "20",
"Symptom Id": "11002602_2E440010"
}
'''

Change-Id: I87418ffc51e0a2eb98e795c53c209965b81cfcd9
Signed-off-by: Faisal Awada <faisal@us.ibm.com>

show more ...

PEL: Add POZ PEL Parser

Parser to parse the POZ PLAT data in the PEL. Changing the component ID
from F400 to 4500 to be used for all the SBE's PEL data parsers.
"o3500.py" will handle only P10 proce

PEL: Add POZ PEL Parser

Parser to parse the POZ PLAT data in the PEL. Changing the component ID
from F400 to 4500 to be used for all the SBE's PEL data parsers.
"o3500.py" will handle only P10 processor SBE. "o4500.py" will be for
Odyssey and Pfuture chips.

Change-Id: I4be341888b6ea7a0b999b3e4555604b4d39ea4ce
Signed-off-by: SwethaParasa <parasa.swetha1@ibm.com>

show more ...

PEL: add new error messages for odyssey sbe related failures

There will be SBE instances for ocmb targets, so adding
error messages for any SBE access failures.

Adding the new attribute "CHIP_TYPE"

PEL: add new error messages for odyssey sbe related failures

There will be SBE instances for ocmb targets, so adding
error messages for any SBE access failures.

Adding the new attribute "CHIP_TYPE" as we now need to cater for
colletcing SBE FFDC data both for proc and ocmb.

Now added "chip type", to the libekb_get_sbe_ffdc method, which is
called in the sbe ffdc handler so that it can collect data for that
specified chip type.

Tested:
'''
"Private Header": {
"Created by": "0xF400",
},
"Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0xF400",
"Error Details": {
"Message": "chipop request failure reported by OCMB SBE",
"SRC6": [
"0x4AA01",
"[0:15] chip position, [16:23] command class,
[24:31] command type"
],
"CHIP_TYPE": [
"0x28",
"Chip Type"
]
},
"Valid Word Count": "0x09",
"Reference Code": "BD20F401",
},
},
'''
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: I622b670d23fc1f6b0d62ad65a41ddcf89c65d319

show more ...

PEL: Update sev of critical threshold errors

The Temperature/Voltage CriticalHigh/Low PELs previously had a PEL
severity of 'predictive', and this commit changes them to
'unrecoverable' so that it m

PEL: Update sev of critical threshold errors

The Temperature/Voltage CriticalHigh/Low PELs previously had a PEL
severity of 'predictive', and this commit changes them to
'unrecoverable' so that it matches the D-Bus severity value it's being
created with.

Note: The D-Bus severity value is 'critical'. While there is a PEL
severity value of 'critical', both 'unrecoverable' and 'critical' get
mapped to the Redfish field value of 'Critical' anyway, and the PEL
'critical' field seems to be just used for system crashes and the like.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I174c48180abe9ddca09d0e020e6d16f81311bb61

show more ...

PEL: Convert missed procedure callouts

The three PELs that were added in parallel to the commit that changed
procedure names to the BMCXXXX values got missed, so fix them up.

Signed-off-by: Matt Sp

PEL: Convert missed procedure callouts

The three PELs that were added in parallel to the commit that changed
procedure names to the BMCXXXX values got missed, so fix them up.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I0bbced6d42da14f66be748d96448847fa95f1fe5

show more ...

PEL: Use raw procedure names in PEL msg reg

Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This wa

PEL: Use raw procedure names in PEL msg reg

Start using the raw maintenance procedure names in the PEL message
registry, such as BMC0001, instead of the enum values, such as
'bmc_firmware'. This way, the script that generates documentation can
list the procedure in the section for that PEL. This was requested by
the support team.

Note that there is still one user of the enums - the checkstop analysis
code uses them when it creates callouts by passing in them via JSON user
data files.

There are pointers added to the README and schema to find the available
procedures and their descriptions.

Tested:
- The unit tests still work which verify the callout contents when PEL
callouts are created via the message registry.
- Also manually verified PEL procedure callouts look correct when
created from the message registry.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I3e8416956120d4dae1ff40592fd0df4f0285d072

show more ...