#
c3038c03 |
| 11-Sep-2023 |
Caleb Palmer <cnpalmer@us.ibm.com> |
Updated analyzer root cause filtering for Odyssey special cases
This updates the RAS data analyzer's root cause filtering to handle special cases for Odyssey OCMBs, in particular ODP data corruption
Updated analyzer root cause filtering for Odyssey special cases
This updates the RAS data analyzer's root cause filtering to handle special cases for Odyssey OCMBs, in particular ODP data corruption root causes, and firmware initiated channel fails due to IUE threshold.
Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Id22dd07b19a68007be0be3881d669eeee3a8078f
show more ...
|
#
adda0540 |
| 06-Apr-2023 |
Zane Shelley <zshelle@us.ibm.com> |
Clarify definition of chip checkstop
Previously, the ATTN_TYPE_CHECKSTOP associated with a signature was synonymous with a system checkstop event. This is certainly true for if a processor chip chec
Clarify definition of chip checkstop
Previously, the ATTN_TYPE_CHECKSTOP associated with a signature was synonymous with a system checkstop event. This is certainly true for if a processor chip checkstops. However, this is not true if a connected OCMB chip checkstops because it is possible in some cases for a system to recover. To differentiate an OCMB chip checkstop from a system checkstop they were previously reported as unit checkstops. With the addition Odyssey OCMBs, which have ability to report both chip and unit checkstops, we decided to fix the confusion and disassociate a chip checkstop from a system checkstop. Now the signatures will properly report the chip attention type and the signature filtering code has been modified to simply associate only chip checkstops from processor chips as system checkstop attentions.
Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iff9822ff8c9c0ae1afe84353010e94759dbdf49d
show more ...
|