PEL: Update README.md with latest functionality

Describe how the code will clear the deconfig flag for replaced fans and
power supplies.

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

PEL: Update README.md with latest functionality

Describe how the code will clear the deconfig flag for replaced fans and
power supplies.

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

show more ...

Address markdownlint warnings

Addressed markdownlint warnings reported by
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Tested: Verified and fixed warnings using
"../openb

Address markdownlint warnings

Addressed markdownlint warnings reported by
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Tested: Verified and fixed warnings using
"../openbmc-build-scripts/scripts/format-code.sh --enable markdownlint"

Change-Id: I6f8fe65373c748b907b9ca55c527800583983538
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

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

show more ...

PEL: Update UserData parser example

Empty JSON dictionaries are ignored by the peltool code so put some data
in the example dictionary.

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

PEL: Update UserData parser example

Empty JSON dictionaries are ignored by the peltool code so put some data
in the example dictionary.

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

show more ...

PEL: Pass in subsystem to use with additional data

There is a requirement to pass in the subsystem to use with
the additional data field. In the process update the user
header code and SRC with the

PEL: Pass in subsystem to use with additional data

There is a requirement to pass in the subsystem to use with
the additional data field. In the process update the user
header code and SRC with the passed-in subsystem value
instead from the message registry.

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

show more ...

PEL: Deleted PELs moved to new folder under logs

- PELs whose corresponding event logs have been deleted
will be available in the archive folder.
- Archive folder size is tracked under sizeWarn

PEL: Deleted PELs moved to new folder under logs

- PELs whose corresponding event logs have been deleted
will be available in the archive folder.
- Archive folder size is tracked under sizeWarning() function.
- Archived PELs log can be viewed using peltool with flag --archive.
- PELs deleted using peltool is not archived.
- Updated README.md

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

show more ...

PEL: enable base infrastructure for SBE FFDC base PEL create

This commits provides the base infrastructure for SBE FFDC based
on createPELWithFFDCFiles`D-Bus method on the
org.open_power.Logging.PEL

PEL: enable base infrastructure for SBE FFDC base PEL create

This commits provides the base infrastructure for SBE FFDC based
on createPELWithFFDCFiles`D-Bus method on the
org.open_power.Logging.PEL.

More details related to usage of this interface is documented
as part of extensions/openpower-pels/README.md.

In the PEL create interface if the type is custom and subtype
is 0xCB, PEL class function invokes SBE FFDC function to process
SBE FFDC to extract Hardware procedure added user data section and
callouts. SBE FFDC class appends the callout json and create
user data file based FFDC information and continue the normal
PEL create function.

SCOPE of this commit:
- Add base infrastructure and control build only for "phal" supported
systems. "phal" feature is mandatory requirement for processing
SBE FFDC.
- Add SBE FFDC raw information in PEL user data section

To enable this feature use the below meson build options
meson build -Dopenpower-pel-extension=enabled -Dphal=enabled

Tested:

"Error Details": {
"Message":"chipop timeout reported during SBE communication",
"SRC6": [
"0x2",
"[0:15] chip position, [16:23] command class,
[24:31] command type"
]
},

"User Data 2": {
"Section Version": "1",
"Sub-section type": "203",
"Created by": "0x3500",
"Data": [
"FF DC 00 12 00 00 A1 01 00 8E CE 72 00 00 FF FE | ...........r....",
"00 00 00 04 00 00 00 00 00 00 00 04 00 00 00 00 | ................",
"00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 02 | ................",
"00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 04 | ................",
"00 00 00 00 00 00 00 00 | ........"
]
}

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

show more ...

PEL: Support user supplied flag to indicate a fatal/terminating

User can supply SEVERITY_DETAIL=SYSTEM_TERM as part
of AdditionalData entry in the event log to set the
severity level in User Header

PEL: Support user supplied flag to indicate a fatal/terminating

User can supply SEVERITY_DETAIL=SYSTEM_TERM as part
of AdditionalData entry in the event log to set the
severity level in User Header of PEL

Tested: I ran unit test using docker. Also tested manually
by setting D-bus event log

Change-Id: I9205c084c32576734c2b5b4c79c273f8defde9d4
Signed-off-by: Vijay Lobo <vijaylobo@gmail.com>

show more ...

PEL: Support creator supplied power fault flag

User can supply POWER_THERMAL_CRITICAL_FAULT=TRUE as part
of AdditionalData entry in the event log to set the power
fault bit in PEL

Tested: I ran uni

PEL: Support creator supplied power fault flag

User can supply POWER_THERMAL_CRITICAL_FAULT=TRUE as part
of AdditionalData entry in the event log to set the power
fault bit in PEL

Tested: I ran unit test using docker. Also tested manually
by setting D-bus event log

Change-Id: Ifa03f091a7d1efcc67f181c2be1cc0a6240891e1
Signed-off-by: Vijay Lobo <vijaylobo@gmail.com>

show more ...

PEL: Document CALLOUT_PRIORITY

In the README, explain how the CALLOUT_PRIORITY AdditionalData keyword
can be used to dictate the priority of the callout passed in with
CALLOUT_INVENTORY_PATH, and ho

PEL: Document CALLOUT_PRIORITY

In the README, explain how the CALLOUT_PRIORITY AdditionalData keyword
can be used to dictate the priority of the callout passed in with
CALLOUT_INVENTORY_PATH, and how callouts will be sorted by priority.

The update itself explains how this is useful.

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

show more ...

pel: fail boot on host errors

Document requirement that host PELs should cause the boot to fail if the
QuiesceOnHwError setting is enabled

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Cha

pel: fail boot on host errors

Document requirement that host PELs should cause the boot to fail if the
QuiesceOnHwError setting is enabled

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I917dc87cce4dc0e12a6fe13d961373053d0d9a8e

show more ...

PEL: Don't fix user specified action flags

Previously, the PEL object would never trust the action flags field
specified in the PEL registry and would always set some of the flags in
it itself based

PEL: Don't fix user specified action flags

Previously, the PEL object would never trust the action flags field
specified in the PEL registry and would always set some of the flags in
it itself based on a set of rules.

It turns out there are some cases where what the user needs doesn't
match the rules, so now only fix up the action flags if they weren't
specified in the registry and leave the flags alone if they were.

Most PELs in the registry should be able to leave out the action flags
field and let the PEL code set them.

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

show more ...

PEL: Document how to pass in multiple callouts

This commit documents how an error log creator can specify multiple
callouts when creating a PEL. At a high level, this is done by
specifying them in

PEL: Document how to pass in multiple callouts

This commit documents how an error log creator can specify multiple
callouts when creating a PEL. At a high level, this is done by
specifying them in JSON and passing that JSON in as an FFDC file.

The JSON format supports multiple callouts of different priorities, and
allows the callouts to be FRUs, symboliic FRUs, or maintenance
procedures. It also has options to guard hardware and to specify
hardware was deconfigured.

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

show more ...

PEL: README instructions for adding python modules

Provide file structure and sample setup.py script for python modules to be
imported by setuptools.

Also added documentation to support UserData an

PEL: README instructions for adding python modules

Provide file structure and sample setup.py script for python modules to be
imported by setuptools.

Also added documentation to support UserData and SRC parsing modules.

Signed-off-by: Harisuddin Mohamed Isa <harisuddin@gmail.com>
Change-Id: Id32a6155d7d3ecf84647489c5f4125ad1f47ba94

show more ...

PEL: Document PEL retention and pruning rules

The amount of disk space that PELs can take up on the BMC as well as the
total number of PELs will be capped. Document what happens when this
cap is re

PEL: Document PEL retention and pruning rules

The amount of disk space that PELs can take up on the BMC as well as the
total number of PELs will be capped. Document what happens when this
cap is reached.

At a high level, this includes removing old PELs from several
categories until those categories take up only a certain percentage of
the allocated space.

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

show more ...

PEL: Document the supported dev callout types

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

PEL: Document saving FFDC in UserData sections

Describe how FFDC (First Failure Data Capture) data can be
placed into UserData sections in PELs via a specific D-Bus
creation method.

Signed-off-by:

PEL: Document saving FFDC in UserData sections

Describe how FFDC (First Failure Data Capture) data can be
placed into UserData sections in PELs via a specific D-Bus
creation method.

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

show more ...

PEL: Explain PEL callouts

Update the READMEs to describe how callouts can be added to PELs.

At a high level, they can be added by specifying them completely in
AdditionalData fields like CALLOUT_IN

PEL: Explain PEL callouts

Update the READMEs to describe how callouts can be added to PELs.

At a high level, they can be added by specifying them completely in
AdditionalData fields like CALLOUT_INVENTORY_PATH, by specifying them
completely in the PEL message registry JSON, or by a combination of the
2.

A future commit will add the new JSON schema.

Note, there is still a use case that maybe isn't covered here, and that
is when an application like openpower-hw-diags gets its full callout
list, including priorities, from its own data. This should cover
everything else though.

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

show more ...

PEL: Add sysinfo UserData section to README

Mention the UserData section that is added to every BMC PEL that
contains system information in the README where it lists the sections
created.

Signed-of

PEL: Add sysinfo UserData section to README

Mention the UserData section that is added to every BMC PEL that
contains system information in the README where it lists the sections
created.

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

show more ...

PEL: Add ESEL event log keyword to README

Explain how the ESEL keyword can be used in the Additional Data event
log property to send in PEL data.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Ch

PEL: Add ESEL event log keyword to README

Explain how the ESEL keyword can be used in the Additional Data event
log property to send in PEL data.

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

show more ...

PEL: Validate the Action Flags field

According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is bein

PEL: Validate the Action Flags field

According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.

In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.

The rules being followed are documented in the PEL readme.

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

show more ...

PEL: Document UserData sections

Add a section in the PEL README to document the UserData sections
that will be created in every new PEL.

Change-Id: I9ff9a69f1d22b56aa8bb9d559802d0595d787c0a
Signed-

PEL: Document UserData sections

Add a section in the PEL README to document the UserData sections
that will be created in every new PEL.

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

show more ...

PEL: Add message registry README

This README describes the message registry in an easier to read way than
what is buried in the JSON schema.

The commit also provides a file to document which compon

PEL: Add message registry README

This README describes the message registry in an easier to read way than
what is buried in the JSON schema.

The commit also provides a file to document which component IDs are
used by which repositories/applications.

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

show more ...

PELs: Document _PID as an AdditionalData keyword

When one uses the new `Create` D-Bus API to create an event
log that will be converted into a PEL, the log-manager daemon
will not know the PID of th

PELs: Document _PID as an AdditionalData keyword

When one uses the new `Create` D-Bus API to create an event
log that will be converted into a PEL, the log-manager daemon
will not know the PID of the creator, unlike when the 'commit'
or 'report' shared library APIs are used.

Document this method for allowing the creator to pass in their
PID, which they can find with getpid(), if they want their PID
in an event log and in the corresponding PEL.

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

show more ...

Add initial OpenPower PEL specific documentation

Add a markdown file just for PEL specific documentation
starting with how to specify a raw PEL in an OpenBMC event log.

Signed-off-by: Matt Spinler

Add initial OpenPower PEL specific documentation

Add a markdown file just for PEL specific documentation
starting with how to specify a raw PEL in an OpenBMC event log.

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

show more ...