(BAxxxxxx) Partition firmware reference (attention) codes

This section describes (BAxxxxxx) partition firmware reference (attention) codes.

For use by authorized service providers.

Partition firmware posts BAxxxxxx system reference codes (SRCs), which offer information about the next target state for the platform firmware. These codes might also indicate that you need to perform an action, like opening a firmware console or checking serial connections.

The BAxxxxxx table uses the following format:
  • The first column, Reference Code, contains numbers that identify a particular action your server performs during initialization of firmware.
  • The second column, Description/Action, offers a brief description about this SRC. It might also contain instructions for continuing the problem analysis.
  • The third column, Failing Item, offers a link to instructions service actions for recovering from a hang on an attention code. Click the failing item code only when you experience a hang condition on an attention code. For example, a hang condition occurs when your server performs a requested action but the SRC in the control panel display does not change for several minutes and the partition firmware appears to be hung.

The partition firmware detected a failure. The first eight characters in the display represent the SRC. Any additional characters represent the associated location code. Record the location code as well as the reference code, and then find the SRC in Table 1.

If you do not find an SRC in the table that follows, contact your next level of support for assistance.
Notes:
  1. The SRCs on this page are from the Power Systems hardware documentation, and the Descriptions apply to a single CEC enclosure or I/O enclosure. The Action and Failing Item fields are modified as appropriate for DS8000® architecture and repair methods.
  2. SRCs missing from the following tables might be found on the Power Systems online documentation. You can use the SRC description as is to define the problem. Do not use the Action and Failing Item without contacting the next level of support first.
  3. To display the Power Systems hardware online documentation, go to the Web site http://www-01.ibm.com/support/knowledgecenter/.
    • In the IBM Systems Hardware Information right content pane, click POWER6 reference codes listing.
Table 1. (BAxxxxxx) Partition firmware reference (error) codes
SRC Description/Action Failing Item
BA000010 The device data structure is corrupted. FWFLASH
BA000020 Incompatible firmware levels were found.

Reflash the platform firmware.

 
BA000030 An lpevent communication failure occurred. FWFLASH
BA000032 The firmware failed to register the lpevent queues FWFLASH
BA000034 The firmware failed to exchange capacity and allocate lpevents FWFLASH
BA000038 The firmware failed to exchange virtual continuation events FWFLASH
BA000040 The firmware was unable to obtain the RTAS code lid details. FWFLASH
BA000050 The firmware was unable to load the RTAS code lid. FWFLASH
BA000060 The firmware was unable to obtain the open firmware code lid details. FWFLASH
BA000070 The firmware was unable to load the open firmware code lid. FWFLASH
BA010000 There is insufficient information to boot the partition. FWIPIPL
BA010001 The client IP address is already in use by another network device. FWIPIPL
BA010002 Cannot get gateway IP address

Refer to partition firmware progress code CA00E174

FWHOST
BA010003 Cannot get server hardware address

Refer to partition firmware progress code CA00E174.

FWHOST
BA010004 Boot failed.  
BA010005 File transmission (TFTP) failed.

Refer to partition firmware progress code CA00E174.

FWHOST

FWADIPL

BA010006 The boot image is too large. FWADIPL
BA020001 Partition firmware password entry error

Reenter the password.

 
BA020009 Invalid password entered - system locked

A password was entered incorrectly three times. Deactivate the partition using the management console, and then reactivate it. When asked for the password, enter the correct password."

 
BA030011 RTAS attempt to allocate memory failed FWFWPBL
BA04000F Self test failed on device; no error or location code information available.

If there was a location code reported with the error, replace the device specified by the location code.

NEXTLVL
BA040010 Self test failed on device; cannot locate package NEXTLVL
BA040020 The machine type and model are not recognized by the server firmware.

Check for server firmware updates, and apply them, if available.

NEXTLVL
BA050001 Failed to reboot a partition in logical partition mode. FWFWPBL
BA050004 Failed to locate service processor device tree node. FWFWPBL
BA05000A Failed to send boot failed message to the service processor. FWFWPBL
BA060003 IP parameter requires 3 period characters "."

Enter a valid IP parameter. Example: 000.000.000.000

 
BA060004 Invalid IP parameter

Enter a valid IP parameter. Example: 000.000.000.000

 
BA060005 Invalid IP parameter (>255)

Enter a valid IP parameter. Example: 000.000.000.000

 
BA060007
A keyboard was not found.
  1. Make sure that a keyboard is attached to the USB port that is assigned to the partition.
  2. Replace the USB card to which the keyboard is attached.
 
BA060008 No configurable adapters found by the remote IPL menu in the SMS utilities.

This error occurs when the remote IPL menu in the SMS utilities cannot locate any LAN adapters that are supported by the remote IPL function.

FWRIPL
BA06000B The system was not able to find an operating system on the devices in the boot list.

See MAP4040 Isolating LPAR operating system boot problems.

 
BA06000C A pointer to the operating system was found in non-volatile storage. FWPTR
BA060020 The environment variable "boot-device" exceeded the allowed character limit. FWNIM
BA060021 The environment variable "boot-device" contained more than five entries. FWNIM
BA060022 The environment variable "boot-device" contained an entry that exceeded 255 characters in length. FWNIM
BA060030 Logical partitioning with shared processors is enabled and the operating system does not support it.
  1. Install or boot a level of the operating system that supports shared processors.
  2. Disable logical partitioning with shared processors in the operating system.
 
BA07xxxx SCSI controller failure FWSCSI1
BA080001 An IDE device remained busy for a longer period than the time out period. FWFWPBL
BA080002 The IDE controller senses IDE devices but with errors.
  • Verify that the IDE devices are properly seated and cabled correctly.
  • Replace the IDE controller (model-dependent).
 
BA080010 An IDE device is busy longer than specified time-out period.

Retry the operation.

FWIDE1
BA080011 An IDE command timed out; command is exceeding the period allowed to complete.

Retry the operation.

FWIDE1
BA080012 The ATA command failed. FWIDE2
BA080013 The media is not present in the tray.

Retry the operation.

FWIDE1
BA080014 The media has been changed.

Retry the operation.

FWIDE1
BA080015 The packet command failed; the media might not be readable.

Retry the operation.

FWIDE1
BA09xxxx SCSI controller failure
This checkpoint might remain in the control panel for up to 15 minutes If the checkpoint persists longer than 15 minutes, do the following:
  1. Power off the server and reboot from the permanent side. Reject the firmware image on the temporary side.
  2. If the problem persists, before replacing any components, refer to the actions for BA090001.
 
BA090001 SCSI DASD: test unit ready failed; hardware error. FWSCSI1
BA090002 SCSI DASD: test unit ready failed; sense data available. FWSCSI2
BA090003 SCSI DASD: send diagnostic failed; sense data available. FWSCSI3
BA090004 SCSI DASD: send diagnostic failed: devofl command. FWSCSI3
BA100001 SCSI tape: test unit ready failed; hardware error. FWSCSI1
BA100002 SCSI tape: test unit ready failed; sense data available. FWSCSI4
BA100003 SCSI tape: send diagnostic failed; sense data available. FWSCSI3
BA100004 SCSI tape: send diagnostic failed: devofl cmd. FWSCSI3
BA110001 SCSI changer: test unit ready failed; hardware error. FWSCSI1
BA110002 SCSI changer: test unit ready failed; sense data available. FWSCSI4
BA110003 SCSI changer: send diagnostic failed; sense data available. FWSCSI3
BA110004 SCSI changer: send diagnostic failed: devofl command. FWSCSI3
BA120001 On an undetermined SCSI device, test unit ready failed; hardware error. FWSCSI5
BA120002 On an undetermined SCSI device, test unit ready failed; sense data available. FWSCSI4
BA120003 On an undetermined SCSI device, send diagnostic failed; sense data available. FWSCSI4
BA120004 On an undetermined SCSI device, send diagnostic failed; devofl command. FWSCSI4
BA130001 SCSI CD-ROM: test unit ready failed; hardware error. FWSCSI1
BA130002 SCSI CD-ROM: test unit ready failed; sense data available. FWSCSI3
BA130003 SCSI CD-ROM: send diagnostic failed; sense data available. FWSCSI3
BA130004 SCSI CD-ROM: send diagnostic failed: devofl command. FWSCSI3
BA130010 USB CD-ROM: device remained busy longer than the time-out period.

Retry the operation.

FWFWPBL
BA130011 USB CD-ROM: execution of ATA/ATAPI command was not completed with the allowed time.

Retry the operation.

FWCD1
BA130012
USB CD-ROM: execution of ATA/ATAPI command failed.
  1. Verify that the power and signal cables going to the USB CD-ROM are properly connected and are not damaged. If any problems are found, correct them, and then retry the operation.
  2. If the problem persists, the CD in the USB CD-ROM drive might not be readable. Remove the CD and insert another CD.
NEXTLVL
BA130013 USB CD-ROM: bootable media is missing from the drive.

Insert a bootable CD-ROM in the USB CD-ROM drive, and then retry the operation.

FWCD1
BA130014 USB CD-ROM: the media in the USB CD-ROM drive has been changed.

Retry the operation.

FWCD2
BA130015 USB CD-ROM: ATA/ATAPI packet command execution failed.

If the problem persists, the CD in the USB CD-ROM drive might not be readable. Remove the CD and insert another CD.

FWCD2
BA140001 SCSI read/write optical: test unit ready failed; hardware error. FWSCSI1
BA140002 SCSI read/write optical: test unit ready failed; sense data available. FWSCSI1
BA140003 SCSI read/write optical: send diagnostic failed; sense data available. FWSCSI3
BA140004 SCSI read/write optical: send diagnostic failed; devofl command. FWSCSI3
BA150001 PCI Ethernet BNC/RJ-45 or PCI Ethernet AUI/RJ-45 adapter: internal wrap test failure.

Replace the adapter specified by the location code.

 
BA151001 10/100 MBPS Ethernet PCI adapter: internal wrap test failure.

Replace the adapter specified by the location code.

 
BA151002 10/100 MBPS Ethernet card  
BA151002 10/100 MBPS Ethernet card FWENET
BA153003 Gigabit Ethernet adapter failure
  1. Check for adapter firmware updates; apply if available.
  2. Remove other cards from the PHB in which the gigabit Ethernet adapter is plugged and retry the operation. If the operation is successful, plug the cards in again, one at a time, until the failing card is isolated. After you identify the failing card, replace it.
  3. Replace the adapter.
 
BA160001 PCI auto LANstreamer token ring adapter failed to complete hardware initialization.

Replace the adapter specified by the location code.

 
BA161001 PCI token ring adapter: failed to complete hardware initialization.

Replace the adapter specified by the location code.

 
BA170xxx NVRAM problems FWNVR1
BA170000 NVRAMRC initialization failed; device test failed FWNVR2
BA170100 NVRAM data validation check failed.

Turn off, and then turn on the system.

FWNVR2
BA170201 The firmware was unable to expand target partition - saving configuration variable, FWNVR1
BA170202 The firmware was unable to expand target partition - writing error log entry. FWNVR1
BA170203 The firmware was unable to expand target partition - writing VPD data. FWNVR1
BA170210 Setenv/$Setenv parameter error - name contains a null character. FWNVR1
BA170211 Setenv/$Setenv parameter error - value contains a null character FWNVR1
BA170998 NVRAMRC script evaluation error - command line execution error. FWNVR3
BA170999 NVRAMRC script evaluation error - stack unbalanced on completion.

This is a firmware debug environment error. There is no user action or FRU replacement for this error.

NEXTLVL
BA180008 PCI device code evaluation error. FWPCI1
BA180009 The Fcode on a PCI adapter left a data stack imbalance

You should load the new adapter Fcode before you use the adapter (specified by the location code associated with this error) for booting.

 
BA180010 PCI probe error, bridge in freeze state. FWPCI2
BA180011 PCI bridge probe error, bridge is not usable. FWPCI3
BA180012 PCI device runtime error, bridge in freeze state. FWPCI3
BA180013 A PCI adapter was found that this machine type and model does not support.
Is the system an IBM Intellistation model?
  • Yes, complete the following steps.
    1. Check for and apply any available server firmware updates.
    2. Replace the adapter at the location code that was reported with the error.
  • No, remove the PCI adapter specified by the location code.
 
BA180100 FDDI adapter Fcode driver is not supported on this system.

This server does not support the Fcode driver of this adapter. IBM might produce a compatible driver in the future, but does not guarantee one. Service support might have additional information.

 
BA180101 Stack underflow from fibre-channel adapter FWFWPBL
BA188000 An unsupported adapter was found in a PCI slot

Remove the unsupported adapter in the slot identified by the location code.

 
BA188001 EEH recovered a failing I/O adapter

Replace the adapter in the slot identified by the location code.

 
BA188002 EEH could not recover the failed I/O adapter

Replace the adapter in the slot identified by the location code.

 
BA190001 Firmware function to get/set time-of-day reported an error. FWFWPBL
BA191001 The server firmware function to turn on the speaker reported an error FWFWPBL
BA201001 The serial interface dropped data packets FWFWPBL
BA201002 The serial interface failed to open FWFWPBL
BA201003 The firmware failed to handshake properly with the serial interface FWFWPBL
BA210000 Partition firmware reports a default catch. FWFWPBL
BA210001 Partition firmware reports a stack underflow was caught. FWFWPBL
BA210002 Partition firmware was ready before standout was ready. FWFWPBL
BA210010 The transfer of control to the SLIC loader failed FWFWPBL
BA210100 The partition firmware was unable to log an error with the server firmware. No reply was received from the server firmware to an error log that was sent previously NEXTLVL
BA210101 The partition firmware error log queue is full NEXTLVL
BA250010 dlpar error in open firmware. FWLPAR
BA250020 dlpar error in open firmware due to an invalid dlpar entity. This error might have been caused by an errant or hung operating system process.
  1. Check for operating system updates that resolve problems with dynamic logical partitioning (dlpar) and apply them, if available.
  2. Check for server firmware updates and apply them, if available.
 
BA250030 A hotplug operation in dynamic logical partitioning (dlpar) was terminated for concurrent firmware update. Retry the hotplug operation after the concurrent firmware update is complete.  
BA278001 Failed to flash firmware: invalid image file

Obtain a valid firmware update (flash) image for this system.

 
BA278002 Flash file is not designed for this eServer™ platform.

Obtain a valid firmware update (flash) image for this system.

 
BA278003
Unable to lock the firmware update lid manager.
  1. Reboot the system.
  2. Make sure that the operating system is authorized to update the firmware. If the system is running multiple partitions, verify that this partition has service authority.
 
BA278004 An invalid firmware update lid was requested.

Obtain a valid firmware update (flash) image for this system.

 
BA278005 Failed to flash a firmware update lid,

Obtain a valid firmware update (flash) image for this system.

 
BA278006 Unable to unlock the firmware update lid manager.

Reboot the system.

 
BA278007 Failed to reboot the system after a firmware flash update.

Reboot the system.

 
BA278008 A server firmware update was attempted from the operating system. You must perform the update by using the Hardware Management Console (HMC).

Perform the server firmware update by using the HMC.

 
BA278009 The server firmware update management tools for the version of Linux that you are running are incompatible with this system.

Go to Service and productivity tools for Linux on POWER™ and download the latest service aids and productivity tools for the version of Linux that you are running.

BA280000 RTAS discovered an invalid operation that might cause a hardware error NEXTLVL
BA290000 RTAS discovered an internal stack overflow FWFWPBL