diff options
| author | Dan Crowell <dcrowell@us.ibm.com> | 2018-03-09 15:18:18 -0600 |
|---|---|---|
| committer | William G. Hoffa <wghoffa@us.ibm.com> | 2018-03-12 12:39:37 -0400 |
| commit | 586b8b1e6088353e34358658ddaad2e15a2e6cf0 (patch) | |
| tree | e3136d5a1854c781d2fb709926d2a08d4760da5c /src/include/usr | |
| parent | 48d464158bc349eee52abc41eb40239424652188 (diff) | |
| download | talos-hostboot-586b8b1e6088353e34358658ddaad2e15a2e6cf0.tar.gz talos-hostboot-586b8b1e6088353e34358658ddaad2e15a2e6cf0.zip | |
Do not elevate severity of reconfig error log
The code as currently written will elevate the severity of any
log that is used to terminate the hostboot ipl. In most cases
this is the correct behavior as we always want a visible log.
However, there are cases where hostboot terminates for the sole
purpose of triggering a reconfig loop via the FSP in order to
recover from a recoverable hardware issue. In this case the log
shouldn't be visible since we don't want the customer to take
any actions.
The fix is to add a little bit of logic to differentiate these
two scenarios to control the severity setting.
Change-Id: I7253aec8c28a40c5cdebf4933ceccbecd119b9f4
CQ: SW420495
Backport: yes
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/55379
CI-Ready: Nicholas E. Bofferding <bofferdn@us.ibm.com>
CI-Ready: Daniel M. Crowell <dcrowell@us.ibm.com>
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>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Nicholas E. Bofferding <bofferdn@us.ibm.com>
Reviewed-by: Marshall J. Wilks <mjwilks@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
Diffstat (limited to 'src/include/usr')
0 files changed, 0 insertions, 0 deletions
