Step 1321-29
Record any extended data found in the Linux system log in Step 1321-24 or the Linux boot (IPL) log in
Step 1321-26. Be sure to record word 13.
Note:
The line(s) in the Linux extended data that begin with
″
<4>RTAS: Log Debug: 04
″
contain the error
code listed in the next 8 hex characters. In the previous example,
″
4b27 26fb
″
is an error code. The
error code is also known as word 11. Each 4 bytes after the error code in the Linux extended data
is another word (for example,
″
04a0 0011
″
is word 12, and
″
702c 0014
″
is word 13, and so on).
If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-28”
on page 130 and “Step 1321-29” for all logical partitions that have Linux installed.
Step 1321-30
Were any error codes or checkpoints recorded in Steps 1321-1, 1321-22, 1321-25, 1321-27, or
1321-29?
No
Go to “Step 1321-31”.
Yes
Go to the “Quick Entry MAP” on page 113 with each recorded error code or symptom. Perform the
indicated actions one at a time for each error code until the problem has been corrected. If all
recorded error codes have been processed and the problem has not been corrected, go to “Step
1321-31”.
Step 1321-31
If no additional error information is available and the problem has not been corrected, shut down the
system.
If an HMC is not attached, you need a laptop computer (and cable, part number 62H4857) capable of
connecting to serial port 1 on the processor subsystem.
Note:
The Linux login prompt cannot be seen on a laptop computer connected to serial port 1.
1. If there is no HMC, attach the laptop computer and cable to serial port 1 on the processor subsystem.
2. When OK displays in the operator panel, press a key on the virtual terminal on the laptop computer.
The service processor menus are available on the attached laptop computer or on the HMC.
3. Examine the service processor (SP) error log. Record all error codes and messages written to the SP
error log. Go to “Step 1321-32”.
4. If the service processor menus are not available, go to “Step 1321-33”.
Step 1321-32
Boot the system to the system management services (SMS) menus. Record all error codes and messages
written to the SMS error log.
Step 1321-33
Were any error codes recorded in steps 1321-31 or 1321-32?
No
Go to “Step 1321-41” on page 133.
Yes
Go to the “Quick Entry MAP” on page 113 with each error code or symptom you have recorded.
Perform the indicated actions, one at a time, until the problem has been corrected. If all recorded
error codes have been processed and the problem has not been corrected, go to “Step 1321-41”
on page 133.
Chapter 3. Maintenance Analysis Procedures
131
Summary of Contents for pSeries 670
Page 1: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 2: ......
Page 3: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 12: ...x Eserver pSeries 670 Service Guide...
Page 16: ...xiv Eserver pSeries 670 Service Guide...
Page 18: ...xvi Eserver pSeries 670 Service Guide...
Page 324: ...Yes Go to Step 154A 14 on page 302 304 Eserver pSeries 670 Service Guide...
Page 718: ...698 Eserver pSeries 670 Service Guide...
Page 848: ...L3 Cache Shorts Test Step 4 828 Eserver pSeries 670 Service Guide...
Page 849: ...L3 Cache Shorts Test Step 5 Chapter 9 Removal and Replacement Procedures 829...
Page 851: ...L3 Cache Shorts Test Step 2 Chapter 9 Removal and Replacement Procedures 831...
Page 853: ...L3 Cache Shorts Test Step 4 Chapter 9 Removal and Replacement Procedures 833...
Page 854: ...L3 Cache Shorts Test Step 5 834 Eserver pSeries 670 Service Guide...
Page 971: ...7040 Model 671 Media Subsystem 1 2 3 4 5 6 7 8 9 10 Chapter 10 Parts Information 951...
Page 973: ...Power and SCSI Cables to the Media Subsystem 1 2 3 5 4 6 Chapter 10 Parts Information 953...
Page 986: ...966 Eserver pSeries 670 Service Guide...
Page 990: ...970 Eserver pSeries 670 Service Guide...
Page 1018: ...998 Eserver pSeries 670 Service Guide...
Page 1020: ...1000 Eserver pSeries 670 Service Guide...
Page 1028: ...1008 Eserver pSeries 670 Service Guide...
Page 1031: ......