System Firmware Startup Messages - IBM QS21 - BladeCenter - 0792 Service Manual

Table 8. Memory test results (continued)
Test Number Status
202- Fail
802-xx
202-901- Fail
xxx
202-801- Abort
xxx
202-000- Pass
xxx

System firmware startup messages

The system firmware displays the progress of the startup process on the serial
console from the time that ac power is connected to the system until the operating
system login prompt is displayed following a successful operating system startup.
If a serial console is not connected, you can use the Advanced Management
Module to monitor the logs and display informational and error messages.
Extended
results Actions
General error:
1. Ensure all memory is enabled by checking Available
memory size is
System Memory in the Resource Utilization section of the
insufficient to run
DSA Diagnostic Event Log.
the test.
2. Make sure that the DSA Diagnostic code is at the latest
level. The latest level DSA Diagnostic code can be found on
the IBM Support Web site at http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA/.
3. Run the test again.
4. Execute the standard DSA memory diagnostic to validate all
memory.
5. If the test continues to fail, refer to the other sections of this
chapter for diagnosis and corrective action.
Test failure.
1. Execute the standard DSA memory diagnostic to validate all
memory.
2. Make sure that the DSA Diagnostic code is at the latest
level. The latest level DSA Diagnostic code can be found on
the IBM Support Web site at http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA/.
3. Turn off the system and disconnect it from power.
4. Reseat the DIMMs.
5. Reconnect the system to power and turn on the system.
6. Run the test again.
7. Execute the standard DSA memory diagnostic to validate all
memory.
8. If you cannot reproduce the problem, contact your IBM
technical-support representative.
Internal program
1. Turn off and restart the system.
error.
2. Make sure that the system firmware code and DSA code are
at the latest level.
3. Run the test again.
4. Turn off and restart the system if necessary to recover from
a hung state.
5. Run the memory diagnostic to identify the specific failing
DIMM.
6. If the test continues to fail, refer to the other sections of this
chapter for diagnosis and corrective action
Chapter 5. Diagnostics and troubleshooting
71