IBM pSeries 690 Service Manual page 389

Hide thumbs Also See for pSeries 690:

Table of Contents

Checkpoints enable users and service personnel to know what the server is doing, with some detail, as it

initializes. These checkpoints are not intended to be error indicators, but in some cases a server could

hang at one of the checkpoints without displaying an 8-character error code. It is for these hang

conditions, only, that any action should be taken with respect to checkpoints. The most appropriate action

is included with each checkpoint.

Before taking actions listed with a checkpoint, check for additional symptoms in the service processor error

log. See the "System Information Menu" on page 795 for information on how to access the service

processor error log.

Note: Go to "MAP 1540: Problem Isolation Procedures" on page 310 for any of the following checkpoint

hang conditions:

v A four-digit code in the range of 8xxx through EFFF not listed in the checkpoint tables.

v A four-digit code is in the checkpoint tables, but does not contain a repair action or FRU listing.

v All of the FRUs listed in the repair action have been replaced and the problem has not been

Checkpoints listed in the following tables are in the format 8xxx, 9xxx, Axxx, Bxxx, or Exxx, where x is any

hexadecimal digit from 1-9 or A-F. If your system hangs with a checkpoint displayed that begins with

anything other than 8, 9, A, B, or E, go to the RS/6000 and Eserver pSeries Diagnostic Information for

Multiple Bus Systems.

Use the following table to determine where to find the checkpoint.

You have a code that is of the form 8xxx, 9xxx, Axxx, or

You have a code of the form Exxx.

You have a four-character code that is not of the form

8xxx, 9xxx, Axxx, Bxxx, or Exxx.

Go to "Service Processor Checkpoints" on page 374.

Go to "Firmware Checkpoints" on page 381.

See the RS/6000 and Eserver pSeries Diagnostic

Information for Multiple Bus Systems.

Chapter 4. Checkpoints