| Name | Context | Path | Description |
|---|---|---|---|
|
PastErrorStatus |
CSLS |
CSLS_NAME/PAST_ERROR, CSLS_NAME/REDU/STBY/PAST_ERROR |
The last fatal error in the CSLS |
| Conditions | Meaning | Action | Mapping |
|---|---|---|---|
| Program Assertion | Unspecified internal software error, e.g. corruption of program causes a null pointer to be returned. | If the fatal condition is persistent, do a manual reset of affected card and contact technical support. If the fatal condition was momentary, contact technical support to report the error. | Bits map directly to identical bits in FAILED_ALERTS in a simplex logic solver. |
| Resource Error | System software could not obtain a hardware or software resource. | ||
| Memory Test Failure | An error occurred in NVM during power up testing. | ||
| Uncommanded Switchover | A switchover occurred due to either proof test, lost IO comms, or lost P2P comms. | ||
| Control Data Mismatch Between Cores | The control subsystems detected a mismatch in outputs or secure parameter data. | ||
| Task Checkpoint Error | A critical task did not complete properly. | ||
| Hardware Watchdog Failure | A powerup test failed on a watchdog timer or a processor did not arm its watchdog within the window during operation. | ||
| Unspecified Hardware Error | An unspecified hardware error occurred. | ||
| Control Subsystem Scheduling Error | The control subsystem was not able to complete module execution in time. | Reduce the number of modules executing in the CSLS. | |
| Dual Active CHARMs Logic Solvers | The CSLS has reset because both partners saw the active role. | Probably due to an issue with the redundancy link. Problem could be with either logic solver (not necessarily the one that reset). Start by replacing the standby unit, then perform a switchover to it. If the condition returns, replace the other logic solver. |