You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the core is guarded with predictive guard policy disabled there will not be any guard record created which indicates core has been guarded.
The PEL created by Hostboot points to the parent FRU as part of the callout as shown below
"Callouts": [
{
"CCIN": "5CF9",
"Location Code": "U78DB.ND0.WZS0340-P0-C15",
"Part Number": "02YK881",
"Priority": "Medium",
"Serial Number": "YA1936698813"
}
Faultlog file captures callout details but it does not indicate error in core, but the same can be found by looking at the corresponding PEL.
Hostboot captures the target that is in fault in the user data section and sends it as a binary blob to phosphor-logging, but the same can be used as user data section varies based on different types of errors, phosphor-logging will not be able to read the data and populate on the logging interface.
At present there is no solution for the issue, need to relook in during p11 time frame.
The text was updated successfully, but these errors were encountered:
More discussion in https://jazz07.rchland.ibm.com:13443/jazz/web/projects/CSSD#action=com.ibm.team.workitem.viewWorkItem&id=561261
When the core is guarded with predictive guard policy disabled there will not be any guard record created which indicates core has been guarded.
The PEL created by Hostboot points to the parent FRU as part of the callout as shown below
"Callouts": [
{
"CCIN": "5CF9",
"Location Code": "U78DB.ND0.WZS0340-P0-C15",
"Part Number": "02YK881",
"Priority": "Medium",
"Serial Number": "YA1936698813"
}
Faultlog file captures callout details but it does not indicate error in core, but the same can be found by looking at the corresponding PEL.
Hostboot captures the target that is in fault in the user data section and sends it as a binary blob to phosphor-logging, but the same can be used as user data section varies based on different types of errors, phosphor-logging will not be able to read the data and populate on the logging interface.
At present there is no solution for the issue, need to relook in during p11 time frame.
The text was updated successfully, but these errors were encountered: