IBM eserver p Series Service Manual page 318

Table 6. Service Processor Error Codes. (continued)
Error Code Description
4064 0EB2 Attention line 1 stuck fault
4064 0EB3 Attention line 2 stuck fault
4064 0EB4 Attention line 3 stuck fault
4064 0EB5 Attention line 4 stuck fault
4064 0EB6 Attention line 5 stuck fault
4064 0EB7 Attention line 6 stuck fault
4064 0EB8 Attention line 7 stuck fault
4064 0EB9 Attention line 8 stuck fault
4064 0EBA Attention line 9 stuck fault
4064 0EBB Attention line 10 stuck fault
4064 0EBC Attention line 11 stuck fault
4064 0EBF Memory error
4064 0EE1 Service processor firmware: invalid MRU to
FRU mapping
4064 0EE2 Service processor firmware fault
4064 0EE5 Firmware error, no callout available
298 EserverpSeries 650 Service Guide
Action/
Possible Failing FRU
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
Go to "MAP 1540: Problem Isolation
Procedures" on page 140.
1. Reboot the system in slow mode to the
SMS menus. See "Performing Slow Boot"
on page 241.
2. Examine the service processor error log.
a. If a CEC subsystem error (a 4xxx yyyy
error) occurred during the slow boot that
calls out the memory, processors, L3
cache modules or the primary I/O book,
replace the part indicated by the
location code.
b. If a CEC subsystem error (a 4xxx yyyy
error) did not occur during the slow
boot, look for a 4xxx yyyy error
immediately preceding the 406x 0EBF
error. Replace the part indicated by the
location code associated with that error.
1. Check for system firmware updates.
2. Call service support.
1. Check for system firmware updates.
2. Call service support.
1. Check for system firmware updates.
2. Call service support.