History log of /openbmc/phosphor-logging/extensions/ (Results 301 – 325 of 682)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
8133134b05-Oct-2021 Matt Spinler <spinler@us.ibm.com>

PEL: Low battery voltage registry entry

Add an entry for the low RTC battery voltage. This is the only voltage
sensor that implements the critical low voltage threshold on IBM
systems.

Signed-off-

PEL: Low battery voltage registry entry

Add an entry for the low RTC battery voltage. This is the only voltage
sensor that implements the critical low voltage threshold on IBM
systems.

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

show more ...

66491c6106-Oct-2021 Patrick Williams <patrick@stwcx.xyz>

catch exceptions as const

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

242be74016-Sep-2021 Vijay Lobo <vijaylobo@gmail.com>

PEL: Update pel_values to support bmcweb

Updates done to support display of Message property in bmcweb.
With the redfish command the message property showed up as
--old-
"Message": "xyz.openbmc_proj

PEL: Update pel_values to support bmcweb

Updates done to support display of Message property in bmcweb.
With the redfish command the message property showed up as
--old-
"Message": "xyz.openbmc_project.Power.PowerSupply.Error.InputFault"
--New--
"Message": "110015F0 event in subsystem: Power Supply",

Note that the "Power Supply" is a $subsystem property and had ':' in the
description, to enhance readability the $subsystem for CEC Hardware is
update with '-' in place of ':'.

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

show more ...

fd0cf4f719-Sep-2021 Jayanth Othayoth <ojayanth@in.ibm.com>

PEL: Add error message registry entry for SBE boot timeout

Adding error entry in the message registry JSON file for
SBE boot timeout failure.

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

PEL: Add error message registry entry for SBE boot timeout

Adding error entry in the message registry JSON file for
SBE boot timeout failure.

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

show more ...

abc88b0219-Sep-2021 Jayanth Othayoth <ojayanth@in.ibm.com>

PEL: Add error message registry entry for SBE boot failure

Adding error entry in the message registry JSON file for
SBE boot failures with FFDC information provided by SBE.

Signed-off-by: Jayanth O

PEL: Add error message registry entry for SBE boot failure

Adding error entry in the message registry JSON file for
SBE boot failures with FFDC information provided by SBE.

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

show more ...

2c36fddc21-Sep-2021 Sumit Kumar <sumit_kumar@in.ibm.com>

PEL: Store system boot state in user data section

For every incoming pel data interface watches the dbus property
that includes the latest boot progress/state value. This value would be
captured and

PEL: Store system boot state in user data section

For every incoming pel data interface watches the dbus property
that includes the latest boot progress/state value. This value would be
captured and stored in user data section of pel.

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

show more ...

8034ddeb10-Sep-2021 Andrew Geissler <geissonator@yahoo.com>

PEL:message_registry: add new HostNotRunning error

The following commit introduced this new error:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/45829

0x3400 was chosen to

PEL:message_registry: add new HostNotRunning error

The following commit introduced this new error:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/45829

0x3400 was chosen to match up with the FSP SMGR component ID.

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

show more ...

b2e541ee31-Aug-2021 Vijay Lobo <vijaylobo@gmail.com>

PEL.Entry update hidden property setting

The condition to set hidden flag depends on the severity type and the
action flag setting. This change is to make sure that the hidden
property is set using

PEL.Entry update hidden property setting

The condition to set hidden flag depends on the severity type and the
action flag setting. This change is to make sure that the hidden
property is set using various conditions and not just hidden action flag.

Tested:
using busctl injected different types of errors and made sure that the
hidden property is set accordingly.

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

show more ...

9d43a72724-Aug-2021 Sumit Kumar <sumit_kumar@in.ibm.com>

PEL: Update bmc & platform dump status in SRC section

With every PEL creation, the status of bmc and platform dumps -
Hardware and Hypervisor would be checked and status bits in SRC
section updated

PEL: Update bmc & platform dump status in SRC section

With every PEL creation, the status of bmc and platform dumps -
Hardware and Hypervisor would be checked and status bits in SRC
section updated accordingly.

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

show more ...

e99a4fd602-Sep-2021 Patrick Williams <patrick@stwcx.xyz>

exception: switch to public sdbus exception

SdBusError was intended to be a private error type inside sdbusplus.
Switch all catch locations to use the general sdbusplus::exception type.

Signed-off-

exception: switch to public sdbus exception

SdBusError was intended to be a private error type inside sdbusplus.
Switch all catch locations to use the general sdbusplus::exception type.

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

show more ...

2fb1021122-Aug-2021 Vijay Lobo <vijaylobo@gmail.com>

PEL.Entry - Add managementSystemAck property

Add managementSystemAck property to PEL.Entry interface to support HMC
acknowledgement of event receipt.

Tested:
1. Created a PEL log using busctl and s

PEL.Entry - Add managementSystemAck property

Add managementSystemAck property to PEL.Entry interface to support HMC
acknowledgement of event receipt.

Tested:
1. Created a PEL log using busctl and set-property managementSystemAck
to true. Verified that the flag is set by using peltool
Result:(output of peltool)
"Host Transmission": "Not Sent",
"HMC Transmission": "Acked"
Restarted phosphor-log-manager and verified that the flag is true.

2. Generated PEL using RAWPEL and verified all the steps as in 1.

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

show more ...

b63f75b718-Aug-2021 Rashmica Gupta <rashmica.g@gmail.com>

PEL: Add altitude PEL registry entries

These will only be used on systems that use PELs and have the virtual
altitude sensor. The errors come from the sensor-monitor app.

Signed-off-by: Rashmica Gu

PEL: Add altitude PEL registry entries

These will only be used on systems that use PELs and have the virtual
altitude sensor. The errors come from the sensor-monitor app.

Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
Change-Id: I5fec3ec86a084f8c62f52194f2826c0565be32eb

show more ...

d54fd73a20-Jul-2021 Andrew Geissler <geissonator@yahoo.com>

PEL:message_registry: add new HostRunning error

The following commit introduced this new error:
https://gerrit.openbmc-project.xyz/c/openbmc/openpower-proc-control/+/44352

This officially defines

PEL:message_registry: add new HostRunning error

The following commit introduced this new error:
https://gerrit.openbmc-project.xyz/c/openbmc/openpower-proc-control/+/44352

This officially defines it within the PEL registry to ensure the
appropriate documentation accompanies it.

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

show more ...

b615b17e12-Aug-2021 Zane Shelley <zshelle@us.ibm.com>

PEL: removed openpower-hw-diags registry SRC desc

The description in the registery is no longer relevent because the
signature description of the error is now being displayed with the
PEL SRC parser

PEL: removed openpower-hw-diags registry SRC desc

The description in the registery is no longer relevent because the
signature description of the error is now being displayed with the
PEL SRC parser.

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

show more ...

ea2873dd18-Aug-2021 Matt Spinler <spinler@us.ibm.com>

PEL: Change BMCSP01 maint procedure to BMC0001

This name change allows 4 characters of uniqueness instead of just 2.

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

PEL: Change BMCSP01 maint procedure to BMC0001

This name change allows 4 characters of uniqueness instead of just 2.

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

show more ...

479b692717-Aug-2021 Matt Spinler <spinler@us.ibm.com>

PEL: Remove 'no_vpd_for_fru' maintenance procedure

This procedure was being used in a callout when the location code could
not be found on an inventory item. The code was changed to just not add
a

PEL: Remove 'no_vpd_for_fru' maintenance procedure

This procedure was being used in a callout when the location code could
not be found on an inventory item. The code was changed to just not add
a callout in this case.

This was done for the following reasons:
1) There's no expected reason that the inventory would be missing a
location code for a valid inventory path.
2) There wasn't a way to give a hint to the end user about what the
callout should be in that case. Usually maintenance procedures should
have steps one can take to still do the appropriate replacement.
3) Because of 1), this case indicates a bad inventory path passed in by
the caller. Theoretically there is a way to have a 'bmc_code'
callout, but that wouldn't be appropriate to add in this log since
the intent of this one is for another problem.
3a) There is no way to create a new error log from inside a PEL section,
and I don't think this one case warrants coming up with a way to do
so.
4) The inventory path in question is still being added into a UserData
section so that development can debug it.

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

show more ...

6741692119-Jul-2021 Matt Spinler <spinler@us.ibm.com>

PEL: Delete raw PEL file after use

To avoid race conditions with the PLDM daemon deleting this file before
this code has a chance to use it, this code will now delete the file
and the PLDM daemon wi

PEL: Delete raw PEL file after use

To avoid race conditions with the PLDM daemon deleting this file before
this code has a chance to use it, this code will now delete the file
and the PLDM daemon will make a change not to.

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

show more ...

afb1b46f21-Jul-2021 Vijay Lobo <vijaylobo@gmail.com>

PEL: Add hidden and subsystem properties

This story adds a new PELEntry interface
org.open_power.Logging.PEL.Entry on existing PEL entry. Then we add 2
properties with their values initialized durin

PEL: Add hidden and subsystem properties

This story adds a new PELEntry interface
org.open_power.Logging.PEL.Entry on existing PEL entry. Then we add 2
properties with their values initialized during the creation of the Interface.

Tested:
1. Verified that the new PEL creation with recoverable error sets the new
attribute in the PEL.entry Interface.
2. Restarted the phosphor-log-manager daemon and made sure the flag is set
with the new Interface created for d-bus
3. Tested with passing a RAWPEL to create from file system and verified
that the hidden attribute is set accordingly on the PEL.entry Interface.
4. Copied the new format error to a system with old code and restored
the error log to make sure it does not crash.
5. Validated both hidden and subsystem properties.

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

show more ...

2ccdcef931-Jul-2021 Sumit Kumar <sumit_kumar@in.ibm.com>

PEL: Guard against hostboot sending down duplicate PEL Ids

This commit is to guard against hostboot sending down PEL Id
that we already have in our repository. This caused PEL to
get orphaned in the

PEL: Guard against hostboot sending down duplicate PEL Ids

This commit is to guard against hostboot sending down PEL Id
that we already have in our repository. This caused PEL to
get orphaned in the filesystem without a corresponding valid
openbmc event log Id.
The action is to move such PELs to archive folder.

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

show more ...

7f1ec94d28-Jul-2021 Shawn McCarney <shawnmm@us.ibm.com>

PEL: Add regulator phase faults to registry

Add two new voltage regulator errors to the message registry:
* N phase fault: No redundant phases remain
* N+1 phase fault: One redundant phase remains

PEL: Add regulator phase faults to registry

Add two new voltage regulator errors to the message registry:
* N phase fault: No redundant phases remain
* N+1 phase fault: One redundant phase remains

The N+1 phase fault is normally treated as an informational error since
the voltage regulator still has some redundancy remaining. However, if
the system is in manufacturing isolation mode, the severity is increased
to be predictive. This allows manufacturing to easily detect the error
and avoid shipping a voltage regulator that has already lost some
redundancy.

Tested:
* Created N phase fault error using busctl command and the
xyz.openbmc_project.Logging.Create interface.
* Created N+1 phase fault error using busctl command and the
xyz.openbmc_project.Logging.Create interface.
* System in normal mode
* System in manufacturing isolation mode

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

show more ...

76198a2e15-Jul-2021 Sumit Kumar <sumit_kumar@in.ibm.com>

PEL: Set critical association to object paths

Create critical association to inventory d-bus objects.
This is being done for the items in callouts that need
their service indicators turned on in its

PEL: Set critical association to object paths

Create critical association to inventory d-bus objects.
This is being done for the items in callouts that need
their service indicators turned on in its code, and
that the other association endpoint is the chasis so
it can be used for health rollup.

The associations property on the
xyz.openbmc_project.Association.Definitions interface
will have following entry added to called out object path:
["health_rollup", "critical",
"/xyz/openbmc_project/inventory/system/chassis"]

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

show more ...

ebc91be627-Jul-2021 Jayanth Othayoth <ojayanth@in.ibm.com>

PEL: fix bitbake failures related to commit e0538848

fatal error: phosphor-logging/log.hpp: No such file
or directory.

Fix: Added phosphor_logging_dep to pel dependencies.

Tested: Unit testing is

PEL: fix bitbake failures related to commit e0538848

fatal error: phosphor-logging/log.hpp: No such file
or directory.

Fix: Added phosphor_logging_dep to pel dependencies.

Tested: Unit testing is successfull.
Created and verified SBE failure related PEL.

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

show more ...

8fd187e426-Jul-2021 William A. Kennington III <wak@google.com>

build: Target c++ arguments specifically where they are needed

This fixes the build with phal enabled, since it tries to add global
project cpp_args after targets have already been declared.

Change

build: Target c++ arguments specifically where they are needed

This fixes the build with phal enabled, since it tries to add global
project cpp_args after targets have already been declared.

Change-Id: I907fbd40a82725da4e751b82c66c71c602dd2018
Signed-off-by: William A. Kennington III <wak@google.com>

show more ...

5c0c917607-Apr-2021 Adriana Kobylak <anoo@us.ibm.com>

PEL: Add phosphor-power NotSupported error

Add an entry to describe the NotSupported error from the phosphor-power
app. This error occurs when the power supply monitoring app detects that
the combin

PEL: Add phosphor-power NotSupported error

Add an entry to describe the NotSupported error from the phosphor-power
app. This error occurs when the power supply monitoring app detects that
the combination of power supplies in the system is not supported, such
as having mismatched models, or less than expected number of power
supplies.

Tested: Forced the power supply error and verified that the new SRC was
created, journal output:
Apr 07 18:58:06 p10bmc phosphor-log-manager[285]: Created PEL 0x50000002
(BMC ID 2) with SRC 110015F7

Error log:
$ curl -k -H "X-Auth-Token: $token" \
https://${bmc}/xyz/openbmc_project/logging/entry/2
...
"Id": 2,
"Message":
"xyz.openbmc_project.Power.PowerSupply.Error.NotSupported",
"Path":
"/var/lib/phosphor-logging/extensions/pels/logs/2021040718580625_50000002",

Change-Id: I96d4d7fd91686761487bc56a019ea1e8f83da5cb
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>

show more ...

f3e619a813-Jul-2021 Jayanth Othayoth <ojayanth@in.ibm.com>

PEL: Add error message registry entry for devtree backup

Adding error entry in the message registry JSON file for
devtree backup failure . During the code update need to
save backup copy of phal dev

PEL: Add error message registry entry for devtree backup

Adding error entry in the message registry JSON file for
devtree backup failure . During the code update need to
save backup copy of phal devtree r/w attributes and update
to new device tree file in the reboot path.
This error entry indicates the failure during this data backup.

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

show more ...

1...<<11121314151617181920>>...28