(CAxx) Partition firmware progress codes

Partition firmware progress codes offer information about the progress of partition firmware as it is initializing. In some cases, a server might hang (or stall) at one of these progress codes without displaying an 8-character system reference code (SRC). Only during such a hang condition should you take any service action related to the progress code.

The table of firmware progress codes uses the following format:

Notes:
  1. If the control panel displays more than eight characters, use only the first eight characters to find the error in the table. Characters that display after the first eight represent a location code that assists you in diagnosing the problem.
  2. Licensed programs frequently rely on network configuration, and system information stored in the Vital Product Data (VPD) on the control panel. If the Repair Action/Possible Failing FRU entry indicates that you should replace the control panel, swap the VPD module from the old control panel to the new one. If you need to replace the old VPD module, call technical support for recovery instructions. If recovery is not possible, notify the system owner that new keys for licensed programs may be required.

Table 1. (CAxx) Partition firmware progress codes

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CA000000 Process control now owned by partition firmware FWFLASH
CA000020 Checking firmware levels FWFLASH
CA000030 Attempting to establish a communication link by using lpevents FWFLASH
CA000032 Attempting to register lpevent queues FWFLASH
CA000034 Attempting to exchange cap and allocate lpevents FWFLASH
CA000038 Attempting to exchange virtual continue events FWFLASH
CA000040 Attempting to obtain RTAS firmware details FWFLASH
CA000050 Attempting to load RTAS firmware FWFLASH
CA000060 Attempting to obtain open firmware details FWFLASH
CA000070 Attempting to load open firmware FWFLASH
CA000080 Preparing to start open firmware FWFLASH
CA000090 Open firmware package corrupted (phase 1) FWFLASH
CA0000A0 Open firmware package corrupted (phase 2) FWFLASH
CA00D001 PCI probe process completed, create PCI bridge interrupt routing properties FWFLASH
CA00D002 PCI adapter NVRAM hint created; system is rebooting FWFLASH
CA00D003 PCI probing complete FWPCI5
CA00D004 Beginning of install-console, loading GUI package FWFLASH
CA00D008 Initialize console and flush queues FWFLASH
CA00D00C The partition firmware is about to search for an NVRAM script NEXTLVL
CA00D00D Evaluating NVRAM script FWFLASH
CA00D010 First pass open firmware initialization complete; establish parameters for restart FWFLASH
CA00D011 First pass open firmware initialization complete; control returned to initialization firmware FWFLASH
CA00D012 Second pass open firmware initialization complete; control returned to initialization firmware FWFLASH
CA00D013 Run-time open firmware initialization complete; control returned to initialization firmware FWFLASH
CA00D020 The partition firmware is about to load and run the SLIC loader FWFLASH
CA00E100 Unspecified partition firmware error

In either the error log for the service processor or the error log in Service Focal Point (if the system has an Hardware Management Console (HMC) attached), look for SRCs that immediately precede this progress code. Perform the repair actions for the SRCs by starting with the most recent entry, and then working backwards until you resolve the problem.

CA00E101 Create RTAS node FWFLASH
CA00E102 Load/initialize RTAS FWFLASH
CA00E105 Transfer control to operating system (normal boot)

See Problems with loading and starting the operating system (AIX® and Linux®)

CA00E10A Load RTAS device tree FWFLASH
CA00E10B Set RTAS device properties FWFLASH
CA00E130 Build device tree FWFLASH
CA00E134 Create memory node FWFLASH
CA00E135 Create HCA node FWFLASH
CA00E136 Create BSR node FWFLASH
CA00E138 Create options node FWFLASH
CA00E139 Create aliases node and system aliases FWFLASH
CA00E13A Create packages node FWFLASH
CA00E140 Loading operating system

See Problems with loading and starting the operating system (AIX and Linux)

CA00E149 Create boot mgr node FWFLASH
CA00E14C Create terminal emulator node FWFLASH
CA00E14D Load boot image

See Problems with loading and starting the operating system (AIX and Linux)

CA00E150 Create host (primary) PCI controller node FWFLASH
CA00E151 Probing PCI bus FWPCI5
CA00E152 Probing for adapter FCODE; evaluate if present FWPCI5
CA00E153 End adapter FCODE probing and evaluation FWPCI5
CA00E154 Create PCI bridge node FWPCI5
CA00E155 Probing PCI bridge secondary bus FWPCI5
CA00E156 Create plug-in PCI bridge node FWPCI5
CA00E15B Transfer control to the operating system (service mode boot)

See Problems with loading and starting the operating system (AIX and Linux)

CA00E15F Adapter VPD evaluation FWPCI5
CA00E170 Start of PCI bus probe FWPCI5
CA00E172 First pass PCI device probe FWPCI5
CA00E174 Establishing host connection FWHOST
CA00E175 BootP request FWHOST
CA00E176 TFTP file transfer

See Problems with loading and starting the operating system (AIX and Linux)

CA00E177 Transfer failure due to TFTP error condition

See Problems with loading and starting the operating system (AIX and Linux)

CA00E17B Processor clock speed measurement NEXTLVL
CA00E199 The partition is rebooting to enact changes that were specified in the ELF header of the boot image

See Problems with loading and starting the operating system (AIX and Linux)

CA00E19A NVRAM auto-boot? variable not found - assume FALSE
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E19B NVRAM menu? variable not found - assume FALSE
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E19D Create NVRAM node
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E1A0 User requested boot to SMS menus by using keyboard entry FWFLASH
CA00E1A1 User requested boot to open firmware prompt by using keyboard entry FWFLASH
CA00E1A2 User requested boot using default service mode boot list by using keyboard entry FWFLASH
CA00E1A3 User requested boot using customized service mode boot list by using keyboard entry FWFLASH
CA00E1A4 User requested boot to SMS menus by using the Hardware Management Console or a service processor command FWFLASH
CA00E1A5 User requested boot to open firmware prompt by using the HMC or a service processor command FWFLASH
CA00E1A6 User requested boot using default service mode boot list by using the HMC or a service processor command FWFLASH
CA00E1A7 User requested boot using customized service mode boot list by using the HMC or a service processor command FWFLASH
CA00E1AA System boot check for NVRAM settings
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E1AB System booting using the default service mode boot list FWFLASH
CA00E1AC System booting using the customized service mode boot list FWFLASH
CA00E1AD System booting to the operating system FWFLASH
CA00E1AE System booted to SMS multiboot menu by using NVRAM settings FWMBOOT
CA00E1AF System booted to SMS utilities menu by using NVRAM settings FWFLASH
CA00E1B1 System booting with HMC or hosting-partition directed boot-device repair FWFLASH
CA00E1B2 XOFF received, waiting for XON FWVTHMC
CA00E1B3 XON received

This checkpoint flashes by so quickly on the control panel that you cannot see it. The progress indicators log may contain a reference to it, which you can access by using the ASMI menus. If a partition hangs on this checkpoint, perform the action specified in the Failing Item column.

FWPCI5
CA00E1B4 HMC or hosting-partition directed boot-string did not load an operating system repair NEXTLVL
CA00E1B5 Checking for iSCSI disk aliases FWPCI5
CA00E1D0 Create PCI SCSI node FWPCI5
CA00E1D3 Create SCSI block device node (SD) FWPCI5
CA00E1D4 Create SCSI byte device node (ST) FWPCI5
CA00E1DC Dynamic console selection FWCONS
CA00E1DD A graphics adapter was selected as the firmware console, but the USB keyboard is not attached.

Ensure that a USB keyboard is attached to a USB port that is assigned to the partition.

FWCONS
CA00E1F0 Start out-of-box experience FWFLASH
CA00E1F1 Start self-test sequence on one or more devices FWFLASH
CA00E1F2 Power on password prompt FWPWD
CA00E1F3 Privileged-access password prompt FWPWD
CA00E1F4 End self-test sequence on one or more boot devices; begin system management services FWFLASH
CA00E1F5 Build boot device list
  1. If the system or partition hangs on this checkpoint, look for a location code in the operator panel. If a location code is being displayed when the hang occurs, suspect the device at that location code.
  2. If the device at that location code is good, suspect the other bootable devices that are on the same bus, such as an IDE bus.
  3. If no location codes are displayed, remove all of the bootable devices in the system or partition. Add them back in one at a time, and reboot the partition after each one is added. This should isolate the device that is causing the hang; replace it.
  4. If step three does not isolate the problem, go to PFW1548.
CA00E1F6 Determine boot device sequence FWFLASH
CA00E1F7 No boot image located

See Problems with loading and starting the operating system (AIX and Linux)

CA00E1F8 Build boot device list for SCSI adapters (displays the location code of the SCSI adapter being scanned) FWPCI5
CA00E1F9 Build boot device list for Fibre Channel adapters (displays the location of the SAN adapter being scanned) FWPCI5
CA00E1FA Building device list for SCSI adapters (displays the device ID and device LUN of the devices being scanned) FWPCI5
CA00E1FB Scan SCSI bus for attached devices FWSCSIH
CA00E1FC Build boot device list for SSA adapters (displays the location code of the SSA adapter being scanned) FWPCI5
CA00E1FE Building device list for Fibre Channel (SAN) adapters (displays the WWPN of the fibre-channel adapter being scanned)
  1. If the system or partition hangs on this checkpoint, removed the fibre channel adapter(s) from the system or partition and reboot. If the problem is resolved, replace the fibre channel adapter that was causing the hang.
  2. If step 1 does not isolate the problem, go to PFW1548.
CA00E1FF Build device list for Fibre Channel (SAN) adapters (displays the LUN for each device being scanned)
  1. If the system or partition hangs on this checkpoint, removed the fibre channel adapter(s) from the system or partition and reboot. If the problem is resolved, replace the fibre channel adapter that was causing the hang.
  2. If step 1 does not isolate the problem, go to PFW1548.
CA00E440 Validate NVRAM, initialize partitions as needed
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E441 Generate /options node NVRAM configuration variable properties
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E442 Validate NVRAM partitions
  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E443 Generate NVRAM configuration variable dictionary words

Suspect a platform firmware problem if this error code persists.

  1. Reboot the partition
  2. Reboot the system
  3. FWFLASH
CA00E701 Create memory VPD FWFLASH
CA00E800 Initialize gdata for control panel FWFLASH
CA00E810 Initializing ioconfig pdfs FWFLASH
CA00E820 Initializing lpevent FWFLASH
CA00E830 Initializing event scan FWFLASH
CA00E840 Initializing hot plug FWFLASH
CA00E843 Initializing interface/aix access FWFLASH
CA00E850 Initializing dynamic reconfiguration FWFLASH
CA00E860 Initializing sensors FWFLASH
CA00E865 Initializing VPD FWFLASH
CA00E870 Initializing pfds memory manager FWFLASH
CA00E875 Initializing rtas_last_error FWFLASH
CA00E876 Initializing rtas_error_inject FWFLASH
CA00E877 Initializing dump interface FWFLASH
CA00E885 Initializing set-power-level FWFLASH
CA00E886 Initializing exit2c FWFLASH
CA00E887 Initialize gdata for activate_firmware FWFLASH
CA00E890 Starting to initialize open firmware FWFLASH
CA00E891 Finished initializing open firmware FWFLASH
CA00EAA1 Probe PCI-PCI bridge bus FWPCI5
CA060203 An alias was modified or created FWFLASH
CA26ttss Waiting for lpevent of type tt and subtype ss

Reboot the system.

FWFLASH
CA2799FD The service processor is receiving a server firmware update module

This checkpoint alternates in the control panel with CA2799FF. This pair of checkpoints might stay in the display for up to 30 minutes with no other indication of activity. Do not assume that the system is hung until ONLY CA2799FD has remained in the control panel for at least 30 minutes with no other indication of activity.

If the system hangs on CA2799FD (it is NOT alternating with CA2799FF), power off the system and reboot from the permanent side. Reject the image on the temporary side.

CA2799FF The service processor is writing a server firmware update module.

This checkpoint alternates in the control panel with CA2799FD. This pair of checkpoints might stay in the display for up to 30 minutes with no other indication of activity. Do not assume that the system is hung until ONLY CA2799FF has remained in the control panel for at least 30 minutes with no other indication of activity.

If the system hangs on CA2799FF (it is NOT alternating with CA2799FD), power off the system and reboot from the permanent side. Reject the image on the temporary side.


Send feedback |  Rate this page