Table 5. Service Processor Error Codes. (continued)Error Code Description Action/Possible Failing FRU406D 0A04 Reboot message (run-time array gard failure) forprocessor 2.Array bit steering, which is a function in thefirmware, may be able to correct this problemwithout replacing hardware.If AIX is available on the system, go to MAP0235 in the RS/6000 Eserver pSeriesDiagnostic Information for Multiple Bus Systems,order number SA38-0509.If Linux is the only operating system on thesystem, schedule deferred maintenance with thecustomer. When it is possible to reboot thesystem, do the following:1. Using the service processor’s system powercontrol menu, disable fast mode boot.(Disabling fast mode automatically enablesslow mode.)2. Boot the AIX diagnostic CD-ROM.3. Run diagnostics in problem determinationmode. If no errors are recorded against anyof the processors (devices with a resourcename of procx), array bit steering wassuccessful and the problem has beencorrected.If errors are reported against the hardware,follow the actions for the error code or SRN.406D 0B00 Problem with internal RIO interface (I/O slot 0,I/O port 0)CEC backplane, U0.1-P1406D 0B01 Problem with internal RIO interface (I/O slot 0,I/O port 1)CEC backplane, U0.1-P1406D 0B02 Problem with internal RIO interface (I/O slot 0,I/O port 2) 1. Check for system firmware updates.2. Check the cabling between the CEC and theI/O subsystems.3. CEC backplane, U0.1-P14. Call service support.406D 0B03 Problem with internal RIO interface (I/O slot 0,I/O port 3) 1. Check for system firmware updates.2. Check the cabling between the CEC and theI/O subsystems.3. CEC backplane, U0.1-P14. Call service support.406D 0B40 Problem with controller chip on CEC backplane 1. CEC backplane, U0.1-P1.2. Call service support.406D 0BF0 Problem with RIO interface (I/O slot 0, I/O port3) 1. Check for system firmware updates.2. Check the cabling between the CEC and theI/O subsystems.3. CEC backplane, U0.1-P14. Call service support.Chapter 5. Error Code to FRU Index 297
