diff options
author | Andrew Geissler <geissonator@yahoo.com> | 2020-10-20 21:49:36 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-10-22 22:13:32 +0300 |
commit | 66160e9b8617fdbc00ae9dcce49a8afbdce475b3 (patch) | |
tree | fb361c98aac2e0e06f6dffd82107b1984aaf6ce3 /meta-openpower/recipes-phosphor | |
parent | 8f1ebaba28c59f19b12de7ecfdcc5b4c4ac4ce92 (diff) | |
download | openbmc-66160e9b8617fdbc00ae9dcce49a8afbdce475b3.tar.xz |
wdt-on-panic: remove from withespoon and mihawk
At a high level, the purpose of this feature was to utilize the BMC
hardware watchdogs to switch the BMC boot flash when certain errors were
hit which were preventing the BMC from booting.
At a high level, this worked but some critical issues were found with
this:
- No failure data is gathered to understand why the boot flash was
switched
- No event or error is logged to notify the user of the system that the
boot flash has switched
- At times, switching sides didn't help because the BMC network
information was not properly copied to the other boot flash which
caused even more confusion for the user
Give the above, this patch proposes a reset on this logic until we can
come back and address the above issues and get this working end to end.
(From meta-ibm rev: d5069cffe865ea104915d8e0fdbe8d7d145644fc)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8c8d2b30c80940f4674e6c6848bd22f759e943a5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-openpower/recipes-phosphor')
0 files changed, 0 insertions, 0 deletions