Table E-1 through Table E-4 describe all of the error, status, and system event messages that can be displayed by the System Controller.
Table E-1 lists the master CPU status messages.
Table E-1. System Controller Master CPU Status Messages
Master CPU Status Message | Context and Meaning of Message |
|---|---|
BOOT ARBITRATION NOT STARTED | The system CPU board(s) have not begun the arbitration process. |
BOOT ARBITRATION IN PROGRESS | The System Controller is searching for the master CPU boot processor. |
ARBITRATION COMPLETE SLOT OxY PROC OxZ | The chosen CPU master has identified itself to the System Controller and communication is fully established. |
BOOT ARBITRATION INCOMPLETE NO MASTER | An error has occurred in the boot process and no CPU master is communicating with the System Controller. |
BOOT ARBITRATION ABORTED | The operator pushed one of the front panel buttons during the boot process. This caused the System Controller to stop looking for the boot master processor. |
Table E-2 lists all of the system error messages.
Table E-2. System Error Messages
Error Message | Error Meaning |
|---|---|
1.5VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
1.5VDC OVER VOLTAGE | The system backplane 1.5VDC power source exceeded the upper tolerance limit. |
1.5VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
1.5VDC UNDER VOLTAGE | The system backplane 1.5VDC power source dropped below the allowed limit. |
12VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
12VDC OVER VOLTAGE | The system backplane 12VDC power source exceeded the upper tolerance limit. |
12VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
12VDC UNDER VOLTAGE | The system backplane 12VDC power source dropped below the allowed limit. |
48VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
48VDC OVER VOLTAGE | The system backplane 48VDC power source exceeded the upper tolerance limit. |
48VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
48VDC UNDER VOLTAGE | The system backplane 48VDC power source dropped below the allowed limit. |
5VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
5VDC OVER VOLTAGE | The system backplane 5VDC power source exceeded the upper tolerance limit. |
5VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
5VDC UNDER VOLTAGE | The system backplane 5VDC power source dropped below the allowed limit. |
-12VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
-12VDC OVER VOLTAGE | The system backplane -12VDC power source exceeded the upper tolerance limit. |
-12VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
-12VDC UNDER VOLTAGE | The system backplane -12VDC power source dropped below the allowed limit. |
-5.2VDC HIGH WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
-5.2VDC OVER VOLTAGE | The system backplane -5.2VDC power source exceeded the upper tolerance limit. |
-5.2VDC LOW WARNING | The voltage is outside the desired tolerance range but will not cause system errors. Power system service may be needed soon. |
-5.2VDC UNDER VOLTAGE | The system backplane -5.2VDC power source dropped below the allowed limit. |
AMBIENT OVER TEMP | The incoming ambient air temperature is too high to provide proper system cooling. |
BLOWER A FAILURE | The system blower fan A has failed. |
BLOWER B FAILURE | The system blower fan B has failed. |
BLOWER A RPM LOW | The System Controller has stepped up the blower speed to compensate for a low RPM reading. |
BLOWER B RPM LOW | The System Controller has stepped up the blower speed to compensate for a low RPM reading. |
BLOWER A RPM HIGH | The blower is running faster than expected. The system is not shut down. |
BLOWER B RPM HIGH | The blower is running faster than expected. The system is not shut down. |
BLOWER A RPM FAILURE | The A blower RPMs are below tolerance after being stepped up to full speed. |
BLOWER B RPM FAILURE | The B blower RPMs are below tolerance after being stepped up to full speed. |
BOOT ERROR | A system processor failed to respond to the System Controller during boot arbitration. |
BRD/CHASSIS OVER TEMP | A detector in a card cage or chassis sensed a temperature over allowed limit. |
CPU NOT RESPONDING | The CPU system master is not responding to requests transmitted over the serial link. |
FP BUTTON STUCK | The System Controller has detected a front panel button that has been depressed for more than 30 seconds. The System Controller cannot function properly under this condition. |
NO SYSTEM CLOCK | The system backplane clock has failed. |
POKA FAIL | Power ok A (POKA); a voltage source supporting the Power Enable A signal failed. |
POKB FAIL | Power ok B (POKB); a voltage source supporting the Power Enable B signal failed. |
POKC FAIL | Power ok C (POKC); a voltage source supporting the Power Enable C signal failed. |
POKD FAIL | Power ok D (POKD); a voltage source supporting the Power Enable D signal failed. |
POKE FAIL | Power ok E (POKE); a voltage source supporting the Power Enable E signal failed. The system will not power down because of this condition. |
POWER FAIL WARNING | The Off-Line Switcher has detected an AC power loss. |
Table E-3 lists the system event messages.
Table E-3. System Event Messages
Event Message | Event Meaning |
|---|---|
NMI | A non-maskable interrupt (NMI) was entered onto the system backplane from a front panel menu option in the System Controller. |
SCLR DETECTED | The System Controller detected an SCLR on the system backplane. The reset was initiated from the System Controller front panel by an operator. |
SYSTEM OFF | The key switch was turned to the Off position and the System Controller powered down the system. |
SYSTEM ON | The System Controller has successfully powered up the system. |
SYSTEM RESET | The System Controller detected an SCLR and initiated a system boot arbitration process. An SCLR process can be generated by any processor board or by the System Controller. |
Table E-4 lists all of the System Controller's internal error messages.
Table E-4. Internal System Controller Error Messages
Error Message | Error Meaning |
|---|---|
|
|
BAD MSG: CPU PROCESS | The CPU or System Controller process has received an invalid message. |
BAD MSG: DISPLAY | The display process has received an invalid message. |
BAD MSG: POK CHK | The power ok check process received an invalid message. |
BAD MSG: SEQUENCER | The sequencer process has received an invalid message. |
BAD MSG: SYS MON | The system monitor process has received an invalid message. |
BAD ALARM TYPE | The firmware attempted to send an invalid alarm to the CPU. |
BAD WARNING TYPE | The firmware attempted to send an invalid warning to the CPU. |
BAD WARNING/ALARM | The routine that decodes alarm and warning messages detected an invalid message. |
COP FAILURE | The Computer Operating Properly (COP) timer has exceeded time limits. The System Controller firmware must write to a COP timer port before it times out. If the firmware exceeds the time allowed between writes to a COP port, an interrupt is generated. The System Controller firmware may have entered an endless loop. |
DEBUG SWITCH ERROR | The System Controller detected data corruption in the non-volatile RAM debug switch location. |
COP MONITOR FAILURE | A Computer Operating Properly (COP) clock monitor failure was detected. The System Controller clock oscillator is operating at less than 10 kHz. |
FP CONTROLLER FAULT | An error was detected in the front panel LCD display control process. |
FP READ FAULT | A read of the front panel status register did not complete successfully. |
FREE MSG NODE ERROR | The free message node queue has overflowed. |
FREE TCB NODE ERROR | The free timer control block queue has overflowed. |
ILLEGAL OPCODE TRAP | The System Controller's microprocessor tried to execute an illegal instruction. Probably because of a stack overrun followed by a process switch. |
PULSE ACCU INPUT | An interrupt was detected on the pulse accumulator input port. The port is not used and an interrupt is considered an error. |
PULSE ACCU OVERFLOW | The pulse accumulator overflow port received an interrupt. This port is unused and the interrupt is considered an error. |
SPI TRANSFER | An interrupt was detected on the synchronous serial peripheral interface. This interface is not supported and the interrupt is an error. |
STACK FAULT PID 0–6 | One of the seven stack areas used by a System Controller process has overflowed its assigned boundaries. |
TEMP SENSOR FAILURE | The System Controller detected an invalid measurement from the temperature sensor. |
TIMER IN COMP 1 | The timer input compare port received an interrupt. The port is not used and the interrupt is considered an error. |
TIMER OUT COMP 1–5 | One of the five timer output compare ports received an interrupt. The port that received the interrupt is not supported and the interrupt is considered an error. |
XMITTER 1 TIMEOUT | The System Controller's 1st UART experienced a failure. |
XMITTER 2 TIMEOUT | The System Controller's 2nd UART experienced a failure. |
Table E-5 lists all of the System Controller messages by message number
Table E-5. System Controller Codes and Long Messages
Code | System Controller Long Message |
|---|---|
040 | Memory board configuration has failed. Cannot load IO PROM. |
041 | All memory banks had to be disabled due to test failures. |
042 | The address line self-test failed. Cannot continue. |
043 | Memory board configuration has failed. Cannot load IO PROM. |
044 | Memory board configuration has failed. Cannot load IO PROM. |
047 | Memory board configuration has failed. Cannot load IO PROM. |
048 | Memory board configuration has failed. Cannot load IO PROM. |
049 | The PROM was unable to disable failing memory banks. |
050 | You must have at least 32 megabytes of working memory to load the IO PROM |
051 | The IP19 PROM did not recognize any memory boards in the system. |
070 | The IP19 PROM did not recognize any IO4 boards in the system. |
071 | Diagnostics detected a problem with your IO4 PROM. |
072 | Diagnostics detected a problem with your IO4 PROM. |
073 | Diagnostics detected a problem with your IO4 PROM. |
074 | Diagnostics detected a problem with your IO4 PROM. |
075 | Diagnostics detected a problem with your IO4 PROM. |
078 | An exception occurred while downloading the IO4 PROM to memory. |
079 | There must be an EPC chip on the IO board in the highest-numbered slot. |
080 | An exception occurred while configuring an IO board. |
081 | The IA chip on the master IO4 board has failed diagnostics. |
082 | The IA chip on the master IO4 board has failed diagnostics. |
083 | The IA chip on the master IO4 board has failed diagnostics. |
084 | The IA chip on the master IO4 board has failed diagnostics. |
085 | The IA chip on the master IO4 board has failed diagnostics. |
086 | The IA chip on the master IO4 board has failed diagnostics. |
088 | The IA chip on the master IO4 board has failed diagnostics. |
089 | The IA chip on the master IO4 board has failed diagnostics. |
090 | The IA chip on the master IO4 board has failed diagnostics. |
091 | The IA chip on the master IO4 board has failed diagnostics. |
092 | The IA chip on the master IO4 board has failed diagnostics. |
093 | The IA chip on the master IO4 board has failed diagnostics. |
094 | The IA chip on the master IO4 board has failed diagnostics. |
087 | The EPC chip on the master IO4 board has failed diagnostics. |
096 | The EPC chip on the master IO4 board has failed diagnostics. |
251 | The PROM code took an unexpected exception. |
252 | The PROM received a nonmaskable interrupt. |
|
|
Table E-6 lists System Controller diagnostic error codes and their meaninss:
Table E-6. System Controller Diagnostic Codes
Code | Meaning |
|---|---|
000 | Device passed diagnostics. |
001 | Failed dcache1 data test. |
002 | Failed dcache1 addr test. |
003 | Failed scache1 data test. |
004 | Failed scache1 addr test. |
005 | Failed icache data test. |
006 | Failed icache addr test. |
007 | Dcache test hung. |
008 | Scache test hung. |
009 | Icache test hung. |
040 | Memory built-in self-test failed. |
041 | No working memory was found. |
042 | Memory address line test failed. |
043 | Memory data line test failed. |
044 | Bank failed configured memory test. |
045 | Slave hung writing to memory. |
046 | Bank disabled due to downrev MA chip. |
047 | A bus error occurred during MC3 config. |
048 | A bus error occurred during MC3 testing. |
049 | PROM attempted to disable the same bank twice. |
050 | Not enough memory to load the IO4 PROM. |
051 | No memory boards were recognized. |
052 | Bank forcibly re-enabled by the PROM. |
060 | CPU doesn't get interrupts from CC. |
061 | Group interrupt test failed. |
062 | Lost a loopback interrupt. |
063 | Bit in HPIL register stuck. |
070 | No working IO4 is present. |
071 | Bad checksum on IO4 PROM. |
072 | Bad entry point in IO4 PROM. |
073 | IO4 PROM claims to be too long. |
074 | Bad entry point in IO4 PROM. |
075 | Bad magic number in IO4 PROM. |
078 | Bus error while downloading IO4 PROM. |
079 | No EPC chip found on master IO4. |
080 | Bus error while configuring IO4. |
081 | Bus error during IA register test. |
082 | Bus error during IA PIO test. |
083 | IA chip register test failed. |
084 | Wrong error reported for bad PIO. |
085 | IA error didn't generate interrupt. |
086 | IA error generated wrong interrupt. |
087 | EPC register test failed. |
088 | Bus error on map RAM rd/wr test. |
089 | Bus error on map RAM address test. |
090 | Bus error on map RAM walking 1 test. |
091 | Bus error during map RAM testing. |
092 | Map RAM read/write test failed. |
093 | Map RAM address test failed. |
094 | Map RAM walking 1 test failed. |
095 | EPC UART loopback test failed. |
096 | Bus err while testing EPC. |
120 | CPU can't access memory |
123 | CC bus tag data test failed. |
124 | CC bus tag addr test failed. |
125 | CPU forcibly re-enabled by the PROM. |
126 | CPU's EAROM can't be corrected. |
127 | CPU's EAROM checksum is bad. |
128 | CPU's EAROM has been repaired - power-cycle the system to re-enable. |
240 | CPU writing configuration info. |
246 | CPU testing dcache. |
247 | CPU testing icache. |
248 | CPU testing scache. |
249 | CPU initializing caches. |
250 | CPU returning from master's code. |
251 | Unexpected exception. |
252 | A nonmaskable interrupt occurred. |
253 | POD mode switch set or POD key pressed. |
253 | Unspecified diagnostic failure. |
254 | Diagnostic value unset. |
255 | Device not present. |