IBM @Server pSeries 630 6C4, Service Manual

Page: 234 / 651

Checkpoint or Error Code - 4xxx xxxx Service Processor Error Codes
What You Should Do
1. Is the system powered up?
NO Go to step 2 below.
YES Go to step 4 below.
2. Find the error code in the service processor error log and check the value of word 13. Go to 3 below.
3. Is the value of word 13 C0xx xxxx?
NO Go to step 7 below.
YES Go to “MAP 1541: JTAG Problem Isolation” on page 126.
4. Is the system running Linux?
NO Go to step 6 below.
YES Go to step 5 below.
5. If the system is not functional, go to step 7 below.
If the system is functional, do the following:
Examine the Linux system log by logging in to the system as the root user and entering the following command:
cat /var/log/messages | grep RTAS |more
Record any RTAS messages found in the Linux system log entry. Ignore all other messages in the Linux system
log.
Find the value of word 13 in the Linux system log entry. For detailed instructions on finding word 13 in a Linux
system log entry, refer to the actions under error code B1xx 4699 in this service guide.
Is the value of word 13 C0xx xxxx?
NO Go to step 7 below.
YES Go to “MAP 1541: JTAG Problem Isolation” on page 126.
6. If the system is not functional, go to step 7.
If the system is functional, do the following:
Examine the AIX error log entry. Find the value of word 13. For detailed instructions on finding word 13 in a AIX
error log entry, refer to the actions under error code B1xx 4699 in this service guide.
Is the value of word 13 C0xx xxxx?
NO Go to step 7 below.
YES Go to “MAP 1541: JTAG Problem Isolation” on page 126.
7. There might be additional error codes and information in the service processor error log. The system must be
powered off to examine the contents of the service processor error log.
a. Is the system still powered on?
NO Go to step 8 below.
YES Ask the customer if the system can be powered off, then go to 7b.
b. Can the system be powered off?
NO Go to step 10 below.
YES Power off the system, then go to step8.
8. Perform slow boot procedure as described in “Performing Slow Boot” on page 209.
9. Confirm this is the first error code that caused the failure as described in “Confirming Initial Error Code” on
page 210
10. Did you come to this step from step 9?
NO Go to “Service Processor Error Codes” on page 249 with the error codes you already have and follow
the instructions in the service processor error codes table.
YES Go to “Service Processor Error Codes” on page 249 with the error codes from 9 above and follow the
instructions in the service processor error codes table.
214
Eserver
pSeries 630 Model 6C4 and Model 6E4 Service Guide