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
Do not gard cores on the initial core wakeup failure
We have seen rare (but non-zero) errors during slave core wakeup
where we never see the new core reporting in. Currently this
will result in a visible log and a core gard. However, there is
currently no indication this failure is actually due to bad
hardware.
As a workaround, this commit adds an indicator that keeps track
of if a core has failed wakeup previously. The first time we
encounter the error there will be a visible log with a FW callout
and no deconfig or gard of the core. That will trigger a boot
failure and a reboot. If we don't fail on the next boot (which
is expected), the counter will be cleared. If we do fail again
there will be a visible log (with a new SRC) that calls out the
core as the primary cause, plus does a deconfig+gard.
Change-Id: I3a25537cf9c9c8e0b679519b67e9ae4e3492736d
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/70993
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
0 commit comments