Handling for host detected LPC timeout
For reasons not explained yet, hardware will not initiate an LPC timeout
attention via NCU timeout FIR bit as we expected. When the host firmware
detects an LPC timeout, it will manually set N1_LOCAL_FIR[61] to force a
system checkstop. The service response for this bit will be to call out
the hardware as if there was a hardware reported LPC timeout.
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I863e8aa3ef50a4b18b5106b3a45c4cf81b2c7808
diff --git a/analyzer/ras-data/data/ras-data-p10-10.json b/analyzer/ras-data/data/ras-data-p10-10.json
index 62e1636..9a53817 100644
--- a/analyzer/ras-data/data/ras-data-p10-10.json
+++ b/analyzer/ras-data/data/ras-data-p10-10.json
@@ -1001,6 +1001,10 @@
{ "type": "plugin", "name": "lpc_timeout", "instance": 0 }
],
+ "host_detected_lpc_timeout" : [
+ { "type": "plugin", "name": "lpc_timeout_workaround", "instance": 0 }
+ ],
+
"master_power_bus_chip_procedure": [
{ "type": "action", "name": "level2" }
],
@@ -19668,7 +19672,7 @@
"3a" : { "00" : "deadman_timer" },
"3b" : { "00" : "self" },
"3c" : { "00" : "level2" },
- "3d" : { "00" : "masked" },
+ "3d" : { "00" : "host_detected_lpc_timeout" },
"3e" : { "00" : "masked" },
"3f" : { "00" : "masked" }
},