Chapter 4. CheckpointsCheckpoints let users and service personnel know what the system is doing, with somedetail, as it initializes. These checkpoints are not intended to be error indicators, but insome cases the system could hang at one of the checkpoints without displaying an8-character error code. It is for these hang conditions, only, that any action should betaken with respect to checkpoints. The most appropriate action is included with eachcheckpoint.Before taking actions listed with a checkpoint, it is a good idea to look for moreappropriate symptoms in the service processor error log. See Chapter 7, “Using theService Processor”, on page 149.Service Processor CheckpointsService processor checkpoints are in the range E001 to E0FF. The message OKindicates successful service processor testing and initialization. Firmware checkpointsare listed in “Firmware Checkpoints” on page 75.Note: Go to “MAP 1540: Minimum Configuration” on page 50 for any of the followingconditions:v A four-digit code in the range of E001 through EFFF displays on the operator panelbut is not listed in the checkpoint table.v A four-digit code displays in the checkpoint table, but does not contain a repair actionor FRU listing.v All of the FRUs listed in the repair action have been replaced and the problem hasnot been corrected.If you replace FRUs or perform an action, and the problem is corrected, go to "MAP410: Repair Checkout" in the RS/6000 and Eserver pSeries Diagnostics Informationfor Multiple Bus Systems.Table 1. Service Processor Checkpoints.Checkpoint Description Action/ Possible Failing FRUE000 System support controller beginsoperation. This is an informationalcheckpoint.Call for support.E010 Starting service processor self-tests Replace I/O board. (See notes onpage 93.)E011 Service processor self-testscompleted successfullyCall for support.E012 Begin to set up service processorhelpsReplace I/O board. (See notes onpage 93.)E01F Bad self-test; cannot continue Replace I/O board. (See notes onpage 93.)71
