tree 2da1c222c3d73f43c87e10e7157ce98b08ee2377
parent 7bdffd1c2ed620a4732c8353954e7af44b223c03
author Andrew Geissler <geissonator@yahoo.com> 1602870339 -0500
committer Andrew Geissler <geissonator@yahoo.com> 1603394003 -0500

wdt-on-panic: remove overrides from meta-phosphor

If these are needed, they really should be done within the meta-aspeed
layer. This was originally done to allow the BMC hardware watchdogs
to control the reboot of the BMC in error scenarios vs. the kernel auto
rebooting itself. This is causing issues on AST2600 hardware because the
watchdogs are not setup correctly. Kernel panics result in the BMC
becoming unusable and not rebooting, requiring a manual power cycle.

The goal with letting the hardware watchdogs control the reboot was that
fancy things like flash side switches could be performed for recovery
scenarios. However the end to end software stack for this was never fully
implemented so if a flash side switch did occur, there would be no
notice to the user of the system, and in most cases the BMC was still
inoperable because the network settings were missing.

For now, we should just go back to the defaults built into the
meta-aspeed layer which is to panic on oops and have the kernel
immediately reboot the BMC when a panic occurs.

Once we iron out the watchdog usage, we can look into changing these
back in the meta-aspeed layer if needed.

(From meta-phosphor rev: 7777a8eda2b4909f34605476813e1e364b0d5728)

Change-Id: I18a15a7769b27d6dd577bcc4e35cc9f60c4d3240
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>