Home
last modified time | relevance | path

Searched refs:PELs (Results 1 – 15 of 15) sorted by relevance

/openbmc/phosphor-logging/extensions/openpower-pels/
H A DREADME.md3 This extension will create PELs for every OpenBMC event log. It is also possible
210 ## Default UserData sections for BMC created PELs
525 maximum number of PELs, remove PELs down to 80% of the maximum.
530 - Pass 1. Remove HMC acknowledged PELs.
531 - Pass 2. Remove OS acknowledged PELs.
532 - Pass 3. Remove PHYP acknowledged PELs.
533 - Pass 4. Remove all PELs.
719 size exceeds warning size all archived PELs will be deleted.
723 ## Handling PELs for hot plugged FRUs
729 includes the PELs created for the fails leading to the degraded mode. These PELs
[all …]
/openbmc/openbmc-test-automation/docs/
H A Dopenbmc_test_tools.md208 -a Display all PELs
209 -l List PELs
210 -n Show number of PELs
212 -h Include hidden PELs
213 -f,--info Include informational PELs
214 -t,--termination List only critical system terminating PELs
216 -D,--delete-all Delete all PELs
219 --archive List or display archived PELs
/openbmc/phosphor-logging/extensions/openpower-pels/tools/
H A Dpeltool.cpp478 std::vector<std::pair<uint32_t, uint64_t>> PELs; in printPELs() local
491 PELs.emplace_back(fileNameToPELId((*it).path().filename()), in printPELs()
497 std::sort(PELs.begin(), PELs.end(), in printPELs()
516 std::for_each(PELs.rbegin(), PELs.rend(), buildJSON); in printPELs()
520 std::for_each(PELs.begin(), PELs.end(), buildJSON); in printPELs()
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/PEL/
H A DEntry.interface.yaml32 PEL. It is the unique ID for a single event. Multiple PELs can be
49 PELs created by subsystems other than the BMC, this can be different
/openbmc/phosphor-logging/
H A Dmeson.options6 description: 'Create PELs',
H A DREADME.md570 - OpenPower PELs
/openbmc/openbmc-test-automation/bin/plug_ins/Stop/
H A Dparm_def7 # "pel_stop_file_path" may contain the path to a file with specifications for which PELs warrant st…
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/
H A DPEL.interface.yaml117 to the PEL log ID for BMC created PELs.
180 The host does not have room for more PELs at this time.
/openbmc/phosphor-logging/test/openpower-pels/
H A Dpel_manager_test.cpp234 "PELs": in TEST_F()
960 "PELs": in TEST_F()
1060 "PELs": in TEST_F()
1140 "PELs": in TEST_F()
1298 "PELs": in TEST_F()
1401 "PELs": in TEST_F()
H A Dregistry_test.cpp31 "PELs":
H A Dsrc_test.cpp36 "PELs":
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DREADME.md3 On the BMC, PELs are created from the standard event logs provided by
35 created PELs.
248 This is looked at by the software that creates the periodic PELs that indicate a
630 4. One can test what PELs are generated from these new entries without writing
/openbmc/docs/designs/
H A Derror-log-handling-for-phal.md28 [Phosphor-logging][3] [Create][4] interface is used for creating PELs.
H A Dvpd-collection.md18 included in the Platform Error Logs (PELs) for calling out FRUs for service.
/openbmc/openbmc-test-automation/openpower/pel/
H A Dtest_bmc_pel.robot616 … # Using peltool -lr, recent PELs appear first. Hence the ID of first PEL is greater than the next.
653 Should Be Equal ${pel_records['Number of PELs found']} ${random}
796 ${no_pel_records}= Set Variable ${pel_records["Number of PELs found"]}