PEL: Emit InterfacesAdded on PEL.Entry iface

The constructor used when creating this interface object doesn't emit an
InterfacesAdded signal, even though the optional skipSignal argument
defaults to

PEL: Emit InterfacesAdded on PEL.Entry iface

The constructor used when creating this interface object doesn't emit an
InterfacesAdded signal, even though the optional skipSignal argument
defaults to false. It turns out skipSignal is only used for skipping
PropertiesChanged signals.

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

show more ...

PEL: Add procedure callout for hwp errors

Added infrastructure to enable procedure callout support
for the HWP failure related PEL.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id:

PEL: Add procedure callout for hwp errors

Added infrastructure to enable procedure callout support
for the HWP failure related PEL.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ia688650a1f1c8a184aebb3d258d99bbb1a15d244

show more ...

PEL: Fix pdbg target traversal error path issues

Existing pdbg target traversal call back function continues
traversal incase any attribute read failure on entity path
associated target. This logic

PEL: Fix pdbg target traversal error path issues

Existing pdbg target traversal call back function continues
traversal incase any attribute read failure on entity path
associated target. This logic is wrong, should be continue
collecting available attribute information and stop traversal
in this case.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I999254dc24f4620f710f84a4d476dbccc573516d

show more ...

PEL: Add location code information support for sub FRUs

only for FRU(Field Replaceable Units) devices. Existing SBE
error handling code doesn't provide Location code information
to PEL back-end code

PEL: Add location code information support for sub FRUs

only for FRU(Field Replaceable Units) devices. Existing SBE
error handling code doesn't provide Location code information
to PEL back-end code, and which creates errors in PEL
processing for sub FRU callouts from PHAL requested error PEL.

This commits helps to fix the this problem by using libphal
based api to get location code instead of direct devtree
attribute read. Libphal api uses algorithm to get Location code
for sub FRUs by getting information from the parent FRU.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I7203c8a3175e17e8126448c4d6605b75c07d591d

show more ...

PEL: Fix for error - unable to read PEL ID file

This is a case when PEL daemon can't read pelID file to get the next
pel Id to use. It could be that the file got corrupted during code
update or fact

PEL: Fix for error - unable to read PEL ID file

This is a case when PEL daemon can't read pelID file to get the next
pel Id to use. It could be that the file got corrupted during code
update or factory reset leading to zeros data in file. The fix is to
delete the file as there is already code later to recreate file if
not available.

Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: I42372cc1d79ece5914e7fdb51f3fa2a2d9cb07e7

show more ...

PEL: Add phosphor-power Output Over-current error

Change-Id: I0f952ebdb39f0d5fe41a844de34dae9c1e628227
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>

PEL: Add isolation procedure for power OC

Add in an isolation procedure for an over-current power problem.

Change-Id: I5da1f3e3e9078f4f52fd78469f1fb8948f497e1b
Signed-off-by: Brandon Wyman <bjwyman

PEL: Add isolation procedure for power OC

Add in an isolation procedure for an over-current power problem.

Change-Id: I5da1f3e3e9078f4f52fd78469f1fb8948f497e1b
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>

show more ...

PEL: Write terminating SRC to the progress SRC

Check for incoming pels for severity type 0x51 - Critical error,
System termination. If found, fetch the SRC and add this SRC to
progress SRC interface

PEL: Write terminating SRC to the progress SRC

Check for incoming pels for severity type 0x51 - Critical error,
System termination. If found, fetch the SRC and add this SRC to
progress SRC interface on dbus. In addition set the terminate bit
in BMC created pels only.

Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: I26194a26743263183dcb61e097c745c4705fa006

show more ...

PEL: Add power on and off timeout entries

Add a message registry entry for power off timeout to be used by the
power sequencer application.

The reason code 0xD002 entry should be power on timeout i

PEL: Add power on and off timeout entries

Add a message registry entry for power off timeout to be used by the
power sequencer application.

The reason code 0xD002 entry should be power on timeout instead of power
on failure.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ic7e2a6af0b8162e62b5f7ea6d6d98ae65b272256

show more ...

PEL: Add fsi path maintenance procedure

Maintenance procedures are part of the PEL callout section.
This procedure is used to indicate the problem could be related
to the fsi hardware path.

Signed-

PEL: Add fsi path maintenance procedure

Maintenance procedures are part of the PEL callout section.
This procedure is used to indicate the problem could be related
to the fsi hardware path.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I36ca9f0484e041adcaa542b9ea17b71ab545c6bd

show more ...

PEL: Add SBE code maintenance procedure

Maintenance procedures are part of the PEL callout section. This
procedure is used to indicate the problem is due to code (a bug)
SBE image.

Signed-off-by:

PEL: Add SBE code maintenance procedure

Maintenance procedures are part of the PEL callout section. This
procedure is used to indicate the problem is due to code (a bug)
SBE image.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I8e1a04b2c8aa83c178990331f181ed026ac62db9

show more ...

PEL: Add next level of support maintenance procedure

Maintenance procedures are part of the PEL callout section.
This procedure is indicates isolation not possible, contact
your next level of suppor

PEL: Add next level of support maintenance procedure

Maintenance procedures are part of the PEL callout section.
This procedure is indicates isolation not possible, contact
your next level of support.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: If1d481604e411947e47cb7c9c20d79e938c65db3

show more ...

PEL: pad hex words displayed in error message

In the message registry under "Documentation" and "Message", users can
include the hex words as part of the error message. This change pads
the displaye

PEL: pad hex words displayed in error message

In the message registry under "Documentation" and "Message", users can
include the hex words as part of the error message. This change pads
the displayed hex words so that the full eight digit hex number is
displayed.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I32c4204a1643b585dc1309f67976f4abb44fb04c

show more ...

PEL: update message registry for openpower-hw-diags

Adding "AdditionalDataPropSource" fields so that Hex Words 6-8 are
set properly.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I440

PEL: update message registry for openpower-hw-diags

Adding "AdditionalDataPropSource" fields so that Hex Words 6-8 are
set properly.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I4407a1f792b6d97981ce0188aa0f9c4af78afbe8

show more ...

PEL: allow optional description in "Error Details"

In message_registry.json under "SRC" and "Words6To9", you must define
"AdditionalDataPropSource" for each hex word so that peltool will know
which

PEL: allow optional description in "Error Details"

In message_registry.json under "SRC" and "Words6To9", you must define
"AdditionalDataPropSource" for each hex word so that peltool will know
which additional user data field maps to hex words 6 through 9. You can
also define a "Description" field for each hex word, which will be
displayed in the "Error Details" section of the PEL. Currently, if
"AdditionalDataPropSource" is defined, then "Description" must be
defined as well. Otherwise, peltool will throw an error and none of the
PEL will be parsed, not even the user data sections.

The "Description" fields in the message registry are static and can
only have one definition per "ReasonCode". However, some components
need more dynamic descriptions of the hex words, which can be done with
python modules specifically created for SRC parsing. This parser output
will be displayed in the "SRC Details" section of the PEL. When the
parser is defined, there is no need to display any any additional
descriptions in the "Error Details" section. Unfortunately, if the
"Description" field is omitted then the "AdditionalDataPropSource" field
in the message registry would have to be omitted as well. The consequence
of this is that peltool would not know how to map the additional data
fields to hex words 6 through 9, which leave them as zero and breaks the
SRC parser because there no long is any data to parse.

This commit allows the "AdditionalDataPropSource" fields can be defined
without the "Description" field so that the data for hex words 6
through 9 can mapped correctly and not display any useless information
in the "Error Details" section of the PEL.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I3bf439e5d886df92c90b6d8d13410bbcf485a14d

show more ...

PEL: Remove HWAS_STATE updates from sbe ffdc processing api

Common PEL hardware Deconfiguration record adding function will
take care HWAS_STATE attribute updates. Removing the duplicate code.

Sign

PEL: Remove HWAS_STATE updates from sbe ffdc processing api

Common PEL hardware Deconfiguration record adding function will
take care HWAS_STATE attribute updates. Removing the duplicate code.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I783aaa94ad864b17dd6d9d018a9e0def7a4fe7f7

show more ...

PEL: Add deconfigure records

PHAL enabled systems enabled harwdare deconfigure (set state
to non-functional, do any Deconfigure actions and create a
deconfigure Record in cec devtree) during PEL cre

PEL: Add deconfigure records

PHAL enabled systems enabled harwdare deconfigure (set state
to non-functional, do any Deconfigure actions and create a
deconfigure Record in cec devtree) during PEL create.
This function enabled only for the PEL create request with
required "Deconfigured" key in the callout information.

libphal api is used for creating deconfigure records.

Tested: Verified deconfigure records in the cec devtree

root@xxxx:~# attributes read /proc0 ATTR_HWAS_STATE
ATTR_HWAS_STATE = 0x50000684 0x40

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I77b630da00d9c1f2807aac06a0220e4c14c79fdb

show more ...

PEL: Guard related service action support for SBE logs

Added required fields in the PEL user data section to create
guard record entries for SBE specific error logs

Signed-off-by: Jayanth Othayoth

PEL: Guard related service action support for SBE logs

Added required fields in the PEL user data section to create
guard record entries for SBE specific error logs

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ic49e15f00562414e915f947e3dcd56f4feaf045c

show more ...

PEL: Added phal specific service action support

This commits enables the basic infrastructure to add service
actions(guard/deconfigure) supports for "phal" feature enabled
systems. Also enabled "gu

PEL: Added phal specific service action support

This commits enables the basic infrastructure to add service
actions(guard/deconfigure) supports for "phal" feature enabled
systems. Also enabled "guard" related service , which includes
creating guard D-Bus object using hardware isolation D-Bus api's

To enable this support, PEL users has to include the array of
JSON callouts, which includes the below required informations.
"EntityPath": entity path of the hardware from the PHAL device tree.
"GuardType": Guard type string defined libekb_p10.
"Guarded": boolean, true to create guard records.

Tested: created guard records and verified
root@xxxx:~# guard -l
ID | ERROR | Type | Path
00000001 | 50000684 | fatal | physical:sys-0/node-0/proc-0
00000002 | 50000685 | fatal | physical:sys-0/node-0/proc-1
00000003 | 50000686 | fatal | physical:sys-0/node-0/proc-2
00000004 | 50000687 | fatal | physical:sys-0/node-0/proc-3

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ibc57ae0363cd5fb9facd2ed7049a70806a5b891e

show more ...

PEL: Add guard record entry create function

Added D-Bus wrapper function to create guard record
entry D-Bus object.

hardware isolation API's used no no-reply mode to avoid
cyclic dependency with lo

PEL: Add guard record entry create function

Added D-Bus wrapper function to create guard record
entry D-Bus object.

hardware isolation API's used no no-reply mode to avoid
cyclic dependency with log manager. PEL log already have
the details of guard records properties. For any failure
during record creation is hardware isolation application
is ignored by log manager. User will get details on this
failure by looking hardware isolation log information.

Tested: verified D-Bus create method.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I8c7703dc28aaf7b39793e3bd1dfe4fac374d9ad5

show more ...

PEL: rename feature flag SBE_FFDC_SUPPORTED

Initially SBE_FFDC_SUPPORTED flag introduced to enable
SBE ffdc specific feature from phal feature enabled systems.
There is new requirement to add addi

PEL: rename feature flag SBE_FFDC_SUPPORTED

Initially SBE_FFDC_SUPPORTED flag introduced to enable
SBE ffdc specific feature from phal feature enabled systems.
There is new requirement to add additional callout details
for phal feature enabled systems.
Changing "SBE_FFDC_SUPPORTED" to PHAL feature specific
name "PEL_ENABLE_PHAL".

Tested: verified build with phal enabled option.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ief4b7a97fa148707f48f70f3f99d2f1a04a05f2e

show more ...

PEL: Set commit time for archived pels

set commit time for archived duplicate pels.

Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: I1f01d6ff936b70b08f6cafb65cae45cf1f61ba52

SW538090: PEL: Fix for pel commit time issue

In PEL commit time logic, commit yearMSB was wrongly interpreted
as created time yearMSB.

Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id:

SW538090: PEL: Fix for pel commit time issue

In PEL commit time logic, commit yearMSB was wrongly interpreted
as created time yearMSB.

Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: I27285fa5d65f4fab69090153fdf072bf41133d95

show more ...

PEL: fix sbe ffdc packet offset calculation

Existing SBE ffdc packet offset calculation logic is wrong
and causing parser function failure for multiple packet
use-cases. Correct logic to calculate o

PEL: fix sbe ffdc packet offset calculation

Existing SBE ffdc packet offset calculation logic is wrong
and causing parser function failure for multiple packet
use-cases. Correct logic to calculate offset based on packet
sizen in bytes.

Tested: manually verified PEL log with two ffdc packet case.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ibc82fead1f49fdbf6510e2c704bc3561654aafed

show more ...

PEL:message_registry: Standby power regulator fault

Added message registry entry for for power off due to standby power
regulator fault condition.

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Chang

PEL:message_registry: Standby power regulator fault

Added message registry entry for for power off due to standby power
regulator fault condition.

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: Ic03700551d9fb39c96034766a4853e27198fef97

show more ...