Dont deconfig PROCs that dont have WOF tables
Dont deconfig PROCs that dont have WOF tables

In the case that WOF data is bad there are two options:
1. Deconfigure the PROC with bad data and let the rest run at WOF speeds
2. Disable WOF on the whole system but use all available PROCs

This commit changes the code to take the second option because if the
first option is taken then the system will lose more than just the PROC.
It will lose all the memory, IO, and--for multinode--the entire drawer.

Going forward, Hostboot expects the PM code to never fail out due to an
error back from WOF accessors. Instead, the log will just be committed
and downgrade things as needed to allow the system to IPL.

Additionally, this means that if a system has only PROCs without WOF
data on them then they can still IPL.

Change-Id: I03b5f29c65e59a56d0794a83fe59a5fa9a1ce324
CQ:SW528182
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/118691
Reviewed-by: Chen Du <10793d83dd2b346092aca99468e01b6a2b9d993a@us.ibm.com>
Reviewed-by: Isaac Salem <c69ff4695291efa8bfa4efde6e5e177cdf719186@ibm.com>
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Tested-by: Jenkins OP HW <0eb0fff262f74a65a832afbcc7b153e391c9a3fd@us.ibm.com>
Tested-by: Jenkins Combined Simics CI <8312af3886dfc9bb930f549023677220805b137e@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Tested-by: Hostboot CI <52521565bd8ea18a2b112942dce4f4220a97c2c8@us.ibm.com>
Reviewed-by: Nicholas E Bofferding <fb8db48116bc8a69e29dd8cdb037246f232f4af5@us.ibm.com>

open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot