PEL: Remove unnecessary include in peltool.cpp

It wasn't being used.

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

PEL: Restore Resolution property for existing PELs

The Resolution D-Bus property is filled in with PEL callouts, but this
wasn't being done on startup for existing PELs. This commit adds that
functi

PEL: Restore Resolution property for existing PELs

The Resolution D-Bus property is filled in with PEL callouts, but this
wasn't being done on startup for existing PELs. This commit adds that
functionality.

With 2500 PELs this takes a second or less.

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

show more ...

meson: simplify dependencies

Leverage wrapfile `[provide]` directives to simplify the dependency
searching in the meson.build. phosphor-dbus-interfaces now defaults to
enabling all of the project o

meson: simplify dependencies

Leverage wrapfile `[provide]` directives to simplify the dependency
searching in the meson.build. phosphor-dbus-interfaces now defaults to
enabling all of the project options, so there is no need to manually
specify this either.

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

show more ...

Add severity entry for voltage regulator failure

Regulator failure code has severity level upgraded to
critical_system_term. Primary purpose is to show correct codes on the
front panel.

Signed-off-

Add severity entry for voltage regulator failure

Regulator failure code has severity level upgraded to
critical_system_term. Primary purpose is to show correct codes on the
front panel.

Signed-off-by: Mike Capps <mikepcapps@gmail.com>
Change-Id: I29963be399d00f23b7b1941055d78031539dd248

show more ...

PEL: Correct "occured" spelling

"occured" is mispelled.
Change it to "occurred"

Signed-off-by: Michael Lim <youhour@us.ibm.com>
Change-Id: I6dc16a334c71b9681015f8ea7a820ba090f616cd

remove severity level for Blackout

Change-Id: I7c8717d4060b037c76ec44b4d02615c9dc749e49
Signed-off-by: Mike Capps <mikepcapps@gmail.com>

PEL: Add service procedure to find SUE root cause

An SUE indicates a UE has occurred in another area of hardware. This
procedure instructs service to look for previous PEL for the root cause
of the

PEL: Add service procedure to find SUE root cause

An SUE indicates a UE has occurred in another area of hardware. This
procedure instructs service to look for previous PEL for the root cause
of the SUE attention.

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

show more ...

PEL: Create trace wrapper for peltool

In preparation for peltool being compiled for non-BMC platforms where
libphosphor_logging.so isn't available, create a wrapper function for
tracing so phosphor:

PEL: Create trace wrapper for peltool

In preparation for peltool being compiled for non-BMC platforms where
libphosphor_logging.so isn't available, create a wrapper function for
tracing so phosphor::logging::log() isn't directly used by the code that
is part of peltool.

For now, the wrapper will just call phosphor::logging::log, but in the
future will be changed to call std::cerr when not on the BMC.

A few files were changed to make use of the new calls. Others will be
done with future commits. Only the code that is built into peltool
needs to use this. This mostly consists of the PEL section classes.

Using this new API does mean no extra data can be stored in the journal
metadata, as the systemd journal may not be available on some platforms
the tool may need to run on, such as AIX. Instead, the data can just be
added into the trace string itself.

In a future commit, the meson.build file will be refactored to remove
the libphosphor_logging dependency so the build will fail if a call to
the phosphor-logging's log() is made within peltool code.

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

show more ...

openpower-pels: add host quiesce error

To ensure we always have at least one error log when halting in the host
quiesce state, log this new error.

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

openpower-pels: add host quiesce error

To ensure we always have at least one error log when halting in the host
quiesce state, log this new error.

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

show more ...

openpower-pels: add systemd target failure logs

These are logs generated by the phosphor-state-manager systemd target
monitor when it sees a monitored target fail. These are somewhat generic
logs le

openpower-pels: add systemd target failure logs

These are logs generated by the phosphor-state-manager systemd target
monitor when it sees a monitored target fail. These are somewhat generic
logs letting the user know that something critical has failed, and to
look at other logs for the specific reason.

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

show more ...

openpower-pels: add manufacturing security check log

This is a predictive error only logged in the manufacturing environment
and is used to let them know something is not configured correctly on
the

openpower-pels: add manufacturing security check log

This is a predictive error only logged in the manufacturing environment
and is used to let them know something is not configured correctly on
the system in regards to secure boot.

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

show more ...

openpower-pels: add critical service failure log

This log indicates a service which is deemed critical has entered the
failed state and the BMC is now in an undefined state due to that.

Signed-off-

openpower-pels: add critical service failure log

This log indicates a service which is deemed critical has entered the
failed state and the BMC is now in an undefined state due to that.

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

show more ...

openpower-pels: add pinhole reset log

This log was added recently to record the fact that a pinhole reset was
initiated via the op-panel by the user. It is used to assist in debug
when looking at fi

openpower-pels: add pinhole reset log

This log was added recently to record the fact that a pinhole reset was
initiated via the op-panel by the user. It is used to assist in debug
when looking at first failure data capture.

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

show more ...

openpower-pels: document chassis power bad log

This error was introduced recently in the phosphor-state-manager
repository to notify the user when a system is unable to power on the
chassis due to a

openpower-pels: document chassis power bad log

This error was introduced recently in the phosphor-state-manager
repository to notify the user when a system is unable to power on the
chassis due to a power failure of some sort.

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

show more ...

PEL: Remove PowerFault from message entries, registries, and code

The PowerFault flag is deprecated and should be removed in both the
registry and code references. Its functionality is superseded by

PEL: Remove PowerFault from message entries, registries, and code

The PowerFault flag is deprecated and should be removed in both the
registry and code references. Its functionality is superseded by the
critical_system severity level.

Signed-off-by: Mike Capps <mikepcapps@gmail.com>
Change-Id: I1bc1898d9589e0678b5a37b87289c6588859f2ee

show more ...

PEL: add possible subsystems to message registry

For openpower-hw-diags, the subsystem field is created dynamically based
on the callouts added to the PEL. This change adds a field in the
message re

PEL: add possible subsystems to message registry

For openpower-hw-diags, the subsystem field is created dynamically based
on the callouts added to the PEL. This change adds a field in the
message registry to list all possible subsystems that can be used for
each reference code used by openpower-hw-diags.

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

show more ...

PEL: Support 'PossibleSubsystems' in msg registry

Add a 'PossibleSubsystems' field to the message registry schema where
someone can list which subsystems they might pass into the PEL_SUBSYSTEM
Addit

PEL: Support 'PossibleSubsystems' in msg registry

Add a 'PossibleSubsystems' field to the message registry schema where
someone can list which subsystems they might pass into the PEL_SUBSYSTEM
AdditionalData property field when creating a PEL.

The PossibleSubsystems value will be used by a off-BMC script that
generates field documentation for SRCs, so it knows what all SRC ASCII
string values are possible for that entry since the subsystem is part of
them. For example, if that field was ['processor', 'memory'], then that
means the possible SRCs are BD10AAAA and BD20AAAA for reason code
'AAAA'.

The Subsystem and PossibleSubsystems fields are mutually exclusive in
the message registry, so code changes had to be made to support the
subsystem field now being optional.

There is now a chance that even though the subsystem is supposed to be
passed in using PEL_SUBSYSTEM, it isn't. In that case, the 'Other'
subsystem will be used, since it seems fairly generic.

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

show more ...

PEL: Shorten D-Bus timeout value

There are several D-Bus method calls made when creating a PEL to collect
data, and if one of the daemons called into is hung, then
phosphor-log-manager can also hang

PEL: Shorten D-Bus timeout value

There are several D-Bus method calls made when creating a PEL to collect
data, and if one of the daemons called into is hung, then
phosphor-log-manager can also hang up to the default timeout value of
25s and an error will be returned to the PEL creator even though the PEL
will eventually be created successfully.

This can cause all sorts of issues for the callers, such as preventing
the PEL from begin reported to the hardware management console to
causing a boot fail because hostboot gets a failure trying to log an
error and shuts down.

To help prevent this, change the timeout value of all D-Bus calls to 10
seconds down from the 25. This would allow two timeouts to occur during
the creation of a PEL without hitting the 25s timeout that callers use.
When timeouts are hit creating a PEL, that field just won't be filled in
and the PEL can otherwise be created with no issues.

Ten seconds was chosen to allow two failures to occur while still
allowing plenty of time for completion from a healthy daemon. Also it
seems like if an operation doesn't complete within 10s it wouldn't
complete within 25 either.

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

show more ...

PEL: Remove severity from power supply errors

In order to allow power supply errors to be issued at critical severity
after 12V power good failure, remove the severity from the entries in
the messag

PEL: Remove severity from power supply errors

In order to allow power supply errors to be issued at critical severity
after 12V power good failure, remove the severity from the entries in
the message registry. The failures will now be issued with the severity
passed at message creation.

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

show more ...

PEL: Only quiesce for certain subsystems

When QuiesceOnHwError is enabled, only actually quiesce if the PEL is
created by specific subsystems. Manufacturing wants to allow some
errors to callout ha

PEL: Only quiesce for certain subsystems

When QuiesceOnHwError is enabled, only actually quiesce if the PEL is
created by specific subsystems. Manufacturing wants to allow some
errors to callout hardware and not quiesce based on who is creating
them.

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

show more ...

PEL: Removed hardcoded RTC battery callout

The sensor monitoring code will already follow inventory associations to
add callouts for threshold alarms, so it isn't necessary to hardcode
them in the m

PEL: Removed hardcoded RTC battery callout

The sensor monitoring code will already follow inventory associations to
add callouts for threshold alarms, so it isn't necessary to hardcode
them in the message registry anymore.

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

show more ...

PEL: Add GPIOError to message_registry

Any GPIO line failed to be found or read will log PEL
with this error interface.
This following commit introduced this new error-
https://gerrit.openbmc-projec

PEL: Add GPIOError to message_registry

Any GPIO line failed to be found or read will log PEL
with this error interface.
This following commit introduced this new error-
https://gerrit.openbmc-project.xyz/c/openbmc/openpower-vpd-parser/+/51475

Signed-off-by: Alpana Kumari <alpankum@in.ibm.com>
Change-Id: Iaa56e2354e77deb268bfde0df95f873bc52eb28f

show more ...

PEL: Add recovered test error to msg registry

This is being added so the test team can inject recovered errors.

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

PEL: Add recovered test error to msg registry

This is being added so the test team can inject recovered errors.

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

show more ...

PEL: Change python plugin error traces to debug

There's been lots of complaints and questions about what these are, if
they're important, and why they show up so much so just make them debug
traces

PEL: Change python plugin error traces to debug

There's been lots of complaints and questions about what these are, if
they're important, and why they show up so much so just make them debug
traces. The plugin parser developers can still enable debug traces to
see the errors if they notice some unparsed sections.

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

show more ...

PEL: Sort & display PELs based on commit timestamp

Its recommended to sort and display PELs based on commit
timestamp instead of pel Ids as some subsystem (like hostboot)
get peltool output always s

PEL: Sort & display PELs based on commit timestamp

Its recommended to sort and display PELs based on commit
timestamp instead of pel Ids as some subsystem (like hostboot)
get peltool output always showed last.

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

show more ...