Searched hist:f380c516 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | log_id.hpp | f380c516 Fri Nov 19 06:07:31 CST 2021 Sumit Kumar <sumit_kumar@in.ibm.com> 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
|
| H A D | log_id.cpp | f380c516 Fri Nov 19 06:07:31 CST 2021 Sumit Kumar <sumit_kumar@in.ibm.com> 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
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | log_id_test.cpp | f380c516 Fri Nov 19 06:07:31 CST 2021 Sumit Kumar <sumit_kumar@in.ibm.com> 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
|