Before using this information and the product it supports, read the information in Appendix. Notices, Safety notices, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z125-5823.
This edition applies to IBM Power Systems™ servers that contain the POWER6® processor and to all associated models.
Safety notices may be printed throughout this guide:
Several countries require the safety information contained in product publications to be presented in their national languages. If this requirement applies to your country, a safety information booklet is included in the publications package shipped with the product. The booklet contains the safety information in your national language with references to the U.S. English source. Before using a U.S. English publication to install, operate, or service this product, you must first become familiar with the related safety information in the booklet. You should also refer to the booklet any time you do not clearly understand any safety information in the U.S. English publications.
Das Produkt ist nicht für den Einsatz an Bildschirmarbeitsplätzen im Sinne § 2 der Bildschirmarbeitsverordnung geeignet.
IBM® servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs.
Laser compliance
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser product. Consult the label on each part for laser certification numbers and approval information.
The following comments apply to the IBM servers that have been designated as conforming to NEBS (Network Equipment-Building System) GR-1089-CORE:
The equipment is suitable for installation in the following:
The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposed wiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to the interfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use as intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connect these interfaces metallically to OSP wiring.
The ac-powered system does not require the use of an external surge protection device (SPD).
The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminal shall not be connected to the chassis or frame ground.
Reference codes are diagnostics aids that help you find solutions to system problems.
Reference codes are diagnostic aids that help you determine the source of a hardware or operating system problem. Using a reference code enables you to find the solution to fix the problem. To use reference codes effectively, you must use them in conjunction with other service and support procedures.
Sometimes, multiple field replaceable units (FRUs) or procedures are called out for replacement by an SRC listed in the service action log (SAL). Each FRU or procedure has a priority, and procedures are always in priority order, from highest to lowest priority. Follow the steps below:
The priorities of performing the FRU replacements or procedures are shown in the following ways, depending on how you view the SAL.SRC:
Procedure error in vertical Licensed Internal Code
Data-set-ready changed to not active; for information only
First call failed, retrying call; no CFI from modem
The remote answer timer expired without the system detecting either the rise of DSR or a call failure indication from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description.
First call failed, retrying call; CFI AB from modem
After dialing, the system detected a call failure indication AB from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description. CFI AB is sent from the modem if the modems timer expires after answer tone was detected and before the modem is ready for data transfer.
First call failed, retrying call; CFI DE from modem
After dialing, the system detected a call failure indication DE from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description. CFI DE is sent from the modem if the modem failed to detect a dial tone when expected or detected a dial tone when another tone was expected. This can occur if the telephone cable is not plugged into the back of the modem.
First call failed, retrying call; CFI ET from modem
After dialing, the system detected a call failure indication ET from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description. CFI ET is sent from the modem if the modem detects a busy signal (engaged tone).
First call failed, retrying call; CFI NT from modem
After dialing, the system detected a call failure indication NT from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description. CFI NT is sent from the modem if the modems timer expires without detecting an answer tone or a ring back, and had detected the expected dial tones. This situation could result from a person answering the telephone.
First call failed, retrying call; CFI RT from modem
After dialing, the system detected a call failure indication RT from the modem. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description. CFI RT is sent from the modem if the modem does not detect the remote answer when the timer expired or the modem is still detecting ring back. This response is also sent if the modem ends a call because the ring counter reached its limit.
Call failed, retrying call; Non-standard CFI from modem
After dialing, the system detected a call failure indication from the modem that was not recognized. The system tries the call again, up to the number of tries specified in the dial retry parameter of the controller description.
Clear-to-send state changed; error limit per 256 reached
Data-set-ready state changed; error limit per 256 reached
Clear-to-send state changed; error limit per 256 reached
Carrier-detect state changed; error limit per 256 reached
Call not completed; error limit per 256 reached
Call completed with error; error limit per 256 reached
Data-line-occupied error; error limit per 256 reached
Abandon-call-retry error; error limit per 256 reached
Present-next-digit error; error limit per 256 reached
Distant-station-connected error; error limit per 256 reached
Data-set-ready state changed; error limit per 256 reached
Incorrect number dialed; error limit per 256 reached
Wrong data block received; error limit per 256 reached
Wrong data block received; error limit per 256 reached
Temporary text delay block sent; error limit per 256
Wait-acknowledge block sent; error limit per 256 reached
Incorrect data block sent; error limit per 256 reached
Communications IOP cannot receive; limit reached
Receive-time-out error; error limit per 256 reached
Continuous synchronization on line; error limit reached
No synchronization received; error limit per 256 reached
Synchronous time-out; error limit per 256 reached
Communications line already in use
V.25 adapter not installed
Incorrect command value sent by vertical LIC
Incorrect parts installed for BSC communications
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Wrong telephone number specified in system configuration
Wrong telephone number specified in system configuration
Data-set-ready error on modem interface
Data-line-occupied initially 'on' error
Automatic call unit has data-line-occupied error
Automatic call unit has present-next-digit error
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Automatic call unit has distant-station-connected error
Automatic call unit has data-set-ready error
Call failed, no Call Failure Indication from modem
The remote answer timer expired without the system detecting either the rise of DSR or a call failure indication from the modem. The system has reached the number of tries in the dial retry parameter in the controller description.
Automatic call unit has call-clear error
Automatic call unit switched link time-out; no answer
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Clear-to-send not active on modem interface
Carrier-detect dropped on modem interface
Data-set-ready did not drop during time-out
Data-set-ready did not come up during time-out
Wrong or no external communications cable installed
Call error; incoming call received during outgoing call
Communications controller storage not available
Automatic call unit has abandon-call attempt
Abandon call retry error; incorrect number length
Automatic call unit power turned off
Data-set-ready dropped on modem interface
Error in I/O card Licensed Internal Code
Communications controller storage not available
Procedure error in vertical Licensed Internal Code
Data-set-ready changed to not active; for information only
Clear-to-send state changed; error limit per 256 reached
Data-set-ready state changed; error limit per 256 reached
Clear-to-send state changed; error limit per 256 reached
Carrier-detect state changed; error limit per 256 reached
Call not completed; error limit per 256 reached
Call completed with error; error limit per 256 reached
Data-line-occupied error; error limit per 256 reached
Abandon-call-retry error; error limit per 256 reached
Present-next-digit error; error limit per 256 reached
Distant-station-connected error; error limit per 256 reached
Data-set-ready state changed; error limit per 256 reached
Incorrect number dialed; error limit per 256 reached
Break character received; error limit per 256 reached
Received storage overrun; error limit per 256 reached
Incorrect stop bit; error limit per 256 reached
Receive-time-out error; error limit per 256 reached
Number of characters discarded; error limit per 256 reached
Procedure error in vertical Licensed Internal Code
Wrong data received; error limit per 256 reached
Automatic call unit port is not installed
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong number specified in controller description
No number specified in controller description
Wrong number specified in controller description
Switched line already in use
Data-line-occupied error at time of starting
Automatic call unit line connection error
Present-next-digit error
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Wrong configuration value sent by vertical LIC
Automatic call unit distant-station-connected time out
Automatic call unit had data-set-ready time out
Time-out on call-clear-request
Automatic call unit line connection error
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Clear-to-send not active on modem interface
Carrier-detect dropped on modem interface
Time-out; data-set-ready did not drop
Time-out; data-set-ready not received
Procedure error in vertical Licensed Internal Code
Wrong or no external communications cable installed
Call received during dialing procedure
Communications controller error
Communications controller error
Abandon-call-retry
Abandon-call-retry; not all numbers dialed
Automatic call unit power turned off
Data-set-ready dropped on modem interface
No action is required if Operations Console is attached.
Procedure error in vertical Licensed Internal Code
Wrong command sent by vertical Licensed Internal Code
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not set. Use the CHGNETA command to set MDMCNTRYID value.
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not valid for this adapter. Use the CHGNETA command to change MDMCNTRYID.
System log entry only, no service action required
Vertical Licensed Internal Code sent an incorrect command
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Communications controller storage not available
Vertical LIC sent commands in wrong order
Vertical LIC sent commands in wrong order
Configuration exceeds allowed maximum for X.25 lines
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
No logical link available for packet network
No outgoing or two-way logical link available
Remote station not connected
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Logical link already disconnected
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical Licensed Internal Code sent wrong password length
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical Licensed Internal Code sent wrong data length
Vertical Licensed Internal Code sent an incorrect command
Number of user requests more than maximum allowed
I/O card LIC followed incorrect procedure
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
I/O card Licensed Internal Code ended abnormally
I/O card Licensed Internal Code stopped because of error
Network procedure error detected by I/O card lic int code
Remote system did not respond to command sent
Remote system did not respond to command sent
Remote system did not respond to disconnect command
Call rejected; wrong value from remote system
Remote system did not respond to test command
Checksum error; error limit per 256 reached
Bad data received; error limit per 256 reached
Remote system not ready; error limit per 256 reached
Vertical Licensed Internal Code sent an incorrect command
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Procedure error in vertical Licensed Internal Code
Outgoing and two-way logical channel not available
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Communications controller storage not available
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Application sent invalid Q/M bit request sequence
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
PLC/HDLC DTE/DCE mode configured not valid
Vertical LIC sent incorrect command values
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Vertical LIC sent commands in wrong order
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Procedure error in vertical Licensed Internal Code
Vertical LIC sent commands in wrong order
No incoming call available to be processed
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
I/O card Licensed Internal Code used incorrect value
Vertical LIC sent incorrect command values
I/O card Licensed Internal Code used incorrect value
I/O card Licensed Internal Code stopped because of error
I/O card Licensed Internal Code stopped because of error
X.25 clear packet sent, packet size negotiation failed
X.25 clear packet sent, window size negotiation failed
Reset packet received; error limit per 256 reached
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Wrong config data given to local area network controller
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
I/O card Licensed Internal Code received unexpected response
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Severe error detected by I/O card Licensed Internal Code
Severe error detected by I/O card Licensed Internal Code
Severe error detected by I/O card Licensed Internal Code
Ring status information logged; not serious
Ring status information logged; serious
Ring status information logged; serious
Token-ring adapter card error
Change the line speed parameter for the Token-ring card. The card must be varied off before changing the line speed.
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
User suspected communications problem.
The adapter does not support Full DUPLEX or did not detect Full Duplex.
Ring status information logged; serious
Address not recognized; error limit per 256 reached
Frame not copied; error limit per 256 reached
Access priority not authorized; error limit per 256 reached
Frames not authorized; error limit per 256 reached
Frames discarded; error limit per 256 reached
Interrupts not expected; error limit per 256 reached
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Required I/O card Licensed Internal Code not active
Procedure error in vertical Licensed Internal Code
Wrong frame received from remote equipment
All unit reference codes that start with a value of B7 and end with any value from 00 through FF have the same meaning as this unit reference code.
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Required I/O card Licensed Internal Code not active
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Wrong frame received from remote equipment
Wrong frame received from remote equipment
I/O processor resource not available
A deactivation failed to get a resource controlled by Licensed Internal Code.
Not valid condition in I/O Processor Licensed Internal Code
An error in an activation or deactivation occurred.
I/O processor resource not available
A resource needed to perform a requested function is not available in the Licensed Internal Code.
Not valid condition in I/O Processor Licensed Internal Code
The Licensed Internal Code has recovered from a condition that was not expected.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor resource not available
The Licensed Internal Code could not allocate memory resources on the I/O processor card.
Not valid condition in I/O Processor Licensed Internal Code
The Licensed Internal Code found a condition that should not have occurred.
I/O processor was not ready for interrupt that occurred
I/O processor resource not available
The I/O processor error log is being filled faster than the errors are being reported to the system. Check other errors reported to the system and correct them.
A permanent I/O processor failure occurred
I/O processor card or Licensed Internal Code error
I/O processor card or Licensed Internal Code error
I/O processor resource not available
An activation or deactivation failed to get a resource controlled by Licensed Internal Code.
Not valid condition in I/O Processor Licensed Internal Code
An error in an activation or deactivation occurred.
I/O processor resource not available
A resource needed to perform a requested function is not available in the Licensed Internal Code.
Not valid condition in I/O Processor Licensed Internal Code
The Licensed Internal Code has recovered from an unexpected condition.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor resource not available
The Licensed Internal Code could not allocate memory resources on the I/O processor card.
Not valid condition in I/O Processor Licensed Internal Code
The Licensed Internal Code found a condition that should not have occurred.
I/O processor was not ready for interrupt that occurred
I/O processor resource not available
The I/O processor error log is being filled faster than the errors are being reported to the system. Check other errors reported to the system and correct them.
A permanent I/O processor failure occurred
I/O processor card or Licensed Internal Code error
I/O processor card error
Display the Service Action Log entry for this SRC. If the Failing Item indicates IOP, then replace the IOP. If the Failing Item indicates SVCDOCS, then do NOT replace the IOP. This is a recoverable error. Perform the following: 1. If the I/O Processor is not operable and disk units are attached, use Hardware Service Manager to re-IPL the IOP. Other resources attached to the IOP may then need to be Varied On. 2. If disk units are not attached, perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources.
Service processor Licensed Internal Code error
A resource needed to perform a requested function is not available in the Licensed Internal Code.
Service processor Licensed Internal Code error
The Licensed Internal Code has recovered from an unexpected condition.
Service processor Licensed Internal Code error
A recoverable microcode condition occurred on the Service processor.
Service processor Licensed Internal Code failed
A microprocessor exception occurred on the Service processor.
Service processor Licensed Internal Code failed
The Licensed Internal Code could not allocate resources on the Service processor.
Service processor Licensed Internal Code failed
Service processor Licensed Internal Code failed
The Service processor was not ready for an interrupt that occurred.
I/O processor resource not available
A deactivation failed to get a resource controlled by Licensed Internal Code.
Not valid condition in I/O Processor Licensed Internal Code
An error in an activation or deactivation occurred.
I/O processor resource not available
A resource that is needed to perform a requested function is not available in the Licensed Internal Code.
Recovered from condition in Licensed Internal Code.
The Licensed Internal Code has recovered from a condition that was not expected.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor card or Licensed Internal Code error
A microprocessor exception occurred on the I/O processor.
I/O processor resource not available
The Licensed Internal Code could not allocate memory resources on the I/O processor card.
Not valid condition in I/O Processor Licensed Internal Code
The Licensed Internal Code found a condition that should not have occurred.
Threshold overflow
The I/O processor card has detected a threshold of recoverable error conditions. The errors are either wrong interruptions or memory error corrections. If in communications, the line is still running. If a large number of these errors occur during a short time, they may be caused by an electrically noisy environment, a defective communications I/O processor card or modem, or a communications I/O processor code problem.
Error reported to system
The I/O processor error log is being filled faster than the errors are being reported to the system. Check other errors reported to the system and correct them.
Communications controller task ended abnormally; type 1
Communications controller task ended abnormally; type 2
Communications controller task ended abnormally; type 3
Disconnect mode frame received during link activation
Disconnect mode frame received when transmitting information
Set-asynchronous-balance-mode frame received in data mode
Wrong response received from remote equipment
First call failed, retrying call; no CFI from modem
First call failed, retrying call; CFI AB from modem
First call failed, retrying call; CFI DE from modem
First call failed, retrying call; CFI ET from modem
First call failed, retrying call; CFI NT from modem
First call failed, retrying call; CFI RT from modem
Call failed, retrying call; Non-standard CFI from modem
Wrong telephone number specified in system configuration
No number specified in controller description
Wrong telephone number specified in system configuration
Wrong command received by communications controller
Wrong procedure followed by I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong data length received by communications controller
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong reset option received by communications controller
Wrong command value received by communications IOP
Wrong session ID received by communications controller
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong storage value received; communications controller
Wrong trace type received by communications controller
Wrong trace length received by communications controller
Communications controller temporary storage area too small
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Procedure error in vertical Licensed Internal Code
DTE/DCE role negotiation not valid for leased line
Wrong or no external communications cable installed
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong adapter type value sent by Vertical LIC
Wrong slot number value sent by Vertical LIC
Incorrect command value sent by vertical LIC
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Communications adapter card not installed
Network uncontrolled-not-ready warning; information only
Network controlled-not-ready warning; information only
Data-set-ready changed to not active; for information only
I/O card Licensed Internal Code resource not available
Incorrect command used by I/O card Licensed Internal Code
Wrong procedure followed by I/O card Licensed Internal Code
I/O card Licensed Internal Code resource not available
Wrong response sent by I/O card Licensed Internal Code
Wrong command value sent by IBM i Operating System licensed program
Wrong command value received by communications IOP
X.21 network not in the ready or receive-data state
Error when releasing communications controller storage
Error when assigning communications controller storage
Data-set-ready error on modem interface
Data-line-occupied initially 'on' error
Automatic call unit has data-line-occupied error
Automatic call unit has present-next-digit error
Data-set-ready state changed; error limit per 256 reached
Clear-to-send state changed; error limit per 256 reached
Carrier-detect state changed; error limit per 256 reached
Data-set-ready error; error limit per 256 reached
Automatic call unit has distant-station-connected error
Automatic call unit has data-set-ready error
Call failed, no Call Failure Indication from modem
Clear-to-send not active on modem interface
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Carrier-detect dropped on modem interface
Data-set-ready signal turn-off time-out
Data-set-ready signal turn-on time-out
Data-set-ready dropped on modem interface
Protocol mismatch during link initialization
Could not send frame to remote equipment; local problem
Frame check error; error limit per 256 reached
Overrun error; error limit per 256 reached
Short frame error; error limit per 256 reached
Abnormal end received; error limit per 256 reached
Long frame; error limit per 256 reached
Send sequence counter error; error limit per 256 reached
Receive sequence counter error; error limit per 256 reached
Response time-out error; error limit per 256 reached
Automatic call unit switched link time-out; no answer
Call error; incoming call received during outgoing call
Automatic call unit has abandon-call attempt
Abandon call retry error; incorrect number length
Automatic call unit power turned off
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not set. Use the CHGNETA command to set MDMCNTRYID.
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not valid for this adapter. Use the CHGNETA command to change the MDMCNTRYID value.
User suspected communications problem.
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Wrong configuration data given to Ethernet controller
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
I/O card Licensed Internal Code received incorrect response
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Serious error detected by I/O card Licensed Internal Code
Serious error detected by I/O card Licensed Internal Code
User suspected communications problem.
Full DUPLEX is not supported on this media type.
Configuration of DUPLEX parameter not supported by network.
Input value error in I/O card Licensed Internal Code
Ethernet adapter card error
Verify that the signal quality error switch in the transceiver that the Ethernet is attached to is set to active.
Procedure error in I/O card Licensed Internal Code
Wrong configuration data given to Ethernet controller
Wrong configuration data given to Ethernet controller
Wrong configuration data given to Ethernet controller
Wrong configuration data given to Ethernet controller
User suspected communications problem.
There are two cables attached to the adapter and only one is allowed. Remove one cable and vary off and then vary back on the resource.
Configuration of DUPLEX parameter not supported by network.
Unable to establish a network link.
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Output value error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Output value error in vertical Licensed Internal Code
Number of stations greater than allowed in configuration
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
First call failed, retrying call; no CFI from modem
The remote answer timer expired without the server detecting either the rise of DSR or a Call Failure Indication from the modem. The system is trying the call again, up to the value of the Dial retry parameter of the controller description.
First call failed, retrying call; CFI AB from modem
After dialing the server detected a Call Failure INDICATION AB from the modem. The system is trying the call again, up to the face value of the Dial retry parameter of the controller description. CFI AB is sent from the modem if the modems abort timer expires after answer tone was detected and before the modem is ready for data transfer.
First call failed, retrying call; CFI DE from modem
After dialing the server detected a Call Failure Indication DE from the modem. The system is trying the call again, up to the value of the Dial retry parameter of the controller description. CFI DE is sent from the modem if the modem failed to detect dial tone when expected or detected dial tone when another tone was expected. This can occur if the telephone cable is not plugged into the back of the modem.
First call failed, retrying call; CFI ET from modem
After dialing the server detected a Call Failure Indication ET from the modem. The system is trying the call again, up to the value of the Dial retry parameter of the controller description. CFI ET is sent from the modem if the modem detects a busy signal (engaged tone).
First call failed, retrying call; CFI NT from modem
After dialing the server detected a Call Failure Indication NT from the modem. The system is trying the call again, up to the value of the Dial retry parameter of the controller description. CFI NT is sent from the modem if the modems abort timer expires without detecting answer tone, is not detecting ring back, and had detected the expected dial tones. This situation could result from a person answering the telephone.
First call failed, retrying call; CFI RT from modem
After dialing the server detected a Call Failure Indication RT from the modem. The system is trying the call again, up to the value of the Dial retry parameter of the controller description. CFI RT is sent from the modem if the modem does not detect the remote answer when the abort timer expired, the modem is still detecting ring back. This response is also sent if the modem ends a call because the ring counter reached its limit.
Call failed, retrying call; Non-standard CFI from modem
After dialing the server detected a Call Failure Indication from the modem that was not recognized. The system is trying the call again, up to the value of the Dial retry parameter of the controller description.
Wrong telephone number specified in system configuration
Wrong command sent by vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in machine instructions
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Incorrect command value sent by vertical LIC
Procedure error in vertical Licensed Internal Code
Command value error in I/O card Licensed Internal Code
Clear-to-send not active to allow data to be sent
Command value error in I/O card Licensed Internal Code
Command value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Vertical LIC sent commands in wrong order
Vertical LIC sent commands in wrong order
Wrong or no external communications cable installed
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Wrong command value sent by IBM i Operating System licensed program
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong number of dial digits in telephone number
No telephone number provided for the call command
Communications line not installed
Automatic call unit cable not installed
Clear-to-send signal dropped warning; information only
Network uncontrolled-not-ready warning; information only
Network controlled-not-ready warning; information only
Data-set-ready changed to not active; for information only
I/O card Licensed Internal Code ended abnormally
I/O card Licensed Internal Code resource not available
I/O card Licensed Internal Code response not correct
I/O card Licensed Internal Code ended abnormally
I/O card Licensed Internal Code response not correct
Incorrect command used by I/O card Licensed Internal Code
Wrong procedure used in I/O card Licensed Internal Code
I/O card Licensed Internal Code resource not available
Command response error in I/O card Licensed Internal Code
Wrong command value sent by IBM i Operating System licensed program
Data-line-occupied already active from automatic call unit
X.21 network not in the ready or receive-data state
Command value error in I/O card Licensed Internal Code
Command value error in I/O card Licensed Internal Code
Communications adapter card interrupt not expected
Clear-to-send off; error limit per 256 reached
Data-set-ready state changed; error limit per 256 reached
Clear-to-send state changed; error limit per 256 reached
Carrier-detect state changed; error limit per 256 reached
Call attempted; error limit per 256 reached
Call completed with error; error limit per 256 reached
Data-line-occupied error; error limit per 256 reached
Abandon-call-retry error; error limit per 256 reached
Present-next-digit error; error limit per 256 reached
Distant-station-connected error; error limit per 256 reached
Data-set-ready error; error limit per 256 reached
Wrong number length; error limit per 256 reached
Call failed, no Call Failure Indication from modem
The remote answer timer expired without the server detecting either the rise of DSR or a Call Failure Indication from the modem. The system has reached the number of tries in the dial retry parameter in the controller description.
Data-set-ready already active on modem interface
Automatic call unit data-line-occupied error
Automatic call unit has present-next-digit error
Automatic call unit distant-station-connected error
Data-set-ready error on modem interface
Automatic call unit command error
Clear-to-send not active on modem interface
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Carrier-detect dropped on modem interface
Data-set-ready turn-off time-out on modem interface
Data-set-ready turn-on time-out on modem interface
Automatic call unit abandon-call-retry error
Automatic call unit telephone-number-length error
Automatic call unit power turned off
Data-set-ready dropped on modem interface
SDLC frame reject type X transmitted
SDLC frame reject type Z transmitted
SDLC frame reject type W received from remote equipment
SDLC frame reject type X received from remote equipment
SDLC frame reject type Y received from remote equipment
SDLC frame reject type Z received from remote equipment
Not valid control field received from remote equipment
Incorrect information field received from remote equipment
Incorrect frame reject received from remote equipment
Wrong sequence number received from remote equipment
No data in information frame received from remote equipment
Nonproductive receive time-out while receiving from remote
Remote equipment sent more data frames than allowed
No data received from remote equipment; time-out
Disconnected mode response received from remote system
Disconnected mode response received from remote system
Remote equipment did not respond causing an idle-time-out
No response from modem during modem test
Retry limit reached for sending frames to remote equipment
Retry limit reached for sending frames to remote equipment
Retry limit reached for sending frames to remote equipment
Retry limit reached for sending poll frame to remote
Could not send frame to remote equipment; local problem
Wrong command value sent by IBM i Operating System licensed program
Wrong response received from remote equipment
Retry limit reached for sending frames to remote equipment
Incorrect command value sent by vertical LIC
Incorrect command value sent by vertical LIC
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Nonproductive receive time-out while receiving from remote
No data received from remote equipment; time-out
Adapter card transmit error
Wrong response received from remote equipment
Incorrect command value sent by vertical LIC
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong response received from remote equipment
Wrong command received from remote equipment
Maximum retries reached on XID polls after answer
Connection cleared after answer after XID exchange
Call cleared after answer; session reset
Call cleared after answer, reset while link disconnected.
Frame-check-sequence error; error limit per 256 reached
Short frame error; error limit per 256 reached
Frame-cancel-received error; error limit per 256 reached
Idle link detected error; error limit per 256 reached
Send sequence counter error; error limit per 256 reached
Receive sequence counter error; error limit per 256 reached
Response time-out error; error limit per 256 reached
Control-not-ready time-out; error limit per 256 reached
Uncontrolled-not-ready time-out; error limit per 256 reached
State-not-known time-out error; error limit per 256 reached
Control-not-ready state changed; error limit per 256 reached
Not-ready state changed; error limit per 256 reached
State-not-known changed; error limit per 256 reached
State interrupt overrun error; error limit per 256 reached
Not valid data; error limit per 256 reached
Data-communications-equipment error; limit per 256 reached
Control-not-ready in data mode; error limit per 256 reached
Incoming call received during outgoing call; limit reached
Missed incoming call; error limit per 256 reached
Clear was missed; error limit per 256 reached
Parity error; error limit per 256 reached
Receive overrun; error limit per 256 reached
Temporary storage overrun; error limit per 256 reached
Network type 1 time-out; error limit per 256 reached
Network type 2 time-out; error limit per 256 reached
Network type 3A time-out; error limit per 256 reached
Network type 3B time-out; error limit per 256 reached
Network type 4A time-out; error limit per 256 reached
Network type 4B time-out; error limit per 256 reached
Network type 5 time-out; error limit per 256 reached
Network type 6 time-out; error limit per 256 reached
Network type 7 time-out; error limit per 256 reached
Network type 20 time-out; error limit per 256 reached
Network type 21 time-out; error limit per 256 reached
Call-progress-signal type 00; error limit per 256 reached
Call-progress-signal type 01; error limit per 256 reached
Call-progress-signal type 02; error limit per 256 reached
Call-progress-signal type 03; error limit per 256 reached
Call-progress-signal type 04; error limit per 256 reached
Call-progress-signal type 05; error limit per 256 reached
Call-progress-signal type 20; error limit per 256 reached
Call-progress-signal type 21; error limit per 256 reached
Call-progress-signal type 22; error limit per 256 reached
Call-progress-signal type 23; error limit per 256 reached
Call-progress-signal type 41; error limit per 256 reached
Call-progress-signal type 42; error limit per 256 reached
Call-progress-signal type 43; error limit per 256 reached
Call-progress-signal type 44; error limit per 256 reached
Call-progress-signal type 45; error limit per 256 reached
Call-progress-signal type 46; error limit per 256 reached
Call-progress-signal type 47; error limit per 256 reached
Call-progress-signal type 48; error limit per 256 reached
Call-progress-signal type 49; error limit per 256 reached
Call-progress-signal type 51; error limit per 256 reached
Call-progress-signal type 52; error limit per 256 reached
Call-progress-signal type 61; error limit per 256 reached
Call-progress-signal type 71; error limit per 256 reached
Call-progress-signal type 72; error limit per 256 reached
Call-progress-signal; error limit per 256 reached
Call cleared by network equipment
Network-controlled not-ready state; information only
I/O card Licensed Internal Code processed wrong command
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
I/O card Licensed Internal Code processed wrong command
I/O card Licensed Internal Code processed wrong command
I/O card Licensed Internal Code used incorrect procedure
I/O card Licensed Internal Code used incorrect procedure
I/O card Licensed Internal Code used incorrect procedure
Communications overrun while receiving network data
Communications adapter error while receiving network data
Communications adapter transmit error on selection sequence
Communications adapter received network data incorrectly
Communications controller storage not available
Call error; incoming call received during outgoing call
Network did not leave controlled-not-ready condition
Network did not leave uncontrolled-not-ready condition
Network remained in unknown condition
Network time-out type 1 occurred
Network time-out type 2 occurred
Network time-out type 3A occurred
Network time-out type 3B occurred
Network time-out type 20 occurred
Clock signal missing from external communications interface
Network call-progress-signal type 20
Network call-progress-signal type 21
Network call-progress-signal type 22
Network call-progress-signal type 23
Network call-progress-signal type 41
Network call-progress-signal type 43
Network call-progress-signal type 44
Network call-progress-signal type 45
Network call-progress-signal type 46
Network call-progress-signal type 47
Network call-progress-signal type 48
Network call-progress-signal type 51
Network call-progress-signal type 52
Communications line not operational
Port or DCE error has recovered; port now available
This reference code does not identify an error but is used to report that an X.21 port used in a short-hold mode, multiple port sharing configuration that was temporarily not operating is now available. One of the following reference codes may have been reported previously:
If any of the listed reference codes are occurring frequently and are causing performance problems, use the reported reference code to isolate the problem.
IOP Activation failed.
MDMCNTRYID parameter in Network Attributes is not set. Use the CHGNETA command to set MDMCNTRYID value.
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not valid for this adapter. Use the CHGNETA command to change MDMCNTRYID.
System log entry only, no service action required
An I/O processor Licensed Internal Code error occurred.
Tampering of cryptographic card suspected.
Operating voltage or temperature range limits exceeded.
Correct any conditions in the physical environment which might have caused the voltage or temperature out-of-range error on the 4758 adapter card. After you correct the conditions, vary off and then vary back on the 4758 device description associated with the 4758 adapter card.
Operating voltage or temperature range limits exceeded.
Correct any conditions in the physical environment which might have caused the voltage or temperature out-of-range error on the cryptographic adapter card. After you correct the conditions, vary off and then vary back on the device description associated with the cryptographic adapter card.
Cryptographic adapter LIC not loaded or not valid.
System log entry only, no service action required
Adapter monitoring circuitry has exceeded threshold.
The adapter can be varied on and used, but should be replaced during the next scheduled maintenance of the system.
Cryptographic adapter not operating at optimum performance
The cryptographic adapter will continue to run, but performance could be improved. Vary off the cryptographic adapter and then vary it on. The vary on may take up to 15 minutes. If the problem does not reoccur, optimum performance has been restored. If the problem does reoccur, contact your next level of support.
Negative-acknowledgment received
Block-check error on data received
Clear-to-send signal dropped on modem interface
Carrier-detect dropped on modem interface
Clear-to-send signal did not come up in required time
Clear-to-send signal did not drop in required time
Remote equipment did not respond in time-out period
Remote equipment did not respond in time-out period
Too many or too few synchronization characters
Time-out; no data received
Unexpected response to temporary-text-delay
Unexpected response to wait-acknowledge
Data loss because receive buffer full
No response to temporary-text-delay or wait-acknowledge
Clock signal missing from external communications interface
Clock signal missing from external communications interface
Communications IOP processed data received too slow
Data-set-ready dropped on modem interface
Negative-acknowledgment received
Remote system did not receive last acknowledgment sent
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Response from I/O card Licensed Internal Code not expected
Number of stations greater than allowed in configuration
Procedure error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Wrong response received from I/O card Licensed Internal Code
Wrong response received from I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Information only, no service action required
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Wrong configuration data given to Ethernet controller
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Wrong configuration data given to Ethernet controller
Wrong configuration data given to Ethernet controller
Ethernet adapter or network device cabling error
Configuration of DUPLEX parameter not supported by network.
Adapter does not support user-configured adapter address
System log entry only, no service action required
Automatic recovery has been attempted on the ethernet port
This error is logged for information only. No service action is required.
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Communications adapter detected storage access error
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Licensed Internal Code received not correct response
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Procedure error in I/O card Licensed Internal Code
Input value error in I/O card Licensed Internal Code
Communications controller task ended abnormally; type 1
Communications controller task ended abnormally; type 2
Communications controller task ended abnormally; type 3
Disconnect mode frame received during link activation
Disconnect mode frame received when transmitting information
Set-asynchronous-balance-mode frame received in data mode
Wrong response received from remote equipment
First call failed, retrying call; no CFI from modem
First call failed, retrying call; CFI AB from modem
First call failed, retrying call; CFI DE from modem
First call failed, retrying call; CFI ET from modem
First call failed, retrying call; CFI NT from modem
First call failed, retrying call; CFI RT from modem
Call failed, retrying call; Non-standard CFI from modem
Wrong telephone number specified in system configuration
No number specified in controller description
Wrong telephone number specified in system configuration
Wrong command received by communications controller
Wrong procedure followed by I/O card Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong data length received by communications controller
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong reset option received by communications controller
Wrong command value received by communications IOP
Wrong session ID received by communications controller
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong storage value received; communications controller
Wrong trace type received by communications controller
Wrong trace length received by communications controller
Communications controller temporary storage area too small
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Wrong command value received by communications IOP
Procedure error in vertical Licensed Internal Code
DTE/DCE role negotiation not valid for leased line
Wrong or no external communications cable installed
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong adapter type value sent by Vertical LIC
Wrong slot number value sent by Vertical LIC
Incorrect command value sent by vertical LIC
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Communications adapter card not installed
Network uncontrolled-not-ready warning; information only
Network controlled-not-ready warning; information only
Data-set-ready changed to not active; for information only
I/O card Licensed Internal Code resource not available
Incorrect command used by I/O card Licensed Internal Code
Wrong procedure followed by I/O card Licensed Internal Code
I/O card Licensed Internal Code resource not available
Wrong response sent by I/O card Licensed Internal Code
Wrong command value sent by IBM i Operating System licensed program
Wrong command value received by communications IOP
X.21 network not in the ready or receive-data state
Error when releasing communications controller storage
Error when assigning communications controller storage
Data-set-ready error on modem interface
Data-line-occupied initially 'on' error
Automatic call unit has data-line-occupied error
Automatic call unit has present-next-digit error
Data-set-ready state changed; error limit per 256 reached
Clear-to-send state changed; error limit per 256 reached
Carrier-detect state changed; error limit per 256 reached
Data-set-ready error; error limit per 256 reached
Automatic call unit has distant-station-connected error
Automatic call unit has data-set-ready error
Call failed, no Call Failure Indication from modem
Clear-to-send not active on modem interface
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Carrier-detect dropped on modem interface
Data-set-ready signal turn-off time-out
Data-set-ready signal turn-on time-out
Data-set-ready dropped on modem interface
Protocol mismatch during link initialization
Could not send frame to remote equipment; local problem
Frame check error; error limit per 256 reached
Overrun error; error limit per 256 reached
Short frame error; error limit per 256 reached
Abnormal end received; error limit per 256 reached
Long frame; error limit per 256 reached
Send sequence counter error; error limit per 256 reached
Receive sequence counter error; error limit per 256 reached
Response time-out error; error limit per 256 reached
Automatic call unit switched link time-out; no answer
Call error; incoming call received during outgoing call
Automatic call unit has abandon-call attempt
Abandon call retry error; incorrect number length
Automatic call unit power turned off
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not set. Use the CHGNETA command to set MDMCNTRYID.
IOP Activation failed.
The MDMCNTRYID parameter in Network Attributes is not valid for this adapter. Use the CHGNETA command to change the MDMCNTRYID value.
User suspected communications problem.
Vertical Licensed Internal Code sent an incorrect command
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Communications controller storage not available
Vertical LIC sent commands in wrong order
Vertical LIC sent commands in wrong order
Configuration exceeds allowed maximum for X.25 lines
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
No logical link available for packet network
No outgoing or two-way logical link available
Remote station not connected
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Logical link already disconnected
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical Licensed Internal Code sent wrong password length
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical Licensed Internal Code sent wrong data length
Vertical Licensed Internal Code sent an incorrect command
Number of user requests more than maximum allowed
I/O card LIC followed incorrect procedure
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
I/O card Licensed Internal Code ended abnormally
I/O card Licensed Internal Code stopped because of error
Network procedure error detected by I/O card lic int code
Remote system did not respond to command sent
Remote system did not respond to command sent
Remote system did not respond to disconnect command
Call rejected; wrong value from remote system
Remote system did not respond to test command
Checksum error; error limit per 256 reached
Bad data received; error limit per 256 reached
Remote system not ready; error limit per 256 reached
Vertical Licensed Internal Code sent an incorrect command
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Procedure error in vertical Licensed Internal Code
Outgoing and two-way logical channel not available
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Vertical LIC sent incorrect command values
Vertical LIC sent commands in wrong order
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Communications controller storage not available
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Application sent invalid Q/M bit request sequence
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Vertical LIC sent incorrect command values
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
Wrong command value sent by IBM i Operating System licensed program
Vertical LIC sent incorrect command values
PLC/HDLC DTE/DCE mode configured not valid
Vertical LIC sent incorrect command values
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Vertical LIC sent commands in wrong order
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
Procedure error in vertical Licensed Internal Code
Vertical LIC sent commands in wrong order
No incoming call available to be processed
This reference code usually identifies a condition that is due to a timing problem that will be recovered.
I/O card Licensed Internal Code used incorrect value
Vertical LIC sent incorrect command values
I/O card Licensed Internal Code used incorrect value
I/O card Licensed Internal Code stopped because of error
I/O card Licensed Internal Code stopped because of error
X.25 clear packet sent, packet size negotiation failed
X.25 clear packet sent, window size negotiation failed
Reset packet received; error limit per 256 reached
Command value error in I/O card Licensed Internal Code
Command value error in I/O card Licensed Internal Code
Wrong or no external communications cable installed
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Incorrect command value sent by vertical lic int code
Incorrect command value sent by vertical lic int code
Incorrect command value sent by vertical lic int code
Wrong command value sent by IBM i Operating System licensed program
Incorrect command value sent by vertical lic int code
Incorrect command value sent by vertical lic int code
Wrong command value sent by IBM i Operating System licensed program
Wrong command value sent by IBM i Operating System licensed program
Incorrect command value sent by vertical lic int code
Network uncontrolled-not-ready warning; information only
Network controlled-not-ready warning; information only
I/O card Licensed Internal Code resource not available
Incorrect command used by I/O card Licensed Internal Code
Wrong procedure used in I/O card Licensed Internal Code
I/O card Licensed Internal Code resource not available
Wrong command value sent by IBM i Operating System licensed program
X.21 network not in the ready or receive-data state
Command value error in I/O card Licensed Internal Code
Command value error in I/O card Licensed Internal Code
Communications adapter card interrupt not expected
Clear-to-send not active on modem interface
Clear-to-send signal failed to drop on modem interface
Clear-to-send signal dropped on modem interface
Data-set-ready turn-on time-out on modem interface
Data-set-ready dropped on modem interface
Input value error in communications IOP LIC
Input value error in communications IOP LIC
Input value error in communications IOP LIC
Too many frames with bad receive sequence counts
iSCSI initiator requested unknown storage target node
iSCSI Login failure
iSCSI Login failure
iSCSI Login failure
iSCSI Login failure
iSCSI Login failure
iSCSI Login failure
CHAP authentication failure
Device no response time-out; temporary error
WS IOP detected error when transmitting data
WS IOP detected parity error from device
Device detected parity error from WS IOP
WS IOP detected error when transmitting data
WS IOP detected wrong data from device
WS IOP detected wrong address from device
WS IOP detected device power turned off, and then on
WS IOP detected wrong device response to start command
Device detected wrong command or device ID from WS IOP
Device detected not valid value from WS IOP
Device detected storage or data overrun
Device detected null or attribute exception error
Device detected wrong start command from WS IOP
WS IOP detected wrong exception response from device
WS IOP detected not valid pass-through command
WS IOP detected wrong request or response from device
WS IOP detected wrong device type from device
WS IOP detected no status change from device
WS IOP detected busy time-out from device
Device no response time-out; temporary error
WS IOP detected error when transmitting data
WS IOP detected parity error from device
Device detected parity error from WS IOP
WS IOP detected error when transmitting data
WS IOP detected wrong data from device
WS IOP detected wrong address from device
WS IOP detected device power turned off, and then on
WS IOP detected wrong device response to start command
WS IOP detected wrong keyboard scan code from display
Device detected wrong command or device ID from WS IOP
Device detected not valid value from WS IOP
Device detected storage or data overrun
Device detected null or attribute exception error
Device detected wrong start command from WS IOP
WS IOP detected wrong exception response from device
WS IOP detected not valid pass-through command
WS IOP detected wrong request or response from device
WS IOP detected error downloading printer definition table
WS IOP detected error downloading printer definition table
WS IOP detected error downloading printer definition table
WS IOP detected error downloading printer definition table
WS IOP detected error unloading printer definition table
WS IOP detected device configuration error
WS IOP detected error downloading LIC to device
WS IOP detected error downloading LIC to device
Wrong magnetic stripe reader response
WS IOP detected wrong device type from device
WS IOP detected wrong display size value
WS IOP detected wrong keyboard identification
Verify that the correct keyboard is attached correctly to the workstation. If the correct keyboard is attached correctly to the workstation, perform the procedure indicated in the failing item list.
Wrong magnetic stripe reader or light pen status
WS IOP detected no status change from device
WS IOP detected busy time-out from device
Device no response time-out; temporary error
WS IOP detected error when transmitting data
WS IOP detected parity error from device
Device detected parity error from WS IOP
WS IOP detected error when transmitting data
WS IOP detected wrong data from device
WS IOP detected wrong address from device
WS IOP detected device power turned off, and then on
WS IOP detected wrong device response to start command
Printer detected equipment error
Device detected wrong command or device ID from WS IOP
Device detected not valid value from WS IOP
Device detected storage or data overrun
WS IOP detected start command to printer was lost
Device detected wrong start command from WS IOP
WS IOP detected wrong exception response from device
WS IOP detected wrong request or response from device
Printer detected equipment error
See printer documentation for more information.
Printer detected equipment error
See printer documentation for more information.
Printer detected equipment error
See printer documentation for more information.
WS IOP detected no status change from device
WS IOP detected busy time-out from device
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Printer detected equipment error
Consult the printer's manual for additional information.
Too many devices active on the workstation IOP
This error occurs if you attempted to activate more workstations than allowed. Switch off power to (or remove) one or more of the display stations (except for the console) that are attached to this workstation I/O processor. Perform an initial program load (IPL) from the control panel to correct the problem. Refer to the local workstation diagrams for the location of workstations if necessary.
WS IOP fails to report part, model and serial number
WS IOP storage failure corrected
WS IOP detected errors on all cables
WS IOP parity errors detected on all cables
WS IOP detected errors on some, but not all cables
WS IOP or IOA error during working operation
WS IOP or IOA operating system program error
WS IOP detected error when transmitting data
WS IOP detected parity error from device
Device detected parity error from WS IOP
WS IOP detected error when transmitting data
WS IOP detected wrong data from device
WS IOP detected wrong address from device
WS IOP detected device power turned off, and then on
WS IOP detected wrong device response to start command
WS IOP detected wrong keyboard scan code from display
Device detected wrong command or device ID from WS IOP
Device detected not valid value from WS IOP
Device detected storage or data overrun
Device detected null or attribute exception error
Device detected wrong start command from WS IOP
WS IOP detected wrong exception response from device
WS IOP detected not valid pass-through command
WS IOP detected wrong request or read response from device
WS IOP detected no status change from device
WS IOP detected busy time-out from device
WS IOP detected error when transmitting data
WS IOP detected parity error from device
Device detected parity error from WS IOP
WS IOP detected error when transmitting data
WS IOP detected wrong data from device
WS IOP detected wrong address from device
WS IOP detected device power turned off, and then on
WS IOP detected wrong device response to start command
Device detected not valid value from WS IOP
Device detected wrong start command from WS IOP
WS IOP detected wrong exception response from device
WS IOP detected no status change from device
WS IOP detected busy time-out from device
Wrong command sent by vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in machine instructions
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Procedure error in vertical Licensed Internal Code
Incorrect command value sent by vertical LIC
Procedure error in vertical Licensed Internal Code
Clear-to-send signal dropped on modem interface
Data-set-ready turn-on time-out on modem interface
Data-set-ready dropped on modem interface
Nonproductive receive time-out while receiving from remote
No data received from remote equipment; time-out
Remote equipment did not respond causing an idle-time-out
Retry limit reached for sending frames to remote equipment
Retry limit reached for sending frames to remote equipment
Retry limit reached for sending poll frame to remote
Could not send frame to remote equipment; local problem
Wrong command value sent by IBM i Operating System licensed program
WS IOP card failing to report part, model and serial number
Wrong or no external communications cable installed
WS IOA buffer utilization threshold exceeded temporarily
User suspected problem
Reference code FFFF is assigned by the ANZPRB (Analyze Problems) for user-detected errors. Run ANZPRB again if the problem still exists or look in the problem log (WRKPRB) for possible failing FRUs.
A B1xx reference code indicates that an event or exception occurred in service processor firmware. To resolve any B1xx reference code, determine if the SRC requires a service action or if it is for tracking purposes only.
Diagnostics analyze an event when it occurs to determine if the event requires service or if the event will only be recorded for tracking purposes and future reference. The determination is based on machine type, model, installed features, configuration, topology and activations at the time of the event.
If you do not find the SRC in a serviceable event view then it is a tracking event only and does not require service.
Dynamic recalibration is not valid on this elastic interface bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: invalid parameter passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The first clock card is defective; all processors have clock errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected a plug count greater than the limit for the multi-chip module
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chip's scan ring did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ASIC scan failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip attention handler was asked to handle an invalid attention type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An scom attention was detected on the current chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the processor subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected thermal failure due to the processor subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the processor subsystem, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be processor subsystem-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The processor VPD was invalid or missing
Failed to unflatten an error log.
A critical thermal sensor detected an over-temperature condition
CINI has detected a JTAG failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an attempt to execute an unsupported operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received invalid data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid GPTR data version.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a CFAM ID mismatch between the VPD and a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a mismatch between the ring length stored in VPD and the actual service processor ring length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A phase-locked loop (PLL) error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to get a PLL sync after 10 attempts.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The version of the data in the PLL vital product data (VPD) record is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A clock check failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chip data flush operation failed to complete in the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip's LBIST signature did not match expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip's LBIST signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip's signature was missing the engineering change (EC) level.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chip ABIST signature didn't match the expected signature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip's HBIST result did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a file error in the LBIST setup data.
The L2 line delete count exceeded the threshold.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system performed a line delete. This is an informational message; no action is required.
None.
The chip's scan ring did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An L3 cache chip's arrays were bad.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The scan ring for a chip did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chips that were tested do not have any of the good arrays required for operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The P6 small array signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SVPD function did not return the expected data length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The module VPD does not have the correct version of the data structure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CFAM ID does not match the CFAM ID in the module VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The fuse ring length does not match the fuse ring length from the module VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
eCMD function fails.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A processor chip's arrays were bad.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A processor chip had an array that was not repairable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor chip test data was bad.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the processor FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware-detected thermal failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the processor FRU, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be processor FRU-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD cannot be updated with the new L2 line-delete information because the record is already full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD indicates less space for line-delete entries than the firmware expects. This is an informational message; no action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware timeout occurred during a cache operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The L2 line delete count exceeded the threshold.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A processor chip had an array that was not repairable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an L3 CST hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an L3 RDT hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Line test failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the processor chip cache.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the processor chip cache, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be processor chip cache-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an error log entry created by a debug routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to stop the instructions.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when starting firmware. This is a secondary error; look for prior entries in the error logs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI detected a processor clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The P6 chips LBIST signature did not match the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The failing array cannot be repaired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data in the status address is not changing. Data should be changing if the test were running correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred while performing a direct memory access (DMA) read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occured while checking the L2 AVPS test status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the processor unit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected thermal failure due to the processor FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the processor unit, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be processor unit-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD cannot be updated with the new L2 line-delete information because the record is already full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor has not handed off the bus after forcing the link down; there must be a hypervisor problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has encountered a software failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI detected a processor clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to start vital clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to find a master time-of-day chip in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an SCOM attention on a chip. This chip will be deconfigured.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a CFAM ID mismatch between the VPD and a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a break in the processor fabric making it unable to find a valid time-of-day path.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to get a phase-locked loop (PLL) synchronization after 10 attempts.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No processor chip was available for the master drawer master.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The P6 chips LBIST signature did not match the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chip's scan ring did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
BIST (built-in self-test) did not finish within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chips that were tested do not have any of the good arrays required for operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The failing array cannot be repaired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CFAM ID does not match the CFAM ID in the module VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A processor chip had an array that was not repairable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor chip test data was bad.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An uncorrectable error on an up-steam bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Wire node CST hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST has detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CST has detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor wire test has detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT has detected a hardware error in the processor wire test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the processor bus controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A thermal event occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the processor bus controller, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be processor bus controller-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Corrupted data from memory was sent to the service processor without an indication that is was corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip's scan ring did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The memory controller detected an uncorrectable memory bus error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller detected a correctable memory bus error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An uncorrectable error on an up-steam bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A correctable error on an up-stream memory bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A down-stream uncorrectable error was detected on the memory bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A down-stream correctable error was detected on the memory bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An uncorrectable error on the command bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A correctable error on the command bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the memory subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the memory subsystem, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be memory subsystem-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The maintenance command timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hardware configuration is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller failed during memory diagnostics.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller did not respond to the command within the time limit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller failed during main storage diagnostics.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A correctable error was detected but the firmware was unable to capture the error information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the memory controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the memory controller, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be memory controller-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid hardware configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected a memory card mismatch. The DIMMs in the DIMM group do not match and therefore form an invalid memory group.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a DIMM group that is missing DIMMs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a missing DIMM group that is required to configure other DIMM groups in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a DIMM connected to a memory controller that does not support it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A mix of memory DIMM frequencies was detected that is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The DIMMs in the callout list are not DDR2-400.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The DIMMS in the callout list are in a configuration that is not supported on this system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The main storage diagnostics detected an uncorrectable error on a DRAM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The main storage diagnostics detected a correctable error on a DIMM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
More than the allowable number of soft memory correctable errors were detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The main storage diagnostics detected too many correctable errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An uncorrectable error on the command bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold for correctable memory errors was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to a memory DIMM or DIMMs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware failure due to a memory DIMM (or DIMMs)
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to a memory DIMM (or DIMMs), but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be memory DIMM-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when trying to set the block offset and length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A n IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the associate fabric chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The value generated was outside the expected range, and an overflow occurred. The system should checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to start vital clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected the DRAMs are not ready.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM attention line is active on the chip being called out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Vital clocks are still running and shouldnt be.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip's LBIST signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
BIST (built-in self-test) did not finish within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller detected an uncorrectable memory bus error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The main storage diagnostics detected a bad memory buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An uncorrectable error on an up-steam bus was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a memory CST hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a memory RDT hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to a memory FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to a memory FRU, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be memory FRU-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fatal error occurred during the elastic interface alignment procedure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD cannot be updated with the new L3 line-delete information because the record is already full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to start vital clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SCOM attention line is active on the chip being called out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chips LBIST signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
BIST (built-in self-test) did not finish within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
L3 diagnostics timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
L3 diagnostics failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unexpected L3 interrupt was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The L3 line delete threshold was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is no more VPD space to save the L3 line delete information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An L3 cache FBIST failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An L3 FBIST time-out limit was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The L3 cache FBIST test is not being run because all EDRAM pair halves contain line deletes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The L3 FIR bits were set before running sequential FBIST.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The transactions was not synchronized.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An interface error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An L3 line delete occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the external cache.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributed to the external cache, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an external cache failure, most likely attributable to a software problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A recoverable error occurred during the elastic interface alignment procedure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware configuration is invalid
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Hardware register access timed out
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find the frequency data that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to start vital clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected an SCOM attention on a chip. This chip will be deconfigured.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A PLL (phase-locked loop) lock error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chips LBIST signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chips ABIST signature did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
BIST (built-in self-test) did not finish within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The scan ring for a chip did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chip is bad - all processors have clock errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Line test failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wire test has detected an RDT error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the I/O subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the I/O subsystem, but could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be I/O subsystem-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: IAP warning
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware operation timed out
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A phase-locked loop lock failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to properly quiesce I/O hardware
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find the associate fabric chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Hardware register access timed out
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware timeout occurred during accessing a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No valid GXPT bus ratio or frequency was found to accommodate the chip in the GXTP slot. The chip will be deconfigured and the boot will continue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chip's JTAG was not granted the PSCOM engine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI failed during the auto TLAR calculation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an attempt to execute an operation that is unsupported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has received invalid data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SCOM attention line is active on the chip being called out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to obtain a PLL lock on the controller chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to obtain a phased-locked loop (PLL) lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chips LBIST signature did not match the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: an L2 line delete was done.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
BIST (built-in self-test) did not finish within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chips scan ring is not working properly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Line test failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the I/O hub.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the I/O hub, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be I/O hub-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI failed to enable the host PCI bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI failed to verify the host PCI bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There has been a hardware-detected problem due to the I/O bridge.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the I/O bridge hardware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be I/O bridge chip-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the I/O bus interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the I/O bus interface, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be I/O bus interface-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chips LBIST result did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip's ABIST signature didnt match the expected signature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chips HBIST result did not equal the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The scan ring on a chip did not work correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the SMA I/O hub.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware failure due to the I/O SMA hub.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the I/O SMA hub, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be I/O SMA hub-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The port ready bit was not set; unable to proceed with the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The port ready bit was not set; unable to proceed with the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A phase-locked loop (PLL) was not locked; unable to proceed with the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A phase-locked loop (PLL) was not locked; unable to proceed with the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Configuring the circumvention register failed; the test cannot proceed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data was not synchronized; unable to proceed with the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error counter was not zero; the test cannot proceed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error counter was not zero; the test cannot proceed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error counter was not zero; the test cannot proceed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chic client thread failed to collect DMA error data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
C hic client thread that was supposed to collect DMA error data encountered an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Time out waiting for CEC debug data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine the type of error from the hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI link is down. No DMAs are possible.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware protocol violation has been detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware timeout has been detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The link needs to be reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The device driver has returned an unknown error type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A file was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The RB keyword is not programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No VPD was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Resources are present but not functioning.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The processor core is not functioning, or it cannot be detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There were no functional nodes found in the system. If this is a multi-processor-drawer system, the first node is not functioning.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This indicates that there are no functional processor clocks in the system, or no active functional processor clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when creating a group object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The P5IOC2 was not functional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is not enough hardware in the system to boot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid unit id was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A card in the system is missing, or its VPD data is corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hole was detected in the plugging of the nodes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip has been found to be missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes . If this is not a tracking event p erform isolation procedure FSPSP46 located in your host server's service guide.
An error occurred while creating a chip object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The configuration of the processor card(s) is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system was found without a functional TPMD card.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A functional TPMD card was not found in a server that requires one.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Timed out waiting for a slow bus operation to complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One or more bus alignment errors occurred; look for prior error log entries with the format B1xxB2DF and take the recommended actions for those entries.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: invalid parameter passed into a function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Fatal bus alignment error occurred between items in the callout list
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Fatal bus alignment error occurred between items in the callout list
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Non-fatal bus alignment error occurred between items in callout list. System will continue to run.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to turn on a chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor was unable to turn off a chip clock.
Failure of a chip clock operation.
Internal firmware error.
The clock selection value is not supported on this system.
The IPL was restarted due to hardware deconfiguration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find a functional communication path between the service processor and the processor. Look at the error logs and guard records to isolate the failing or missing hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This is an error log entry created by a debug routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power fault was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
T he call to rdal_scom_open failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to rdal_scom_close failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ADAL SCOM error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL PSI error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL JTAG error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL mailbox error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when closing the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when shifting data in.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when shifting data out from a chip as part of a scan operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to read data from a ring inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to read data from an SCOM register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to write data to a ring inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an error when trying to write data to an SCOM register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to write data to a general purpose register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to start a data flushing process on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SCAN/SCOM device driver encountered an error when trying to write to an internal register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an ADAL MBX scratch read error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected that the value scanned out from the instruction status register of the chip is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SCOM attentions were detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a CRC miscompare, or a non-SCOM vital error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware detected a CRC miscompare error from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected either a parity error or an invalid command attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware has detected an SCOM attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI detected a processor clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid hardware configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI failed during the auto TLAR calculation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to start vital clocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a DIMM group that is missing DIMMs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected a missing DIMM group that is required to configure other DIMM groups in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to find a master time-of-day chip in the node.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Clocks that should be stopped at this point are still running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Vital clocks are still running and shouldn't be.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No processor chip was available for the master drawer master
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
eRepair data was successfully saved.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The wire test error log is full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Wire test received an invalid input parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
eRepair data was successfully applied.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system processor group object was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDT was run using the current IPL speed and type settings, even though the manufacturing flag that allows the RTD to be run at the maximum speed was enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CST detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hardware may not exist or was garded out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware may not exist or was garded out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CST has detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CST has detected a hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CST has detected a hardware error in the processor wire test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
RDT has detected a hardware error in the processor wire test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational only: Guard actions performed on items the system detected and guarded during runtime.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational only: Guard actions performed on items the system detected and guarded during runtime, or that were guarded out using the ASMI.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The guard data did not exist because it was the first boot of this system, or NVRAM had been cleared. Guard data is now available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Guard detected a new version of the guard data area. The guard data area was reformatted and the previous guard actions have been lost.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: gard actions were performed on devices the system detected and garded out during runtime.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
AH log read failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The AH server process failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip attention handler was asked to handle an invalid attention type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An scom attention was detected on the current chip.
There was a callout failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid register value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid callout was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the CEC hardware subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware problem in the CEC hardware subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the CEC hardware subsystem, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a CEC hardware subsystem failure, most likely attributable to a software problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The permanent and temporary firmware sides are both marked invalid
Power-off reset occurred. FipsDump should be analyzed: Possible hardware problem
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a pattern mismatch during the DMA test between the service processor and the processor; memory could not be read from or written to correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was received when attempting a DMA operation between the service processor and the processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware error was detected on an internal bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A CEC hardware failure was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The secondary service processor was deconfigured because there was no commuication between the primary and the secondary for more than one hour.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new DRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new NVRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An NVRAM address has appeared multiple times.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of bad blocks in the NVRAMs flash memory was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
FSI IRQ loop event occurred; one or more engines was masked.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The health monitor found that a threshhold had been exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The secondary service processor was deconfigured because there was no communication between the primary and the secondary for more than one hour.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new NVRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The threshold of bad blocks in the NVRAMs flash memory was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an ERC GPIO (general purpose I/O) failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an I2C open failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
IVPD is unable to determine the presence of end devices.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
While detecting the end device status using the I2C ADAL, both the SDA and SCL lines were found to be low. This means no devices are present on the I2C bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure the I2C bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
First-failure-data-capture unlock failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
First-failure-data-capture failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read from an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read from an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to seek on an I2C ADAL handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close an I2C ADAL handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An "invalid sub-device" error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An I2C read/write operation was retried, and failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An "invalid command" or "invalid bus speed" error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Sub-bus reset failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A query of the hub status failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The IVPD query of the HUB version failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IVPD query of the HUB version failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IVPD query of the HUB version failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IVPD query of the HUB version failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when validating vital product data (VPD) in the converged format.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid VPD format found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An I2C bus configuration operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a local device string, or the read operation was successful but the data did not match.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to set the block offset and length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when writing to the I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when attempting to reset a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The enclosure feature code is the same as the system's machine type and model. To resolve this, the enclosure "FC" keyword must be verified and reentered if necessary.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A keyword cannot be found in the VPD buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The vital product data (VPD) code exited.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to validate the format of the VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A file index was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid call was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to get the block entry information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid device type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid vital product data (VPD) format was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The file index was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The block offset and block length are greater than the calculated vital product data (VPD) image size, or the block read size is not the same as the size in the table of block data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
VTOC block offset and VTOC block length are greater than the calculated VPD image size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A parameter was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid parsing operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid synchronization file was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The synchronization success was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system ID is invalid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Setting an attribute failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Building a location failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the module VPD from an I2C SEEPROM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure trying to read one of the smart chip blocks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ECC check failed on the given FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get VTOC block entry information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Checksum failed on a FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The world-wide node name is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The RB system keyword is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system storage serial number (SG) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system unique ID (SU) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system serial number (SE) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system model (TM) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system storage type model (TN) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The world-wide part number (WN) is not valid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to connect.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A process failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A read failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when writing a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The resource ID (RID) was not tagged.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SCED sense operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the DIMM change parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the DIMM speed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No valid copy of the system vital product data (VPD) was found on this system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A recalculation failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The vital product data (VPD) was guarded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No valid copy of the enclosure vital product data (VPD) was found on this system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when finding a data block in the converged-format vital product data (VPD).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Configuration on the I2C DP failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in finding the serial number keyword data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading the table from p1.
The RB system keyword is invalid or has not been programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Validation before update failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Validation after update failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a mismatch in the VPD data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A card has been detected in the system, but valid VPD cannot be collected for it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid vital product data (VPD) port number was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid VPD port number was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A card in the system is missing, or its VPD data is corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No functional direct memory access (DMA) paths were found. The system cannot boot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An engine is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL JTAG error was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the CEC hardware JTAG.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the CEC clock control hardware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a CEC hardware JTAG failure, most likely attributable to a software problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to turn on a chip clock.
Failed to turn off the chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure of a chip clock operation.
Unable to get a pointer to the CEC cage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The clock selection value is not supported on this system.
CINI has detected a clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI detected a processor clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip is bad - all processors have clock errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the CEC hardware clock controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the CEC JTAG hardware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a CEC hardware clock control failure, most likely attributable to a software problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The panel was deactivated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Too many panels are present in the system. This is an invalid configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
More physical control (operator) panels are in the system than is allowed. This is an invalid configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is a problem with the service processor hardware time-of-day clock (RTC). It does not appear to be counting.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while writing the service processor hardware time-of-day clock (RTC). The service processor hardware may need to be replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service procesor time-of-day is invalid. If the error occurred while reading the service processor's hardware time-of-day clock (also known as the real time clock), this error indicates that the time of day must be set to a valid time. If the error occurred while setting the service processor's hardware time-of-day clock (the RTC), the service processor may need to be replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor battery needs to be replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI link is down. No DMA operations are possible.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Communication paths on the service processor side are not enabled to do DMA operations.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The link needs to go through retry/failover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was detected by the operating system when communicating with the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No functional direct memory access (DMA) paths were found. The system cannot boot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An IAP error that was not fatal occurred, or an IAP warning was issued. The system should be rebooted in slow mode to diagnose this potential problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find a functional communication path between the service processor and the processor. Look at the error logs and guard records to isolate the failing or missing hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a pattern mismatch during the DMA test between the service processor and the processor; memory could not be read from or written to correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was received when attempting a DMA operation between the service processor and the processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI link is not active on the service processor side after enabling it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The PSI link has errors on the processor side after enabling it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hypervisor has not handed off the bus; there may be a hardware problem with the interrupt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A PSI link surveillance failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware failure due to service processor code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A PSI link error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No PSI link error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A socket error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A connection error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor synchronization (SINK) interface timed out waiting for a firmware component to create a synchronization lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The operation to dynamically load a library failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Network data was not available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A cable is not plugged properly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The host is only on one network.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid connection was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power fault was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open a synchronization file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The DMA driver has encountered an error, and the firmware was not able to determine if the error was due to a checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error, and the firmware was not able to determine if the error was due to a checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a read operation in the IPL mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error in IPL mode in which a write has worked but a read has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a write operation in the IPL mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error in IPL mode during write operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a read operation in the TCE mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error in TCE mode in which a write has worked but a read has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a write operation in the TCE mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error in TCE mode during a write operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A DMA adal read returned zero bytes of data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
User-given data length doesn't match the amount of data being DMA'ed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A DMA adal write returned zero bytes of data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
User-given data length doesn't match with the amount of data being DMA'ed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test failed because the data being read does not match the data that was previously written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test failed because the data being read does not match the data that was previously written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test for DMA failed while writing random data at the host address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation type was not read or write.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the file name for a new socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor has not allocated enough storage for the data structures being built.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor either retrieved invalid data from CEC memory, or there are too many FRUs to process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An integrity check failed on data that the service processor retrieved from CEC memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clocks are in the wrong state for this SCOM operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected a plug count greater than the limit for the multi-chip module
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The main storage diagnostics detected a special type of uncorrectable error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to a subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to a subsystem, but it might also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem, but this could also be miscellaneous subsystem-related problem or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by software. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI link is down. No DMAs are possible.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CEC is not configured properly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A DMA operation failed, but the hypervisor is not accepting messages. In this case, DMAs are invalid so an informational error log is passed back to the caller.
An error occurred when deactivating the wake-on-LAN hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request to clear the error/event log has been processed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: the error logging server has been started.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data synchronization thread on the error logging server was not started.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data sync thread was cancelled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Sub-bus reset failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The role changed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the error logging firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IPL is being terminated due to the loss of the primary node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error due to the loss of surveillance when activating a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is a node present that is not under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a node controller failover request by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a request to disable a note controller by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the ping acknowledgement received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A node controller surveillance error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
RDAL reported a GPIO close failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
RDAL handle failure
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hard socket failure disconnection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write data to a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system power interface (SPIF) server thread was canceled while sending a command to the system power control network (SPCN).
These SRCs are added to the primary SRC to show control flow.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was passed to a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to verify the type of system enclosure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine the enclosure type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SMP cables are plugged incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IVPD data for a cable does not match any known cable types; check for improperly plugged cables and correct any problems that are found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SMP cables are not plugged in securely.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find a functional communication path between the service processor and the processor. Look at the error logs and guard records to isolate the failing or missing hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a user-overridden logical memory block (LMB) size that is not valid for the systems memory size. The CINI will instead use the default LMB size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Resources that had been guarded out were returned to the functional state to allow the system boot to continue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor is about to be reset with toolreset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Communications failure with RETAIN.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system called home to the IBM service center. This entry tracks the successful communication with the RETAIN server. Errorlog information shows the PMH number in the user details section. with the RETAIN server. Errorlog information shows the PMH number in the user details section.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Service center did not respond as expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system failed to log into the IBM service center.
Verify system is entitled to RETAIN/IPAP service. Verify call home settings are correct. perform call home test and examine error log for other fialures.
Verify that the correct hemisphere data has been programmed. Also confirm that the system is entitled for service via the IBM service center.
Verify that the system is entitled to service and is registered with RETAIN.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to an unknown subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware failure, but the cause cannot be determined.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to something in the hardware, but could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem from an unknown subsystem; it will require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by an unknown entity. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Processor runtime diagnostics (PRD) has found an invalid attention type in the attention data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new NVRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: The hyperboot capability registry entry was changed to capable and the IPL speed to hyper because NVRAM was reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor rebooted to Standby on iplp/NextSide.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hyperboot capability setting was changed to capable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The iplp/IplSpeedOverride and iplp/CurrentIplSpeed values are being changed to the input speed Value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor's time-of-day clock is invalid. This error indicates that the time-of-day clock must be set to a correct time before the next system IPL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the real time clock ADAL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Internal service processor time-of-day data was initialized to a default value. This may be due to an NVRAM battery or service processor replaceme nt, or because the service processor was reset to factory defaults.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor's time-of-day has changed. The error log detail contains information that is useful in analyzing time change events.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The timed-power-on function was disabled when the service processor discovered that its time-of-day was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data was received by a service processor time-of-day process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Write the IPL type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Tool reset has been requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power-cycle reset request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The fspipltype variable's value was modified to modified to keep the primary and secondary service processors' roles in sync.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A duplicate add event was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A duplicate removal event was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error during a forced device addition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The IOMUX (I/O multiplexer) configuration is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The configuration file key is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
frum detected a bad fsi link.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failover could not be initiated because rmgrBackupFailoverCapability indicates that it is not allowed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open the dhclient.pid file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
ipconfig failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a DHCP link error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open the DHCP client leases file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the DHCP lease file information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to check to see if the link is up or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to read DHCP failure tracking registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
When the node controller was booting, it was unable to obtain an IP address for 30 minutes or more. However, the DHCP client was able to get an IP address and the controller booted successfully. A dump was generated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
When the node controller was booting, tftp failed multiple times. It then recovered and the node controller booted successfully. A dump was generated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IP address for the node controller was not assigned based on the node ID and side but is from a pool.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDAL's ERC connection failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
RDAL's ERC write failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
I nvalid AIO parameters were passed to rdal_aio_ctx_submit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The RDAL ERC object was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC hard failure was recorded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The BFMK ERC object was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The IPL type was written to the registry.
There was an error when closing the session.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the SSL part of the connection
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when getting the socket options.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when setting the network interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to read the registry value that indicates whether or not the network is available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Return from the error log indicates that the connection to a storage subsystem was not made and the connection timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure from the nets_process_sess_cmd() function occurred during a serial-over-LAN session. The message was received from a storage subsystem but failed to process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: Serial over LAN (SOL) processing was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A time-out occurred because the file does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The loading of a shared library has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a library DL synchronization error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: cannot open a device
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: failed to set up the FSI adapter; the sibling is not present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: failed to set up the FSI adapter; the sibling is not present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
IFCONFIG mailbox 2 failure.
If this is a tracking event, no service actions are required. IBM Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set up the FSI adapter; the sibling is not present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure the IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to write to a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A network reset was issued as the pin value changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A network reset was issued as the pin value changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: FrumWaitDeviceList timed out; cannot open the device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A software open error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A VLAN remove operation was performed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The network configuration data from the user was incorrect.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The device cannot be opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting an IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ARP send operation was performed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mailbox route was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A DHCP failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure when creating the route.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A dump request was rejected by the service processor. It is possible that a dump was already done or in progress at the time of the request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while trying to write data to CEC memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An integrity check failed on data that the service processor retrieved from CEC memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error log was generated at the end of the memory test. This indicates that non-terminating errors were generated during the test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A secondary SRC was added to show control flow. The primary SRC indicates the actual error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory test completed successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Terminations have been disabled so AVP-related errors will simply cause reboots.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open the directory into which this data file should have gone.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to find the input keyword or record in the module VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The processor core is not functioning, or it cannot be detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: an IAP warning was issued.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The elastic interface alignment procedure never completed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fatal IAP error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Keys were not found in a table. This could be any table and any keys, so the details in the error log entry are very important in debugging this type of error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when forcing a lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CEC encountered a power line disturbance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The secondary service processor has detected missing devices.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The parent chip returned a null value for ruleCommonFacade.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The clocks are in the wrong state for this SCOM operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An operation was attempted on a non-functional unit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Internal software information log entry; informationl message only.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An engine is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when opening an ADAL (access device abstraction layer) to a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when the firmware tried to close the SCAN/SCOM device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver is unable to scan the data out from the ID register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an internal problem: a chip doesnt have a valid scan interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL SCOM error was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL PSI error was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL JTAG error was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an ADAL mailbox error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when shifting a command into a chip as part of a scan operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware timed out when waiting for a JTAG lock to be granted by the JTAG ADAL (access device abstraction layer).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver encountered an error when trying to read the status register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an error when trying to read data from a ring inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to read data from an SCOM register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver encountered an error when trying to read a GP (general purpose) register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCAN/SCOM device driver encountered an error when trying to read an internal register on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected that the value scanned out from the instruction status register of the chip is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an SCOM attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected either a parity error or an invalid command attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware has detected an SCOM attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ivJtagEnginePtr pointer is NULL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a user-overridden loginal memory block (LMB) size that is not valid for the system's memory size. The CINI will instead use the default LMB size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The number of memory errors detected by main storage diagnostics exceeded the manufacturing threshold.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A memory-preserving IPL occurred, so a summary error log was created to terminate the IPL, and that previous logs that pointed to hardware or software failures had been created and committed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One or more of the wrap tests failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The L2 AVPS test has completed successfully (informational message).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Summary errorlog: this error log indicates that there is one or more memory AVPS test failures.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A summary error log was created to terminate the IPL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Summary errorlog: this error log indicates that there is one or more L2 AVPS test failures.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: The memory test case completed successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unexpected signal was caught.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected informational message of unknown origin. No action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an informational message due to hardware, but could also be software-related. No further action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a software problem; this is an informational message. No action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This indicates the requested action failed because the sibling service processor is not in the working state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This error log entry is generated when the hypervisor fails to send its heartbeat message within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This error log entry is generated when the HMC fails to send its heartbeat message within the allotted time. The reason could be network issues, or the Ethernet cable is disconnected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There has been a hardware-detected problem due to the firmware subsystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the firmware subsystem, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a firmware subsystem problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by a firmware component. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure in the service processor firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
"Malformed" SRC
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error; unable to determine if a hardware checkstop has occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error; unable to determine if a hardware checkstop has occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a read operation. (The checkstop needs to be analyzed to determine the root cause of the failure. The dma failure is a secondary effect of the hardware checkstop.)
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error during a read operation. The error information needs to be analyzed to determine the cause.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a write operation in IPL mode. Look for an error log entry generated by PRD (processor runtime diagnostics). (The checkstop needs to be analyzed to determine the root cause of the failure. The DMA failure is a secondary effect of the hardware checkstop.)
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error during a write operation. The error information needs to be analyzed to determine the cause. If the first DMA operation always fails with this error, it is probably a hardware problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a read operation. (The checkstop needs to be analyzed to determine the root cause of the failure. The DMA failure is a secondary effect of the hardware checkstop.)
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error during a read operation. The error information needs to be analyzed to determine the cause.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an error due to a hardware checkstop during a write operation in TCE mode. Look for an error log entry generated by PRD (processor runtime diagnostics). (The checkstop needs to be analyzed to determine the root cause of the failure. The DMA failure is a secondary effect of the hardware checkstop.)
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver has encountered an unknown error during a write operation. The error information needs to be analyzed to determine the cause.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A read was attempted, but the DMA driver returned zero bytes of data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The amount of data being transferred by DMA does not match the length passed in by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A write operation was attempted, but the DMA driver returned zero bytes of data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The amount of data being transferred by DMA does not match the length passed in by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA driver could not be opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA user attempted a DMA read with a length of zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA user attempted a DMA write with a length of zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
DMA user provided NULL as an address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
NULL was received by a function as the service processor's (or system controller's) address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA user attempted a DMA during a window in which DMAs are not available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The sbcu/BusController register did not contain one of the expected values.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CEC is powering off. There has been a power off just before, or during, the DMA operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test failed because /dev/urandom could not be opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test failed because /dev/urandom could not be read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chic client thread timed out trying to collect DMA error data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The event management constructor failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to read registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is a DMA code error. One thread is overwriting another.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The timer returned an unknown error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Chic call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chic client thread failed to collect DMA error data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Manufacturing test failed because of incorrect DMA mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Chic client thread that was supposed to collect DMA error data encountered an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Svpd call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Svpd call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current resource ID did not match the list of available resource IDs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA path could not be determined.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
DMA paths were found, but none of them was marked as the primary path.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DMA user provided an invalid address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Dmae detected an unexpected event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The spif/PowerState register is undefined.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
DMAE could not determine if the CEC was powering off.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Time out waiting for CEC debug data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A CEC data processing operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to interpret the first-failure-data-capture (FFDC) data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
PSI link is down.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Communication paths on the service processor side are not enabled to do DMA operations.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CEC is not configured to do DMA operations.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The link needs to go through a reset, then failover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Software detected a timeout.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A DMA was attempted with an invalid address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A DMA was attempted using an invalid TCE token.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor is trying to write a read-only or read a write-only page.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is a problem in the device driver code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation was cancelled by the caller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid HOM node information was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A component name of NULL was passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Corrupted data was sent to the service processor or system controller without an error being flagged.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Corrupted data from memory was sent to the service processor without an indication that is was corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The user passed in a component name of NULL.
Failed to open the master I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure the master I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the panel via the master I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the master I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the slave I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a slave read error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to close the slave I2C device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid parameter was passed into the function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The panel attention command that was received did not have a valid checksum.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The panel attention command that was received was not valid because the "press and release" button sequence was violated, or an invalid button action was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to lock the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to stop the execution of the thread holding the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to lock the mutex with a timeout.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unlock the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a value from a registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the possible resource identities of all the panels in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No panels may be installed in this system according to VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to determine if the panel is present or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the number of panel resource IDs that may be installed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred getting the master and slave I2C device paths and the panel I2C device address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No master I2C device was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the internal scroll command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the soft reset command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the display data write command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the lamp test command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the button control command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the LED control command to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a panel attention command from the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a problem in the way the function was called, or it an invalid parameter was passed to it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invaled attribute was specified in an attribute parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid address list was specified in the address list parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An errror was encountered while trying to detect the SVPD read mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The mode is unknown.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was encountered by the external library interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The external library interface received a zero-size data length from the svpd_read_data_persistancy interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A non-null value was detected in the data address pointed to by the data address pointer parameter; a null pointer is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered by the external library interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A first-failure-data-capture deadlock was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to configure the I2C bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
First-failure-data-capture unlock failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
First-failure-data-capture failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read from an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to seek on an I2C ADAL handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid device information was passed to the IVPD library.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close an I2C RDAL handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close an I2C ADAL handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An I2C bus node was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An "invalid sub-bus" error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An "invalid command" error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An "invalid bus speed" error was returned by the hub expansion processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid operation was specified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The first level of basic input parameter validation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The process message request data size is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was insufficient data in the process message request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was insufficient data in the process message request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SVPD_get_dev_addr_string failed and returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to reset the I2C engine or bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when trying to read the thermal sensor temperature data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A null pointer was received in an array parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid device type was used to call a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid device type was used to call a function, or the register that was requested is not available on this chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid device type was used to call a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A device was closed but never unlocked. This may cause I2C bus problems later.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
IVPD detected that the SEEPROM interface was called to access a non-SEEPROM device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A node controller was missing from the address string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid node was found in the address string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A node was missing in the address string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An I2C device path was missing in address string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A subbus address was missing in the address string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to configure the I2C bus for a module.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open the I2C bus for a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Tried to open the master I2C but to a device, but it was already open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the control registers of a module.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the read register command to a module.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The last function sent failed after several retries.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to convert a bad device string into a device structure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to reset the open master I2C bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The master I2C bus going to the device to be read is not open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The node controller B I2C device path was missing in the string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The address list that was created was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to call process functionality that is not supported at this time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid argument was passed to a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to ADAP open failed for the secondary file descriptor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The message received was larger than the message buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A nonzero return code was returned by the smartchip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unexpected null pointer, or zero, passed to routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A null pointer was expected for a given parameter in this routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain the svpd read mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain svpd read mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the data persistency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain data from persistent memory in filemode. The file corresponding to the device given does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write block data to persistent memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain the block in filemode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The block that was searched for does not exist or contains invalid data in filemode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid block data size in filemode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid block name length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure the UART.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to reset the UART.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a UART handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the UART device handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the UART buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read data from the UART buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The size of the data written to the UART buffer is not equal to the size of the data that was sent to it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data obtained from the UART is bigger than the expected data size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned when extracting the node ID from the device address string.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to check on the existence of the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to rename the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to rename the smartchip lock file, and thus failed to release the lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain a handle on the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain a handle for the smartchip lock file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Device address format given is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain the free space on a given smartchip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain the free space on a given smartchip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Timed out waiting for a response from the universal asynchronous receiver/transmitter (UART) read buffer command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid number of bytes was returned by a chip in response to a read command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid process message operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to receive a request buffer from the process message interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The process message request buffer had no data in it
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The smartchip request size is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The smart chip packet size was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unlock the UART FFDC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unlock the universal asynchronous receiver/transmitter (UART) RDAL failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A first failure data capture (FFDC) at the thread level returned multiple blocks of data; this is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure of an attempt to see if padding of the packets being sent to the chip is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to perform presence detection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to enable/disable the smartchip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create a context for a control block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize an event structure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize a control block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A submit operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A wait operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Return data operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A UART event extraction failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A UART event extraction failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Multiple attempts to recover from a chip communication failure have been made, and failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A time-out occurred waiting for the response from the universal asynchronous receiver/transmitter (UART) read buffer command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A non-zero return code was returned by the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip responded to with a "receive ready" flag to a resynchronization request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip sent a response to a non-resynchronization request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Sending a packet as a response to a chip resynchronization failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A bad response was received from a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the chip line status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write the chip line status changes to enable the port's DCR lines.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write the chip line status changes to enable the chip reset line.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write the chip line status changes to disable the chip reset line.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to reset the UART.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Locking a binary semaphore failed when attempting to reserve a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unlocking a binary semaphore failed when attempting to reserve a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Locking a binary semaphore failed when attempting to release a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unlocking a binary semaphore failed when attempting to release a lock .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip lock has been taken over due to two minutes of inactivity.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The user number received to lock out the chip was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip returned an unexpected response when attempting to lock out a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The attempt to delete aiocb failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The RDAL UART event extraction call returned an invalid status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A device address string was received that shorter than 22 bytes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip lock has been taken due to inactivity for a specified length of time, or the priority of the current user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The smartchip for the device given is not reserved.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The smartchip is currently reserved by this caller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The smartchip for the given device is locked by another user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SPIF application received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_once POSIX function has returned an error in system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_setspecific POSIX function returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) internal error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) internal error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid parameter was passed to a system power interface firmware (SPIF) function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_mutex_lock function returned an error in system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_mutex_lock function returned an error in system power interface firwmare (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) failed to create a software object necessary for further processing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) timed out waiting for a particular event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured during the updating of system power interface (SPIF) server's internal power state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SPIF detected invalid data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SPIF failed to synchronize with the power process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured in system power interface firmware (SPIF) while processing an error log object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured in system power interface firmware (SPIF) while processing an error log object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One of the spif_queue mutexes could not be initialized.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured while attempting to initialize SPIF thread condition variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured while attempting to erase SPIF thread condition variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One of the spif_queue mutexes could not be erased.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) terminated the system because it detected a power fault.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_cond_wait function returned an error in system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The pthread_cond_signal function returned an error when called from system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_create function has failed in system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) failed to cancel its threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_setcancelstate function returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_join function has failed to join the SPIF server threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SPIF server has routed an acknowledgment message to the command queue. This indicates an internal problem with the SPIF server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A command sent by SPIF was rejected by the power firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SPIF client found that the SPIF server was not ready for communication.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System Power Interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was caused by invalid arguments in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) internal failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) internal failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_detach function has failed to detach in system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured while updating the operator (control) panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Power on/off notification failed because of bad service processor state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Power off notification by SPIF to the service processor's state manager failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Power on notification by SPIF to the service processor's state manager failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_cond_timedwait() call timed out on a thread condition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The pthread_cond_timedwait function returned an error when called from system power interface firmware (SPIF).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log is returned by SPIF when a queue is full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This error log is used by SPIF when the queue is empty.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One of the two input parameters is NULL. The SPIF server cannot function without these parameters.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SPIF client failed to send a message to the SPIF server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unexpected data were detected by SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal function call has failed in SPIF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) internal error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Power-related function failed in SPIF
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A system power interface firmware (SPIF) command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System power interface firmware (SPIF) communication error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
REMP initialization failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Memory allocation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when creating a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid parameter was passed to a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid command was received from an RPC device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The message had an invalid function ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call returned a time-out condition, but no time-out was specified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The file descriptor that was expected was not set after the system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CDAL call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to insert the initial events into the queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when removing a message from the queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error log was committed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The power lock error log was committed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The netc close operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error from the event manager was committed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a token queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to insert tokens into the token queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The number of threads exceeded the maximum.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the power lock (PLCK) interface was opening the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced an error when unlocking or closing the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock interface experienced an error when initializing the header of the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the power lock (PLCK) interface was reading the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the power lock (PLCK) interface was updating the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced an error while trying to read the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced an error while trying to write to the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface was not able to read the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid pointer was passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid parameter was passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power state of the system was not valid for the IPL lock that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface could not determine the current power state of the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open and lock the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close or unlock the power lock lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A firmware component has used the power lock (PLCK) interface incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A firmware component has tried to use the power lock (PLCK) interface incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A firmware component has used the power lock (PLCK) interface incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the power lock (PLCK) interface was allocating memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced a threading error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when removing the lock from the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware component that requested the unlock operation did not have a lock on the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The requested IPL has been blocked by the power lock (PLCK) component. The IPL will proceed when the lock has been released.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A value passed into a function was out of range.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface received an immediate IPL request and bypassed any existing power locks.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The state manager (SMGR) firmware component has rejected an IPL request made by the power lock (PLCK) interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power IPL has already been requested and queued by the power lock (PLCK) interface. Therefore, this IPL request will be rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send a power-on event to the panel for the requested IPL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send a power-off event to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) process did not initialize correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) process was did not initialize correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid argument was passed into the timer thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) process received an unexpected signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced a threading error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power IPL was already in progress, so another IPL lock could not be created.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface could not determine if a power on or power off was in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced an error when indicating that a power IPL was started.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface was unable to determine the current firmware state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A firmware component has used the power lock (PLCK) interface incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface was not able to determine the size of the lock data file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The power lock (PLCK) interface experienced a problem while determining how much time has elapsed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The power-on request cannot be processed because the system has not been granted the appropriate permission by the IPMI component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The original IPL request has been mapped to an APOR IPL type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read apor/armed from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid parameter passed into the function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a registry value.
An unexpected signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A fork operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function received less data than it was expecting.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A synchronization failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A registry read failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A registry write failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to build a constructor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get an SRC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in an event monitor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A daemon was not ready.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
PLCK returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A bad return code was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The secondary service processor (or system controller) did not reach standby within the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the wake-on-LAN policy from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the service processor role from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the system operation mode from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the service processor device driver level from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write the wake-on-LAN policy to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the p0 file path from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read svpd/WakeOnLAN from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when activating the wake-on-LAN hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when deactivating the wake-on-LAN hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wake-on-LAN is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wake-on-LAN is not supported on this system because there is no Ethernet card.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The value of the wake-on-LAN policy is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the current power state of the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the current wake-on-LAN policy.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the MAC address from VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to determine from VPD whether wake-on-LAN is supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wake-on-LAN is not supported on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the status of a FRU from VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the maximum number of field replaceable units (FRUs) from vital product data (VPD).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start the wake-on-LAN process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the process synchronization file for the wake-on-LAN process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Another wake-on-LAN process was already running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to power on the system via wake-on-LAN.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while processing the wake-on-LAN interrupt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while waiting for the wake-on-LAN interrupt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to wait for the requested state of the wake-on-LAN interrupt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the general purpose I/O pin to the appropriate level.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the general purpose I/O device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the general purpose I/O device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to shift the data into the target chip via the JTAG device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to lock the JTAG device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the JTAG device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the JTAG device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to initialize an asynchronous input/ouput control block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the context for an an asynchronous input/ouput device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Received the wrong number of asynchronous input/output control blocks from the AIO device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Submitted the wrong number of asynchronous input/ouput control blocks to the AIO device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to delete the asynchronous input/output control block from memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to delete the context for an asynchronous input/output device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to drive the input/ouput pin to the correct level.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the general purpose input/output device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the general purpose input/output device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to initialize the general purpose input/output events.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to shift data into the target chip via the JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to lock the JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open the JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A vital product data (VPD) error occurred.
Use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred when processing a request in TMGT
The sensors could not be read due to thermal monitoring being disabled
The processor FRU RID is not present in the TMGT configuration tables
The alert level is invalid
The domain is invalid
The o_throttlePowerArray is NULL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Command to POWR via SPIF failed
Request to CHIC/PRD failed
When the processors were being polled about their utilization levels, at least one processor returned an invalid status.
The processor card's thermal index is invalid, or the function is not supported
Invalid chip number
Invalid message size
GPIO read failure
Registry read operation failure
A TPMF failure was logged during a reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A critical error occurred on the thermal/power management device (TPMD); it is being disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a TPMD download failure in state 3.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An I2C send failure was logged.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A checksum failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
TPMF communications was not established, or an unsupported application was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The TPMF failed to respond.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The TPMF response has an invalid length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was created by the thermal/power management device (TPMD).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The I2C interface controller failed to enable the I2C interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
chicReserve failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
chicRelease failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid thermal throttle value was passed in set command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The get throttle status command was not sent because there was no communication to the TPMF.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Received zero entries back from chicGetCoreStatus call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
"IPMI Throttle Watts" call failed when getting the maximum power cap.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to get a common card identification number (CCIN).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Safe mode is complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The thermal and power management firmware (TPMF) is not in a good state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mode will not be changed - already in nominal mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write the current power cap value to a registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Mnfg mode is enabled and TPMF is oversubscribed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The get throttle status command was not sent because TPMD is being downloaded.
The mode will not be changed - already in nominal mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to change the memory controller mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to calculate the system's ideal clock speed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get into the active state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The frequency change was canceled due to failures to read the registry.
A TPMF voltage change timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to calculate the system's ideal clock speed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mode change that was required for concurrent maintenance failed.
Informational message: the mode change was successful.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
When the thermal and power management firmware (TPMF) was polling for the utilization of each processor, no functional processor cores were found. At least one should have been found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to acquire an I2C bus lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Changing to a new state or mode is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error writing the new TPMF state to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid voltage control command was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The daemon received a message with an invalid function field.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The POWR server wasn't ready for the command it was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The daemon received a request while running on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The "power off unit" command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A secondary error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The array depth was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Non-terminated input was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The input was null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The input was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The instance was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Code update was busy.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when writing a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when getting data from a registry variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set a registry variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system firmware installation image is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system firmware installation image is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is at least one part of the firmware in the specified flash that is corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A problem was encountered during system firmware installation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The process that started firmware update is not the process that is requesting that the firmware update be ended.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to write the registry data, but it had already been written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A flash side other than temporary (T) or permanent (P) was specified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: Firmware update is attempting to update the P side of the firmware flash.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system firmware installation image is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Firmware image module does not exist .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A firmware update module did not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Firmware installation was not allowed due to a limitation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to request a power lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system firmware installation image is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The buffer provided is too small to store the data and header information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A firmware installation was attempted the side from which the system was booted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to installation the system firmware on the flash side with the good image when the other flash side has a bad image. This is prohibited; otherwise, both sides could become corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
After the firmware was installed, the newly-installed firmware was found to be corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to execute cupdLidValidation()
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request was made to installation a file beyond the file's size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a problem with the flashing of the firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid component ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A firmware installation code module was being modified, when another modify request was received. The request was denied.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The digital signature does not match the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: A firmware installation was successfully performed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid code installation type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A data file was sent with the incorrect header format.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The power state is invalid. Firmware update from the HMC is only allowed when the managed system is at standby or running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The file offset that was specified exceeded the file size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request has been received to abort the flash update.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was detected while creating an event manager object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The wrong firmware image was sent to the service processor to be flashed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This indicates that the service processor no longer has the power lock (that is refreshed by the HMC) during a firmware update because it has rebooted for some other reason.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data is not correct.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Reading a file failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data necessary to store a certain type of information is not the correct size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid system firmware flash installation file was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the keyword that indicates the bank ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The code update policy cannot be changed due to an inband update.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hardware management console (HMC) requested an invalid operation, or an operation that is no longer supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Setting CTX from the registry failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Mirroring of volumes failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Set "no updates allowed" policy on a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to obtain a firmware module's cyclic redundancy check (CRC) value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The stat command failed on a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Reading a file failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The operation failed to create a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Generic network communication failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Network communication receiving failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Generic network communication failure closing a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to establish communication pipe to the error log server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to talk to the hypervisor failed, and will be retried.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Generic failure writing data to the file system; possible file system problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Generic read failure of data on the current stream.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to expand an error log failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to read the manufacturing policy flags failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to read via the error log server pipe failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An event caught by the error log server was found to have an incorrect data length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to notify the system of a new error log entry has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to collect error logs that were committed prior to the error log server being fully initialized has failed; possible file system problems.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The change of state failed for the given entry ID.
Input data was found to be corrupted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to assign a unique entry ID failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to turn on the platform service indicator failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log operation failed due to an invalid section header ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log operation failed due to the section size being invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log operation failed due to an invalid section version.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation failed due to an invalid section count in the section header.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Generic network communication failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log server detected an unrecognized signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current operation failed due to invalid data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log file system detected a possible problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Operation to call home has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log server failed to initialize its file system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to format the error log file system failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log server has been fully initialized; informational only; no action required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log server received a syslog message which requires attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current operation failed due to the current Linux system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to unload the file headers into the error log file system failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation failed due to the secondary service processor not responding during the alloted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to initialize the P3 statistics file.
The error log server detected a possibly fatal hardware error in the service processor flash.
The error log server detected a possibly fatal hardware error in the service processor flash.
The data synchronization thread on the error logging server was not started.
The data sync thread was cancelled.
The role c hanged
The event monitor detected that the sibling service processor's (or system controller's) state changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A generic unknown failure was received; current error log operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A bad command argument was passed to IPLP.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The argument after "iplp speed_override" is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The argument after "iplp speed_override" was invalid in a command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
iplp_process_msg recevied an invalid operation code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid number of arguments in a command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred reserving the iplpInterface semaphore.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An iplp application received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A side-switching boot is not allowed for the given CecIplType.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A side-switch reboot failed; firmware is not valid on the new NextSide.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data was received for SysClickToAcceptState.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextPlatformIplSide.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextSystemIplMode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextPlatformIplSpeed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextPlatformIplSpeedOverride.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextHypervisorIplState.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextRpaPartitionIplMode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received for NextCecLmbSize.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The iplpRegMon daemon discovered that the P2 registry was recently cleared, and all entries were set back to default values. Some customer settings may have been lost. If the P2 registry was not intentionally cleared, it's possible that there's a firmware or hardware problem with the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The iplpRegMon daemon could not get the lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A task failed to fork.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was rebooted due to invalid registry data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The interface that was called is not supported in the current context.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A side-switching IPL is needed, but the firmware on the secondary service processor is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The argument after 'iplp set_maxiplspeed' is invalid.
The argument after 'iplp set_maxiplspeed' is missing.
The service processor is no longer booting in hyperboot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: The IPL speed was changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A firmware installation was done, so the next system boot will not be in hyperboot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal service processor time-of-day process did not complete successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data was received by an service processor time-of-day function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to set the service processor's time-of-day when the service processor was not at standby.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A service processor device driver returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while reading time-of-day function parameters from service processor storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while writing to the service processor time-of-day clock. Install all server firmware updates before any hardware is replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error log could not be properly constructed by the time-of-day process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor time-of-day process encountered a fatal error and had to be restarted. Install all server firmware updates, if available, before any hardware is replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the real time clock ADAL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid time-of-day operation request was received by the service processor, most likely from the HMC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor process could not get exclusive access to resources that were needed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor time-of-day process failed to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor time-of-day process failed to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while the hypervisor was attempting to set the service processor's time-of-day clock. This is a temporary error that may indicate that the command took too long to process and had to be repeated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor time-of-day process failed to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure trying to fork the smgrinit process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to allocate storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to write MSQueue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
State (current/next pair) invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Terminate request was received from non-CTRM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Registry size to data mismatch.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Registry data incorrect
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Registry read failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Registry write failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Call to service proces sor initialization routine failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Read in do_dump failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The state manager's state was set to invalid.
Smgrinit has failed to open /proc/reset/.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Smgrinit has failed to decode the reset values.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Smgrinit has failed to build the message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system was powered on with service processor failover disabled, even though a functional secondary service processor is installed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error synchronizing the trans handler and request handler threads with a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Bad message passed to trans handler thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error reading data from internal mapfile data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The request to reboot the service processor was returned or it failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Incorrect map data, or no map data, for the IPL request type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A parameter was out of range.
Reading the MNFG flag for reset/reload failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Smgr client library has been passed a bad parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Smgr client lib has detected an extneral error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Smgr client lib has failed to synchronize with server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Validation of the persistent control storage failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A power cycle reset request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A counter's time stamp was incorrect.
A time-out occurred while waiting to unlock the file so that is could be read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error reading the specified file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The exec to run the command to reboot all node controllers failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to get a valid value from a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The exec to run the command to reboot all node controllers failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error opening the sys entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
error returned from exchangeBootSide()
error returned from exchangeFspIPLType()
error returned from exchangeInfoExgCompleteCmd()
Error returned state execution
An error was returned when writing the redundancy status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Discovery exceeded the retry limit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
error returned from exchangePreviousMaster()
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when trying to connect to the sibling service processor or system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
When checking the guard state, the sibling service processor or system controller was found to be guarded out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The response from the machine-type, model, and serial number exchange was empty.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to create an address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to create an address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading the service processor's state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from goodPathRelationDetermination()
Error returned from sibling when requesting that he sets up his role
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported command was received from the sibling service processor or system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The response from the secondary service processor contains no data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from setAddressObj()
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from setSiblingState()
Error returned from an information exchange function
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to switch sides.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A sibling was detected, but the communication lines broke down, and the error threshold was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data read from the I/O multiplexor did not equal the data written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from rdal_fsi_ffdc_extract()
An error was returned from the role determination object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Undefined data was received from the sibling service processor or system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error returned from a utility when getting data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Undefined position data was read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call was made to set the error number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined sibling state was passed into a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading the service processor's state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Timed out waiting for GPIO device to appear
An artificially injected error used for debugging
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when trying to read a keyword.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading the service processor's state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The amount of data that was read was not expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from adal_mbx_open()
There was an error in the data received from the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another firmware component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading 1 byte from the SYS entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in opening the sys entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from rdal_iomux_seek()
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the call to another component interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error returned from rdal_iomux_query_state()
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A command to start VPD sync returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A n error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
setsocketopt system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The getsockopt system call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_jtag_shift_cmd interface for JTAG returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_jtag_shift_data interface for JTAG returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_gpio_write_pin interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_gpio_open interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_jtag_open interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned while waiting for JTAG-lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rdal_gpio_open interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from rdal_gpio_set_mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The ppcdbg_open_jtag interface for JTAG returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from an interface to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from an interface to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from an interface to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from an interface to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned when setting up or triggering a kernel panic.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when trying to read the sibling service processor's scratch pad register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when writing to the mailbox.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting up or reading the cable ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when closing the FSI device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Vital product data (VPD) collection was disabled because of previous VPD collection failures.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Data of incorrect length was read from the VSRC block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from an open command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a seek command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a write command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was received when trying to write a trace file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a write command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when checking the I/O multiplexer state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Timed out waiting for the GPIO device to appear.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when collecting the system VPD when known to own local bus zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when opening the position file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The position file does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading the position file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The position file contained undefined data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from utilreg::write.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A n error was returned from Util when closing the service processor position file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A sscanf call was made to set the error number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined sibling state was passed into setSiblingState().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from utilreg::read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from ReadScratchPadReg().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from SVPD_collect_system_vpd
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from ReadCableID()
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data read from the IOMux was not equal to the data that was written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from rdal_iomux_close().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from rdal_iomux_ffdc_extract().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from rdal_fsi_ffdc_extract().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the role determination object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from setFspRole().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from sendRcv().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from setupSibling().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from getCmdResponse().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from readNvramMTMS().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from CollectSystemVPD().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from is FSPGarded().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from ReadVSRCBlock().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from ReadFSPSerialNumbers().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from recvRoleCmd().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from goodPathRelationDetermination().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the sibling service processor when requesting that it set up its role.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Returned error from SingleFSP_CommFail_RoleDeter mination()
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned becomeSlave().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from becomeMaster().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from CheckVPDAndDetermineRole().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined command was received from the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The response from the secondary service processor contained no data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from setAddressObj().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from incrementReEntrant().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from setSiblingState().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from an information exchange function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from dscvReadFspState().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from PrimarySideCheck().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from iplp when attempting to switch sides.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned SecondarySideCheck().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from GardGetFspState().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when trying to connect to the sibling
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from GetSiblingFSIState().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from netsConnectServer().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error log entry to record the sibling service processor's status was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
While making the connection to establish the handshake, the message from the sibling service processor contained no data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A host ADAL or registry failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An event detection failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A firmware failure caused a signal to be received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The event loop exited.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to chdir failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a multiplexer configuration file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC file read failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A FRU manager (FRUM) even failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to fork the process.
Failed to unflatten the error log from the network message.
Failed to read the path from the registry.
Failed to read the sibling service processor's state from the registry.
Failed to read the service processor's role from the registry.
Failed to read the service processor's position from the registry.
Failed to write the watchdog-complete key to the registry.
Failed to write the configuration change key to the registry.
The key that was requested from the registry is not valid for this function.
Failed to set the synchronization file for the client.
Failed to synchronize with the field replaceable unit (FRU) manager server.
Failed to send a network message.
Failed to receive a network message.
Failed to establish communication with server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close an open socket.
Failed to create the network client address object.
Failed to create the network server address object.
Failed to find the network address server.
Failed to listen on the network server address.
Failed to listen for a network server connection.
Failed to initialize the thread attribute variable.
Failed to set the thread attribute variable.
Failed to create the monitor thread.
Failed to lock the device list mutex.
An error occurred when unlocking a mutex thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to wait for the mutex conditional.
A parameter passed into a function is not valid.
An error occurred when reading from or writing to the message buffer.
The message type that was received is not valid.
Message flags were received that indicate this was not a response message.
The message that was received does not contain data about a device from the caller list.
The ACTION environment variable was missing.
No ERC event sequence variable was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The DEVPATH environment variable was missing.
The CFAM environment variable was missing.
The LINK environment variable was missing.
A subsystem type argument was missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create an event manager object.
Failed to look for events from the list.
An unknown event was received.
Failed to send an event for CFAM.
An "add event" for a device has been received twice. This indicates a problem with hot-plug processing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A "removal event" for a device has been received twice. This indicates a problem with hot-plug processing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get a device list to validate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ERC validation mismatch occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an ERC validation mismatch.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Validation of the device list failed due to the lists being disjointed, missing primary devices, or missing backup devices.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
ERC forced a device addition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The node that was requested is out of range.
Failed to get the node status or device driver level.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the hot-plug event list, or the vector size was zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to guard out the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The local bus grab operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The multiplexer configuration key is not valid with the sibling state change.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The actual I/O multiplexor size does not equal the saved control data size.
The size was incorrect for the I/O multiplexor configuration file.
Failed to extract the first-failure-data-capture (FFDC) data for the I/O multiplexor device driver.
Failed to unlock the failure data for a multiplexer device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a multiplexer device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close a multiplexer device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to reposition the read/write offset for the multiplexer device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the state of a multiplexer device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to validate a multiplexer through a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to mark a multiplexer as not valid through a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to a multiplexer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read from a multiplexer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the size of a multiplexer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to extract the failure data for a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unlock the failure data for a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure a communication link to a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to configure the I2C bus.
Failed to close the I2C device driver.
Failed to extract the "first failure data capture" data from the I2C device driver.
Failed to unlock the FFDC for the IIC device driver.
Failed to open the I2C device driver.
Failed to extract the failure data for a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unlock the failure data for a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close a device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the output pins on the GPIO.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the blink rate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Configuration file size is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Configuration file key is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure detected in a communication link.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when initializing the mutex attribute.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the mutex attribute type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a mutex thread initialization.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unrecovered FSI error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The maximum number of recovered FSI errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failover could not be initiated because rmgrBackupFailoverCapability indicates that it is not allowed.
Failed to set the I2C bus frequency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A time-out occurred while waiting on the status of the devices.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was time-out from the devlist server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid callout file size was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
ERC forced the configuration timer to expire.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ERC deferred setcc; no primary service processor was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ERC deferred setcc; local devices are missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ERC deferred setcc; node devices are missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Setting the primary node controller failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ERC RDAL SCAN failed to open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to get the pulse length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to set the pulse length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to close.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to extract the FFDC (first failure data capture) information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to unlock the FFDC (first failure data capture) information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to extract the FFDC (first failure data capture) information
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to get the GP1 value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write the SCOM GP1 register.
An ERC RDAL SCAN failed to reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to get the arbiter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to set the arbiter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to close.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to extract the FFDC (first failure data capture) information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ERC RDAL SCAN failed to unlock the FFDC (first failure data capture) information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A netlink socket connection operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket send operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket send operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A netlink socket receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: an invalid request was send to the node manager; it will be ignored.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the IP address from node controller surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IPL is being terminated due to the loss of the primary node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to perform a node controller failover because the redundancy policy is not set to correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to perform a node controller failover because there is no node controller under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to make node controller B primary because only node controller A is under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to make node controller A primary because only node controller B is under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to send a command to the secondary service processor because it is in a bad state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading a register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error due to the loss of surveillance when activating a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failover was made due to node correlation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Node controller correlation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Node controller correlation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid parameter was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to make node controller B primary because only node controller A is under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to make node controller A primary because only node controller B is under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to perform a node controller failover because there is no node controller under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to start the FRUM configuration timer after a new node controller was discovered by the system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to broadcast an event after a new node controller was discovered by the system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request was sent to the NPL to insure that there is a functional node controller in a node.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
First failure data collection (FFDC) was done on BPH side A.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
First failure data collection (FFDC) was done on BPH side B.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller lost communication with a node controller for an extended period of time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a surveillance failure of a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A node is present that is not under surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There are two secondary node controllers.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Only node controller A was visible to the system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Only node controller B was visible to the system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The interface to read node controller entries from P1 received an invalid argument.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller was unable to communicate with a node controller for an extended period of time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller was unable to communicate with a node controller for an extended period of time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The controller selected was not the primary.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid request to read all alerts was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A perc signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: surveillance on a node controller was turned off at the request of an external component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: A reboot of a node controller was requested by an external component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: A reboot of a node controller was requested by an external component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: When a node controller was disabled, it was rebooted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system controller is trying to start services on a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller did not receive a response (within the allotted time) to a ping command from the node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a ping command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a ping command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller did not receive a response (within the allotted time) from a node controller after sending a surveillance off command to the node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a surveillance off command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a surveillance off command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller did not receive a response (within the allotted time) from a node controller after sending a reboot command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a reboot command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a reboot command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller did not receive a response (within the allotted time) from the node controller after sending a "hold sibling in reset command".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a "hold sibling in reset command" to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received bad data back after sending a hold sibling in reset command to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system controller lost the connection to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller did not receive a response (within the allotted time) from the node controller after trying to start services on the node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received unexpected data back from a node controller when trying to start services on the node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controller received an error message from a node controller when trying to start services on the node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system controllers see a different number of nodes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Node controllers that were visible during a previous boot are no longer visible.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The node controller is rebooting by request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A time-out occurred when getting data from a node controller surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A node controller was found with an invalid ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Node controllers were found with pool IP addresses.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The node controller did not become visible in time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when getting the IP address from the dynamic node controller list.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The node controller was disabled by a command line request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The node controllers moved to the surveillance service level.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Timed out waiting for the data from the node manager daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A reboot of a node controller was requested by an external component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No target IP address was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was received from the scandir function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when opening the error log file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was received from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The was a node controller surveillance failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The was a node controller surveillance failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was received from the remove function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The requested trace buffer was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own node driver_name registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own role registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own node driver_name registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own role registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own role registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own role registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own node driver_name registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own eth0-ip-address registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own eth1-ip-address registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own eht1-ip-address registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own node controller-ID-address registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own node controller-DD-address registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when calling the p-open function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the PRA word to zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading the PRA word.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying to read its own role registry value. Refer to the primary SRC for additional detail.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A perc signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when calling a system function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when the node controller was trying write a unique error ID to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A panic request was received from the system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Connect to the server failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A error occurred on an operation that could not be retried with a communications channel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The connection timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The connection timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write data to a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a message from the channel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call back failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The incoming message has no callback correlator.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is FFDC data from the building block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
NMGR returned a failure; there is a broken link or a node does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The rmgrd daemon received a signal that was not expected.
Invalid AIO parameters were passed to rdal_aio_ctx_submit.
Unable to find the proxy control block.
The context cannot be cleaned up after the submission fails.
The context cannot be cleaned up after the submission fails.
The dispatcher shutdown timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Writing the message to the channel failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Writing the message to the channel failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Reading the message from the channel failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Reading the message from the channel failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to get the target node's IP address; the sibling service processor or the node is inactive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDAL reported a GPIO close failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RDAL handle failure
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occured, but FFDC could not be extracted
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
FFDC data was extracted, but the unlock failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid error log was passed into an FFDC function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid RDAL object was returned from an open command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was detected while setting the DD level of the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to initialize the address structure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The connection to the server failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hard socket failure disconnection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The connection timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The connection is closed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write data to a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The permanent and temporary firmware sides are both marked invalid
Perform FSPSP02 .
The service processor boot watchdog timer expired and forced the service processor to attempt a boot from the other firmware image in the service processor flash memory
Perform FSPSP02 .
Power-off reset occurred. FipsDump should be analyzed: Possible software problem
Perform FSPSP02 .
Link 0 is not plugged.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A service processor kernel panic was caused by an out-of-memory condition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A service processor kernel panic was caused by uncorrectable error in the flash memory on the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Registry write failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wrong bus owner in the argument
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid number of command line arguments
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Missing reserve ID, no argument value for --r option
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Multiple -c arguments
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
-s option specified with -c
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Multiple -s arguments
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
-c option specified with -s
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid command line options
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Bad command line arguments
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No numeric input for reserve ID
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Empty numeric string for reserve ID
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid character encountered in conversion.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Processor stop instruction failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Processor state query failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A requested SRC was not found in the list of SRCs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A possible file system problem was detected when attempting to open a directory for reading.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation requested by an external entity was not understood.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when trying to read a registry key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid input data was found during an SRCI operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The size specified for the SRCI operation was inaccurate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A generic stream failure has been detected during an SRCI operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A possible file system failure while SRCI operation attempted to create a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SRCI detected bad input data; a valid identifier byte was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SRCI received a signal it does not understand.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM is already in the termination state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM is already in the power-off state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ctrm currently processing a poweroff request from the SPCN
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM is currently processing a request to terminate the service processor from another service processor firmware component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Termination request to the state manager failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered with the IPL request during the processing of a power fault.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Too many client connections were established.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unexpected signal was received.
If this is a tracking event, no service actions are
Client request timeout.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The event timed out waiting for the termination state.
An error was encountered starting the request process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Synchronization with client process failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A client request failed due to "server busy" condition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered while receiving from socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when connecting to the communications server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to trace SRC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error reading registry entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error updating registry entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware state was not reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No error log passed to the CTRM client library.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to retrieve the embedded SRC from the error log.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error processing client request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error processing client request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM server error binding to socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error while attempting to obtain a lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM server error when canceling client request processing threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unknown error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid error log object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid errlog data size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid client request data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An event manager constructor failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to bind socket.
If this is a tracking event, no service actions are
CTRM server error binding to socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM failed to create a termination thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware cannot cancel the transition files.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid attempt was made to reset the CTRM server while processing a power fault.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when reading the registry entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a firwmare error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unknown service processor role.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM has already terminated with forced failover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CTRM is already processing a "terminate with failover" request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to display SRC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The termination failed, which left the firmware in an invalid state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid request was received. No operation was performed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when updating a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Processing was terminated on the secondary.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
gardCheckFailoverCapable() returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid error log object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when connecting to the network.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid Errorlog object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The sending of a CTRM client request to the server failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The sending of a CTRM client request to the server failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Synchronization with CTRM server failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client failed to retreive the P0 root path.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Termination failed without failover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function in the firmware has called another function without an error handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
rmgrNotifySibling( ) FAILED
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from trying to clear the dscv role lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in selecting the socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "SSL listen".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the bind operation for UNIX .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the bind operation for SSL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when accepting a UNIX connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when opening a vtty session.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in accepting a TCP/IP connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating the unique key for the message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred during message queue creation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when queueing messages.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the "receive message" queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when deleting the old message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating the inbound thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the inbound connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when receiving outbound messages.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when calling a routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in "receive message".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred sending a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when deleting the old message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The maximum number of socket connections for TCP clients was reached
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in the address creation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing the inbound socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in deleting the message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to remove the previous mount.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing to a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when closing the vtty.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to activate the user configuration set up file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A NETS script was executed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the system name.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid name was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when setting the user password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when validating the password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in the initial set up of the out bound remote thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when killing a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in SSL for a remote message object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when requeueing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The kill operation was called; the virtual TTY (VTTY) server will close.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when deleting the old message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when creating a process thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating a session thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in using userconfig.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when reading a registry value. .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The user password value's length was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when opening the port for connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the universal asynchronous receiver/transmitter (UART) configuration for the baud rate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when setting the status field to "failure" in the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when verifying the dynamic password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the password signature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the manufacturing password signature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the universal asynchronous receiver/transmitter (UART) configuration for parity.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was found in the configuration of the universal asynchronous receiver/transmitter (UART) configuration for trans_normal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when sending a message to a client.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the machine type vital product data (VPD).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when reading the system serial number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when reading the machine brand.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when initializing the serial server daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error ocurred when creating a session thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in the stat file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid error path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when writing the manufacturing password signature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid socket descriptor was selected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The signal length exceeded the limit.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error statistics are available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Memory allocation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The universal asynchronous receiver/transmitter (UART) configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The universal asynchronous receiver/transmitter (UART) configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid error path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was found in a certificate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The wrong password was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred. .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred with a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when enabling a login.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in an SSL write.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in PERC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid error path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when starting the vtty daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in obtaining a file descriptor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when validating the password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when writing the manufacturing password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when setting the user password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating a key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The UART adal configuration failed for serial-type connections.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in getting the HMC certificates.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in SSL_CTX_new.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in SSL_CTX_use_certificate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in SSL_CTX_use_PrivateKey.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in SSL_CTX_check_private_key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in readCertKeyPair.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in BIO_new_socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in setsockopt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in getsockopt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failover was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid tool was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The process to open a file failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The IP query failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in eraseCertKeyPair.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error with the daemon; no parent or child was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure in the acceptance portion of the TCP/IP-type connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The TCPIP socket listen failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The Unix socket accept operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An improper error path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when setting the user password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An IP query for the HMC failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid value was passed into an EvenMgt method call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid value was passed into an EvenMgt method call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid message has been received by either the client or the daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
These SRCs are added to the primary SRC to show control flow.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the file name for a new socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Event notifier initialization failed because a thread could not be created.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An event could not be sent to one or more subscribers.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Attempted to signal an event using an invalid event ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unexpected signal has been received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The user specified a time limit to wait for an event, and the time limit was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Attempted to subscribe to or unsubscribe from an event while the event management object was in use by another thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The subscribed process appeared to have ended without unsubscribing.
Internal firmware error: an invalid filter value was passed into the EvenMgt method call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error: an invalid event id was passed into the EvenMgt method call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error: a bad parameter was passed into the EvenMgt method call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error: the caller wanted to monitor for events but is not subscribed to any.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error: the caller did not pass in a valid buffer pointer to hold event-related data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error: a bad parameter was passed into the EvenMgt constructor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The user passed in a buffer that was too small to hold all of the event-related data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Reading the registry failed to obtain the path to the socket file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An application has received an unexpected signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A process is calling another process without being set up correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A process is calling a procedure more than once.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An application has received an unexpected signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error processing the stack trace.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error processing the stack trace.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error ocurred when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating a file handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in a session to create a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when bind ing a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "socket listen".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when writing a session entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the client name.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The maximum number of sessions is already active.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid offset entry was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when updating a session entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "read for session entry".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "lookup in session entry".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "seek for session entry".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "session entry read".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in "session entry read".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid entry number was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in a "session entry seek".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when updating a session entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid PID was found in a session entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error when creating a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Creation of the socket path failed due to a registry read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a message constructor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Allocation of memory for a message failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Allocation of memory for a message failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in the buffer length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A null value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid message was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid message was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A null value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in a UNIX connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a time-out on a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when an SSL socket was being closed at the same time an SSL connect was occuring.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when closing a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in a routine
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A connection failed due to the connection timing out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A connection failed due to a timeout.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A connection timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A socked error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A connection failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a selection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to make a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to make a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a secure read failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a serial connection message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a disconnection message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a serial connection message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a send operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when opening a port number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing to a port.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting up the passwords.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in a receive operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) device abstraction layer (ADAL) configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) ADAL configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) ADAL configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) ADAL configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) ADAL configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The universal asynchronous receiver/transmitter (UART) ADAL configuration failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a time-out on the secure receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A secure receive error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A polling error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Poll events occurred on the secure receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A secure receive operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a secure receive operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A connection error occurred in TCP/IP.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A socket error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A socket time-out occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing the serial connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing the eth0 connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing the eth1 connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a time-out on the secure receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when receiving.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A time-out occurred while waiting for data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in SSL receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in secure receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned by the poll command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in a message processing function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in SSL write.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in a send/receive function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when reading the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A private key failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A read certificate and key error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A private key mismatch occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to complete a connection, but not because of a time-out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when trying to close a TCP/IP connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An SSL handshake failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
These was an error in a write operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in TCP/IP select.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A timeout occurred in "select" while waiting for data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in "received message".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occured when getting the header.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a timeout while waiting for TCP/IP.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A certificate clean-up error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in TCP/IP "select".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A semaphore error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An SSL shutdown failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A set up error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Generating a key failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in when closing a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading a registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a sibling connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when connecting to the first interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when obtaining the private key for SSL communications.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when writing a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Bad data was sent in through a constructor .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error in creating an ivSSL object using the SSL_new() function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred in setting a socket option.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The ssl connection timed out during the open ssl operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get access to shared memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to attach to shared memory area.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid pointer was passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create a sychronization file that is used to inform other code modules about the completion of a signal handling operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to registry which serves as a flag to indicate that a service routine is no longer running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to detach shared memory area.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create shared memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start instructions on the selected processor to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the registry which serves as a flag to indicate a service routine is running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid service routine was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid command was found in the attention memory area; it does not match the service routine that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Received a fatal attention during a service routine run.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to erase shared memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the status of a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No threads are functional on the requested processor core.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A dependent process was not running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start a dependent process which is required to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A request was made to run a service routine on a processor core that is not functional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get selected processor core functionality.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the general purpose registers.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set up registers during the setup to run service routines.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the special purpose registers.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set up a register during the setup to run service routines.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to save memory area during the setup to run service routines.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the proper fabric identity so that storage could be read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to unmap the memory pointed to by the processor control area addresses.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the processor control area from the host data area.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read memory during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Timed out waiting for the service routine to finish.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to erase a synchronization file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get access to a structure necessary to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to intialize a buffer during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write the service routine address into a general purpose register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set up the special purpose registers.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to intialize a buffer during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to intialize a buffer during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set up the special purpose registers to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to save a register value during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write the reset vector.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the thread status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write the reset vector.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service routine address was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to memory during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to release a reserved ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to intialize a register during the setup to run a service routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid service routine address was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to service routine state in the registry to indicate that a service routine is not running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the service processor synchronization (SINK) interface tried to read firmware data.
The service processor synchronization (SINK) interface timed out waiting for a firmware component to create a synchronization lock.
The service processor synchronization (SINK) interface timed out waiting for a firmware component to establish a synchronization lock.
An invalid synchronization lock was passed to the service processor synchronization (SINK) interface.
An invalid synchronization lock file was passed to the service processor synchronization (SINK) interface.
A firmware component failed to create a synchronization lock.
The service processor synchronization (SINK) interface detected that another firmware server is currently running.
An error occurred when the service processor synchronization (SIN K) interface tried to delete a synchronization lock.
An internal error occurred in the service processor synchronization (SINK) interface.
An error occurred when the service processor synchronization (SINK) interface tried to read firmware data.
An invalid file was passed to the service processor synchronization (SINK) interface.
An error occurred when the service processor synchronization (SINK) interface tried to build a directory path.
An invalid file was passed to the service processor synchronization (SINK) interface.
A firmware component passed an invalid file to the service processor synchronization (SINK) interface.
An invalid parameter was passed to the service processor synchronization (SINK) interface.
The service processor synchronization (SINK) interface was not able to synchronize with a specific firmware component.
The service processor synchronization (SINK) interface timed out waiting for a synchronization lock to be established by another firmware component.
An invalid file was passed to the service processor synchronization (SINK) interface.
Invalid arguments were passed to the service processor synchronization (SINK) interface.
The maximum number of files that are allowed to be created and open using process synchronization was exceeded.
An invalid parameter was passed to the service processor synchronization (SINK) interface.
The service processor synchronization (SINK) interface timed out waiting for the power interface to stabilize.
The service processor synchronization (SINK) interface detected a synchronization error between two firmware components.
The system controller received bad data back after sending a "hold sibling in reset command" to a node controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The calling component requested an invalid key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The calling component did not provide a buffer large enough for reading the data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The util registry write operation failed due to the an underlying building block failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The platform extension information for this registry key was not retrieved correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Redudant "side" write operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An operation to send a signal event for the current registry key failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Redudant "side" write operation failed due to a stream failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Util failed to accurately acquire the size of a registry key due to an underlying building block failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A was failure detected when forming a path to a registry key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current util file operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current util operation failed because the file in question is not open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current util operation failed due to end-of-file being reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory pointer acquired from a caller is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An operation failed due to end-of-file being reached on the current stream.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to remove a file failed; possible file system isssue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The file lock operation failed to acquire the lock that was requested; possible system-wide problem
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to initialize a semaphore; possible kernel issue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to initialize a semaphore; possible kernel problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The semaphore operation failed; possible file system problems.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A semaphore initialization failure occurred due to system call failure; possible kernel problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to dynamically load a library failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when loading a shared library symbol.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to synchronize the current registry key to the back-up failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get a value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to read a registry key has failed due to a failure in the underlying building block method.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An operation failed to read a platform extension due to a failure in an underlying building block method.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation to synchronize the file operation via RMGR has failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation failed while reading the file stream.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open a firmware component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to set bits in a register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to configure the virtual local area network (VLAN) adapter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to configure the virtual local area network (VLAN) adapter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading the valid bits.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to add the virtual local area network (VLAN) adapter to the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A problem occurred when resolving the name of a domain name server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write to the flash memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write to a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to configure the adapter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the gateway address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A n error occurred when writing the virtual local area network (VLAN) address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A n error occurred when writing a variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A network reset was issued as the pin value changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to add the VLAN adapter to the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading the valid bits.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the gateway address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the gateway address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid network configuration was specified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the virtual local area network (VLAN) ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to configure the adapter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid user error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A network reset was issued because the pin value changed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the virtual local area network (VLAN) enabled/disabled flag to enabled .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A virtual LAN was removed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A virtual LAN was added.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A configuration file was opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A socket was opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open the device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP socked was opened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP socket binding failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP operation to get the IP address failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP get IP address operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to correctly route mailbox traffic.
Failed to route mailbox traffic.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An DHCP failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP binding failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A receive failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A polling failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when creating a route.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ARP open failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred with a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred with a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when receiving a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A machine type/model/serial number mismatch occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An I/O control failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A machine type/model/serial number mismatch occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid IP address was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid gateway was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write to a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the gateway (IPv4).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An address was null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A subnet failure occurred (IPv4).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A subnet mask was null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A broadcast address failure occurred (IPv4).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A broadcast address was null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The routing file was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An IPv4 address failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A listif command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the gateway.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The interface was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware failure occurred when getting the IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware failure occurred when getting the subnet.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware failure occurred when getting the broadcast address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the IP address in the hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware failure occurred when setting the subnet.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the broadcast address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An IPv6 address failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid prototype was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Getting the IF flags failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Setting the IF flags failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No prototype was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when getting the hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A socket open failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported link speed was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in the link speed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A link status error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when processing a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An IP address failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The maximum number of DHCP addresses was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The maximum number of static addresses was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The maximum number of addresses was exceeded (IPv6).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The maximum number of addresses was exceeded (IPv4).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid address type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid version was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid buffer type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An address was not found (IPv4).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The buffer was too small.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was passed into a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The interface configuration was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid buffer size was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The dynamic host (DH) client stopped.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The dynamic host (DH) client was released.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A DHCP directory failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A PID failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The netv daemon was unable to read the side ID that is used to determine which bulk power controller (BPC) the daemon was running on.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine which bulk power controller (BPC) the netv daemon is running on.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine the type of enclosure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unknown card was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The netv daemon was unable to open the FSI device to get the side ID that is used to determine which bulk power controller (BPC) the daemon was running on.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The netv daemon determined that there are too many error logs to the be transferred to the system client.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VLAN map configuration is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The PVID configuration is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A host on the network has an invalid IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Duplicate IP addresses were detected; the system firmware should be updated. If the condition persists, replace the hardware that is reporting the duplicate addresses.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Duplicate MAC addresses were found on Ethernet ports.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred while trying to allocate memory. The service processor reset itself to recover from the error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred while trying to allocate memory. The service processor reset itself to recover from the error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred while trying to allocate memory. The service processor reset itself to recover from the error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred while configuring CEC memory. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An integrity check failed on data that the service processor retrieved from CEC memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor could not find vital product data (VPD) for a FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor could not find the vital product data (VPD) for a FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor could not find vital product data (VPD) for a FRU.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An integrity check failed on data that the service processor retrieved from CEC memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The current communications link to the hypervisor (PSI) for a service processor was not found or is not functional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation initiated by mboxmainprocess was unable to open the mbox device driver within the allotted time.
An attempt was made by a user to set the hypervisor mode to a value that is not allowed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid SCOM address was found in the AVP test case list.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The load type of the test case structure did not indicate a memory-type test case.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null functional unit pointer was found while iterating through the list of core functional units that were found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The test did not finish in the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data in the status address is not changing. If the test were running successfully, this address should be changing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to get the functional unit group for the CEC cage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CEC cage number that was provided did not match the CEC cage number that was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred while writing the test case data from a file into the data buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the instruction status for the core.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null functional unit pointer was found while iterating through the list of core functional units that were found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An I/O control operation failed when trying to set the data terminal ready (DTR) pin.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operating system protocol does not match the currently-supported service processor version.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The open operation on the requested device, a serial port, failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware was asked to open a serial port that does not exist. The only valid serial ports are S1 and S2.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A request was made for the modem control signal status but the port was not open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An I/O control error occurred when trying to read the status register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when reading data from a serial port.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A write operation to the serial port failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware got stuck for more than two seconds when trying to write to a serial port. The write operation will be restarted and an error logged.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to initialize the mutexes for locking classes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to create a semaphore.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The kernel call failed to create a thread
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was unable to make an entry in its error log that the hypervisor requested
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The kernel device driver returned an error writing hardware settings
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No bytes were r eturned by a mailbox read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The mailbox daemon is not running, so no attempt can be made to talk to the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor requested the execution of a function in the service processor firmware, and the execution of that function resulted in an error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The size of the data sent exceeded the maximum allowed size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to start the timer to block code update.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was unable to establish a virtual session on a serial port
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid message received by the service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to receive the error log from the daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to initialize the processing queues.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor attempted to pass an invalid value to the hypervisor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The state manager returned bad status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor (or system controller) invalidated a dump because it was not a platform or service processor (or system controller) dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was unable to complete state changes during a boot
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The HMC is trying to use an invalid ID
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A message was sent to the hypervisor when the hypervisor was in an invalid state to receive messages
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The kernel device driver returned error when setting or clearing bits
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor sent the service processor an invalid SRC to display
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: In a system with redundant service processors (or system controllers), there are times when messages from the hypervisor are blocked; this is expected. This occurred, and does not indicate a problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: In a system with redundant service processors (or system controllers), there are times when messages from the hypervisor are blocked; this is expected. This occurred, and does not indicate a problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The mailbox device driver failed to open.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No tone control block was created by the device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor's virtual NVRAM is not supported on this system
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor attempted to read past the end of a file
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to write past the end of a file during a synchronization operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor's virtual NVRAM has an unexpected size
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Clearing the hypervisor's NVRAM is not allowed while the system is running
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open the PSI device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to reset the mailbox device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A duplicate message from the hypervisor was received in the mailbox. The duplicate will be discarded, but this may indicate a problem with the PSI interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware was unable to generate an audible sound on the speaker.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor detected an error with a PSI link. If this is predictive, follow the procedures called out in the FRU list in the error log entry. If this is informational, it was not possible to tell if this occurrence was a real error or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is no working communication path between the service processor and the operating system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor application performed an invalid sequence of commands.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor function is currently in use; repeat the operation later.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor application performed an invalid sequence of commands.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: The virtual NVRAM thread did not shut down in time. This might cause problems with the hypervisor's virtual NVRAM the next time the system is booted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mailbox function was told to terminate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: The mailbox was told to terminate, and it did so without error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The device driver indicated that an error occurred prior to his operation, so this operation should be retried.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VNVRAM block list was the wrong size during a partial synchronization attempt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mailbox server has forced an unlocking of VNVRAM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The error log data read back from the hypervisor didn't match the data that was written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump notification was sent from the service processor to the hypervisor.
The mailbox start-up data was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data read back from the flash memory for virtual NVRAM did not match the data that was written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Mailbox data was missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A block number that is too large was passed into the function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid signal was received.
Failed to read the IPL type from the registry.
An error occurred when the service processor capacity on demand interface was writing firmware data to the registry.
The service processor capacity on demand (SCOD) interface does not recognize the power-off IPL type.
An error occurred when the service processor capacity on demand interface was reading a registry value.
A firmware component tried to use the service processor capacity on demand (SCOD) interface in an invalid manner.
An error occurred when the service processor capacity on demand interface was updating a firmware entry in the registry.
An error occurred when the service processor capacity on demand interface was updating a firmware entry in the registry.
An error occurred when the service processor capacity on demand interface was updating a firmware entry in the registry.
Failed to read a value from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed when trying to read the registry value to determine the state of the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed when trying to read the registry to determine the value of iplp/SysOpMode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed when trying to read the registry to determine the value of panl/SysPwrDnTime.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the current power state of the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed when trying to write the control panel information to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The server is no longer available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the synchronization file for clients.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to synchronize with the server process for client commands.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the panlmain daemon synchronization file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The panlmain daemon is already up and running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to lock the firmware code lock when trying to execute the desired action for the decrement button.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to lock the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to lock the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to unlock the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Timed out waiting for the mutex conditional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to wait for mutex conditional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to wait the allotted idle time for the worker thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start the service processor dump function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid argument was passed into the attention monitor thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to initialize the desired attribute for the thread that is being created.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to initialize the thread attribute object for the thread that is being created.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to kill the thread holding the mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to connect to the client socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to bind to a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to listen for messages.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to accept a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to assign a name to the socket that was created.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to begin listening on the socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to accept the connection from a listening socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create or connect to the socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to close the listening socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the server address socket object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the message through the accepted connection socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to receive a message through the server-accepted connection socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The client address socket doesn't exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the action response to a concurrent maintenance operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to receive a reply.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to connect to the panel server to send a message to be processed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An incorrect data size was received for the function action that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No data was passed into the function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function received an invalid parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The reply message that was received did not have the same number of functions that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The reply message that was received contained an error log.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The response message was supposed to contain data; it contained none.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Received a response message that was not the correct type for the message that was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the message and receive the reply.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The reply message that was received contained more data than the buffer can hold.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A reply message was received that did not contain the right data size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A power transition request failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The user name in the message is not recognized and cannot request a power transition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid power transition type was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid request data was received with the message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No change flags were set for the system dump parameters.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported operation was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation request is not allowed because it was requested on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to receive a message on the event message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create a timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to delete a timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set time for the timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The panel function is not active.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid function was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The subfunction is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to execute the panel function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The subfunction is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the minimum and maximum subfunction values for the power function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function that was requested has no subfunction capability.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the minimum and maximum subfunction values when trying to increment the function number on the control panel .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to perform a lamp test on the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to perform a lamp test via power.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to perform the power function that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the initiate service tool command to the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to start a platform dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to execute a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the dump firmware content.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the dump hardware content.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to find out if dump is enabled or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the dump collection policy to the requested value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The value of the dump collection policy that was received is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the dump hardware content to the requested value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The value of the dump hardware content that was received is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set the dump firmware content to the requested value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The value of the dump firmware content that was received is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the number of SRC entries for the system status SRC trace function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the number of SRC entries for the diagnostic status SRC trace function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the system trace SRC that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the system trace object, or there were no entries for system trace.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initiate the IPL that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the power on IPL request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send the power off IPL request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send a reboot request to the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The current and next state of the system will not allow a reboot of the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the HMC information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the IP address for the requested Ethernet port.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the location code for the requested Ethernet port.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the installed resource IDs for the HMC connectors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the maximum number of resource IDs for the HMC connectors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This SRC indicates that the panel component is done with the input function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid function number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function requested is disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function range is disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to determine if a concurrent maintenance operation is in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid sub-function was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to build the display for the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No sibling service processor was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to deactivate the panel function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The secondary service processor cannot activate a panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the SRC displays for the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to modify the panel display when the increment button was pushed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send display data to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to send the SRC display data to the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the worker thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to increase the work force when it was determined it was needed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No panel is active.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to push a work message onto an existing queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to take appropriate action for the event that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An event was received that is not supported by the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to subscribe to the event manager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to receive an event from the event manager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the event monitor thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Function 26 was done before function 25 was executed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the current power state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the current service processor dump enablement state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to enable the scroll lock when trying to increment the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create the timer for the scroll lock button.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the time-out for the scroll lock timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start the power off timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to take action after the power off timer expired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to take the proper action after the power off timer expired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create a timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set the time-out for the timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to delete the timer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to block client process synchronization.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to a panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to change the power LED to a new state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The button action that was received is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to allocate memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to set up the decrement button on the control (operator) panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to create a timer for the decrement button on the control (operator) panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to conduct the decrement action for the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to perform the increment action for the panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the panel function that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the panel attention monitor thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set up the panel when activating the requested panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the number of possible panels in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A control (operator) panel is already active in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Another concurrent maintenance operation is already in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The role of the service processor will not allow the activation of the requested panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
More physical control (operator) panels are in the system than is allowed. This is an invalid configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The control (operator) panel is not present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid resource ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No active panel was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid command was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unknown caller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function that was requested is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to request IPL for the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The panel lamp test failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The operation that was requested cannot be performed on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the state manager function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An output parameter pointer is NULL.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A platform dump function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The requested function is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the mailbox function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the system power interface function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The requesting owner does not own the requested function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function that was requested is disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure during a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The requested sub-function is outside the valid range.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to start the service processor dump process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The function requested is disabled or not active.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the SVPD ML2 socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ML2 failed to connect to a server socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ML2 server failed on socket receiver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a problem with the path to the secondary system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The ML2 server failed on a socket send.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ML2 failed to close a connection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid operation was sent to an ML2 server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This function was called by the user with an invalid parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when trying read a file from persistency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when closing and/or unlocking the file for the given resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered trying to read the SVPD state information file into the persistency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was found when firmware tried to read the size of the registry key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A data mismatch, or read failure, occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to lock out all threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to gain a lock on a VPD file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to lock the file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to unlock the threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the device type for the resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A device write failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A device reset occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was encountered whne synchronzing the file to the other service processor in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to locate a string in a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when generating the location code while trying to rebuild the RLCA table.
Failure to write to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A keyword error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A keyword error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure was encountered when finding or reading the module VPD file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client failed on a socked send of receive.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This operation needs message data from the client but there was no message data in the client message
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid state type was passed in by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid command was sent to the ML3 server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client failed to get message data from the server when mesage data was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Invalid data in the module VPD .out file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when reading a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write raw VPD data into the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when writing NVRAM to VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a mismatch between the VPD data and the values in NVRAM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Data read from the rlcainst table is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Firmware needs to add support for an additional resource to the given FRU type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get FRU status for the given RID in registry update function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed trying to determine the resource ID's associated with the given FRU type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the VPD and update the registry entry for the input RID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when reading the Anchor (VPD) card.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Writing to the Anchor card I/O multiplexer failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when getting the field replaceable unit (FRU) status for the resource ID in the registry update function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid keyword data was input by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The user passed in a keyword size that is greater than the actual keyword size in the VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This system's machine ID is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A smaller number of bytes was written to the I2C device than was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to write to an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to update the IN keyword in the VRTN block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed when updating one of the smart chip blocks
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid format was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A record is not found in the VPD data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid length was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid offset for retrieving raw entry data from the .out file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function was called with an invalid parameter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The data reference does not support keyword parsing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The files were not synchronized for this request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The two copies of the chips were re-synchronized.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to read the module vital product data (VPD) from the I2C device failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the mode attribute to hardware mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to generate a location code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was encountered duing VPD collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered during VPD collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt to delete the old event queue failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in the firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find the input RID in our RLCA table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to convert VPD format.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when converting the VPD to multiple stanza format.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The BR keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The enclosure FC keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The ID keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The NN keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The RB keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SG keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SU keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SE keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The TM keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The TN keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The WN keyword needs to be programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to identify a RIO cable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the I2C DP.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when synchronizing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A send/receive failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No manufacturing flag was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The manufacturing policy flag is not set.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Updating the System p BR keyword is not allowed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Updating the SSD BR keyword is not allowed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to open a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown type of error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An initialization operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to set a thread attribute.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create and initialize an attribute object that was needed to create a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed during vital product data (VPD) collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed during vital product data (VPD) collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to lock out all threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to unlock the threads.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing a handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The type/model field has already been updated once; the second update is not allowed because the type part of the type/model data does not match.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An update for the given keyword not allowed for the second time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when trying to read a pin.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was encountered when trying to find the VSYS record from the sytem VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No valid service processor VPD was found on this system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when collecting the system VPD to rebuild the VPD data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write to a registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid data was found in the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An untagged entry was found in the resource ID tree.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when setting the bus speed attribute for reading or writing an I2C device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read the system serial number on NVRAM, or invalid keyword length.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when synchronizing files.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when setting the DIMM change flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when setting the speed attribute before reading a resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid device type was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD is being recollected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A synchronization error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
All of the VPD was not collected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when converting a string.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to synchronize the service processors (or system controllers).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system VPD was not collected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to delete an entry from a table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processing of a table failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to load a table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A problem occurred when collecting the system VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a FRU callout.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Verification of the path from the service processor to the Anchor card cannot be done because the sibling service processor does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A recalculation failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure in FRUM call to set up iomux for the anchor card.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure during FRUM waiting on anchor card device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure during FRUM waiting on configuration being complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure during FRUM waiting on gpio devices becoming present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure when starting the background svpd server process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The svpd server process encountered a problem and has terminated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to obtain the machine ID. It is possible that the system firmware does not support this model.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Vital product data (VPD) validation was successful during a keyword update
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the IM keyword in the VPD record in this system's Anchor card. Reprogram the Anchor card with the correct VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD was guarded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An untagged entry was found in the RID tree.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
VPD is not collectible. Recollection of the VPD will be attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A listening failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A process message was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A synchronization between the primary and secondary service processors was requested. This operation timed out before it was complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to dynamically rebuild the module VPD table.
An error occurred when trying to dynamically rebuild the instance table.
An error occurred when setting the vital product data (VPD) state after a code or table check failure on the secondary service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to find a record during system vital product data (VPD) collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Too many devices were in the list.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned by lstat() even though the directory entry should have been valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Two I2C hub devices are in the list consecutively.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No I2C devices were present in the vital product data (VPD) table device string that was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to dynamically rebuild the HVAT table.
An RLCA table of size 0 was read from P1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An RLCA table of size 0 was read from P1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An RLCA table of size 0 was read from P1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when trying to clear the data synchonization gzip file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SCED read for the backup path failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in converting the string for verification of the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error in converting the string for verification of the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the IM keyword in the VSBP VPD record in this system's anchor card. The anchor card must be programmed with VPD which contains this keyword.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when synchronizing with the server from the SVPD client side.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the parent CCIN of the resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find a part number for a resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find a serial number for a resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Too many entries in this file; it could be the wrong file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an invalid operation on the VPD formatted for a blade system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Configuration on the I2C DP failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the node ID from the device address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the device string from the device address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the device string from the device address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when reading the file in "util generate file name".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error returned from tmgt when called from SVPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The anchor card is tagged for concurrent maintenance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to obtain the anchor chip resource IDs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the file from RO/svpd.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processing of the PD table failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
"Process and store" on the LED table failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to load tables to p1/svpd.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RLCA INIT failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when setting the IPL speed to slow.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when setting the IPL speed to fast.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an MDIA error when setting the DIMM change flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when getting the RID array while trying to rebuild the RLCA table.
Failed to read the VPD collection status flag from the RLCA table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD data for the resource ID was not found in p1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The serial number and feature number data in p1 are zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD read status was set to false in the RLCA; there was no VPD data in p1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VPD data for the resource ID was not found in p1.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred during the renaming of the module VPD file.
An error occured when trying to clear the data synchronization gzip file.
A failure occurred when reading the FN value for the RID.
A failure occurred when reading the serial number value for the RID.
Failed to add a file to the global synchronization list so that it can be scheduled for deletion on the secondary service processor.
Failed to add a file to the global synchronization list so that it can be scheduled for synchronization with the secondary service processor.
The global HVAT table is null, so writing the table to p1 is not possible.
An error occurred when loading the table from p1.
The primary device address is null.
Unable to find the table in p1.
The p1 table version does not match the NFS or RO/svpd.
The redundant device address value is null.
Failed to rebuild VPD tables.
There was a mismatch between the machine ID on the primary Anchor card and the secondary Anchor card. The secondary Anchor card will be guarded out and the machine ID on the primary Anchor card will be used.
Failed to delete an entry from the RLCA table or its copy.
The system VPD was not collected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Firmware validation was successful.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Firmware validation before a firmware installation was not successful.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Firmware validation after a firmware installation was not successful.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid command was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Request to get data for a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to get data for a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to obtain data for a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to get data for a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occured while locating an enclosure LED for the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to operate a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software or hardware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to identify a service LED due to a sofware or hardware issue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A software error was caused by invalid function parameters.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed..
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed due to a device driver problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Request to turn on, turn off, or blink a service LED failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occured during first failure data collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call was made to get LED access data based on the RID, but the call to malloc failed to allocate memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call was made to drive an LED to a specific state, but an error was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call was made to drive an LED to a specific state, but an error was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call was made to drive an LED to a specific state, but an error was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a constructor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chip was in an invalid position on the chain.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No chips were in the chain.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The commands that were added exceeded the chain command size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip was not found in the chain.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ring buffer size was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to release the lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure when getting the facility.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid device number was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An abort was signalled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to release a lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to release a lock that was not held.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid command ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The GetSCOM operation never completed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid use was made of the JTAG interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid use was made of the JTAG interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unmatched cyclic redundancy check (CRC) was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip detected cyclic redundancy check (CRC) miscompares on scan-in.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SCOM attentions were detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Bad parity or an invalid command was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid flush operation code was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The last bits of the chip status command were not the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid ring selection was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to turn on a chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to stop the specified chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid function call was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid function call was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A prohibited command was found during an IPL step.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find a processor node.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chip ID that was scanned did not match the chip ID that was restored.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The domain pointer is of an unknown type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid operation was specified by the function caller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A node without cards of a certain type should not be on top of a node with those cards.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor core functional unit in a nonfunctional state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor core is not functioning, or it cannot be detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There were no functional nodes found in the system. If this is a multi-processor-drawer system, the first node is not functioning.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor clock is not active, or there is no active clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The processor clock is not functioning, or it cannot be detected, or there is no active clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The object wasn't initialized.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No functional direct memory access (DMA) paths were found. The system cannot boot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The resources used to complete a memory path are not functional.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The resources used to complete a memory path are not detectable .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The time-of-day clock is not functional, or there is no active clock.
The time-of-day clock is not functioning, or it cannot be detected, or there is no active clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The P5IOC2 was not functional.
The P5IOC2 is not functioning, or it cannot be detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unsupported cards (designated by a CCIN of FFFF) were detected in the system. These cards have been deconfigured and are unusable system resources.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when using the rule facade classes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A FRU was not found for this object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A FRU or MRU was not found for this object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid value was passed into the function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clock interface instance is null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred with the hardware access monitor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The frequency for this clock card is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid VPD port number was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The resource ID is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An MCM has an invalid plug count.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is not enough hardware in the system to boot.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when creating a group object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid unit id was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is no mainstore memory initialized; the size is zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hole was detected in the plugging of the nodes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SMP cables are plugged incorrectly, or the SMP cables are the wrong type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The amount of memory that is configured has changed since the last system boot, so main storage cannot be preserved.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A light strip has been plugged in incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A card is plugged into an invalid slot. If this error occurred during a concurrent maintenance operation, it is possible that the system does not support adding this card concurrently.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when using spif WBC commands.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The RTBL chip override key was set.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an error when attempting to create a group, and the function returned a null group pointer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Zero chips were found on the new or replacement card.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when attempting to create a system domain, and a null pointer was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The creation of a cage pointer failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a problem in calculating the clock multiplier and divider.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from ecmdDataBuffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attention or checkstop was detected on the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Memory cannot be preserved due to clock stop sequence.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error in performing a sendCmd operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A processor chip was found to have zero cores active, which is an invalid configuration for the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SMP cables are plugged incorrectly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The cable data doesn't match a known value. Verify that the SMP cables are plugged in securely.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to access an invalid processor unit ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A concurrent maintenance quiesce operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A concurrent maintenance switch command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A concurrent maintenance node hot add operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SMP cables, or the processor cards, are not plugged in correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to perform a hardware operation without a valid hardware operation lock.
An invalid card record was found in persistent memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to access a processor chip unit with an invalid ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No functioning service processor (or system controller) was found. The system boot must be aborted.
The node configuration is invalid.
A system was found without a functional TPMD card.
A functional TPMD card was not found in a server that requires one.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An abort signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The error analyzer detected a mailbox ADAL error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Dynamic recalibration is not valid on this elastic interface bus.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unknown system type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SMGR_NON_MS_RIPL recovery IPL is hung.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Memory is not preserved.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Internal software error: invalid object type passed to function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: the hardware is not in a valid state for the requested operation
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: data buffer used incorrectly
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: the firmware is in an invalid state for the requested operation
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
One or more bus alignment errors occurred; look for prior error log entries with with the format B1xxB2DF and take the recommended actions for those entries.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: test routine failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: invalid parameter passed into a function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
System attention line became active, but no chips appear to be activating it
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find the other side of the interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: an operation was attempted on deconfigured hardware
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Chips that are not supported were found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmare encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A chip-checker can only contain a pre-defined set of clock states, and the clock state of this chip-checker is not in this set.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The inversion mask of a ring can not be found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an internal firmware problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered a internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware is unable to allocate memory to store a list of rings. in its database.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an internal firmware problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmare encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmare encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected a problem where the defined data of a chip-checker is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an internal firmware problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an internal firmware problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The parity checking of the chip data failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered a problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered a problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware has detected a problem where a chip is accessed when the chip is not at an appropriate clock state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmare encountered an internal problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The scan ring's factory pointer is null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor was unable to turn on a chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was unable to turn off a chip clock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure of a chip clock operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal firmware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clock selection value is not supported on this system.
Internal firmware error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The chiplet base address is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function was illegally called.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The tables were asked for information they didn't have.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was encountered while trying to create an object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The node ID and domain ID did not describe a unique entry in this table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
File failure or end-of-file detected while reading the table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The end of the table was reached before it was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid parameter was passed in or detectd from the table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open the general purpose I/O (GPIO) engine to read the slot ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Rule was unable to open, or access, the library that was indicated in the table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A class indicated in the tables has not been found in the shared libraries on this build.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was error returned from ecmdDataBuffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported HDCT formatVersion was found.
There is no record of this card in the configuration of this system; unable to find a resource ID for it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal firmware error occurred - unable to create a directory in the filesystem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - an invalid parameter was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal software error occurred - the part that was specified does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware or firmware is not in a valid state to execute the operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - an "out of space" condition was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported system type or multi-chip module (MCM) type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal software error occurred - there was a posix thread failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - the data cannot be flattened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - the buffer sizes were not consistent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - the data cannot be flattened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - the data cannot be flattened.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The "manual power off" setting is not allowed since there is only one node in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The IPL was restarted due to hardware deconfiguration. This is an informational message; no action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - there was a data buffer error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to find a functional communication path between the service processor and the processor. Look at the error logs and guard records to isolate the failing or missing hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred - the registry key was set to an invalid value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal software error occurred - a persistent data value was not set as expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware was not able to find a processor card in this system. Look for other error log entries that indicate problems with VPD collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD cannot be updated with the new L2 line-delete information because the record is already full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is no space left in the line delete table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD cannot be updated with the new L3 line-delete information because the record is already full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD indicates less space for line-delete entries than the firmware expects. This is an informational message; no action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal software error occurred - there was a data size mismatch.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An undefined memory channel was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The vital product data (VPD) already has a failing bit for this interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal software error occurred - the part that was specified is already deconfigured.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The VPD information was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a pattern mismatch during the DMA test between the service processor and the processor; memory could not be read from or written to correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was received when attempting a DMA operation between the service processor and the processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Am internal software error occurred; attempting to execute firmware on the secondary service processor to recover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal error occurred - the hardware is in an unexpected state the for current operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
This is an error log entry created by a debug routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A CHIC abort was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported system type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The secondary service processor cannot be tested in its current state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal firmware error occurred when attempting to handle a hardware error. Look for previous entries in the error logs indicating a hardware error and follow the recommended actions.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CHIC operation received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed when writing data to a memory buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware detected corruption of the GX reservation are in P2.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system must be rebooted before making a GX adapter slot reservation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Not enough memory was available to reserve a GX adapter.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The calling function passed an invalid resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A potential deadlock was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A lock was held beyond the threshold.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No progress on the IPL due to locks being held.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CEC experienced a power line fault or outage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The secondary service processor is seeing missing devices.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware object manager (HOM) operation exceeded the allotted time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hardware object manager (HOM) firmware may be hung.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to stop instructions on a processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: attempt to perform operation from the wrong state
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: the hardware to perform requested operation was not found
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: hardware in incorrect state for attempted operation
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: invalid parameter passed into function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to start executing instructions on a processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to step instructions on a processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ECMD returned a non-zero return code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure occurred while attempting to flush caches out to main storage
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to complete self-synchronization.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to properly quiesce I/O hardware
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: required data is missing
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: requried data missing
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: error received from device driver
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory queues are not empty.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A maintenance command timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A memory operation failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A command was in progress while trying to send a maintenance command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Hardware SMP bus alignment did not complete successfully
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: required attribute not set
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: attempted to call invalid function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: an operation was attempted on deconfigured hardware
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software information log entry; informationl message only.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Hardware configuration is invalid
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error: data buffer used incorrectly
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to initialize internal hardware bus
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Errors were detected on an internal bus
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
HEA (host ethernet adapter) SCOM did not complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware timeout occurred during a cache operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware time-out occurred when attempting to access a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hardware error was detected on the LDC chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The information from wire test is not available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
T he hypervisor has not handed off the bus. There may be a hardware problem with the interrupt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine a valid self-sync delay value based on the system type and nest frequency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hot removal operation did not complete successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The value for the maximum number of threads per processor core was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The throttling bits were invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
SMA microcode failed to execute correctly
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware operation timed out
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: bootstrap was successful, but the service processor (or system controller) was not allowed to set the MP available latch.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A checkstop was detected on a chip during a concurr ent maintenance operation
The firmware encountered an internal problem: it can't create an engine object for the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an internal problem where the JTAG lock usage counter has an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem when it created a JTAG engine object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware was unable to create a JTAG chain object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an internal problem: it attempted a JTAG scan operation without a JTAG lock being granted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A duplicate device string was in the list of devices returned from the field replaceable unit (FRU) manager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An engine is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware is unable to collect the FFDC data from the ADAL (access device abstraction layer).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware is unable to unlock the FFDC data after collecting it from the ADAL (access device abstraction layer).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware is unable to reset the ADAL (access device abstraction layer) after an error condition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encounters an error when opening an ADAL (access device abstraction layer) to a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when the firmware tried to close the SCAN/SCOM device driver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver is unable to scan the data out from the ID register
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: a chip doesn't have a valid scan interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL SCOM error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An ADAL PSI error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An ADAL JTAG error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the appropriate ADAL interface for the device type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open the test of a JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to close the test of a JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an error when shifting a command into a chip as part of a scan operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when shifting data into a chip as part of a scan operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when shifting data out from a chip as part of a scan operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when shifting data out from the JTAG chain into a memory buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware timed out when waiting for a JTAG lock to be granted by the JTAG ADAL (access device abstraction layer).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when requesting the JTAG ADAL (access device abstraction layer) to release the JTAG lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware is unable to set the JTAG TAP (test access port) controller to a desired state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG device driver was unable to write to the scan register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG device driver is unable to clear the scan register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG ADAL (access device abstraction layer) failed to perform an SSR (simple scan register) scan.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG ADAL (access device abstraction layer) failed to perform an STSR (storage scan register) scan.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG device driver encountered an error when reading one of the registers inside the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG device driver encountered an error when writing to one of the registers inside the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware was unable to reset the JTAG TAP (test access port) controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The JTAG device driver encountered an error when trying to scan the hardware level register out from a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
JTAG device driver encountered an error when trying to shift data into or out of a chip
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
ADAL returned error from the call to rdal_jtag_force_lock.
The SCOM device driver encountered an error when trying to read the status register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to read data from a ring inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to read data from an SCOM register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to write data to a ring inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error when trying to write data to an SCOM register inside a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver encountered an error when trying to read a GP (general purpose) register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCOM device driver encountered an error when trying to write to a GP (general purpose) register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ADAL failed to send a command to a chip to perform a specified operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to start a data flushing process on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to stop a data flushing process on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCAN/SCOM device driver encountered an error when trying to read an internal register on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The SCAN/SCOM device driver encountered an error when trying to write to an internal register of a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI (processor support interface) device driver encountered an error when reading an SCOM register from the service processor chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI (processor support interface) device driver encountered an error when writing to an SCOM type register from the service processor chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The PSI (processor support interface) device driver encountered an error when reading from an SCOM-type register on the service processor chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes
The PSI (processor support interface) device driver encountered an error when writing to an elastic interface type register from the service processor chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an ADAL mailbox scratch read error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware detected an internal problem: it released a JTAG lock that wasn't granted to it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: it can't create a chip status object for a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected that the value scanned out from the Instruction status segister of the chip is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an SCOM attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected a non-SCOM vital error from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected a CRC miscompare error from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected either a parity error or an invalid command attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: a request to send an invalid JTAG command to the chip was made.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an error in the CRC calculation from the last data scanned out from the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an internal error: a chip doesn't have a valid functional unit or rule facade.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an error: access to a ring that does not exist in the system data base was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected an internal error: access to an invalid GP (general purpose) register was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: a request to send an invalid JTAG command has been sent to the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: it can't create a chip status object for a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: the number of SCAN and SCOM device strings doesn't agree.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware has detected an SCOM attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware detected a parity attention raised from the specified chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: access to an invalid GP (general purpose) register is requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error doing operations using the ECMD data buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware cncounters an internal problem: the string that specifies the location of a chip is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal register address was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A scan register was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An SCOM register was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an internal error: access to an invalid service processsor register type is requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: access to a PSI (processor support interface) register with an incorrect offset was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: access to an invalid service processsor register address is requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: access to an invalid service processsor) register address was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Calling out the service processor test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The same device string appeared more than once in the list returned from FRUM FRU mGetDeviceList().
The firmware encountered an internal problem; it can't find a chip object that is supposed to be system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system has issued an abort request while a chip is being scanned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The virtual power on (VPO) GetSCOM operation never finished.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An illegal call to getChipIds for hyperboot mode was made with a hyperboot registry key that was not enabled.
The firmware encountered an internal error: a chip command is sent in to the wrong type of chips.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ivJtagEnginePtr pointer is NULL.
The scan error type was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an internal problem: a request to send an invalid JTAG command ID has been sent to the LDC chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal problem: it can't create a chip status object for a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The ivFspEnginePtr pointeris NULL.
Failed to initialize a chip status object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The firmware encountered an internal error: the position of a chip in a JTAG chain is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: the number of commands sent into the chips (in a chain) exceeds the storage buffer size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: it can't locate a chip that is supposed to be on specified JTAG chain.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware encountered an internal error: the size of the data buffer that was provide is not large enough to hold the data scanned out from the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The verification of the JTAG chains in the system failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unsupported scan type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The general purpose (GP) register number was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chip checkstop was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has encountered a software failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A clock failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI detected a processor clock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI failed to enable the host PCI bus
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI failed to verify the host PCI bus
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid sharing configuration. Too many or too few memory controllers are present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find a system elastic interface table for this backplane.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find an elastic interface ID entry for the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI tried to get an object that could not be found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI received a bad parameter from the calling function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find the frequency data that was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid hardware configuration.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a user-overridden logical memory block (LMB) size that is not valid for the systems memory size. The CINI will instead use the default LMB size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to find a plugin object for the functional unit object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received an object that is not the correct type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Before an object was initialized, a function was called on it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CEC initialization interpreter failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected an attempt to execute an operation that is unsupported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received invalid data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A CINI call to an ECMD function returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No master time-of-day clock chip was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI has detected an SCOM attention on a chip. This chip will be deconfigured.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected an invalid frequency setting.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received a chip ID that was not found in the elastic interface table.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI failed to find a connection to or from the chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find the time-of-day wire delays.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find the card name for the CCIN that was passed in.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has detected a time-of-day delay for a chip that is too large.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No fabric path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The time-of-day clock path was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CINI was unable to reach the requested clock frequency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to obtain a phased-locked loop (PLL) lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Setting the clock frequency failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is no memory available in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to place a TCE in available memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI was unable to find the chip ID of the attached I/O hub.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received an unrecognized logical memory block (LMB) size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Multiple requests were made for the same interleaving group for in-memory trace.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received a request for in-memory trace that is larger than the available memory in the group.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
CINI has received a request for in-memory trace that would cover the first 64 MB of addressable memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when getting the configuration variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No object was found that describes and allows access to the hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware that is being accessed is marked "not functional".
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is no way to determine the hardware characteristics necessary to access it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The proper setup was not done prior to accessing hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clocks must be on, and they are not on.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clocks are still running; they must not be running to access an array.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The functional unit target had not been selected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Setup was done incorrectly prior to calling the firmware that accesses hardware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The input stage flags were not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The proper setup was not done prior to entering a mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Setup was done incorrectly prior to attempting to access the general purpose register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to access the processor hardware without the proper set up being done.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Instruction execution timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Core-specific array access requires a core unit ID; none was provided.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A funtion was called that is not supported.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was detected when reading system storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The clocks are off, and no scan method is available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid chip ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a procedure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to initialize optimizations when optimizations are currently enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Scanring caching is on; it must be off prior to accessing a scanring.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
No trace arrays were found on a chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid relative thread number was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid trace array type was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid chip ID for the I/O hub was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid chip ID was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid chip ID was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal address counter error was detected while reading system storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A command error was detected while reading system storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was detected when reading system storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid address range was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid starting address was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The number of bytes was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid memory address was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to enter a mode with a thread that is not functioning.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An attempt was made to enter RAM mode with a processor core that is not functioning.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to read main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to read main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to read main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to write to main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown chip group was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Parameter 1 was invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The valid bit was not set.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid clock state was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unexpected signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RSN code authorization failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The SMGR returned bad status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid istep was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The beginning istep name was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid istep name was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Ring cache is enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A memory address was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A memory service routine failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The licensed internal code sent incorrect command values.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The application received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CHIC was aborted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The string parameter cannot be empty for this function type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when receiving a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid command was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when obtaining a lock in the serial thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when receiving a message.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error initializing the server daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error handle passed in was null.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when flattening data for a call to the hardware object manager (HOM).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A parameter was missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unrecognized command was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There were unused parameters.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown option was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A value was missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid function type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A variable was out of range.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid character was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A buffer was too small.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown output type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A network error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported HMC operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when flattening a data buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when unflattening data returned from a call to the hardware object manager (HOM).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when manipulating a buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when manipulating a buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function does not support group IDs.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Function calls were made outside the server process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system performed a line delete. This is an informational message; no action is required.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The command table had an invalid command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware was unable to get the I/O hub object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get a pointer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware failed to call the ecmd functions.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A checkstop was detected on a chip before the main storage diagnostics were started.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A summary log was written.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This was a memory-preserving IPL, so this summary error log was created to terminate the IPL and to indicate that the firmware created and committed previous logs that pointed to defective hardware, or logs for software failures that were caused by the maintenance command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The failed to get the time of day.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller object was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory controller had been set to an invalid state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The main storage diagnostics detected an uncorrectable error on a DRAM.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Too many correctable errors were detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The firmware failed to read the line delete from VPD.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The RIO port speed is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The number of packets received did not equal the number of packets sent, of the cyclic redundancy check (CRC) did not = 0.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The physical status registers were not set to link; the test cannot proceed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
T he number of packets received did not equal the number of packets sent, of the cyclic redundancy check (CRC) did not = 0.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid address was found in the test case list.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The load type of the test case structure did not indicate the memory type test case.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
While iterating through the list of core functional units, a null pointer was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get a pointer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The test did not complete within the specified time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The test did not complete within the specified time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data in the status address is not changing. Data should be changing if the test were running correctly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The L2 AVPS test has completed successfully (informational message).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the CEC cage functional unit group.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The test case number that was provided was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CEC cage number that was provided did not match the expected value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to read AVPS data from a file into ecmd data buffer
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occured while checking the status of the memory test case.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occured while getting instruction status from the core, but the attention handling routine didn't find any errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The memory AVPS test has completed successfully (informational message).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was no core in the EC range.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
While iterating through the list of core functional units, a null pointer was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get connected fabric functional pointer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: An L3 line delete occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Wire test detected a CST error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The wire test firmware detected an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The wire test error log is full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A null pointer was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A problem was found with a hardware object manager (HOM) unit ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The calling function provided an invalid L3 chip hardware object manager (HOM) unit ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: An e-repair was done successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system processor group object was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Wire test detected more than 64 wire errors; the log file is full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was detected by the operating system when communicating with the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Wire test has detected an RDT error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An e-repair was successfully applied.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An e-repair was applied successfully.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when getting the functional unit for the receiver.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was detected by the operating system when communicating with the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The resource was guarded out.
Informational only: Guard actions performed on items the system detected and guarded during runtime, or that were guarded out using the ASMI.
The guard data did not exist because it was the first boot of this system, or NVRAM had been cleared. Guard data is now available.
Guard detected a new version of the guard data area. The guard data area was reformatted and the previous guard actions have been lost.
The guard firmware detected corrupted guard data. The guard data was reformatted and all previous guard actions have been erased.
The guard function was not able to open the guard memory file.
A bad return code was received from reading a utility file or seeking in a utility file when trying to read the processor domain data from the guard file.
A bad return code was received from reading a utility file or seeking in a utility file when trying to read the processor domain data from the guard file.
Failed to get the hardware object manager (HOM) unit ID.
An error was received when trying to read a registry value.
An error log was received from the SVPD when trying to read the VPD for a given resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The resource ID was not found in the system guard data file.
Manual deconfiguration of the service processor (or system controller) is not allowed because the service processor has already been deconfigured by the system, or the system is at runtime.
Unguarding the sibling service processor is not allowed at runtime.
A nonzero status code was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown error occurred when trying to obtain the indicator status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor reported an error when turning off the parent indicator.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unknown error occured when trying to update the indicator status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure when getting the SPIF data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Socket creation (for listening) failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to bind() failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A signal was received that not is handled by the ASMI.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor is being reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The write interface failed while initializing a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The read utility failed on a breakpoint attention
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The write operation failed when writing to the attnDataFile.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize the HYSR flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The read utility failed after a breakpoint attention
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was received from the mapper; a pointer to the JTAG engine being used was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system failed to respond after a recoverable error was eliminated .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A JTAG failed while waiting for an attention
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
DA alter failed during the write to main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure when reading a JTAG register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to enable attentions through the enable attentions interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
JTAG timed out while waiting for a lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Disabling the attentions failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get P0 root path size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write a flag to the registry .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when opening the Ahdata.dat file for a write operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hypervisor wrote an invalid SRC in the attention area.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A communications failure occurred on the primary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The write utility failed when writing the termination flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An emergency power off (EPO) PLCK failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A spurious attention was detected after attempting to clear all attentions for the ISR.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CHIC timed out while getting a reserve ID to process a processor checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed while attempting to release the CHIC reserve.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The processor runtime diagnostics failed to create an error handle for a processor checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read main storage after a breakpoint attention
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write to main storage after a breakpoint attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A bad return code was received from a write operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A JTAG lock cannot be released.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
CHIC failure when getting a functional group
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
HDAT failed while mapping main storag e to get attention areas.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
DA display failed during the write to main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An EcmdDataBuffer set length failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
AH server processor failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
HYRS interface failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A CCSP interface failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
SBCU interface failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Disabling the attentions failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure of the mailbox interface on an asset protection attention .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CECserver firmware detected a stopped clock due to an error attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
AH server process failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function returned with a failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The read utility failed to read the current IPL type from the state manager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A chip was asked to service a special attention, but it doesn't support it .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hypervisor requested a TI; an error log is built with the terminating SRC
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Manufacturing interface to read the policy flag failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to generate an event failed during a non-IO checkstop.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was received; a pointer to the functional unit group SystemProc was expected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The list of chips at attention came back empty; attention processing cannot continue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The read utility failed to read the current role of the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An event timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The chip attention handler was asked to handle an invalid attention type .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A master attention alone was detected. This is a condition where the master attention bit is active when there are no valid attention types triggering this attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A thread that isn't alive raised a special attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
One or more lines are stuck low because the value read back does not match the value
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An scom attention was detected on the current chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The incorrect object was used.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the FSI thread attribute object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
F ailed to get a lock
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The attention handler received an unexpected signal .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Error creating the chip ADAL strings file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
P5IOC attention-handling-in-progress set.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No attention line group object was found for this chip.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to get the chip device strings
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Call out the chips on the attention line that caused the attention.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a callout failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threads are not finished.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a connection failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid register value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An empty list was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An SCOM attention/checkstop scenario was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The attention component is terminating.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A monitor failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown box value was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when reading a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to read the processor speed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when a query was made of the power management mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to configure a target.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when forking a child process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to signal the other processes to clean up via a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The daemon may not be running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The parser encountered too many of a special character on a single line.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a new daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred in a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open the log file header after two attempts.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open the log file after two attempts. .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write the log file header.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to write the log file data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The stepsize is zero, which is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred in a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The expected number of processors was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid number of arguments was received for a command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The requested pass-through command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid command was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred when a query was made of the current power management mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when forking a child process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The input argument was not a valid string buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when updating the table iteration count.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when executing a table command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing the number of the currently-executing line.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a slew command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when executing a sweep command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: The customer-requested power mode was changed outside of this application's control. The power mode was probably changed by an external entity.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error while accessing the cluster machine type/model.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An operation on a session entry object failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to construct a netc address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call into a NETS component interface failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The mboxOpenHMCInterface call succeeded but the hypervisor returned an error when attempting to open a hypervisor session.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read or write data to or from a data buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A mailbox component interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to read or write a registry key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The caller attempted to create an event broadcast object using an unknown broadcast type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The caller attempted to perform an operation on an invalid file type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to mkdir failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed trying to subscribe to, or signal, an event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Memory allocation failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware management console (HMC) was unable to open a hypervisor session because the service processor (or system controller) firmware determined that the hypervisor was not running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call into spifWriteBlockCommand to get the cage and frame number failed. The failure is not specified, so the service processor (or system controller) will return a generic failure status to the hardware management console (HMC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was received when trying to open the LEDs file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Using the non-blocking mode for semaphore operations, it was determined that no operation was performed during the lock table command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The caller of an interface supplied an invalid parameter or the interface unexpectedly failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to calculate the timestamp stored in the session entry object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to acknowledge surveillance.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware management console (HMC) sent an invalid record.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client was not able to obtain the requested resource lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client was unable to release a resource lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
UTIL component file-related operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The client that was attempting to authenticate itself supplied an invalid password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An SMGR component operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A command sent to the hypervisor failed with a return status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to issue this command unless the hypervisor is at standby.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A SPIF component operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The response data from SPIF was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A validation error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A code update (CUPD) error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The CHIC component returned a failure code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Informational message: No system memory was found by the guard function, so the system has never been booted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to perform the requested operation due to lack of access permissions.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A concurrent maintenance interface returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to initiate the node controller dump due to the wrong target system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A resource was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to spawn a process, or a failure occurred in a Unix system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An SDR record that was not type 2 or type 3 was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to create the IPMI server process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An open operation failed on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A close operation failed on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A read operation failed on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A write operation failed on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A configuration operation failed on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to open the general purpose I/O (GPIO) engine to read the slot ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to close the general purpose I/O (GPIO) engine of a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when trying to read the general purpose I/O (GPIO) pin.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a process.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The dispatcher received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to create the dispatcher thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An IPMI command timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unrecognized IPMI command was encountered.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the path from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to fork a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create a synchronization file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unexpected reply was received from a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to synchronize with a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the network client address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to establish the listening queue on the network server address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to bind the network server address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the network server address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The input parameters were not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to lock a thread mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to unlock a thread mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize a mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize a condition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A partition dump request failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to find the LED access record for the requested LED.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to drive an LED with the drive LED function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unexpected maximum resource ID (RID) was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create an event thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unrecognized event was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a registry variable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the current state data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the current power state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open an engine on a device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write to the general purpose (GP) I/O pin.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to close the general purpose (GP) I/O engine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to create a context.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The initial attempt to submit "press" control blocks failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when waiting for the control blocks to complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to submit control blocks failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the pins to an unconfigured mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to set the button debounce interval
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to configure the power good (pgood) register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function reported a failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to determine if a power lock is being held or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The general purpose (GP) I/O device that the control (operator) panel did not show up within the allotted time
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The snoop string was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Phone numbers for call home are not programmed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Missing information in set up panel for customer pager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Dialing the customer pager failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Missing account information in call home setup.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Missing information in the modem setup panels. Make sure all fields are filled in.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error; the daemon process failed to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A child process failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error; the call home process received a signal that was not handled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error; a process received a signal that was not handled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error; communications failure with service center.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Socket connection to service center failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The customer initated a call home test.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Call home test initiated by test methods.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error; process failed to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Communications problem with modem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The snoop string was found in the input data; a system reboot has been requested.
Failed to write to a general purpose I/O (GPIO) pin.
An invalid return code was received when opening the serial device used for UPS detection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Communication error with serial port; unable to open the UART device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error communicating with the serial port.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal hardware error while trying to clear the DTR signal on serial port 1 (while attempting UPS detection).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal hardware error while trying to set the DTR signal on serial port 1 (while attempting UPS detection).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error occurred during reboot attempt.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was received while waiting for the secondary service processor to terminate.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure when reading the registry.
There was a failure when reading the registry.
RBOT was told to power the system back on, but the power wasn't off.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The LED control firmware was busy handling another request; the semaphore was locked.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system power control network (SPCN) command was retried, and failed again.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system power control network (SPCN) command was retried, and failed again.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Internal software error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system power control network (SPCN) command to collect the LED data did not return any data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system power control network (SPCN) command to control the physical attention LED failed. The LED and the NVRAM could be out of sync.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data transferred from the hypervisor was incomplete. The data that was returned has been truncated for some unknown reason.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SURVserver daemon received a unexpected signal
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize a thread attribute.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to initialize a thread attribute.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to accept a client request failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to receive a client message failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to synchronize; another instance of surveillance is already running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when creating a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when connecting to a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending and receiving data from a daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to synchronize with an internal firmware server.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to close the client socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to close a socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to read a value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An event signal error was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to write a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to read a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the mailbox function when attempting to notify the hypervisor of a change in a status flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function received an invalid client name.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function received an invalid client type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to flatten the error log; unable to send the error log to the client.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when attempting to extract flattened error data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The client gateway was not able to communicate with the primary service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create the gateway address to send the surveillance heartbeat to the primary service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when sending data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to bind the listening address failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to listen in failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt to open a directory failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The reason for this error is stored in the userdata1 portion of the error log entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when creating an address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was found in an address object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
rdal_psi_open call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
rdal_psi_wait call failed
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to a function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Indicates that the adal_base_ffdc_wait for the FSI mailbox device returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an FSI surveillance failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to a function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to a function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Opening a function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
rdal_psi_close failed.
rdal_mbx_close failed.
There was a PSI ADAL first-failure-data-capture unlock failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the service processor firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the service processor firmware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a service processor firmware problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by the service processor firmware. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure in the service processor firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error while attempting read the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to lock the sinkfile.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
netcSendRecv returned error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid major op was recieved from the service tags.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error while attempting to create a listening socket.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error returned by netsSend call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
rmgrd application failed during a fork() call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system call to initialize the thread parameters failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A system call to initialize thread parameters failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A system call to create a posix thread failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when creating a message queue.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid component type was received when attempting to create a handler thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error returned by netcConnect call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The NectSendRecv call returned an error when communicating with the rmgrd daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The netcClose call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Synchronization with server call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A call to bind returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Listen call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error returned by netsConnectServer().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The rmgrd daemon received a unexpected signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered while initializing mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error encountered while locking mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error encountered while unlocking mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error returned by netsClose call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The daemon encountered an error while attempting to return error log data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unknown minor operation id received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the initialization routine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from spawning a thread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid operation request was made to the data correlation handler.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from initthread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the function call to set the service processor role to primary.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid thread type has been sent by the caller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A non-existent registry variable was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The file that was requested for synchronization does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error attempting to open file for reading.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error returned when reading a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error while attempting write the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Error while writing to the file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A data correlation command can only be issued by the secondary service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Function returned error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned when the primary service processor (or system controller) attempted to retrieve it's system firmware module level information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when finding the size of a registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to read the size of the data key.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the discovery function retrieving the FSI state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to create the event handler object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid event ID was received; notification cannot be done.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when attempting to signal a service processor role change event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the function retrieving the current service processor role.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the function retrieving the redundancy value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the function retrieving the sibling service processor's state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from the function retrieving the service processor position.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid operation requested a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The primary and secondary service processors (or system controllers) do not have the same system firmware loaded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to restore a flattened error log.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when unflattening the log sent by the primary service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An administrative failover request was sent to the service processor (or system controller) that did not have the primary role; the request was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when beginning an administrative failover at standby.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when writing a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A network receiving operation from the sibling service processor failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when writing a registry value.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to create an event handler object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This indicates the requested action failed because the sibling service processor is not in the working state.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
plckIPLRequest call to initiate an administrative failover at standby returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The state manager did not return a valid failover type to be used.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A surveillance failure of the primary service processor (or system controller) was detected at pre-standby.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Redundancy cannot be enabled because the secondary service processor is not at standby.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A command line option was incorrectly removed or added.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid time-out was specified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system's state does not allow failover to be initiated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned when an operation was requested on the sibling service processor (or system controller).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
smgrInitiateToolReset() call returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failover readiness check was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A forced termination and failover operation is requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The attempt to terminate the service processor and failover failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
smgrFspIplTypeRequest() returned error on a IPL request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid IPL type was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The redundancy manager is determining the type of error that occurred during an administrative fail-over.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: the primary service processor is performing an administrative failover to the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An administrative failover request was received from the primary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An emergency failover is being performed by the secondary service processor. The hypervisor requested the failover after resetting the primary service processor, or the primary service processor terminated due to a failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Call to fspinit_do_transition failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failover was requested when another was already in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid operation requested the rconUtil function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The secondary service processor returned an error when starting to implement an administrative failover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failover block request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request to unblock a failover was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error was encountered when sending data to stop a message service of an HMC that is failing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Sibling returned an error on the requested operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The secondary service processor (or system controller) was asked to initiate a reset/reload.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to the function that switches from one service processor to the other failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The last known state of the primary service processor was runtime, and the secondary is not at runtime.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The synchronization of a nonexistent file was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The synchronization of a nonexistent registry was requested
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Surveillance communication with the sibling service processor failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
rmgrremote daemon received an unexpected signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An operational error occurred on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
SYNC should not have been called by the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The caller specified a non-existent target component.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Timed out waiting for a response from the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A n error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Attempts to connect to the sibling service processor failed on all links.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to connect to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure while attempting to send a request to the sibling service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
rmgrUtilSync was called by a function other than util.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The position of the service processor has not yet been determined; the mailbox cannot be configured.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A system command to call ifconfig returned errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A system command to call ifconfig did not complete without errors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid operation target was provided for the library functions to handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Redundancy is being modified.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A log was passed into a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Redundancy cannot be enabled if the system is not at standby if the request is from the HMC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when joining a pthread.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: redundancy was enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: redundancy was disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request was made to read from a registry that doesn't exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A synchronization call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call during redundancy enablement was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An emergency power off (EPO) was requested when the system was in the transitory state. This will cause termination of the secondary service processor first, then failover will begin.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failover has been unblocked.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Service processor failover is not supported in this system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned by guard when attempting to deconfigure the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An administrative failover to the secondary service processors not allowed at this time due to the state of the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when closing a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a remote deletion request
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No clock signals were detected on the sibling service processor's link.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hidden service processor error log entry to help correlate with the dump will be generated due to the recovery action.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A stream was reqested on a file that is on the synchronization list.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to dlsym() failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from utilfile.sync().
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dumpForceSync call was made during a request to enable redundancy.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The secondary service processor (or system controller) was unable to communicate with the primary service processor (or system controller) for longer than one hour, and initiated a service processor failover to assume system management.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The notification was rejected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call was rejected during redundancy enablement.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Service processor (or system controller) redundancy is disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined error was returned when generating statistics on what should be a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when checking to see if a file exists.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from deleting a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined minor operation was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when writing a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The p3 registry does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when checking the redundancy policy.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a directory synchronization call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a file synchronization call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a registry synchronization call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a send data call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when opening a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when closing a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to pack the registry into an empty buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error when reading a directory entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed on a directory entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported element was encountered during a directory synchronization.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A n error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a system call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a stream synchronization call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to pack data into a butter that was not empty.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to pack data into a butter that was not big enough for the data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to append fewer than zero, or zero, bytes to a buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to pack a registry of an invalid size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request was made to sync a file that exceeds the maximum buffer size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request was made to synchronize a file that exceeds the maximum buffer size.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from rolling the buffer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The space allocated for the file data does not equal the amount of file data to transfer.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to create a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An attempt was made to synchronize a directory with something that isn't a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a p3 registry comparison.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a p3 registry comparison.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when writing to the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the call to delete t he directory contents.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to delete a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An undefined error was returned when generating statistics on what should be a directory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from a function call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to unlink an element .
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from util when attempting to seek.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A stream counter overflow occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid operation code was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This SRC indicates that the system ran for a long time with only one bulk power assembly (BPA), and a large number of firmware updates were done. Then a sibling BPA was added (or swapped in).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A type other than time-of-day, HMC password, or CEC name was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The bulk power assembly (BPA) and its sibling have the same IP address.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to open a synchronization file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call to lock returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This bulk power assembly (BPA) does not have an IP address stored for a sibling BPA for the synchronization process to use. It is possible that there is no sibling BPA present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was injected for debugging purposes.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred in a utility register.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A synchronization failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A NETS failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A thread failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A client failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A code update (CUPD) failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A mailbox (MBOX) failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A direct memory access (DMA) failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A CHIC failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid SMA system was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to load and boot the IPC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A null pointer was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to start the IPC.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to perform a reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The reset was not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump request failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The handle was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump was unexpectedly invalidated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump utility failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An event failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: an informational error log entry was generated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor firmware was unable to get the SRC from the irrecoverable error log.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Unable to read the reason for the reset from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor failed to clear bits in the device immediate status register (DISR).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The reset/reload function is called with an insufficient number of arguments.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid reset/reload routine was called.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An unexpected signal was received when reset/reload was running.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor failed to set the bits in the device immediate status register (DISR), which is used to communicate the reset/reload status to the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A service processor reset/reload occurred. The error log for the error that caused the reset/reload could not be retrieved. Use other error/event logs or a service processor dump to gather error information.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The HMC requested a reset/reload to termination.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An XREF session entry failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an XREF API failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the hypervisor state registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No CM lock was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed to get the maximum number of resource IDs (RIDs) for a given field replaceable unit (FRU) type.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to enable a panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in the hardware object manager (HOM) API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an RTIM API failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF CCMM internal error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF CMD build failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure during concurrent maintenance recovery.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The concurrent maintenance firmware encountered an unexpected failure when calling the mailbox interface to disable the current time-of-day topology.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF sequence error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read a checkpoint; all are in use.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the checkpoint registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a code version mismatch.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The event management component returned an error when the concurrent maintenance firmware tried to subscribe to the sibling service processor state change event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to guard out the concurrent maintenance service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The command line parser failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when trying to run a concurrent maintenance xml file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to send a progress code.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to read the service processor role from the redundance manager.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF redundant service processor failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An abort was detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF invalid hardware failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF condition failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to connect to the concurrent maintenance daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to convert an RID (resource ID) to a HOM (hardware object manager) unit ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No environment path was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The cross reference (XREF) file was not found.
Informational message: this platform does not support concurrent maintenance operations.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when creating a thread; aborting ccmmsrv
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The command request had invalid concurrency.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to convert the resource ID to the HOM (hardware object manager.) unit ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Cannot load symbol.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
While a concurrent maintenance operation was in progress, an API failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
While a concurrent maintenance backup isolation operation was in progress, an API failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open the buddy JTAG device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open the buddy GPIO (general purpose I/O) device.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to open a handle.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The concurrent maintenance firmware is isolating the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to read an error log from the repository.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unhandled signal was received by the concurrent maintenance firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF HMC disconnection event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This is a generic SRC logged to flag a recovery action.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF state change event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF power off event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an attention API failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A concurrent maintenance operation was aborted while the Anchor VPD card was not installed in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system level activation status received from the hypervisor was invalid, or indicated an error. This usually indicates that a hypervisor error was detected during a concurrent maintenance operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The concurrent maintenance firmware detected a ccmmsrv crash and will try to recover.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF system reset/reload event.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an XREF failover during CMOP.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The recovery director received a reason for recovery that was not recognized.
The recovery director received a reason for recovery that was not recognized.
The utility routime read 0 bytes from the service processor's state file.
There was no concurrent maintenance capability on the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when clearing the IPL speed override.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The attempt to unmask the FSI interrupts returned an error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to retrieve the HMC ID for the NCR action.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to retrieve the HMC ID for the NCR action.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when trying to check the power save mode.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The timer tick expired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure in an API.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The step is done.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The target CCIN was not found
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A registry read failure occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A time-out occurred while waiting for the secondary system controller.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A PSI failure occurred with the query active.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when disabling the PSI link.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Rebooting a network controller failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A node instance was found that is not recognized.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A timer expired.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred when the secondary service processor (or system controller) was reset.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The XML file was skipped.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: A concurrent maintenance operation was started.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: A concurrent maintenance operation was stopped.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
This error code is reserved.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred during a service processor (or system controller) dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occured while attempting to determine if a service processor dump exists.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred during a file I/O operation.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump operation was attempted that violated the dump policy.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to obtain or release a lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown dump content type was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unsupported copy operation was attempted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Null global data was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occured while attempting to denote a completed service processor dump as valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occured while attempting to access a file.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the service processor attempted to notify the operating system that a service processor dump had been deleted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred when the service processor attempted to notify the operating system that a service processor dump occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred during a file I/O operation on a pipe.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An operation on a lock for a dump operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system error was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: The dump storage file system was formatted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to write to the control (operator) panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal service procssor operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service procssor operation failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to display a new progress code on the operator panel.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to enable the service processor dump feature.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to notify the HMC that a service processor dump occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to notify the HMC that a service processor dump occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to notify the HMC that a service processor dump occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine if the service processor dump feature is enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine if the service processor dump feature is enabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Dump files were deleted before they were captured in the dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor dump failed because there was not enough room left to store it.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while processing a dump file
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine the name of a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine the size of a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine the system serial number.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to determine the service processor hostname.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A service processor dump operation did not complete
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Encountered an out-of-storage condition while attempting to collect a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while processing a dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while processing a dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occured while attempting to determine if a service processor dump exists.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while retrieving a dump
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A failure occurred when opening the dump device
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A dump was attempted when another dump was in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to delete a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to retrieve a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A service processor (or system controller) plug-in dump was taken.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while attempting to delete a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A service processor (or system controller) dump was invalidated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The dump storage device was full.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An error occurred while collecting a service processor dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The system is not running on the primary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The PLID of the latest request did not match the PLID of the current request; unable to delete the file.
A hardware unit dump request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A system dump collection request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Dump is disabled.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The file does not exist.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The MDRT source and destination tables are incorrect.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A new dump object could not be created because one already exists.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Deletion of the request block failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There is no file in which to store the request block.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A post dump reboot is being requested with bad chips in the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system is not running on the primary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump buffer access error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There is no location in which to store the dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The dump is not complete and cannot be extracted.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failed to create a memory the DumpToExtract memory object.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A dump collection is already in progress.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The system manager will not allow the dump transition.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The dump request is rejected because a system dump is already present.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Dump was disabled by a manufacturing flag.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
DMA operations are not allowed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
DMA operations are now allowed; will CTRM the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A request to invalidate the dump was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid update dump request was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from the statfs call.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The dump component has received a dump extraction request.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Collection of a dump has been interrupted, usually by a reset/reload or service processor failover during the dump.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The HMC has been notified that a hardware dump was just collected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Critical storage levels were exceeded, invalidating or deleting hardware unit dump collection.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
HOM detected a memory configuration change during a main store IPL and the dump has been marked complete without main storage.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hardware unit dump collection was told to abort.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor tried to abort the hardware unit dump, but it didn't stop in time.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A checkstop IPL was requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No mapping was found for the unit ID types.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The code update component, or the concurrent maintenance component, has the lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure when determining the number of processors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure when determining the number of processors.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure of the DADA "get array data" command.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Cannot determine whether the hypervisor is active or not.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
eCommand Failure
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The creation of an object failed.
An invalid command was received.
An invalid hardware object manager unit ID was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure occurred during processor cleanup.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The mailbox message to the hypervisor failed; the notification of invalidation was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The internal value that tracks whether or not the hypervisor in active is in the wrong state.
There was an error when retrieving the facility list from rules with the provided content.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
SMGR request (smgrIplTypeRequest) failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
SrciSrc object construction failure.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was an error reading the system dump id from the registry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned from rtim_GetTimeOfDay.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
RMGRGetFspRole failed; cannot determine the service processor's role.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a failure when notifying the HMC that a hardware unit dump is ready.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when verifying that panel function 42 is enabled.
Stopping the clock failed on the core.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A failure was returned from hysrRunServiceRoutine.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Failure when trying to get the concurrent maintenance operation lock.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error occurred when calling a function.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to adal_fsi_open failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to adal_fsi_wait failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to adal_fsi_config to determine the number of CFAMS failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to adal_fsi_config failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A local bus is not owned.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_scan_dram failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new DRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_scan_nvram failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of new NVRAM errors was reached.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An NVRAM address has appeared multiple times.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_fork failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_file failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The threshold of bad blocks in the NVRAM's flash memory was exceeded.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_open failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The call to watchdog_ping failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A signal was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Call to statfs() failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
PCS usage has reached 90%.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
PCS usage has reached 80%.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
FSI IRQ loop event occured; one or more of this type event was not detectable.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The user specified a link, or CFAM, but not both.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A call to a function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A clean function failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to initialize the library load mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to lock the library load mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An error was returned when attempting to unlock the library load mutex.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal error occurred when checking the health of the flash memory on the service processor. This may or may not indicate a degredation of the flash memory performance. Check the details of the error log entry.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The number of one-bit flips exceeded the threshold. The service processor hardware will have to be replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The number of uncorrectable bit flips exceeded the threshold. The service processor hardware will have to be replaced.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor kernel is reporting that the system is running out of space in the flash memory.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor kernel is reporting that there is not enough free space in flash memory to boot the system.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A local bus loss event occurred, but an error was returned when attempting to determine which bus was lost.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A PSI error has been detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid HOM node information was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid PSI device was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
GXHBC was not found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function call to get the DMA paths did not return a value corresponding to the current resource ID.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function call to get the DMA paths did not return any primary DMA paths.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function call to get the maximum number of resource IDs returned zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The function call to get the resource IDs returned zero.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No resource ID matches the resource ID of the current service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A function call failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A PSI error has been detected.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to read from the bulk power controller (BPC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
No functional processor clock was found.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Communication paths on the service processor side are not enabled to do DMA operations.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The CEC side is not configured properly.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failure to validate the password.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Detected a unexpected command after a service routine run.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
SPIRA does not have sufficient space for the main store dump results table entries.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hypervisor did not allocate enough storage for the data structures being
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor timed out while waiting for the hypervisor to start.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor either retrieved invalid data from CEC memory, or found that a mainstore dump is invalid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal service processor error occurred. Check for system firmware updates and apply if available before replacing the service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The data read from main storage is not the same as what was written to main storage.
The service processor attempted to send a message to the hypervisor when the hypervisor message queue was already full
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Nobody was waiting on the message that was just received from the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The service processor was unable to make an entry in its error log that the hypervisor requested.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor did not provide a valid address to the service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The wrong number of bytes was written on the mailbox interface.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an invalid value in a message from the hypervisor to the service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor did not provide enough data to complete the function
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Sending a message to the HMC took too long
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor attempted to add a already-existing buffer to the list of HMC buffers
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor is garding out a hardware resource
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The communications path to the hypervisor is currently disabled at the request of the hypervisor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A request was made to disable communications between the hypervisor and the service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor sent the service processor an invalid value during a boot operation
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor is not responding to messages from the service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor attempted to use an invalid HMC buffer
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A function performed by the hypervisor ended with an error
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
In a system with redundant service processors, the secondary service processor is not booting with the primary service processor
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
Failed while waiting on a message from the hypervisor; probably timed out.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor sent the service processor an invalid SRC to display.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There are no valid PSI links that can be used for mailbox activity. Check the guard records regarding DMA paths to see why there are no valid links. Whatever took the PSI links down has already occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The hypervisor did not read messages from the service processor (or system controller) within the allotted time. Either the hypervisor is unresponsive or the PSI links are down.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The device driver indicated that an error occurred prior to his operation, so this operation should be retried.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Informational message: Due to reset/reload or failover, the hypervisor is being told to synchronize data to the secondary service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The offset from the hypervisor was beyond the size of the firmware update module being read.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The checksum calculated by the service processor (or system controller) did not match the checksum in the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
It has taken the hypervisor a long time to pull a message off the mailbox hardware. Although this is below the 45 second predictive error limit, it can cause HMC incompletes when it occurs a couple times.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An internal firmware error occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hypervisor has not handed off the bus after forcing the link down; there must be a hypervisor problem.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A hypervisor occurred.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An unknown error occurred when trying to update the indicator status.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the hypervisor firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the hypervisor firmware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hypervisor firmware problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by the hypervisor firmware. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
An invalid voltage control command was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The daemon received a message with an invalid function field.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The POWER server was not ready for the command it was sent.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A resource ID was not in the table,
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Invalid input was received.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The daemon received a request while running on the secondary system controller or service processor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The power off unit command failed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The bulk power controller (BPC) is currently performing a validation operation. This operation should be retried. If the condition persists it is probably a firmware problem; the BPC firmware should be updated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
An invalid request was sent to the network validation daemon.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The version value sent in the message doesn't to match the current version.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The was a communication problem with the remote bulk power controller (BPC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The network validation daemon received a signal.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The netv daemon determined that there are too many error logs to the transferred to the system client.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The service processor was unable to collect the network data.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The PVID configuration is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The virtual LAN mapping was not correct.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The VLAN enablement configuration is not valid.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The MAC address is not available.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
A host's IP address on network side A does not match the IP address on side B.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The multiplexer configuration key is not valid with the sibling state change.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Unable to get the card type from the environment.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
The wrong function passed was in.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The HMC is attempting to send a message that exceeds the maximum size of a message between the service processor and the hypervisor.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a hardware-detected problem due to the HMC firmware.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to HMC firmware, but it could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an HMC firmware problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The hardware detected a problem that was caused by the HMC firmware. The dump that was taken may need to be analyzed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A DMA operation was attempted in TCE mode before setup for TCE mode was complete.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
The error log server received a syslog message that requires attention.
A power error was validated.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
BOOTP: Discovering the server timed out.
Refer to partition firmware progress codes using code CA00E174.
An invalid network configuration was entered by the user.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Service switch error. Function 26 was done before function 25.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a service switch error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
Customized data is missing.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A lab test was performed.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions. For more information on tracking versus serviceable events, go to (B1xx) Service processor firmware reference codes .
There was a hardware-detected problem due to the external environment or a user error.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A hardware failure was detected in the central electronics complex (CEC).
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was a failure most likely attributable to the external environment or a user error, but could also be software-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
There was an external environment failure, most likely attributable to a software problem, but it could also be hardware-related or require further support.
If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service actions.
A B2xx reference code indicates that an event or error was detected and logged by virtual service processor firmware.
The logical partition associated with the event or error can be identified from the "LP=pppp" ASCII string found in the SRC word 1 extension field, where 'pppp' is the logical partition ID.
To resolve a B2xx reference code, determine if the SRC requires a service action.
If the SRC is listed in a serviceable event view, use the FRU list from the serviceable event view to determine the actions to take.
If you do not find the SRC in a serviceable event view, then it is an informational event and does not require service action.
A problem occurred during the migration of a partition
The partition ID is in extended word one as LP=xxx in decimal format. The user attempted to migrate a partition to a system that has a power or thermal problem. The migration will not continue. Look for and fix power or thermal problems on this system and then retry the migration.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A platform LIC error occurred while it was trying to allocate memory. The IPL will not continue. Perform a platform dump and contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This is a partitioning configuration problem. The LPARCFG Symbolic FRU will help correct the problem. If the problem persists, call your next level of support.
A problem occurred during the migration of a partition
The migration of a partition did not complete. The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A failure occurred due to a validation error. The IPL is terminated. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The partition attempted to IPL prior to the platform fully initializing. Retry the partition IPL after the platform IPL has fully completed and the platform is not in standby mode. If that IPL fails, call your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This is a partitioning configuration problem. The partition is lacking the necessary resources to IPL. This error might occur when you shut down a partition that is set to automatically IPL and then turn the managed system off and back on. When the partition automatically IPLs, it uses the resources specified in PHYP NVRAM, and this error occurs when the server does not find the exact resources specified in NVRAM. The solution is to activate the partition by using the partition profile on the HMC. The HMC applies the values in the profile to NVRAM. When the partition IPLs, it uses the resources specified in the profile.
A problem occurred during the IPL of a partition.
The partition could not IPL at the Timed Power On setting because the IPL setting of the partition was not set to Normal. The partition ID is in extended word one as LP=xxx in decimal format.
A problem occurred during the IPL of a partition.
The partition could not IPL. The partition ID is in extended word one as LP=xxx in decimal format. An operating system MSD IPL was attempted with the IPL side on D-mode. This is not a valid operating system IPL scenario, and the IPL will be halted. This SRC is usually seen when a D-mode SLIC install fails and attempts an MSD.
A problem occurred during the IPL of a partition.
The partition could not IPL. The partition ID is in extended word one as LP=xxx in decimal format. You are attempting to IPL an operating system that is not supported or not enabled. On certain models the IBM i Operating System operating system can be enabled or disabled from the ASM menu. If you are attempting to run IBM i Operating System in a partition on such a model, check the ASM menu to ensure that IBM i Operating System is enabled.
A problem occurred during a partition Main Storage Dump.
A mainstore dump IPL did not complete due to configuration mismatch. Contact your next level of support.
A partition memory error occurred
An attempt to perform a partition dump failed. A partition memory error occurred. The failed memory will no longer be used. The partition dump was terminated. The partition ID is in extended word one as LP=xxx in decimal format. Re-IPL the partition.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A partition running on I/O reporting mode has abnormally terminated. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. No alternate (D-mode) IPL IOP was selected. The IPL will attempt to continue, but there may not be enough information to find the correct D-mode load source. Have the customer configure an alternate IPL IOP for the partition. Then retry the partition IPL.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. No default load source IOP was selected for an A/B-mode IPL. The IPL will attempt to continue, but there may not be enough information to find the correct load source. Have the customer configure a load source IOP for the partition. Then retry the partition IPL.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The IOA for the load source device needed an IOP, and none was detected. Check your LPAR configuration and make sure the correct slot is specified for the IPL load source. Then retry the partition IPL.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. During the partition IPL, code tried to determine if the device in a slot was an I/O Processor or an I/O Adapter. That check failed. Check your LPAR configuration and make sure that the correct slot is specified for the IPL load source. Then retry the partition IPL. If this does not resolve the problem, perform [LIC]LICIP15[/LIC].
A problem occurred during a partition Main Storage Dump.
A mainstore dump IPL did not complete due to a copy error. Contact your next level of support.
A problem occurred during a partition Main Storage Dump.
A mainstore dump IPL did not complete due to a configuration mismatch.
A problem occurred during a partition Main Storage Dump.
A mainstore dump IPL did not complete due to a copy error. Contact your next level of support.
A partition property was set to default setting
The partition ID is in extended word one as LP=xxx in decimal format. A partition property that was supported on the original system is not supported on this system. The property has been set to a default setting. Check all the partition properties of the migrated partition and ensure they are set to the desired values.
A partition property could not be transferred
The partition ID is in extended word one as LP=xxx in decimal format. A partition property could not be transferred during a partition migration. The partition migration continued. No immediate action is necessary. At the earliest convenient time or service window, re-IPL the partition to restore partition properties.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A slot that was needed for the partition was unavailable. See the Symbolic FRU SLOTUSE for more information on the cause of this error.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A problem occurred when an attempt to power off a Virtual I/O slot was performed. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A slot that was needed for the partition was unavailable. See the Symbolic FRU SLOTUSE for more information on the cause of this error.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The platform LIC for this partition attempted an operation. There was a failure. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The platform LIC for this partition attempted an operation. There was a failure. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The platform LIC for this partition attempted an operation. There was a failure. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The platform LIC for this partition attempted an operation. There was a failure. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A slot that was needed for the partition was either empty or the device in the slot has failed. See the Symbolic FRU SLOTUSE for more information on the cause of this error. If you have a RAID enablement card (CCIN 5709) on your system, it will disable an embedded SCSI adapter. If that embedded slot is called out in the error, you can safely ignore this error.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The platform LIC for this partition attempted an operation. There was a failure. Contact your next level of support.
System log entry only, no service action required
A user requested an immediate termination and main store dump of a partition. The partition ID is in extended word one as LP=xxx in decimal format.
A problem occurred during the IPL of a partition.
IPL did not complete due to a copy error. Contact your next level of support.
A problem occurred during the IPL of a partition.
The adapter type might not be supported. Contact your next level of support.
System log entry only, no service action required
The adapter type might not be supported. Ensure that a valid I/O Load Source is tagged.
A problem occurred during the IPL of a partition.
The adapter type cannot be determined. Ensure that a valid I/O Load Source is tagged. If the problem persists, contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the IPL of a partition.
Verify that the tagged Load Source Slot is supported for IPL. If it is, contact your next level of support.
A problem occurred during the IPL of a partition.
The search for a valid load source device was exhausted. The partition ID is in extended word one as LP=xxx in decimal format. Perform [LIC]LICIP15[/LIC].
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A problem occurred on the path to the load source for the partition. If present, look in the Serviceable Event View for a B7xx xxxx during the partition's IPL. Correct that error and retry the partition IPL.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The B2xx xxxx SRC Format is Word 1: B2xx3114, Word 3: Bus, Word 4: Board, Word 5: Card.
System log entry only, no service action required
The partition ID is in extended word one as LP=xxx in decimal format. Retry count exceeded. This is logged for each unsuccessful attempt to IPL with a loadsource candidate. If the IPL fails, look for other serviceable errors.
System log entry only, no service action required
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This is a platform LIC main store utilization problem. The platform LIC could not obtain a segment of main storage within the platform's main store to use for managing the creation of a partition.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An unexpected failure return code was returned when attempting to query the IOA slots that are assigned to an IOP. Look for B700 69xx errors in the Serviceable Event View and work those errors.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. If word 3 is zero, then this SRC is informational and can be ignored. Otherwise there is a problem in the platform LIC. A nonzero bus number has no associated bus object. Look for B700 69xx errors in the Serviceable Event View and work those errors. If there are no serviceable B700 69xx errors, or if correcting the errors did not correct this problem, contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An unknown bus type was detected.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The load source IOP is not owned by the partition. This is a configuration problem in the partition. Have the customer reconfigure the partition to have the intended load source IOP. If there is not a configuration problem then contact your next level of support.
System log entry only, no service action required
The IOP in the slot used for the last successful IPL of the operating system was replaced with an I/O Adapter. The IPL will continue by searching for a valid load source device. Check the LPAR configuration if required, and ensure that the tagged I/O for the partition is correct.
System log entry only, no service action required
The I/O Adapter in the slot used for the last successful IPL of the operating system was replaced with an I/O Processor. The IPL will continue by searching for a valid load source device. Check the LPAR configuration if required, and ensure that the tagged I/O for the partition is correct.
System log entry only, no service action required
The I/O Adapter in the slot used for the last successful IPL of the operating system was removed. The IPL will continue by searching for a valid load source device. Check the LPAR configuration if required, and ensure that the tagged I/O for the partition is correct.
System log entry only, no service action required
The I/O Processor in the slot used for the last successful IPL of the operating system was removed. The IPL will continue by searching for a valid load source device. Check the LPAR configuration if required, and ensure that the tagged I/O for the partition is correct.
System log entry only, no service action required
The virtual adapter type specified is invalid. The IPL will attempt to continue. Check the LPAR configuration, if required, and ensure that the virtual adapter type selected for this partition is valid.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This error indicates a failure during a search for the load source. There may be a number of these failures prior to finding a good load source. This is normal. Look for SRCs in the Serviceable Event View logged at the time the partition was performing an IPL. If a B2xx3110 error is logged, a B2xx3200 may be posted to the control panel. Work the B2xx3110 error in the Serviceable Event View. If the system IPL hangs at B2xx3200 and you cannot check the SRC history, perform the actions indicated for the B2xx3110 SRC.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This error indicates a failure during a search for the load source. It is usual for a number of these failures to occur prior to finding a valid load source. This is normal. Look for SRCs in the Serviceable Event View logged at the time the partition was performing an IPL. If a B2xx3110 error is logged, a B2xx3200 may be posted to the control panel. Work the B2xx3110 error in the Serviceable Event View. If the system IPL hangs at B2xx3200 and you cannot check the SRC history, perform the actions indicated for the B2xx3110 SRC. If there are other SRCs in the Serviceable Event View, then work those errors. If this SRC is posted on the control panel and there are no other SRCs listed in the Serviceable Event View, then perform [LIC]LICIP15[/LIC].
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A failure occurred. Critical resources could not be provided for this operation. The IPL is terminated. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There is not enough space to contain the partition main storage dump. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was a partition main storage dump problem. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There is not enough space to contain the partition main storage dump. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was an error reading the partition's main storage dump from the partition's load source into main storage.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A partition main storage dump has occurred but cannot be written to the load source device because a valid dump already exists. Use the Main Storage Dump Manager to rename or copy the current main storage dump.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was an error writing the partition's main storage dump to the partition's load source.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The partition ID is in extended word one as LP=xxx in decimal format. An error occurred when writing the partition's main storage dump to the partition's load source. No service action required.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The partition ID is in extended word one as LP=xxx in decimal format. An error occurred when writing the partition's main storage dump to the partition's load source. No service action required.
Timeout occurred during a main store dump IPL
There was not enough memory available for the dump to complete before the timeout occurred. The partition is currently in a failed state. Retry the MSD IPL, or else power on the partition normally.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was an error writing the partition's main storage dump to the partition's load source.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was an error writing the partition's main storage dump to the partition's load source.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was an error writing the partition's main storage dump to the partition's load source.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An error occurred while doing a main storage dump that would have caused another main storage dump. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An error occurred while doing a Firmware Assisted Dump that would have caused another Firmware Assisted Dump. Contact your next level of support.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a copy error. Contact your next level of support.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a read error. Contact your next level of support.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a copy error. Contact your next level of support.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a copy error. Contact your next level of support.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a copy error. Contact your next level of Support.
System log entry only, no service action required
A problem occurred during a partition Firmware Assisted Dump. The dump completed successfully but register information might be missing. The partition ID is in extended word one as LP=xxx in decimal format.
A problem occurred during a partition Firmware Assisted Dump
The partition ID is in extended word one as LP=xxx in decimal format. A Firmware Assisted Dump did not complete due to a copy error. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A platform LIC error occurred when the partition's memory initialized. The IPL will not continue. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition could not reserve the memory required for IPL. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The partition's LID failed to completely load into the partition's mainstore area. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The load source media is corrupted or not valid.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. This is a problem with the load source media being corrupt or not valid.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A failure occurred when allocating memory for an internal object used for LID load operations. Ensure the partition was allocated enough main storage, verify that no memory leaks are present, and then retry the operation.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. Error on load source device.
A problem occurred during the IPL of a partition.
An error occurred while copying Open Firmware into the partition load area. Contact your next level of support.
System log entry only, no service action required
The partition ID is in extended word one as LP=xxx in decimal format. An error condition was encountered when communicating with the load source I/O Processor for the partition identified in the xx field of the B2xx SRC. This informational error indicates a failure resetting the I/O Processor in the preceding B2xx3200 error. This may be normal. If there is a hardware failure there will be a different serviceable event. If the system IPL hangs at B2xx7200 and you cannot check the SRC history, perform the actions indicated for the B2xx3110 SRC.
System log entry only, no service action required
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An internal LIC timeout has occurred. The partition may continue to IPL but it may experience problems while running.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was a failure loading the VPD areas of the partition. Possible causes are:
If the problem is due to media, replace the load source media. If the problem is due to insufficient resources, allocate enough resources to the partition. If the problem is due to unsupported partition configuration, correct the partition configuration.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The IPL is terminated. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was a problem getting a segment of main storage in the platform's main store.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A failure occurred. The IPL is terminated. Ensure that there is enough memory to IPL the partition.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. Contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A failure occurred. The IPL is terminated.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A problem occurred on the path to the load source for the partition. There was an error mapping memory for the partition's IPL. Call your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. A problem occurred on the path to the load source for the partition. There was a failure verifying VPD for the partition's resources during IPL. Call your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. There was a low level partition to partition communication failure.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
Partition did not IPL due to platform Licensed Internal Code error. Contact your next level of support.
A problem occurred during the IPL of a partition.
A problem occurred associating the partition terminal to the console serial port. This association is only attempted when in Manufacturing Default Configuration (MDC) mode. There may be a service processor problem. Check for firmware updates and install them. If there are no firmware updates available, look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. If that does not resolve the problem, contact your next level of support.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without the VPD information for a slot. The partition ID is in extended word one as LP=xxx in decimal format. An error occurred while retrieving a location code.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without retrieving location code information for a slot or a bus. The partition ID is in extended word one as LP=xxx in decimal format. An error occurred while retrieving a location code.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without retrieving the port location labels for an embedded slot. The partition ID is in extended word one as LP=xxx in decimal format.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without all available slot information. The partition ID is in extended word one as LP=xxx in decimal format.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without all available processor information. The partition ID is in extended word one as LP=xxx in decimal format.
System log entry only, no service action required
A problem occurred during the IPL of a partition. The IPL continued without all available physical I/O information. The partition ID is in extended word one as LP=xxx in decimal format.
Platform LIC detected an error
The partition ID is in extended word one as LP=xxx in decimal format. A platform Licensed Internal Code error occurred. Perform a platform dump and contact your next level of support.
Platform LIC detected an error
The partition ID is in extended word one as LP=xxx in decimal format. A platform Licensed Internal Code error occurred. The partition assigned resources beyond its maximum capacity. Use HMC, IVM or ASMI to increase the Logical Memory Block (LMB) size and/or use HMC or IVM to reduce the number of virtual devices for the partition.
No active system processors
Contact your next level of support.
A problem occurred during the migration of a partition
Contact your next level of support.
A problem occurred during the migration of a partition
Contact your next level of support.
A problem occurred after a partition ended abnormally.
The partition ID is in extended word one as LP=xxx in decimal format. This partition could not stay running and shut itself down. Work any error logs in the Serviceable Event View. If there are no errors, contact your next level of support.
A problem occurred after a partition ended abnormally.
The partition ID is in extended word one as LP=xxx in decimal format. This partition could not stay running and shut itself down. Work any error logs in the Serviceable Event View. If there are no errors, contact your next level of support.
A partition terminated due to a bad processor
A lower priority partition lost a usable processor to supply it to a higher priority partition with a bad processor. The partition ID is in extended word one as LP=xxx in decimal format. If the partition is an IBM i Operating System partition, main store will be saved to disk. The partition will be powered off after the process is completed. For all other partition types, the partition will power off immediately. Evaluate the entire LPAR configuration. Adjust partition profiles with the new number of processors available in the system.
System log entry only, no service action required
A problem occurred after a partition ended abnormally.
The partition ID is in extended word one as LP=xxx in decimal format. There was a communications problem between this partition's service processor and the platform's service processor. The platform will need to be re-IPLed before that partition can be used. Call your next level of support.
A problem occurred during a power off a partition
Internal platform Licensed Internal Code error occurred during partition shutdown or re-IPL. Contact your next level of support.
A problem occurred after a partition ended abnormally.
The partition ID is in extended word one as LP=xxx in decimal format. There was a communications problem between this partition and code that handles resource allocation. Call your next level of support.
A problem occurred during a power off a partition
During the partition IPL, the partition terminal was associated to the console serial port. During partition shutdown, the unassociation of the partition terminal to the console serial port failed. There may be a service processor problem. Check for firmware updates and install them. If there are no firmware updates available, look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. If that does not resolve the problem, contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. An operation has timed out. Ignore this error if there are other serviceable errors. Work those error logs for this partition and for the platform from the Serviceable Event View. If there are no errors, contact your next level of support.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. Partition processors did not start LIC within the timeout window. Capture a Partition Dump and call your next level of support.
System log entry only, no service action required
A system request to power off a partition failed. The partition ID is in extended word one as LP=xxx in decimal format. The partition did not respond to a system request to power off the partition. This partition had a communications problem. If the partition is an IBM i Operating System partition, capture a Partition Dump. Contact your next level of support.
System log entry only, no service action required
The partition ID is in extended word one as LP=xxx in decimal format. The partition did not respond to a system request to power off the partition.
A problem occurred during the IPL of a partition.
The partition ID is in extended word one as LP=xxx in decimal format. The code load operation for the partition's IPL timed out. Work any error logs for this partition in the Serviceable Event View. If there are no errors, contact your next level of support.
A problem occurred during a power off a partition
The partition ID is in extended word one as LP=xxx in decimal format. A problem occurred on the path to the load source for the partition. A timeout occurred during the process of trying to stop a partition from running. Contact your next level of support.
A problem occurred during the IPL of a partition.
During an IPL, a timeout occurred while waiting for a ready message from the partition. Look for other errors. Re-IPL the partition to recover.
System log entry only, no service action required
During an IPL, a timeout occurred while waiting for a response to a message. Look for other errors. Re-IPL the partition to recover.
System log entry only, no service action required
During an IPL, a timeout occurred while waiting for a response to a message. Look for other errors. If this SRC is displayed in the operator panel, then panel function 34 might be used to retry the current IPL while the partition is still in the failed state.
System log entry only, no service action required
During an IPL, a timeout occurred while waiting for a response to a message. Look for other errors. If this SRC is displayed in the operator panel, then panel function 34 might be used to retry the current IPL while the partition is still in the failed state.
System log entry only, no service action required
During an IPL, a timeout occurred while waiting for a response to a message. Look for other errors. If this SRC is displayed in the operator panel, then panel function 34 might be used to retry the current IPL while the partition is still in the failed state.
Timeout occurred during a main store dump IPL
If this SRC is displayed in the operator panel during a main store dump IPL, then panel function 34 might be used to retry the current main store dump IPL while the partition is in the failed state.
These error codes indicate a problem in the connection monitoring between the Hardware Management Console and a partition that is running on the managed system.
The HMC posts these error codes into the error log in Service Focal Point but does not report them to the operating systems running on the managed system.
Hardware Management Console (HMC) or partition connection monitoring fault
HMC or partition connection monitoring fault
Perform the following steps:
Hardware Management Console (HMC) or partition connection monitoring fault
HMC or partition connection monitoring fault
Before using the entry in the FRU List, do the following:
Hardware Management Console (HMC) or partition connection monitoring fault
Before using the entry in the Failing Items column, do the following:
The communication link between the service processor and the Hardware Management Console (HMC) failed.
A single partition HMC link failed.
Perform FSPSP33
Multiple partition HMC links failed.
Perform FSPSP33 .
All partition links for a single system to HMC failed.
Perform FSPSP33 .
All system links from one system to a single HMC failed.
Perform FSPSP33 .
The links between a single HMC and a single managed system failed.
Perform FSPSP33 .
A single HMC link to more than one managed system occurred.
Perform FSPSP33 .
One HMC link to another single HMC failed.
Perform FSPSP33 .
One HMC link to more than one HMC occurred.
Perform FSPSP33 .
The HMC lost links to all managed systems.
Perform FSPSP33 .
Multiple HMCs lost links to a single managed system.
Perform FSPSP33 .
Multiple HMCs lost links to multiple managed systems.
Perform FSPSP33 .
Multiple HMCs lost links to multiple managed systems.
Perform FSPSP33 .
The Network Interface Card (NIC) failed.
Use the error codes offered in the HMC Focal Point to diagnose and repair the problem. For more information, see Using Service Focal Point .
A single partition HMC link failure occurred on a redundant path.
Perform FSPSP33 .
A single HMC link to one HMC failure occurred on a redundant path.
Server firmware connection monitoring to the flexible service processor failed.
Perform FSPSP33 .
Flexible service processor connection monitoring of server firmware failed
Perform FSPSP33 .
The communication path (mailbox) between server firmware and the flexible service processor failed.
Perform FSPSP33 .
Customer reported a console problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a power problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a processor problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a LAN problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a software problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer tested problem reporting by creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a power problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a processor problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a LAN problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a software problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer reported a problem when creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
Customer tested problem reporting by creating a serviceable event on the HMC user interface.
Contact the customer for more information about the problem.
The HMC failed to retrieve a dump from a managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem.
After receiving this error, perform the following steps:
The HMC failed to retrieve a platform system dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem.
After receiving this error, perform the following steps:
The HMC failed to retrieve a dump from the service processor. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem.
After receiving this error, perform the following steps:
The HMC failed to retrieve a power subsystem dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem.
After receiving this error, perform the following steps:
Primary HMC arbitration failure for domain {0} with peers {1}.
After receiving this error, perform the following steps: This error code indicates that this HMC did receive primary information from a peer HMC. To resolve this issue ensure that there is connectivity to the service processor and the other HMC connected to the managed system.
Primary HMC arbitration failure for domain {0} with peers {1}.
After receiving this error, perform the following steps: This error code indicates that this HMC could not communicate with the service processor to either set itself as a primary or to determine if other HMCs are connected. To resolve this issue ensure that there is connectivity to the service processor and the other HMC connected to the managed system.
The DVD RW drive or disk has failed.
Ethernet network failure
Do the following:
Ethernet network failure
Do the following:
Operating system status code
This reference code is for information only. It is shown in the Product activity log as a side effect of a condition that was detected by LIC. Normally, no action should be taken as a result of information reference codes. However, to isolate the root cause, use these suggestions:
A machine check occurred during IPL
Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9 before attempting to IPL again and report the problem to your Software Service Provider.
Terminate Immediate reference code is bad
More than one request to terminate the system was issued
Main storage dump must be copied for service
The server detected an unrecoverable machine check condition. Collect all the words of the SRC and the main store dump and send to your system manufacturer for analysis.
An unrecoverable memory error occurred
Re-IPL the partition that terminated. Then, look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View that indicate the replacement of memory in the failing item list. If there are no B1xxxxxx SRCs in the Serviceable Event View that indicate a memory problem, perform a slow boot by using Performing a slow boot in order to run diagnostics on the memory. Then, look for and correct erros with SRCs of the form B1xxxxxx in the Serviceable Event View.
Unrecoverable read error
Restore the Licensed Internal Code using Utilities to install and restore IBM i Licensed Internal Code.
The system ASP has run out of disk storage
The out of storage condition in the system ASP can be caused by an allocation failure in some other system software. This could be a looping condition that continues to allocate storage. Contact your service representative for assistance with the Main Storage Dump.
Disk sanitize action completed successfully
No service action required. This entry is logged for information only.
Disk sanitize action did not complete successfully
Provide the Product Activity Log entry to your next level of support for analysis.
Contact was lost with the device indicated
Do not power off the system. Perform the procedure indicated in the failing item list.
Contact was lost with the device indicated
Do not power off the system. Perform the procedure indicated in the failing item list.
Contact was lost with the device indicated
Do not power off the system. Perform the procedure indicated in the failing item list.
Component specific exception handler return code not valid
Exception while storage management lock is held
LIC exception code detected a problem
Component Specific Exception Handler recursion is detected in an IBM i Operating System process.
LIC exception code detected a problem
Component Specific Exception Handler recursion is detected in an IBM i Operating System process.
Code resumed to not valid address following exception
A machine check occurred during authority initialization
Unhandled exception during IPL or install
Unhandled exception in authority recovery
Unhandled exception in data base recovery
Unhandled exception in data base initialization
Unhandled exception in journal synchronization
Unhandled exception in commit initialization
Install of operating system failed on read from media
The information loaded from the install media is not valid
The information loaded from the install media is not valid
The information loaded from the install media is not valid
Bad return code creating a queue or message
Attempt to destroy a task with critical flag on
Maximum stack size exceeded in process or task
Resource management segment could not be created or extended
A main store dump was initiated. Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9. Perform a system IPL and collect the Product activity log and main store dump and provide them along with the recorded SRC information to IBM Service Support. The problem may also be that there is not enough auxiliary storage.
Invalid LID directory detected
During system IPL, the LIDMgr detected an I/O failure or media failure while trying to read the LID directory.
LID directory unusable
During system IPL, the LIDMgr detected that the LID directory and associated load source is not usable. Reinstall the Licensed Internal Code by using Utilities to install and restore IBM i Licensed Internal Code. For more information, contact IBM Service Support.
The LinkLoader has found its bad flag ON
This reference code is usually the result of a system termination while the LinkLoader is performing its work. Reinstall the Licensed Internal Code by using Utilities to install and restore IBM i Licensed Internal Code.
Unable to perform programmed IPL
The LinkLoader was not successful in performing a programmed IPL. Perform a system IPL. If the problem persists, examine the main storage dump and determine the reason for the failure of the programmed IPL.
The LinkLoader was not able to allocate a segment
Perform the D mode IPL again. If the problem persists, there might be a memory problem. Contact your next level of support.
The LinkLoader was not able to load a critical LID
Perform the D mode IPL again. If the problem persists, contact your next level of support.
Enqueuing a task to the TDQ which is already enqueued on TDQ
MISR not readable; must be readable for Normal Mode install
MISR is not readable. Perform a manual install to reinitialize the system.
Failure reading media or not install media
Determine that correct install media is loaded. If correct install media is installed, media could be corrupt. Obtain another copy of the install media and reattempt the install. If the install still fails, contact your service representative.
Critical database segment could not be created
Not able to create APPN task
An error occurred during task creation which requires a power off of the system.
An attempt to create a segment failed
The create could fail for two reasons:
An IPL is needed to restore system performance
Licensed Internal Code has detected a condition that is impacting system performance. System operation can continue, but system performance may be noticeably reduced until the next IPL. Look at the Product Activity Log entry, and find the value at offset x'000180'. If the value equals x'00000122', the error was caused by too much processor memory being installed. For more information, contact IBM Service Support.
LPAR service function directed a Main Storage Dump.
Copy the current main storage dump to media. For more information on how to copy a Main Storage Dump, refer to Copying a main storage dump.
Installation of LIC failed
Words 12 and 13 of this SRC contain additional diagnostic information. Install LIC using physical media. To determine what caused the failure, collect SRC information and contact your next level of support.
Installation of LIC failed
A main store dump was initiated. Words 12 and 13 of this SRC contain additional diagnostic information. To recover the partition using the previously installed LIC, perform a B-mode IPL. You can then re-try the installation of LIC. Otherwise, install LIC using physical media. To determine what caused this failure, collect SRC information and main store dump and contact your next level of support.
Missing DASD units.
Copy the current main storage dump to media. For more information on how to perform a Main Storage Dump, refer to Copying a main storage dump.
Missing DASD units.
Copy the current main storage dump to media. Then exit the Main Storage Dump Manager. For more information on how to perform a Main Storage Dump, refer to Copying a main storage dump.
Storage Management failed to reach full paging.
Copy the current main storage dump to media. For more information on how to perform a Main Storage Dump, refer to Copying a main storage dump.
Auto copy failed or not attempted.
Copy the current main storage dump. If copying to system ASP, existing copies may need to be deleted or renamed. Then exit the Main Storage Dump Manager. For more information on how to perform a Main Storage Dump, refer to Copying a main storage dump.
System ASP threshold exceeded after auto copy done.
Delete other system ASP copies or exit the Main Storage Dump Manager and then from DST copy the Auto Copy to media and then delete the Auto Copy in system ASP.
MSD Manager not configured to save dump information
The platform produced dump data, but the Main Storage Dump (MSD) Manager was not configured to automatically copy the dump to an Auxiliary Storage Pool (ASP). The dump will be lost if the system power is lost. Use MSD Manager to manually copy the current platform dump to media or an ASP.
Insufficient space in the ASP to store a platform dump
The platform produced dump data, and the Main Storage Dump (MSD) Manager was configured to automatically copy the dump to an Auxiliary Storage Pool (ASP), but there was not sufficient free space available in the ASP. The dump will be lost if the system power is lost. Manually copy the current platform dump from the platform by performing one of the following:
A platform dump is saved in MSD Manager
The platform produced dump data. The dump data was copied to the Main Storage Dump (MSD) Manager.
Processor On Demand error detected.
Processor on Demand Data Block key is not valid. Replace the Processor Capacity card.
Processor On Demand error detected.
Processor On Demand Data Block contains data that does not match the expected data. Contact your service provider.
Processor On Demand error detected.
Processor On Demand Serialization has failed during IPL. Contact your service provider.
Processor On Demand error detected.
SPCN communication failure during Processor On Demand. Look in the Product Activity Log for other SPCN errors and perform the actions indicated for those errors.
Processor On Demand error detected.
Correct any Processor Capacity card or SPCN failures.
Incorrect Processor Capacity Card installed.
The Processor Capacity Card is the failing item since it has been swapped in from a different system. Put the Processor Capacity Card back in the system it came from, and reinstall this system's original Processor Capacity Card.
The CUoD data is not present. A problem may exist.
The Processor Capacity Card was changed and there may be a problem. If the system did have any activated standby processors before the Processor Capacity Card was replaced, then new processor on demand activation codes must be obtained to restore the previous activations. Contact your service provider.
Processor On Demand error detected.
Correct any Processor Capacity card or SPCN failures.
Processor On Demand error detected.
Processor On Demand standby processors are in use. Contact your service provider.
Processor On Demand error detected.
The Processor On Demand Trial Activation period is not valid. Contact your next level of support.
Processor On Demand error detected.
Contact your service provider.
Processor On Demand error detected.
The Processor On Demand Activation code just entered is not valid. Contact your next level of support.
Processor On Demand error detected.
An invalid Processor On Demand Activation code has been entered more than 5 consecutive times. Contact your service provider.
Processor Capacity card replaced on activated POD system.
Contact IBM Support to order a replacement Processor On Demand activation code.
1 hour left in POD 14 day Trial Activation Period.
If a new activation code was purchased, it should be entered now. Otherwise, the system will revert back to its previous activation state at the end of the Trial Activation Period.
DST received no response from a work station controller
The workstation I/O processor for the system or partition console did not respond.
DST problem attempting to use the system console
A code problem occurred during an attempt to use the system console.
Service program failed
The ASCII system console failed to respond.
DST console failed to respond
The system console failed to respond.
Service program failed
The workstation adapter system console failed to respond.
Service program failed
The workstation adapter console failed to respond.
DST lost contact with the console
A service program lost contact with the system console.
IPL service function ended abnormally
A service program lost contact with the system console.
System startup failed in unattended IPL mode
Perform the following:
System is in DASD migration mode
Install Licensed Internal Code and Upgrade Load Source was specified but the key is not in the manual position. Change the key position to manual and perform a system IPL.
IASP detected a failure during the vary on operation
System LIC detected a program exception
System LIC detected a programming problem. If performance or other system degradation is occurring, the system may be operating with reduced resources. Check the Product activity log for related entries. If this reference code is logged with an error class of Informational, then no action is required. Otherwise, perform the procedure indicated in the failing item list.
LIC program exception occurred
System LIC detected a programming problem for which a main storage dump may have been initiated. A problem log entry may be generated for this ref code.
LIC program exception occurred
System LIC detected an IOP programming problem for which an IOP dump may have been initiated.
LIC program exception occurred
System LIC detected an interface problem with the IOP or an IOP programming problem for which an IOP and main storage dump may have been initiated.
Addressed device failed to respond to selection
IOP timed out a disk command
An IOP dump was initiated
Copy the IOP dump entry and any related entries from the Product Activity Log to suitable media, and give to an IBM service representative.
LIC program exception occurred
The system was in a D IPL mode when the problem was detected. A main storage dump was not taken.
Insufficient entitled memory for the I/O configuration
Use the HMC or IVM to increase the entitled memory capacity of the partition and restart the I/O adapter. To restart a storage I/O adapter, use Hardware Service Manager to re-IPL the virtual I/O processor that is associated with this I/O adapter. To restart a communications I/O adapter, vary the line off and vary it on using the vary configuration (VRYCFG) command.
Virtual adapter not supported in a shared memory partition
Use the HMC or IVM to remove the virtual adapter from the partition.
Insufficient entitled memory for the I/O configuration
Use the HMC or IVM to increase the entitled memory capacity of the partition and restart the partition.
System LIC detected a missing IOP LIC code load
System LIC detected a missing IOP LIC code load during IPL of the IOP. This indicates that either the IOP code load is not installed on the system load source device or that system LIC was unable to successfully read that load from the load source device.
System LIC detected an IOP timeout during IOP IPL
Verify that all IOP cable connections are secure, and check tape and other non-disk devices and media to verify that they are in a ready state.
LIC program exception occurred
An IOP signalled to system LIC that it had entered a critical internal state. LIC automatically attempted to restart the IOP. This reference code is logged for information only. No action is required.
The system issued a reset/reload to the IOP.
System Licensed Internal Code detected that an IOP Reset/Reload has occurred, and that the IOP successfully recovered. Users who were signed on to a Workstation device under the IOP will need to sign back on. Any LAN/WAN communications lines under the IOP will need to be restarted. Tape/Optical devices under the IOP may need to be varied back on. To determine the cause of the IOP Reset/Reload, check the Product Activity Log for additional entries logged with the same System Log ID, and perform any actions indicated for those errors.
IOP Reset was issued
LIC has detected a problem with the Service Processor IOP and has reset it but has not initiated reload of the Service Processor. If the load source is mirrored, some system operations may be able to continue normally. However, some system service operations have been suspended and the system should be scheduled for power down as soon as possible.
LIC program exception occurred
System LIC detected a logical partition configuration data consistency error. Copy the Product Activity Log data for this error and any related entries and contact your next level of hardware service support.
LIC program exception occurred
LPAR configuration data does not match current system configuration. The system will not IPL past DST until the problem is corrected. Following is a list of problems which may have caused this SRC to be reported:
LIC program exception occurred
LPAR configuration data informational error. The LPAR configuration data was found to be or inconsistent on a secondary partition's load source. The data was automatically updated to the current system level.
LIC program exception occurred
LPAR configuration data informational error. The LPAR configuration data was found to be inconsistent on a primary partition and could only be corrected with an older copy of the data.
Secondary partition not running at optimum.
Check the Primary partition's Product Activity Log for system processor entries from approximately the same time. Perform the actions indicated for those entries.
Secondary partition not running at optimum.
Check the primary partition Product Activity Log for system memory entries from approximately the same time. Perform the actions indicated for those entries.
Secondary partition not running at optimum.
Check the Primary partition's Product Activity Log for system processor entries from approximately the same time. Perform the actions indicated for those entries.
Secondary partition not running at optimum.
Check the Primary partition's Product Activity Log for system memory errors from approximately the same time. Perform the actions indicated for those entries.
Secondary partition not running at optimum.
The interactive performance specified in the configuration data for this partition could not be met. Contact your next level of support.
Secondary partition software release not supported
The logical partition software version is outside the supported release delta. Check the Release Delta from the Primary partition "Display Partition Release Level" screen. Check the LPAR documentation for the release level of the Primary partition and determine what the supported Release Delta is.
LIC program exception occurred
Record the Product Activity Log (PAL) hex data for this SRC or print the PAL entry. Contact your next level of support.
LIC program exception occurred
Record the Product Activity Log (PAL) hex data for this SRC or print the PAL entry. Contact your next level of support.
The copying of DASD log data to the IOP log was successful
IOP log data can be copied to a spool file for examination by the development lab.
SLIC I/O DASD subsystem error recovery in progress.
Unrecoverable read error
VPD data could not be read. Look for other errors implicating hardware. There is no way to know what VPD read has failed, but the resource is not useable and should generate an error. If no such error occurred, call your next level of support.
System bus error
Contact your next level of support.
Bus Expansion Adapter card failed
Contact your next level of support.
Bus Expansion Adapter card failed
Contact your next level of support.
Optical bus failed
Contact your next level of support.
High Speed Link (HSL) I/O bridge failure
LIC could not access part of the HSL I/O bridge VPD. The bridge and HSL loop may be prevented from becoming operational. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log (SAL) or serviceable event view on the HMC is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) I/O bridge failure
LIC detected invalid data in the HSL I/O bridge VPD. The bridge and HSL loop may not have become operational. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log (SAL) or serviceable event view on the HMC, is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) I/O bridge failure
LIC data in the I/O bus vpd could not be accessed. The I/O Bus identified in the SRC may not have become operational. If there is a B6xx 6906 reference code, close this problem in the serviceable event view you are working with and work the 6906 error. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log or serviceable event view on the HMC or service processor is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) I/O bridge failure
LIC detected invalid data in the I/O bus VPD. The bus and resources associated with it may not be operational. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log (SAL) or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed. If the serviceable event view only indicated a frame or enclosure see the locations section for the frame or enclosure type. The location of the HSL I/O Bridge will be given in the locations tables. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
I/O processor failure
An I/O processor timed out, returned bad status, or is not following the system bus protocol.
Not valid system configuration detected
This system model does not allow a configuration of more than three (non-OptiConnect) I/O Processors. Power down the system and remove the extra (non-OptiConnect) I/O Processor(s) so that there are three or less. Restart the system.
Missing or failed I/O processor cards
A system bus appears to be empty. If the bus is not empty, two I/O processors in consecutive slots may be missing or broken. If there are broken I/O processors, then another more serious SRC has occurred. Otherwise find the bus number for this failure from the Product activity log and use the system configuration list to verify the configuration of the I/O processors on that bus.
Multi-adapter bridge card slot error, do not use card slot
Slot unavailable due to 64 bit card in adjacent slot. One of the messages documented with the symbolic FRU will describe the problem. See the SLOTERR symbolic FRU for a list of messages and corrective actions.
Multi-adapter bridge card slot error, do not use card slot
LED control failure, do not use slot. The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code. See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log or a serviceable event viewer on the HMC is available for this problem then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.
Multi-adapter bridge card slot error, do not use card slot
Power control failure, do not use slot. If there is a Linux partition in the system, any IOPs plugged into slots owned by a Linux partition will not power on. This error will be logged. Correct the situation by removing the IOP cards. The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code. See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log, or serviceable event view on the HMC is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.
Multi-adapter bridge card slot error, do not use card slot
Power control failure, do not use slot. The card location is not available for use. The Failing Item with the card slot error is in the Failing Item list for this reference code. See the SLOTERR symbolic FRU for the list of messages and a further description of the problem detected by Licensed Internal Code. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code. If serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.
Multi-adapter bridge configuration change or error
One of several errors or configuration problems has occurred under a Multi-adapter bridge. If you are using the Service Action Log (SAL), or the serviceable event viewer on the HMC or the service processor, then the correct FRU, description and card position(s) will be listed. Use the FRUs and descriptions in the serviceable event view you are working with to determine the problem. If you do not have access to the Service Action Log, or serviceable event view on the HMC or service processor, then word 4 of the SRC has more information. Examine the last 4 digits in word 4 to determine the problem by comparing them to the list below and using the FRU(s) listed here.
See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Multi-adapter bridge configuration change or error
Card type not supported in this slot. An I/O processor or I/O adapter card type is installed in the location indicated in word 7 of the SRC. The card type is not supported in that slot under the multi-adapter bridge. The card is unavailable. See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Multi-adapter bridge configuration change or error
I/O processor removed from multi-adapter bridge card slot. On the previous IPL an I/O processor was in the card location specified in word 7 of the SRC. The I/O processor was not detected on this IPL. See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Multi-adapter bridge configuration change or error
I/O adapter unavailable due to moved I/O processor card. The I/O adapter specified in word 7 of the SRC is not available. On the previous IPL there was an I/O processor card the adapter was assigned to. The I/O processor was not detected on this IPL. See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Multi-adapter bridge configuration change or error
IOA removed from multi-adapter bridge slot. On the previous IPL an I/O adapter was in the card slot specified in word 7 of the SRC. That I/O adapter was not detected on this IPL. See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Multi-adapter bridge configuration change or error
I/O adapter replaced by I/O processor card. On the previous IPL there was an I/O adapter in the location specified in word 7 of the SRC. This IPL LIC detected that the IOA was replaced by an IOP in that location. See the MABRCFG symbolic FRU for the list of messages, a further description of the problem detected by Licensed Internal Code and the corrective action.
Card slot could not be validated
This can be caused by "PCI error injection policy" being set to "YES" and an I/O Processor being installed on the same Multi-adapter bridge domain as the I/O Adapter. Do one of the following: -- Using the HMC or a customer PC with a Web browser access the Advanced System Management Interface (ASMI) and disable PCI error injection policy. OR -- Vary off the I/O Adapter. Using Hardware Service manager in SST/DST, locate the I/O Adapter resource. Using concurrent maintenance on the associated packaging resource, remove the I/O Adapter and install it in a location that does not have I/O Processors on the same Multi-adapter bridge domain. OR -- Vary off the I/O Adapter. Use the concurrent maintenance option in Hardware Service Manager in SST/DST to power off all I/O Processors located on the same multi-adapter bridge domain as the I/O Adapter. Use concurrent maintenance to power off and power on the I/O Adapter. Then use concurrent maintenance to power on the I/O Processors located on the same multi-adapter bridge domain as the I/O Adapter.
High Speed Link (HSL) resource failure
A system PCI bus failure was detected. Word 7 of the SRC contains the bus number. This failure can occur when a tower in an HSL loop is powered off using concurrent maintenance. If this is the case, close this problem. This error is most likely in the hardware that makes up the PCI bus, the PCI bus side of the HSL I/O bridge or the multi-adapter bridge. In some cases it may be caused by a failing IOP in the multi-adapter bridge's domain. When an IOP is causing the problem, the failing IOP cannot be identified. NOTE: This SRC can occur for the PCI bus resource on a PCI bus in an I/O expansion unit when the unit is powered off for a concurrent maintenance action. If the Service Action Log, or serviceable event view on the HMC or service processor, is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) resource failure
A failure occurred in a multi-adapter bridge or on the bus to the card location it controls. If a serviceable event view is available, use the failing item list presented there for servicing this reference code. If a serviceable event view is not available, use the failing item list documented here.
High Speed Link (HSL) resource failure
Multi-adapter Bridge (MaB) failure detected. For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event viewer you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log (SAL) or serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code. If a serviceable event view is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.
High Speed Link (HSL) resource failure
Multi-adapter Bridge has detected a problem in the card installed in the location specified in word 7 of the SRC. Use the FRU list in the Service Action Log (SAL), or serviceable event view you are working with. If you are working from this document's FRU list use the Symbolic FRU BRDGSET to determine the failing items.
Multi-adapter bridge configuration change or error
PCI I/O processor rejected the assignment of or the removal of an I/O adapter.
The system issued a reset/reload to the service processor.
Service processor error.
Service processor failure.
For this reference code the failing item list presented in the Service Action Log (SAL), or serviceable event view you are working with, can be different from the failing item list documented here. That is due to the differences in system models and features installed. If the Service Action Log (SAL) or a serviceable event viewer on the HMC is available then use the failing item list presented there for servicing this reference code. If a serviceable event viewer is not available then use the failing item list documented here. By following the procedures in the symbolic FRUs listed here you will isolate to the correct FRU list based on system model and features installed.
Network Interface Controller (NIC) failure
The FRU list displayed in the Service Action Log (SAL) or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) I/O bridge failure
Cycle power on the frame identified as the frame with failed HSL I/O Bridge prior to replacing FRUs. The FRU list displayed in the Service Action Log (SAL), or serviceable event view you are using, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you. If you find either a B6xx 6982 or B6xx 6984 SRC logged at approximately the same time as this SRC then they were caused by the same failure. If you find a 6982 SRC logged at approximately the same time then close this problem and service the 6982 SRC. The failing item listed for this SRC is one of the failing items listed for B6xx 6982. If the serviceable event view's entry for this SRC has a location listed then record the location for use in servicing the 6982 SRC. NOTE: This SRC can occur for the HSL I/O Bridge resource in an I/O expansion unit when the unit is powered off for a concurrent maintenance action. NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
High Speed Link (HSL) connection failure
If this SRC is not in the Service Action Log (SAL) or serviceable event view you are using, then it is informational or statistical only. It does not require a service action. Otherwise, this is a connection failure on an HSL link. Perform the procedure indicated in the failing item list.
An invalid High Speed Link (HSL) configuration was detected
An HSL loop has an invalid configuration. Word 4 of the SRC contains the program return code (PRC) which identifies the problem with the loop's configuration. Use the PRC and the FRU listed to determine the problem. If you are using the Service Action Log (SAL) or serviceable event view you are working with, the FRU description may already indicate the configuration problem.
High Speed Link (HSL) loop status message
An HSL loop has switched to its alternate path. This is an informational SRC only. Word 7 of the SRC contains the loop number in the leftmost 4 digits. The loop number is in hexadecimal format. You must convert the hexadecimal loop number into decimal format to recognize the loop number in HSM. This SRC can be caused by a tower on the HSL loop powering off. This SRC may also appear in the Service Action Log (SAL), or serviceable event viewer you are using, with a B6xx 6982 or B6xx 6981 logged at approximately the same time. In that case the other SRC is reporting a failure and this SRC is reporting that the alternate HSL path is now being used. Service the other SRC if present.
High Speed Link (HSL) loop status message
If this SRC is not in the Service Action Log (SAL), or serviceable event view you are using, then it is informational. Use FRU SIRSTAT to determine what this SRC means. Otherwise, continue with the following steps: This error can appear as a serviceable event when a tower, or I/O unit or another system in the loop did not complete powering on before LIC on this system checked this loop for errors. Search the Product Activity Log (PAL) for the last B6xx 6985 SRC logged for this loop and use FRU SIRSTAT to determine if this error requires service. If the last entry indicates the loop is functioning (determined by FRU SIRSTAT) then no service action is required, close this problem There may be multiple B6xx 6985 logs with xxxx 3205 in word 4 errors for the same loop resource in the serviceable event view. This is caused by retry and recovery attempts. If there is a B6xx 6985 with xxxx 3206 or xxxx 3208 in word 4 after the above B6xx 6985 entries in the PAL, then the recovery efforts were successful. If this is the case, close all the B6xx 6985 entries for that loop resource in the serviceable event view.
NOTE: A fiber optic cleaning kit may be required for optical HSL connections.
System bus error
During IPL, system LIC detected an HSL I/O bridge that was already initialized. The bridge should have been in a flushed and unintialized state after powering on. There is a problem with SPCN components that prevented the tower from powering off after a previous power off was issued. The tower will not be configured for this IPL. This reference code is equivalent to 1xxx 90F0. When referring to the "CBLALL" symbolic FRU in the Failing Item list, perform the "CBLALL" procedure using reference code "90F0". Word 5 of the SRC identifies the frame. Determine the frame by breaking down word 5: Word 5 -> xxxx xxNN where: NN is the frame number in hexadecimal format.
High Speed Link (HSL) connection failure
Failures are occurring on the HSL link. There may be B6xx 6982 errors logged on the same loop and about the same time as this error. Close those errors and continue to correct the problem by working this error.
Service processor failure.
The FRU list displayed in the Service Action Log (SAL), or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.
Service processor failure.
A failure occurred with the service processor hardware or the service processor LIC. The FRU list displayed in the Service Action Log (SAL), or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.
Service processor failure.
The FRU list displayed in the Service Action Log (SAL) or serviceable event view you are working with, may vary from the failing item list given in this document. Use the FRU list in the serviceable event view if it is available to you.
Wrap plug is installed on Bus Expansion Adapter card
This reference code is for information only. It indicates the presence of a wrap plug on the local optical link card.
Informational bus reference code
This reference code is for information only and might include the following:
Bus hardware configuration problem
Contact your next level of support.
A failure occurred communicating with another LPAR or system participating in Opti-connect with this LPAR or system. Starting with IBM i release 7.1 this event will be logged in the Product Activity Log but it will not be in the Service Action Log or the Problem Log. This event normally occurs when the other LPAR or system is powered off. If both LPARs or systems are running and have no Opti-connect errors then this event is indicating a possible problem with Opti-connect.
Contact your next level of support if you suspect an Opti-connect problem. Otherwise this is a tracking event.
HSL Opticonnect normal connect to another sys. or partition.
This reference code is informational only. HSL OptiConnect has established connection normally. The local system or partition is participating in HSL Opticonnect with other systems or partitions on the same HSL loop.
HSL Opticonnect normal disconnect from other sys. or partitn
This reference code is informational only. HSL Opticonnect disconnected normally from a remote node. The local system or partition has stopped participating in HSL Opticonnect with the remote system or partition on the same HSL loop. Possible reasons include:
I/O processor failure
Contact your next level of support.
HSL Opticonnect abnormal disconnect from other sys. or prtn.
The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. The problem is most likely with the remote system or partition. Intervention at the remote system is most likely required. Examine both the local and remote HSL OptiConnected systems or partitions for problems on this HSL loop. Possible reasons include: A fatal error in software or hardware in the remote system or partition or a power failure in the remote system. If there was not a complete HSL loop before this error occurred then a failure or power down in an HSL component between the local system or partition and the remote system or partition could have caused this error. Check for a problem with: an HSL cable, HSL I/O bridge or a power problem in an expansion I/O tower or unit on this loop. Examine the Service Action Log (SAL), or serviceable event view you are using on the local system or partition for HSL failures on the same HSL loop at approximately the same time this error occurred. Examine the remote system or partition for problems. If the remote system or partition is powered on and IPL'd then examine the Service Action Log (SAL), or serviceable event view you are using, on the remote system or partition for problems on the same HSL loop at approximately the same time this error occurred. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers. When the remote system is IPL'd it will automatically reconnect with this system or partition. If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.
HSL Opticonnect abnormal disconnect from other sys. or prtn.
The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. LIC will attempt to recover from the error. Intervention at the local or remote system or partition may be required. Possible causes are: time out, hang or hardware failure. The problem may be with: the local system or partition or the remote system or partition. If there was not a complete HSL loop before this error then a failure or power down in an HSL component between the local system or partition and the remote system or partition could have caused this error. Check for SRCs with FRUs like: HSL cables, HSL I/O bridge or a power problem in an expansion I/O tower or unit on this loop. Examine the SAL or serviceable event view you are working with on the local system or partition for failures on the same loop, or with the Network Interface Controller at approximately the same time. Examine the remote system or partition for problems. Correct any HSL or NIC problems you find with the remote and local systems or partitions. If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log (PAL) information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.
HSL Opticonnect abnormal disconnect from other sys. or prtn.
The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. All of the HSL OptiConnect connections on this loop will be in a failed state. LIC will attempt to recover from the error. Intervention at the local or remote system or partition may be required. Possible causes are:
The problem may be with:
Examine the Service Action Log (SAL), or serviceable event view you are using, on the local system or partition for HSL failures on the same HSL loop, or with the Network Interface Controller at approximately the same time this error occurred. Examine the remote system or partition for problems. Examine the Service Action Log (SAL), or serviceable event view you are using, on the remote system or partition for problems on the same HSL loop or with the Network Interface Controller at approximately the same time this error occurred. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers. If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on all systems or partitions. Be sure to record all words in the SRCs. Contact your next level of support.
HSL Opticonnect abnormal disconnect from other sys. or prtn.
The local system or partition disconnected from a remote system or partition due to an failure in a LIC virtualized bus unit. LIC will attempt to recover from the error. Possible causes are:
Examine the Service Action Log (SAL), or serviceable event view you are using, on the local system or partition for HSL Opticonnect failures that occurred at approximately the same time this error occurred. Examine the remote system or partition for problems. Examine the Service Action Log (SAL), or the serviceable event view you are using, on the remote system or partition for HSL Opticonnect problems that occurred at approximately the same time this error occurred. Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support with the information you have collected.
HSL Opticonnect abnormal disconnect from other sys. or prtn.
LIC internal error. All systems participating in HSL OptiConnect will be disconnected. The system must be re-IPL'd to recover. Before re-IPL'ing the system initiate a main store dump. After getting the dump, examine the Service Action Log (SAL), or serviceable event view you are using, on the local system or partition for HSL Opticonnect failures that occurred at approximately the same time this error occurred. Examine the remote systems or partitions for problems. Examine the Service Action Log (SAL), or serviceable event view you are using, on the remote systems or partitions for HSL Opticonnect problems that occurred at approximately the same time this error occurred. Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support with the information you have collected.
Bus Expansion Adapter card failed
Contact your next level of support.
Bus Expansion Adapter failed
Contact your next level of support.
Host Ethernet Adapter (HEA) failure
Firmware detected a hardware failure in the Host Ethernet Adapter (HEA).
System log entry only, no service action required
LIC failure
A Licensed Internal Code error occurred. The partition will continue to run with this Host Ethernet Adapter (HEA) disabled. Perform a partition dump and then IPL the partition to recover the HEA. Send the partition dump to your next level of support.
The HEA is not connected to the Ethernet switch
The Host Ethernet Adapter (HEA) is not connected to the Ethernet switch. If the HEA connection is not needed, no service action is required. If the HEA connection is needed, verify that the cable is connected and the switch is powered on. After repairing the problem, verify that the connection has been restored.
The HEA connection to the Ethernet switch has been restored
System log entry only, no service action required.
HEA Media Interface Adapter Failure
Firmware detected a failure in the HEA Media Interface Adapter.
Bus Expansion Adapter card failed
Contact your next level of support.
Bus Expansion Adapter failed
Contact your next level of support.
Bus Expansion Adapter failed
Contact your next level of support.
Bus Expansion Adapter failed
Contact your next level of support.
TCP/IP informational error
This reference code is logged when the TCP/IP Attribute Log Protocol Errors is set, and the TCP/IP System LIC silently discards an inbound datagram. Silently discard is defined to mean discard the received datagram without reporting an error to the originating host device. Examples of such datagrams are those with checksums or destination addresses which are not valid. This reference code is for information only. Normally no action should be taken as a result of this reference code. It is generated in order to assist with remote device or TCP/IP network problem determination.
Statistics were logged, no service action required
This reference code is logged for information only.
APPN session initiation attempt has timed out
This reference code is used to indicate that LIC timed out on a request to initiate a session. The user must run problem analysis for this reference code. If this indicates a software problem, the user should dial IBM Software Support for assistance. The Problem Determination Procedure (PDP) will indicate whether the original timeout condition still exists and what the corrective actions should be.
APPN session initiation attempt has failed
This reference code is used to indicate that LIC attempted to satisfy a session initiation request, but some failure condition was detected by LIC. The failure condition could be a configuration or operational problem in the network. The user must run problem analysis for this reference code. If this indicates a software problem, the user should dial IBM Software Support for assistance. The Problem Determination Procedure (PDP) will indicate whether the original timeout condition still exists and what the corrective actions should be.
APPN CP-CP session ended.
A utility failure occurred
This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a utility failure.
Utility power restored
This reference code is for information only. The Uninterruptible Power System (UPS) is reporting that utility power has been restored.
A battery low condition was detected
This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a battery low condition.
Uninterruptible Power System reported a bypass active
This reference code is for information only. The Uninterruptible Power System (UPS) is reporting a bypass is active.
Battery low condition was reset
This reference code is for information only. The Uninterruptible Power System (UPS) is no longer reporting a battery low condition.
UPS reported bypass no longer active
This reference code is for information only. The Uninterruptible Power System (UPS) is no longer reporting a bypass active condition.
Battery Power Unit needs service
The replacement period for BPU 1, installed in the System Unit, has been exceeded.
Battery Power Unit needs service
The replacement period for BPU 2, installed in the System Unit, has been exceeded.
Battery Power Unit needs service
The replacement period for BPU 1, installed in the Expansion Unit, has been exceeded.
Battery Power Unit replacement dates do not match
The replacement dates for one of the Battery Power Units do not match. Run "Display Hardware Configuration" and verify that the dates match the labels on the batteries.
System LIC detected a program exception
Storage Management detected a DASD datacheck condition and the defective sector was reallocated. Perform a system IPL to restart the system.
Hardware configuration change detected
A hardware resource is missing. The resource reported in to the system on a previous IPL, but has not reported in on the current IPL. This could occur for several different reasons.
An external storage subsystem disk unit connection failed
Look for other errors in the Service Action Log (SAL), or serviceable event view you are working with, and fix them.
An external storage subsystem disk unit connection failed
Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.
Maximum number of redundant connections exceeded
An attempt to activate a connection from another I/O adapter to an external storage subsystem disk unit failed because the maximum number of connections are already active for this disk unit. No action required.
External storage subsystem disk unit connection was restored
No action required.
An external storage subsystem disk unit connection failed
Could not read configuration information from the disk unit. Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.
High performance connection failed
A high performance connection to an external storage subsystem disk unit failed. There are still two or more external storage subsystem disk unit connections, but performance might be degraded. Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.
High performance connection failed
A high performance connection to an external storage subsystem disk unit failed. There is still one more external storage subsystem disk unit connection, but performance might be degraded. Look for other errors in the Service Action Log, or serviceable event view you are working with, and fix them.
High performance connection was restored
A high performance connection to an external storage subsystem disk unit was restored. Performance is no longer degraded. No action required.
A platform firmware error log was reported to LIC without an SRC in the platform log. LIC will create a log in the PAL with SRC B600B700 to store the platform firmware log in. The platform firmware log will be copied to the component specific data area in the LIC log in the same position it normally is for platform errors.
Contact your hardware service provider. This is a platform firmware problem.
Permanent error on removable media device.
A type D IPL terminated because of a removable media load source device failure. If the removable media load source is an external device, check the cables. If that does not correct the problem, replace the device. If the removable media load source is an internal device, replace the device. If the removable media load source is a virtual device, ensure it is set up correctly.
Unsupported removable media device configuration.
A type D IPL terminated because of an unsupported removable media device configuration. Retry the D-IPL with a different removable media device.
Optical library device condition not expected
The optical disk drive addressing within the optical library is incorrect. This error is likely to be the result of faulty cabling or switch setting following service to an optical library. Contact your hardware service provider.
Media determined to be bad in Optical library
LPAR service function directed a Main Storage Dump.
The hypervisor terminated a partition with an unresponsive Operating System. A Main Store Dump must be done for service. Call your next level of support when the dump is complete.
LIC program reported informational error
This reference code is logged for information only. No action required.
LIC program failed and data was captured
This reference code indicates first failure data capture (FFDC) data was collected for a problem reported by licensed internal code. The user should dial IBM Software Support for assistance.
A B7xx reference code indicates that an event or error was detected and logged by platform firmware.
To resolve a B7xx reference code, determine if the SRC requires a service action.
If the SRC is listed in a serviceable event view, use the FRU list from the serviceable event view to determine the actions to take.
If you do not find the SRC in a serviceable event view, then it is an informational event and does not require service action.
Platform LIC detected an error
A machine check occurred during IPL. Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9 before attempting to IPL again and report the problem to next level of support.
Platform LIC failure
The platform Licensed Internal Code (LIC) detected an internal problem. Collect all the SRC words and the platform system dump, then contact your next level of support.
Platform LIC failure
Machine check, undefined error occurred.
Platform LIC detected an error
More than one request to terminate the system was issued.
Platform LIC failure
A secondary failure due to an invalid SRC occurred when the platform attempted to terminate. Collect all the SRC words and the platform system dump, then contact your next level of support.
Platform LIC failure
The server detected an unrecoverable machine check condition. Collect all the words of the SRC and the platform dump and send to your system manufacturer for analysis.
System firmware has experienced a low storage condition
As soon as possible, collect all ASMI logs, IQQYLOGs and partition logs, if applicable. Work with the customer to determine a convenient time to perform a platform dump and re-IPL the platform. Record the firmware level of the system, and send the platform dump and all logs to development. Check to determine if the problem is already fixed in a newer firmware level.
No immediate action is necessary. Continue running the system normally. If firmware-related commands are not responding or are failing, or firmware tasks have failed (e.g. SRC B7000602), work with your service provider to take a platform dump at the earliest convenient time or service window.
Platform firmware detected an error
Work with the customer to determine a convenient time to perform a platform dump and re-IPL the platform.
No immediate action is necessary. Continue running the system normally. At the earliest convenient time or service window, work with your service provider to take a platform dump.
The paging VIOS did not respond correctly to a LIC request.
If the platform is HMC-managed:
If the platform is not HMC-managed, or the above steps do not resolve the problem, contact your service provider.
Platform LIC failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. Perform a platform system dump and notify your service provider. IPL the system.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. The platform encountered an error early in the IPL or termination process.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
System log entry only, no service action required
Support can use this SRC and associated data to determine why the time of day for a partition was lost. No corrective action is required.
Platform LIC detected an error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. Platform Licensed Internal Code (LIC) detected an error condition. The second word indicates the severity of the error and the specific error condition. If word 2 is 10000A01 then record the SRC words and call your next level of support; otherwise this does not require service.
System clock problem
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. For systems managed by an HMC, use the ASM interface to reset the system clock at power on standby. For systems without an HMC, you can ignore this error. If the error occurs a second time, call your next level of support.
Informational event logged at each Platform IPL. System log entry only, no service action required
Platform LIC detected an error
A platform LIC failure occurred. Perform a platform dump and contact your next level of support.
Platform LIC detected an error
Resource management was unable to allocate main storage. A platform dump was started. Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9. Collect the platform dump and the configuration of the memory allocation for all partitions on this system. Provide the platform dump, configuration data, and the recorded SRC information to your next level of support.
The system detected an error in the system clock hardware
This is a serviceable event only if this error appears in a serviceable event view. If this is a serviceable event, then work with the FRU list in the serviceable event view if there is one. Otherwise, use the FRU list documented in the Failing Items column to determine the parts to exchange. If the system did not log this error as a serviceable event, then no service action is required.
System log entry only, no service action required
System log entry only, no service action required
A user request initiated an I/O tower/drawer power off. System log entry only, no service action required.
Fault indicator activation failure
A failure occurred while trying to activate a fault indicator. Look for and correct errors in the Serviceable Event View that were logged at approximately the same time as this error. If this problem persists, contact your next level of support.
System log entry only, no service action required
No action is required, unless the Hardware Management Console (HMC) indicates that the concurrent platform firmware update failed. In that case, the system must be re-IPLed in order for the firmware update to occur. Collect the error log data for this SRC and contact your next level of support.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. The platform encountered an error communicating with the service processor. The platform code attempts a graceful shutdown of partitions and powers off the server after a certain time, or when the last partition indicates shutdown, whichever comes first.
The platform encountered an event indicating that the power status has changed. System log entry only, no service action required
Platform LIC detected an error
The VPD for the system is not what was expected at IPL. When word 9 is 00180003, a redundant VPD chip exists, and the system will continue to run. Replace the VPD card at your next scheduled maintenance. When word 9 is not 00180003 replace the VPD card immediately. Work with the FRU list in the serviceable event view, if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange.
Platform LIC detected an error
The VPD for the system is not what was expected at IPL. The VPD on a memory DIMM is not correct and the memory on the DIMM cannot be used, resulting in reduced memory. Work with the FRU list in the serviceable event view, if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange.
Platform LIC detected an error
The VPD for the system is not what was expected at IPL. The VPD on a processor card is not correct and the processor card cannot be used, resulting in reduced processing power. Work with the FRU list in the serviceable event view if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange.
Platform LIC failure
A Platform Licensed Internal Code error occurred. The IPL will not continue. Look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. If there are no serviceable B1xxxxxx errors, or if correcting the errors did not correct this problem, reset the server firmware settings. Attention: Resetting the server firmware settings results in the loss of all of the partition data that is stored on the service processor. Before continuing with this operation, make sure that you manually record all settings that you need to preserve. To reset the server firmware settings, your authority level must be Administrator or Authorized service provider. On the ASMI Welcome pane, specify your user ID and password, and click Log In. In the navigation area, expand System Service Aids. Then select Factory Configuration. Select Reset server firmware settings and click Continue. The service processor will reboot after all settings have been reset. If that does not resolve the problem, replace the service processor.
A VPD collection overflow occurred
Look for and resolve other errors in the serviceable event view. If that does not resolve the problem, check for firmware updates and install them, if available. If that does not resolve the problem, contact your next level of support.
Platform LIC detected an error
A platform LIC failure occurred during VPD collection. Look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. If that does not correct the problem, contact your next level of support.
There is a platform dump to collect
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. Use the operating system's interface designated to collect platform dumps.
Platform LIC failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. The platform LIC detected an internal problem. Contact your next level of support.
Platform LIC failure
A platform LIC error occurred while attempting to allocate the memory necessary to create a platform resource dump.
Platform LIC detected an error
A problem occurred when initializing, reading, or using system VPD. Look for errors with SRCs of the form B1xxxxxx in the Serviceable Event View. Work those errors first. If that does not correct the problem, replace the VPD card. Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
Platform LIC detected an error
The system has been running with full Capacity on Demand resources activated. In one hour, the system will terminate and unlicensed resources will no longer be available. To prevent the system from terminating, enter an activation code of all zeroes. Then obtain the proper activation codes for the resources being used or allocate fewer resources in the LPAR configuration.
Platform LIC failure
The Capacity on Demand function is not available. If Capacity on Demand function is required, re-IPL the system. If that does not correct the problem, contact your next level of support.
A Capacity on Demand change has been detected
Utility Capacity on Demand resources have been activated.
Fast system IPL changed to slow system IPL
The data obtained from the system is not what was expected. The system will perform a slow IPL in order to obtain the correct data. If other errors occur, contact your next level of support.
(N/A for external service docs)
Platform LIC detected an error
The server detected a not valid Capacity On Demand activation and terminated the system. The allocated resources for the system might exceed those that are available for use.
(N/A for external service docs)
Platform LIC detected an error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the system is not exhibiting problematic behavior, this error may safely be ignored. Otherwise, contact your next level of support.
Platform LIC failure
Licensed Internal Code program exception occurred. Platform Licensed Internal Code detected a programming problem for which a platform dump may have been initiated. Send the system error log and the platform dump, if it occurred, to your next level of support.
Platform LIC detected an error
Platform Licensed Internal Code detected that an IOP request failed. This error indicates a failure during a search for the load source. There may be a number of these failure prior to finding a good load source. This is normal. If a B2xx3110 error is logged, a B2xx3200 or B7005122 may be posted to the control panel. Work the B2xx3110 error in the Serviceable Event View. If the system IPL hangs at B2xx3200 or B7005122 and you cannot check the SRC history, perform the actions indicated for the B2xx3110 SRC.
Platform LIC detected an error
A Licensed Internal Code program exception or data collection occurred. This may indicate an IOP programming problem or an IO Adapter boot problem. Look for other errors. If no other errors are present, Licensed Internal Code has recovered from any exception conditions, or this SRC has logged informational platform boto or hardware data.
Operating System error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. The platform detected a problem in an Operating System. Check for errors in the partition ID specified in word 4 of the SRC. If correcting those errors does not correct the problem, or if you find no errors, contact your next level of support.
A virtual adapter configuration error occurred. A partition tried to use a virtual adapter which is associated with another virtual adapter in a remote partition and virtual slot. However, either no virtual adapter is configured there, or the wrong kind of virtual adapter is configured there. The partition ID of the virtual adapter with the problem is in word 4 of the SRC (in hexadecimal format). The virtual slot number of the adapter with the incorrect configuration is the last four digits of word 6 of the SRC (in hexadecimal format).
Use the Hardware Management Console (HMC) to verify or reconfigure the incorrect virtual adapter configuration. If the configuration is correct, contact your service provider.
Platform LIC detected an error
System Licensed Internal Code detected an IOP timeout during IOP IPL. This may be caused by loose connections, improperly seated cards, media, or removeable media drive not in a ready state. Look for other errors.
Platform LIC detected an error. Information only, no service action required.
Platform LIC detected a failure while partitioning resources
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. Platform partitioning code encountered an error. This SRC represents a large number of possible problems, most of which involve the platform Licensed Internal Code (LIC). Work any error logs found in the Serviceable Event View. If this fails to correct the problem, or if there are no other errors, contact your next level of support.
An LPAR configuration problem was detected.
System detected a problem with the Logical Partition (LPAR) Configuration. Use the Hardware Management Console to reconfigure the LPAR configuration. Check Hardware Management Console (HMC) partition state.
If the problem persists, collect a system dump and contact your next level of support.
An unsupported Preferred Operating System was detected
The Preferred Operating System specified is not supported. The IPL will not continue. Use ASMI to select a supported Preferred Operating System and then, re-IPL the system.
An unsupported Preferred Operating System was detected
The Preferred Operating System specified is not supported. The IPL will continue. Use ASMI to select a supported Preferred Operating System and then, re-IPL the system.
The number of available World Wide Port Names (WWPN) is low.
To obtain an additional WWPN root, please contact your system vendor.
There are no remaining World Wide Port Names (WWPN).
To obtain an additional WWPN root, please contact your system vendor.
A resource has been disabled due to hardware problems
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. The platform detected a problem with a processor. The processor is not functional. Look in the Serviceable Event View for a B1xx xxxx error that implicates a processor. If the Serviceable Event View contains no B1xx xxxx error, or if resolving the error fails to correct the problem, contact your next level of support.
Platform LIC detected an error
The system will terminate. Collect all the SRC words and the platform system dump, and then contact your next level of support.
System log entry only, no service action required
A processor checkstop recovery occurred. A previous error log should provide notification of the failure, as well as any necessary service action. This error log provides additional information regarding the detected reason for the failure and the recovery action taken.
System log entry only, no service action required.
An attempt to initialize, read or use system VPD was unsuccessful. No action is required for this SRC. Look for other hardware errors in the Serviceable Event View and if present, perform the actions indicated.
Platform LIC failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. There was a problem initializing, reading, or using system VPD.
Platform LIC detected an error
The system has out-of-date VPD LIDs. Contact IBM support for new VPD LIDs.
Enclosure feature code and/or serial number not valid. Platform Licensed Internal Code detected invalid VPD (feature code and/or serial number) for a System or I/O Enclosure. The invalid VPD may prevent the use of Concurrent Maintenance on any FRU in the enclosure and prevent hardware errors from being reported correctly, so it should be fixed at the next opportunity.
Look at the FRU callout list in the serviceable events view for the B7005603 SRC to obtain the location information which contains the invalid feature code and/or serial number. Note: This SRC does not require a service action if the location information is "U####.###.#######". Next, find the System or I/O enclosure associated with this location, and locate the enclosure's physical label which contains the correct feature code and serial number. Depending on whether the invalid VPD is for a System or I/O Enclosure, use the procedure below to correct the VPD. If System enclosure: Note: the system must be powered off prior to changing the System Enclosure VPD.
If I/O expansion unit:
If the problem has not been resolved, contact your next level of support.
PCI host bridge failure
If you find a B7006981 SRC logged at about same time and listing parts from same enclosure as one of the FRUs here, then close this problem and work the B7006981 SRC. Work with the FRU list in the serviceable event view, if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available, use the failing item list presented here for servicing this reference code.
System bus error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
System bus error
If this event appears in a serviceable event view, work with the failing item list found there. If this event does not appear in a serviceable event view, no service action is required.
System bus error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
System bus error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
Platform LIC unable to find or retrieve VPD LID file.
Collect error logs and contact next level of support.
Platform LIC unable to find or retrieve VPD LID file.
Contact your next level of support.
Platform LIC detected an error
A system bus appears to be empty. If the bus is not empty, a hardware or configuration problem might exist. Look for other errors.
Platform LIC detected an error
A platform dump has occurred. The system has lost all the configured system settings (such as the HMC access and ASMI passwords, time of day, network configuration, hardware deconfiguration policies, etc.) that you might have set through user interfaces. Also, the system has lost the platform error logs and partition-related information, and the service processor is reset. Perform the recovery actions for the SVCPROC FRU but do not replace the service processor. The platform dump should be sent to your service provider.
Platform LIC detected an error
An error occurred because a partition needed more NVRAM than was available. The partition is still functional, but is operating in a degraded mode. Configuration information may be lost at the next IPL. In order to make more NVRAM available, delete one or more partitions.
NVRAM was cleared. System log entry only, no service action required
NVRAM unavailable following service processor reset/reload.
Contact your next level of support.
An NVRAM failure was detected.
An NVRAM failure was detected.
An NVRAM failure was detected.
Contact your next level of support.
Platform LIC detected an error
Unknown hardware detected. Look for other errors.
PCI host bridge failure
If this event does not appear in a serviceable event view, no service action is required. If this event appears in a serviceable event view, and if you find a B7006981 SRC logged at about the same time and listing parts from the same enclosure as one of the FRUs listed in the serviceable event view for B7006970, then close this problem and work the B7006981 SRC. Otherwise, work on the B7006970 SRC.
PCI secondary bus failure
If this event appears in a serviceable event view, work with the failing item list found there. If this event does not appear in a serviceable event view, no service action is required.
System bus error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
System bus error
If you find a B7006981 SRC logged on the same expansion unit as one of the FRUs here, then close this problem and work the B7006981 SRC. Use the unit value of the location codes to determine if the expansion unit is the same. Work with the FRU list in the serviceable event view, if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange.
IOP rejected the assignment of an IOA
An I/O Processor rejected the assignment of an I/O Adapter during the IPL of an IBM i Operating System partition. If the partition IPLed successfully, this event is logged for information only. No service action is required. If the partition failed to IPL, replace the IOA. If that does not resolve the problem, replace the IOP that controls the IOA. The Direct Select Address (DSA) of the IOA is in word 7 of the SRC. In order to find the location of the IOA, see PIPBUSDSABDOWN to get the unit type in which the IOA is located. Then using the DSA and unit type, find the location of the IOA.
The Processor Serial Interface (PSI) link failed. Look for B1xx SRCs that were logged at approximately the same time that this SRC occurred and resolve them. System log entry only, no service action required.
System log entry only, no service action required
Connection from service processor to system processor failed
Look for B1xxxxxx SRCs in the Serviceable Event View and resolve them. If there are no B1xxxxxx SRCs logged, then replace the failing items listed in the Serviceable Event View, if they are available. Otherwise, work with the failing items listed here.
RIO, HSL or 12X controller failure
If the serviceable event view contains a FRU list, work with those FRUs. Otherwise, exchange the failing items listed here. NOTE: A fiber optic cleaning kit may be required for optical RIO or HSL connections. A platform dump has occurred. Send the dump to your service provider.
RIO, HSL or 12X I/O bridge failure
If you find a 1xxx SRC logged on the same expansion unit as one of the FRUs here, then close this problem and work the 1xxx SRC. Use the unit value of the location codes to determine if the expansion unit is the same. Work with the FRU list in the serviceable event view, if there is one. Otherwise, use the FRU list documented here to determine the parts to exchange.
RIO, HSL or 12X connection failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. NOTE: A fiber optic cleaning kit may be required for optical RIO or HSL connections.
An invalid RIO, HSL or 12X configuration was detected.
The four rightmost characters of word 4 in the reference code represent the Program Return Code (PRC), which describes the problem detected. The four leftmost digits of word 7 represent the loop number in hexadecimal format. Use the DSA translation procedure to convert the loop number to a location. To determine the problem, find the PRC in the list below. Note: The FRU description in the serviceable event view may already contain a message that identifies the problem.
If the problem still exists, contact your next level of support. This ends the procedure.
System log entry only, no service action required
A RIO, HSL or 12X loop has switched to its alternate path. This is an informational SRC only. Word 7 of the SRC contains the loop number in the leftmost 4 digits. The loop number is in hexadecimal format. You must convert the hexadecimal loop number into decimal format to recognize the loop number. This SRC can be caused by a tower on the RIO, HSL or 12X loop powering off. This SRC may also appear in a Serviceable Event View you are using, with a B700 6982 or B700 6981 logged at approximately the same time. In that case the other SRC is reporting a failure and this SRC is reporting that the alternate RIO, HSL or 12X path is now being used. Service the other SRC if present.
RIO, HSL or 12X loop status message
This is a serviceable event only if this error is in a serviceable event view. If this is a serviceable event then perform [LIC]RIOIP12[/LIC]. Otherwise if this is NOT a serviceable event then to determine what this SRC means use symbolic FRU [LIC]SIRSTAT[/LIC]. Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. NOTE: A fiber optic cleaning kit may be required for optical RIO or HSL connections.
System bus error
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.
RIO, HSL or 12X connection failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.
An unrecoverable memory error caused a tower failure.
Look for any B12xE500 SRCs which require service action, and perform the actions indicated to resolve the memory failure. After completing those actions, you will need to power the failing tower off/on to recover.
I/O expansion drawer cables are incorrectly connected.
Return the cables to their previous position.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.
Platform LIC failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.
Service processor failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.
User intervention required
The system is in the process of terminating. When all the partitions have terminated, an SRC indicating the exact cause will be shown on the operator panel. If the system does not terminate in a reasonable amount of time, one or more partitions may need to be terminated manually. If this is not possible, re-IPL the system and look for errors. If no errors are found, contact your next level of support.
HSL OptiConnect established a normal connection to another system or partition. System log entry only, no service action required.
HSL OptiConnect disconnected normally from a remote node. System log entry only, no service action required.
Platform LIC detected an error
Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. The problem, which most likely originates with the remote system or partition, probably requires intervention at the remote system. Examine both the local and remote HSL OptiConnected systems or partitions for problems on this RIO or HSL loop. Possible reasons include: A fatal software or hardware error in the remote system or partition, or a power failure in the remote system. If a complete RIO or HSL loop did not exist before this error occurred, the cause of this error might be a failure or power down in a RIO or HSL component between the local system or partition and the remote system or partition. Check for a problem with the following:
On the local system or partition, examine the Service Action Log (SAL) or serviceable event view. Look for RIO or HSL failures that occurred on the same RIO or HSL loop at approximately the same time as this error. Examine the remote system or partition for problems. If the remote system or partition is powered on and IPL'd, examine the SAL or serviceable event view on the remote system or partition. Look for problems on the same RIO or HSL loop that occurred at approximately the same time as this error. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or RIO or HSL loop components. When the remote system is IPL'd, it will automatically reconnect with this system or partition. If you find no problems with either the local or the remote systems or partitions, collect all the Product Activity Log (PAL) information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.
Platform LIC detected an error
Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. Licensed Internal Code will attempt to recover from the error. Intervention at the local or remote system or partition might be required. Possible causes include time out, hang, or hardware failure. The problem may be with the local system or partition or the remote system or partition. If a complete RIO or HSL loop did not exist before this error occurred, the cause of this error might be a failure or power down in a RIO or HSL component between the local system or partition and the remote system or partition. Check for SRCs with FRUs that indicate problems with the following:
On the local system or partition, examine the SAL or serviceable event view. Look for failures on the same loop or with the RIO or HSL controller that occurred at approximately the same time as this error. Examine the remote system or partition for problems. Correct any RIO or HSL controller problems you find with the remote and local systems or partitions. If you find no problems with either the local or the remote systems or partitions, collect all the PAL information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.
Platform LIC detected an error
Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. All of the HSL OptiConnect connections on this loop will be in a failed state. Licensed Internal Code will attempt to recover from the error. Intervention at the local or remote system or partition might be required. Possible causes are:
The problem may be with:
On the local system or partition, examine the SAL or serviceable event view. Look for RIO or HSL failures on the same RIO or HSL loop or with the RIO or HSL controller that occurred at approximately the same time as this error. Examine the remote system or partition for problems. On the remote system or partition, examine the SAL or serviceable event view. Look for problems on the same RIO or HSL loop or with the RIO or HSL controller that occurred at approximately the same time as this error. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or RIO or HSL loop components. If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on all systems or partitions. Be sure to record all words in the SRCs. Contact your next level of support.
Platform LIC detected an error
Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an failure in a Licensed Internal Code virtualized bus unit. Licensed Internal Code will attempt to recover from the error. Possible causes are:
On the local system or partition, examine the SAL or the serviceable event view. Look for HSL Opticonnect failures that occurred at approximately the same time as this error. Examine the remote system or partition for problems. On the remote system or partition, examine the SAL or the serviceable event view. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. Collect all the Product Activity Log information for this failure on all systems and partitions on this RIO or HSL loop. Be sure to record all words in the SRCs. Contact your next level of support.
Platform LIC detected an error
Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Licensed Internal Code internal error. All systems participating in HSL OptiConnect will be disconnected. You must re-IPL the system to recover. Before re-IPL'ing the system, start a platform dump. On the local system or partition, after getting the dump, examine the SAL or the serviceable event view. Look for HSL Opticonnect failures that occurred at approximately the same time as this error. Examine the remote systems or partitions for problems. On the remote systems or partitions, examine the SAL or the serviceable event view. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. Collect all the PAL information for this failure on all systems and partitions on this RIO or HSL loop. Be sure to record all words in the SRCs. Contact your next level of support.
The 12X link is noisy, and has hit a threshold on bad packets.
If SRC B7006982 is in the serviceable event view, perform the actions listed for that SRC. If B7006982 is not present, work with the SRC B70069D2 FRU list in the serviceable event view. For an Internal link failure, the I/O backplane (TWRBKPL) is the probable cause. For an External link failure, the probable FRUs are listed below.
For External links, unplug and replug the 12X cable to see if the problem corrects itself.
Host Ethernet Adapter (HEA) failure
Firmware detected a hardware failure in the Host Ethernet Adapter (HEA).
A non-terminating Host Ethernet Adapter error was detected. System log entry only, no service action required
Platform LIC failure
A Platform Licensed Internal Code error occurred. The system will continue to run this Host Ethernet Adapter (HEA) disabled. Perform a platform dump and then IPL the system to recover the HEA. Send the platform dump to your next level of support.
Host Channel Adapter (HCA) failure
The 12X Host Channel Adapter has failed.
Platform LIC failure
A Platform Licensed Internal Code error occurred related to 12X technology. The system will continue to run with this Host Channel Adapter disabled. Perform a platform dump prior to IPLing the system. An IPL is required to recover the Host Channel Adapter.
System log entry only, no service action required
Part of the HCA chip failed but was not terminating. When thresholded, these errors will result in a B70069E1.
An invalid 12X configuration was detected
An error was detected in the 12X fabric. Have the customer check for problems reported at the IBM Network Manager. This includes cases such as path migration, etc.
System log entry only, no service action required
A 12X communications error occurred. Unrecognized command from Subnet Manager. Does not require service.
System log entry only, no service action required
The cable connection to the 12X switch is broken. Verify that the cable is connected and the switch is powered on. After repairing the problem, verify that the connection has been restored by using the IBM Network Manager. Does not require service.
System log entry only, no service action required
The cable connection to the 12X switch has been restored. No service action required.
System log entry only, no service action required
Initial communication has occurred with the Subnet Manager. No service action required. The CEC and switch firmware are now communicating.
System log entry only, no service action required
Subnet Manager connection is established. No service action required.
User intervention required
A 12X configuration error was detected by the HCA. Verify that the 12X configuration is correct at the HCA. The Port 1 and 2 configurations conflict.
User intervention required
A 12X adapter in the server does not support connections to I/O enclosures. Upgrade the adapter at the location given in the serviceable event view to a new version. Contact support for assistance.
RIO or 12X link is not operating at optimal bandwidth
An RIO 12X cable connection initialized to a lower signal frequency. The link is operational but operating at a bandwidth below its rated capacity. This may lead to degraded I/O throughput. Perform the [LIC]RIOIP56[/LIC]. Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange.
I/O unit backplane is not operating at optimal bandwidth
Replace the I/O unit backplane at your next scheduled maintenance.
12X controller failure
The 12X controller has failed. For I/O loop connections, all I/O enclosures on this loop will be in a failed state. For Host Channel Adapter (HCA) connections, all HCA connections on this 12X Fabric will be in a failed state. Work with your service provider to collect error logs. Then work with the FRU list in the Serviceable Event View if there is one, otherwise, use the FRU list documented here to determine the parts to exchange.
12X controller recovered; Do NOT replace any FRUs
The 12X controller recovered from a failure. The location code of the 12X controller is in the error log with the procedure FRU as point of reference only. Check if all I/O Adapters in the loop recovered. The four leftmost digits of SRC word 7 represent the loop number in hexadecimal format. Convert the loop number to decimal format. Using the HMC, locate and record the decimal loop number's information in the Hardware Topology screen. Determine what I/O Adapters or 12X switches are connected to that loop. Determine if any I/O Adapter in the loop are in a failed state. If there are I/O Adapters in a failed state, the partition to which the failed I/O Adapter is connected may need to be re-IPLed to complete recovery. If there are no I/O Adapter(s) in a failed state but there are errors logged against I/O Adapter(s) or I/O Processor(s) for the same loop, close those errors. The controller recovered successfully.
12X controller recovery failure
The 12X controller failed. Exhaustive attempts to recover the controller failed. All connections on this loop will be in a failed state. If there are errors logged against I/O Adapters on this loops, do not replace any I/O Adapter hardware. This SRC is the root cause. Collect the loop configuration of the system. The four leftmost digits of SRC word 7 represent the loop number in hexadecimal format. Convert the loop number to decimal format. Using the HMC, locate and record the decimal loop number's information in the Hardware Topology screen. Work with your service provider to collect error logs. Then work with the FRU list in the Serviceable Event View if there is one, otherwise, use the FRU list documented here to determine the parts to exchange.
12X controller failure
The 12X controller has failed. All connections on this loop will be in a failed state. If there are errors logged against I/O Adapters on this loops, do not replace any I/O Adapter hardware. This SRC is the root cause. Collect the loop configuration of the system. Then work with your service provider to collect error logs. Work with the FRU list in the Serviceable Event View if there is one, otherwise, use the FRU list documented here to determine the parts to exchange.
12X controller failure
The 12X controller detected an invalid firmware action. All connections on this loop will be in a failed state. If there are errors logged against I/O Adapters on this loops, do not replace any I/O Adapter hardware. This SRC is the root cause. Work with your service provider to collect error logs and a platform system dump. Then, check for firmware updates and install them, if available. If that does not resolve the problem, replace the 12X controller.
Unrecoverable 12X I/O Bridge failure.
Collect error logs and info logs. Replace the 12X I/O Bridge FRU in the I/O enclosure, and send the failed FRU with the error log data to IBM for fault analysis.
12X I/O Bridge recovered; Do NOT replace any FRUs.
12X I/O Bridge recovery failure
The 12X I/O Bridge FRU should be replaced. I/O slots associated with the 12X I/O Bridge FRU may have been affected, causing I/O adapters to be in a failed state. No service action should be taken against the I/O adapters, but partitions which were using these failed I/O adapters may require actions to restart affected applications. Collect error logs which occurred around the same time as this SRC, as well as the I/O configuration, and send to IBM.
12X I/O Bridge failure
If there are any Power Problems (SRC 1xxxxxxx) in the serviceable event view, perform the actions indicated. Otherwise, collect error logs and all configuration data associated with the failing 12X I/O Bridge adapter, including I/O backplanes and I/O adapters associated with the loop. Look for power faults for the related drawer/backplane. and check 12X cables and power cables for good connections. If the problem persists, contact your next level of support.
12X I/O Bridge failure
Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. If this does not resolve the problem, collect error logs, work with the customer to collect a platform dump, and check for firmware service pack updates.
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
(N/A for external service docs)
Platform firmware detected an error
Platform firmware detected unexpected or not valid data returned from non-platform firmware. Contact your next level of support.
Platform firmware detected a condition which may impact error reporting to a partition.
Collect the error logs and contact your next level of support.
Platform LIC failure
Work with the FRU list on the serviceable event view if there is one, otherwise, use the FRU list documented here to determine the parts to exchange. The platform LIC detected an internal problem. Collect all the SRC words and the platform system dump, then contact your next level of support.
Operating System error
Platform Licensed Internal Code terminated a partition. If SRC word 3 is 0018, then a user may have initiated a function 22 prior to the operating system completing the IPL. If a function 22 was not performed, or if SRC word 3 is not 0018, look for other serviceable errors which occurred at same time frame. If SRC word 3 is 0007 or 0009, then the failing partition received a Machine Check without having a Machine Check handler enabled. This could be due to the Machine Check occurring while the partition was in an IPL. If an IPL was not in progress, or word 3 is different, look for other serviceable errors which occurred at approximately the same time, and contact your next level of support.
Platform LIC detected an error
The platform LIC detected an internal problem. Collect all the SRC words and the platform system dump, then contact your next level of support.
Platform LIC detected an error
The system will terminate. Collect all the SRC words and then contact your next level of support.
Dynamic replacement of checkstopped processor failed.
Collect all the SRC words and then contact your next level of support.
A firmware error caused the system to terminate.
Collect all the SRC words and the platform system dump, and then contact your next level of support.
Perform a platform dump.
Platform LIC detected an error
Look for errors with SRCs of the form B1xx xxxx in the Serviceable Event View. Work those errors first. If that does not correct the problem, collect all the SRC words and the platform system dump, then contact your next level of support.
A resource has been disabled due to hardware problems
The platform detected a problem with a processor. The processor is not functional. Work with the FRU list in the serviceable event view if there is one, otherwise contact your next level of support.
The platform LIC detected an internal problem performing Partition Mobility
Collect all the SRC words and the platform system dump, then contact your next level of support.
Platform firmware detected an error
The platform is unable to support the requested architecture options requested by the operating system via ibm,client-architecture-support interface.
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, then find the SRC in the following list.
The device data structure is corrupted
Reboot the system or partition.
Incompatible firmware levels were found
Reboot the system or partition.
An lpevent communication failure occurred
Reboot the system or partition.
An lpevent communication failure occurred
Reboot the system or partition.
The firmware failed to register the lpevent queues
Reboot the system or partition.
The firmware failed to exchange capacity and allocate lpevents
Reboot the system or partition.
The firmware failed to exchange virtual continuation events
Reboot the system or partition.
The firmware was unable to obtain the RTAS code lid details
Reboot the system or partition.
The firmware was unable to load the RTAS code lid
Reboot the system or partition.
The firmware was unable to obtain the open firmware code lid details
Reboot the system or partition.
The firmware was unable to load the open firmware code lid
Reboot the system or partition.
The user did not accept the license agreement
There is no further action required. If the user did not accept the license agreement, the system will not function.
Failed to get the firmware license policy
Reboot the system or partition.
Failed to set the firmware license policy
Reboot the system or partition.
Unable to load a firmware code update lid
Reboot the system or partition.
The partition firmware was not actually updated and a reboot is required to recover. This SRC does call home.
Reboot the system or partition.
The registration of a partition firmware platform dump failed. If a partition resource dump is initaited, it may have incomplete or no data.
An lpevent communication failure occurred.
Reboot the system or partition.
Failure when initializing ibm,event-scan
Reboot the system or partition.
Failure when initializing PCI hot plug
Reboot the system or partition.
Failure when initializing interface to AIX or Linux
Reboot the system or partition.
Failure when initializing dynamic reconfiguration
Reboot the system or partition.
Failure when initializing sensors
Reboot the system or partition.
There is insufficient information to boot the partition
The client IP address is already in use by another network device
Cannot get gateway IP address
Refer to partition firmware progress codes using code CA00E174.
Cannot get server hardware address.
Refer to partition firmware progress codes using code CA00E174.
Bootp failed
Refer to partition firmware progress codes using code CA00E174.
File transmission (TFTP) failed.
Refer to partition firmware progress codes using code CA00E174.
The device does not have the required device_type property.
Contact service support.
The device_type property for this device is not supported by by the iSCSI initiator configuration specification.
Contact service support.
The arguments specified for the ping function are invalid..
Verify that all arguments comply with the iSCSI initiator configuration specification.
The itname parameter string exceeds the maximum length allowed.
Verify that all arguments comply with the iSCSI initiator configuration specification.
The ichapid parameter string exceeds the maximum length allowed.
Verify that all arguments comply with the iSCSI initiator configuration specification.
The ichappw parameter string exceeds the maximum length allowed.
Verify that all arguments comply with the iSCSI initiator configuration specification.
The iname parameter string exceeds the maximum length allowed.
Verify that all arguments comply with the iSCSI initiator configuration specification.
The LUN specified is not valid.
Verify that all arguments comply with the iSCSI initiator configuration specification.
The chapid parameter string exceeds the maximum length allowed.
Verify that all arguments comply with the iSCSI initiator configuration specification.
SET-ROOT-PROP could not find the / (root) package
Look for server firmware updates; apply if available.
The arguments specified for IP v6 are invalid.
Verify that all arguments comply with the iSCSI initiator configuration specification, and that the server addresses are correct.
The information in the error log entry for this SRC provides network trace data.
Informational message: no action is required.
The information in the error log entry for this SRC provides network trace data.
Informational message: no action is required.
A trace entry addition failed because of a bad trace type.
Check for system firmware update. Contact your next level support for assistance.
A trace entry addition failed because of a bad trace type.
Check for system firmware update. Contact your next level support for assistance.
Opening the TCP node failed.
Look for server firmware updates; apply if available.
TCP failed to read from the network
Look for server firmware updates; apply if available
TCP failed to write to the network.
Look for server firmware updates; apply if available.
Closing TCP failed.
Look for server firmware updates; apply if available.
The TCP re-transmission count of 8 was exceeded. This indicates a large number of lost packets between this client and the boot or installation server.
Failed to open the TFTP package
Verify that the TFTP parameters are correct.
Failed to load the TFTP file
Verify the the TFTP server and network connections are correct.
Opening the BOOTP node failed.
Look for server firmware updates; apply if available.
BOOTP failed to read from the network
Refer to the actions for checkpoint CA00E174.
BOOTP failed to write to the network
Refer to the actions for checkpoint CA00E174.
The discover mode is invalid
Look for server firmware updates; apply if available.
Closing the BOOTP node failed
Look for server firmware updates; apply if available.
The BOOTP discover server timed out
Refer to the actions for checkpoint CA00E174.
Opening the DHCP node failed
Look for server firmware updates; apply if available.
DHCP failed to read from the network
DHCP failed to write to the network
The DHCP discover server timed out
DHCP::discover no good offer
DHCP discover did not receive any DHCP offers from the server(s) the meet the clients's requirements. Insure that the DHCP server's configuration file is not overly constrained such that it was not able to meet the configuration requested by the client.
DHCP::discover DHCP request timed out
DHCP::discover: 10 incabable servers were found
Ten DHCP servers have sent DHCP offers, none of which met the requirements on the client. Check the configuration that the client is requesting, and the server's DHCP configuration files, for compatibility.
DHCP::discover received a reply, but without a message type
Insure that the DHCP server is properly configured.
DHCP::discover received a reply, but without a message type
DHCP::discover: DHCP decline
DHCP::discover: unknown DHCP message
DHCP discover received an unknown DHCP message type. Insure that the DHCP server is functioning properly.
Closing the DHCP node failed.
Look for server firmware updates; apply if available.
Selftest failed on device, no error and/or location code information available
If there was a location code reported with the error, replace the device specified by the location code.
Self test failed on device; cannot locate package.
The machine type and model are not recognized by the server firmware.
The firmware was not able to build the UID properly for this system. As a result, problems may occur with the licensing of the AIX operating system.
The firmware was unable to find the "plant of manufacture" in the VPD. This may cause problems with the licensing of the AIX operating system.
Setting the machine type, model, and serial number failed.
Retrieving the machine type, model, and serial number failed.
Look for server firmware updates; apply if available.
The h-call to switch off the boot watchdog timer failed.
Setting the firmware boot side for the next boot failed.
Rebooting a partition in logical partition mode failed.
Locating a service processor device tree node failed.
Failed to send boot failed message to the service processor
The environment variable "boot-device" exceeded the allowed character limit.
The environment variable "boot-device" contained more than 5 entries.
The environment variable "boot-device" contained an entry that exceeded 255 characters.
Logical partitioning with shared processors is enabled and the operating system does not support it.
The operating system does not support virtual real memory (VRM).
Install or boot a version of the operation system that supports VMR.
The system or partition is configured to use huge pages, but the operating system image does not support huge pages.
Do one of the following:
The hypervisor supports dynamic partitioning of the huge page-type of memory allocation, but dynamic partitioning of huge pages is not supported.
Use the ASMI to disable dynamic partitioning of huge pages.
The operating system expects an IOSP partition, but the operating system failed to make the transition to alpha mode.
The operating system expects a non-IOSP partition, but the operating system failed to make the transition to MGC mode.
The operating system does not support system's processor(s).
Boot a newer version of the operating system that supports the system's processors.
Invalid number of vectors from the operating system.
Boot a newer version of the operating system.
Failed to set the operating system's boot list from the MM bootlist
Failed to read VPD "boot path" field value
Check for firmware updates (MM, H8, system firmware), and apply if available.
Failed to update VPD with new "boot path" field value
Check for firmware updates (MM, H8, system firmware), and apply if available.
An I/O error on the adapter from which the boot was attempted prevented the operating system from being booted.
SCSI controller error
Do the following:
SCSI controller error
An IDE device remained busy for a longer period than the time out period.
The IDE controller senses IDE devices but with errors.
An IDE device is busy longer than specified time-out period.
Retry the operation.
An IDE command timed out; command is exceeding the period allowed to complete.
Retry the operation.
The media is not present in the tray
Place bootable media in tray and retry the opearation.
The media has been changed
Retry the operation.
The packet command failed; the media might not be readable.
Retry the operation.
SCSI disk unit: test unit ready failed; hardware error
SCSI disk unit: test unit ready failed; sense data available
SCSI disk unit: send diagnostic failed; sense data available
SCSI disk unit: send diagnostic failed: devofl command
The virtual fibre channel boot driver had an unexplained time out when trying to access the boot media.
Unable to access the boot media due to "busy" response from the fibre channel storage server.
An attempt to read the boot disk failed because of a reserve condition.
An attempt to send a command to the fibre channel boot disk failed at the NPIV layer.
An event happened on the virtual fibre channel adapter that forced a full disconnection from the fibre channel fabric.
Generic SCSI sense error.
Generic SCSI sense error can be:
The media are write-protected
Check the media and retry the operation.
The media are unsupported or are unrecognizable.
Check the media and retry the operation.
The media are not formatted correctly.
Replace the media and retry the operation.
The media are not present
Insert or replace the media and retry the operation.
The number of times the retry command has to be executed has exceeded the limit.
The SCSI device type is not supported
Replace the SCSI device with a supported device.
SCSI tape: test unit ready failed; hardware error.
SCSI tape: test unit ready failed; sense data available.
SCSI tape: send diagnostic failed; sense data available.
SCSI tape: send diagnostic failed: devofl command.
SCSI changer: test unit ready failed; hardware error
Before replacing any system components refer to the notes in error code BA09xxxx.
SCSI changer: test unit ready failed; sense data available.
SCSI changer: send diagnostic failed; sense data available.
SCSI changer: send diagnostic failed: devofl command.
On an undetermined SCSI device, test unit ready failed; hardware error.
On an undetermined SCSI device, test unit ready failed; sense data available
On an undetermined SCSI device, send diagnostic failed; sense data available
On an undetermined SCSI device, send diagnostic failed; devofl command
An I/O error on the adapter from which the boot was attempted prevented the operating system from being booted.
SCSI CD-ROM: test unit ready failed; hardware error.
SCSI CD-ROM: test unit ready failed; sense data available
SCSI CD-ROM: send diagnostic failed; sense data available.
SCSI CD-ROM: send diagnostic failed: devofl command.
USB CD-ROM: device remained busy longer than the time-out period.
Retry the operation.
USB CD-ROM: execution of ATA/ATAPI command was not completed within the allowed time.
Retry the operation.
USB CD-ROM: execution of ATA/ATAPI command failed.
USB CD-ROM: ATA/ATAPI packet command execution failed.
The CD in the USB CD-ROM may not be readable. Try another CD.
SCSI read/write optical: test unit ready failed; hardware .error
SCSI read/write optical: test unit ready failed; sense data available.
SCSI read/write optical: send diagnostic failed; sense data available
SCSI read/write optical: send diagnostic failed; .devofl command
PCI Ethernet BNC/RJ-45 or PCI Ethernet AUI/RJ-45 adapter: internal wrap test failure.
Replace the adapter specified by the location code.
10/100 MBPS Ethernet PCI adapter: internal wrap test failure.
Replace the adapter specified by the location code
Gigabit Ethernet adapter failure
Verify that the MAC address programmed in FLASH EEPROM is correct.
Gigabit Ethernet adapter could not be mapped-in by system firmware
HEA h-call error
Check for system firmware update; apply if available.
Required open firmware property not found
Check for system firmware update; apply if available.
Bad argument from user
Check for system firmware update; apply if available.
TFTP package open failed
Check for system firmware update; apply if available.
Transmit operation failed
Check for system firmware update; apply if available.
Failed to initialize HEA port or queue
Check for system firmware update; apply if available.
Receive operation failed
Check for system firmware update; apply if available.
VPD (vital product data) capability not found.
A problem was found in the adapter's VPD (vital product data).
VPD (vital product data) keyword error. Additional error log data should show whether the keyword was missing or invalid.
Failed to allocate the VPD (vital product data) buffer.
A registry property was not found.
The assigned-address property was not found.
Memory map-in failed for the control register set memory region.
Failed to acquire the semaphore for the flash register.
The flash register was not ready when initially checked prior to reading the MAC address.
The flash register was not ready following the reading of the MAC transition.
A parity error occurred when reading the MAC address from the flash memory.
Initialization of the adapter chip set failed.
Failed to open the OBP-TFTP package.
PCI token ring adapter: failed to complete hardware initialization.
Replace the adapter specified by the location code.
PCI token ring adapter: failed to complete hardware initialization.
Replace the adapter specified by the location code.
NVRAM data validation check failed
Reboot the system or partition; this failure should correct itself.
The firmware was unable to expand the target partition -saving configuration variable
The firmware was unable to expand the target partition - writing error log entry
The firmware was unable to expand the target partition - writing VPD data
The firmware was unable to write a variable value into NVRAM because not enough space exists in NVRAM.
Do the following:
The setenv/$setenv function had to delete network boot information to free space in NVRAM.
You might need to use the SMS menus to reenter the parameters for network installation or boot.
NVRAMRC script evaluation error - command line execution error.
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.
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.
PCI device runtime error, bridge in freeze state.
A PCI adapter was found that this machine type and model does not support.
Is this system an IBM Intellistation model?
No responce was received from a PCI slot during probing
A PHB reset/recovery was successful.
A PHB was reset more than once during the boot or reboot of a system or partition.
PCI probe error, bridge in freeze state, slot in reset state.
FDDI Adapter FCode driver is not supported on this system.
This server does not support the Fcode driver on this adapter. Service support might have additional information.
An unsupported adapter was found in a PCI slot.
Remove the unsupported adapter in the slot specified by the location code.
EEH recovered a failing I/O adapter.
This is an informational code only, and no action is required. Since it is informational, no location code will be reported.
EEH could not recover the failed I/O adapter.
Replace the adapter in the slot specified by the location code.
The hypervisor function to turn on the speaker reported an error.
The serial interface failed to open.
Check console settings to ensure the console is defined to the correct port. Ensure the console cables are connected to the port that is defined as the console.
The firmware failed to handshake properly with the serial .interface
Check for system firmware update. Contact your next level support for assistance.
Partition firmware reports a stack underflow was caught.
Partition firmware was ready before standout was ready.
Partition firmware detected a data storage error.
An open firmware stack-depth assert failed .
Check for system firmware update. Contact your next level support for assistance.
Open firmware free memory chain corruption detected and isolated.
Check for system firmware update. Contact your next level support for assistance.
The transfer of control to the SLIC loader failed.
The transfer of control to the I/O reporter failed.
NVRAMRC forced-boot problem; unable to load operating system that was loaded on previous boot.
Use the bootlist menus in the SMS to verify that the operating system image can still be detected by firmware. If firmware does not see the image, reload the operating system.
There was a partition firmware error when in the SMS menus.
Look for server firmware updates; apply if available.
The I/O configuration exceeds the maximum size allowed by partition firmware.
Increase the logical memory block size to 256 megabytes (MB) and reboot the managed system.
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.
The partition firmware error log queue is full.
Contact service support.
There was a communication failure between partition firmware and the hypervisor. The lpevent that was expected from the hypervisor was not received.
There was a communication failure between partition firmware and the hypervisor. There was a failing return code with the lpevent acknowledgement from the hypervisor.
The partition firmware got an error during USB hotplug probing. USB hotplug may not work properly on this partition.
Do the following:
CRQ registration error; partner vslot not valid.
From the HMC, verify that this client virtual-slot device has a valid server virtual-slot device in a hosting partition.
dlpar error in open firmware due to an invalid dlpar entity. This error may have been caused by an errant or hung operating system process.
Do the following:
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.
Unable to generate device-tree node for partition migration
After performing the FWFLASH procedure, check for operating system updates and apply them if available.
Failed to flash firmware; invalid image file
Obtain a valid firmware image for this system.
Flash file is not designed for this eServer platform.
Obtain a valid firmware image for this system.
Unable to lock the firmware update lid manager.
Do the following:
An invalid firmware update lid was requested.
Obtain a valid firmware image for this system.
Failed to flash a firmware update lid.
Obtain a valid firmware image for this system.
Unable to unlock the firmware update lid manager.
Reboot the system.
Failed to reboot the system after a firmware flash update.
Manually reboot the system.
A server firmware update was attempted from the operating system. You must perform the update by using the Hardware Management Console (HMC).
Perform the flash update from the HMC.
The server firmware update management tools for the version of Linux that you are running are incompatible with this system.
Go to the Service and productivity tools for Linux on POWER link and download the latest service aids and productivity tools for the version of Linux that you are running.
Firmware flash failed due to hardware error being reported.
Resolve any problems that are found in the error logs, then retry the firmware flash.
RTAS discovered an invalid operation that may cause a hardware error.
Do not perform the action again.
The partition exceeded the maximum number of logical memory blocks allowed under the new memory allocation scheme.
Function call to isolate a logical memory block failed under the standard memory allocation scheme.
Do the following:
Function call to make a logical memory block unusable failed under the standard memory allocation scheme.
Do the following:
The partition, which is running the traditional memory representation, exceeded the limit of 8192 logical memory blocks allowed by the standard memory allocation scheme.
Do the following:
The firmware operation to write the MAC address to vital product data (VPD) failed
Invalid vital product data (VPD): no description was found.
Memory allocation error in partition firmware.
memory allocation error
memory allocation error
memory allocation error
memory allocation error
A virtual real memory (VRM) pin page function call failed.
A virtual real memory (VRM) unpin page function call failed.
An error occurred when attempting to create a system plan; this normally results in no system plan being created. This is an informational code; typically, no hardware needs to be replaced. The problem may be an intermittent hardware error, or may be firmware-related.
Informational message: the string property value is longer than the buffer that was allocated. The string has been truncated to fit in the buffer space that was allocated.
Failed to obtain the time and date from firmware.
An error occurred in the firmware function that manages parent topology identifiers.
DMA trace buffer overflow; informational message.
Check for system firmware updates; apply if available.
DMA map-out size mismatch; informational message.
Check for system firmware updates; apply if available.
The Linux operating system detected a failure in the emulex driver.
The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error, and the last three characters specifies the error condition. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity.
Use the following list to locate the (BF67) Linux SRC that you want to find, then perform the suggested actions.
An ELS IOCB command was posted to a ring and did not complete within ULP timeout seconds.
If no ELS command is going through the adapter, reboot the system.
The driver attempted to issue READ_SPARAM mailbox command to the HBA but there were no buffer available.
This message indicates one of the following conditions:
The driver attempted to issue REG_LOGIN mailbox command to the HBA but there were no buffer available.
This message indicates one of the following conditions:
This error might indicate a software driver, firmware or hardware problem.
This message indicates one of the following conditions:
The Rctl/Type of a received frame did not match anyfor the configured masks for the specified ring. This error might indicate a software driver or firmware problem.
Received an unknown IOCB command completion. Thiserror might indicate a software driver or firmware problem.
The driver wan unable to find a matching command forthe completion received on the specified ring. This error might indicate a software driver or firmware problem.
A unknown mailbox command completed. This error mightindicate a software driver, firmware or hardware problem.
The configuration parameter for scan-down is out ofrange. Software driver error.
The driver attempted to register the HBA interrupt serviceroutine with the host operating system but failed. This error might indicate a hardware or driver problem.
The driver manages its own memory for internal usage.This error indicates a problem occurred in the driver memory management routines. This error might also indicate the host system in low on memory resources. This error might indicate a driver or host operating system problem.
This error might indicate a software driver problem.
This message indicates one of the following conditions:
The driver decided to drop an ELS Response ring entry.This error might indicate a software driver or firmware problem.
Received a mailbox completion interrupt and there areno outstanding mailbox commands. This error might indicate a hardware or firmware problem. Update firmware.
The driver issued a CONFIG_LINK mbox command to theHBA that failed. This error might indicate a firmware or hardware problem. Update firmware or replace adapter.
The driver issued a READ_SPARAM mbox command to theHBA that failed. This error might indicate a firmware or hardware problem.
The driver issued a CLEAR_LA mbox command to the HBAthat failed. This error might indicate a firmware or hardware problem.
A read nvparams mailbox command failed during configport. This error might indicate a hardware or firmware problem.
The driver cannot find the specified buffer in its mappingtable. This error might indicate a software driver or firmware problem.
The adapter failed during power-up diagnostics afterit was reset. This error might indicate a hardware or firmware problem.
The adapter failed during power-up diagnostics afterit was reset. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing READ_REVmailbox command. This error might indicate a hardware or firmware problem.
Outdated firmware was detected during initialization.This error might indicate a hardware or firmware problem. Update firmware.
Adapter initialization failed when issuing DUMP_VPDmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing CONFIG_PORTmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing CFG_RINGmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing CONFIG_LINKmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing READ_SPARMmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing READ_CONFIGmailbox command. This error might indicate a hardware or firmware problem.
Adapter initialization failed when issuing INIT_LINKmailbox command. This error might indicate a hardware or firmware problem.
The driver received an interrupt indicting a possiblehardware problem. This error might indicate a hardware or firmware problem.
The Linux operating system detected a failure in the ipr driver.
The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error, and the last three characters specifies the error condition. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity. For example:
Use the following list to locate the (BF75) Linux SRC that you want to find, then perform the suggested actions.
8155: An unknown error was received. Have the customerupdate the device driver.
Firmware file %s not found. Have the customer updatethe adapter microcode.
Invalid microcode buffer. Have the customer updatethe adapter microcode.
Microcode buffer allocation failed. Have the customerupdate the adapter microcode.
Microcode buffer copy to DMA buffer failed. Have thecustomer update the adapter microcode.
Microcode download required. Have the customer updatethe adapter microcode.
Failed to map microcode download buffer. Have thecustomer update the adapter microcode.
8151: IOA microcode error. Have the customer updatethe adapter microcode and the device driver.
Adapter being reset due to command timeout. Have thecustomer update the adapter microcode.
Invalid resource address. Have the customer updatethe device driver.
7001: IOA sector reassignment successful. Media error.
Unsolicited device bus message received.
Device hardware error.
Predictive failure analysis.
Device error. May occur normally during concurrent maintenance.
Out of alternate sectors for disk storage.
9031: Array protection temporarily suspended, protectionresuming. Hardware configuration error. Perform MAP 3310 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
This message indicates one of the conditions below.
Perform MAP 3390 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
IOA detected a SCSI bus configuration error. Device bus error, message or command phase. Perform MAP 3350 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
IOA cache data exists for a missing or failed device. Perform MAP 3332 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Disk unit has been modified after the last known status.Incorrect hardware configuration change has been detected. Perform MAP 3333 in the PCI-X SCSIRAID Controller Reference Guide for Linux .
A permanent cache battery pack failure occurred. Perform MAP 3300 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Cache data associated with attached devices cannot befound. Perform MAP 3320 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Array missing two or more devices with only one devicepresent. Perform MAP 3311 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
One or more array members not at required physical locations. Perform MAP 3312 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Array is missing a device and parity is out of sync. Perform MAP 3313 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Required cache data cannot be located for a disk unit. Perform MAP 3331 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
IOA resources not available due to previous problems. Perform MAP 3321 in the PCI-X SCSI RAID Controller Reference Guide for Linux .
Disk unit requires initialization before use. Perform MAP 3334 in the PCI-X SCSIRAID Controller Reference Guide for Linux .
Permanent IOA failure.
Invalid response handle from IOA.
IOA unit check with no data.
IOA taken offline - error recovery failed.
Adapter not supported in this hardware configuration.Remove the unsupported adapter from the system.
Failed to set PCI DMA mask.
Write of cache line size failed.
Failed to save PCI configuration space.
Soft PCI bus error.
Adapter hardware error.
The Linux operating system detected a failure in a driver or subsystem.
The first five characters (BFyyy) of these SRCs indicate the driver or subsystem responsible for the error:
The last three characters specify the error condition. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity. For example:
Use the following list to locate the (BF77) Linux SRC that you want to find, then perform the suggested actions:
The driver was unable to send a received packet to theupper layer protocols because there is insufficient free memory. The customer may need to increase system memory.
Unrecognized command code or unrecognized buffer address.
The olympic driver was unable to initialize the tokenring card. Corrective action may be possible depending upon the error code.
The Cardbus token ring adapter did not respond to initializationcommands. Ensure that Cardbus adapter is properly inserted.
The token ring adapter was unable to join the ring.Have the customer use the network configuration tool supplied by the distributor to specify a ring speed (instead of automatically detecting ring speed).
The adapter open request failed with the specified errorcode.
The specified hardware, PCI or parity error has occurred.Have the customer reset the adapter
The specified interrupt has occurred, but was not expectedby the driver or a timeout occurred during device close processing. For occasional occurances, no action is required. For excessive occurrences, have the customer reset the adapter. If resetting the adapter does not work, perform the action specified in the Failing Item column.
Unrecognized srb command or cannot set mac/laa addresswhile card is open. Have the customer reload the driver
A short circuit has been detected.
An internal hardware error has been detected in thespecified adapter during auto removal processing. Have the customer reload the driver
An FDX protocol error has been detected. Have thecustomer reload the driver
Invalid return code in asb. Have the customer upgradethe driver
The driver was unable to use 32-bit DMA. Have thecustomer verify the driver software level.
Memory allocation failed.
Transmit timed out, resetting. Have the customer verifythe driver software level.
A FIFO error has occurred. Have the customer verifythe driver software level.
The transmit pointers are out of synchronization.Have the customer verify the driver software level.
The driver could not enable the PCI device.
The hardware did not request any IO resources.
The IO addresses for the card are already allocated.Have the customer verify the driver software level.
The chip can not be accessed in 32-bit or 16-bitmode. Have the customer verify the driver software level.
Unable to find or create the directory under /proc/net.Have the customer verify that procfs is supported by the kernel.
Insufficient kernel memory available for allocation.
The driver was unable to use either 64-bit or 32-bitDMA. Have the customer verify driver software level.
Linux does not support a hardware feature which has been enabled. Run diagnostics to disable Turbo Teaming.
Memory allocation failed - buffer parameters may beset too high.
Conflicting rx_coalesce_ticks (0) and rx_max_coalesce_frames(0) parameters.
Conflicting tx_coalesce_ticks (0) and tx_max_coalesce_frames(0) parameters.
The value given to the stats_coalesce_ticks parameteris invalid. Have the customer change the stats_coalesce_ticks parameter of the driver.
Either this adapter or the system does not allow theuse of adapter based transmit descriptors.
This adapter does not support hardware checksum offload.
This adapter does not support hardware TSO.
This adapter hardware does not support frames sizesover 1500 bytes. Have the customer verify the driver software level. If you replace the adapter, use one that offers additional capablities
Unable to read the adapter's NVRAM. Have the customerverify the driver software level
Cannot get MAC addr from NVRAM. Have the customerverify the driver software level
Unable to read PCI Config space or NVRAM. Have thecustomer verify the driver software level
Internal error in driver, kernel, or firmware.
Insufficient kernel memory is available for the driver.
Internal error in driver, kernel, or firmware.
Not enough memory for the driver. Unable to initialize(or reinitialize) the adapter card.
The BIOS has assigned conflicting address spaces todifferent devices.
The driver requested a DMA configuration that your systemdoes not support.
The adapter's MAC address is not a valid Ethernet address.
The EEPROM on the network adapter may be corrupted.
The driver cannot enable the adapter as a PCI device.
The network adapter failed its self-test.
Cannot enable DMA for either 32 bits or 64 bits.
Unable to access PCI data area for checksum value. However,the device id is valid.
The MAC type is not ethernet as expected.
Adapter hardware failure.
This information was developed for products and services offered in the U.S.A.
The manufacturer may not offer the products, services, or features discussed in this document in other countries. Consult the manufacturer's representative for information on the products and services currently available in your area. Any reference to the manufacturer's product, program, or service is not intended to state or imply that only that product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any intellectual property right of the manufacturer may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any product, program, or service.
The manufacturer may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to the manufacturer.
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The manufacturer may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to Web sites not owned by the manufacturer are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this product and use of those Web sites is at your own risk.
The manufacturer may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning products not produced by this manufacturer was obtained from the suppliers of those products, their published announcements or other publicly available sources. This manufacturer has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to products not produced by this manufacturer. Questions on the capabilities of products not produced by this manufacturer should be addressed to the suppliers of those products.
All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
The drawings and specifications contained herein shall not be reproduced in whole or in part without the written permission of the manufacturer.
The manufacturer has prepared this information for use with the specific machines indicated. The manufacturer makes no representations that it is suitable for any other purpose.
The manufacturer's computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure. In addition, users must establish procedures to ensure that there is independent data verification before relying on such data in sensitive or critical operations. Users should periodically check the manufacturer's support websites for updated information and fixes applicable to the system and related software.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
INFINIBAND, InfiniBand Trade Association, and the INFINIBAND design marks are trademarks and/or service marks of the INFINIBAND Trade Association.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
The following Class A statements apply to the IBM servers that contain the POWER6 processor.
The following Class A statements apply to the servers.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A respecte est conforme à la norme NMB-003 du Canada.
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment.
The following is a summary of the VCCI Japanese statement in the box above:
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio interference may occur, in which case, the user may be required to take corrective actions.
Declaration: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may need to perform practical action.
The following is a summary of the EMI Taiwan statement above.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user will be required to take adequate measures.
IBM Taiwan Contact Information:
Please note that this equipment has obtained EMC registration for commercial use. In the event that it has been mistakenly sold or purchased, please exchange it for equipment certified for home use.
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022 Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022
Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:
"Warnung:
Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Maßnahmen zu ergreifen und dafür aufzukommen."
Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem "Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG)". Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A.
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Konformitätserklärung nach des EMVG ist die IBM Deutschland GmbH, 70548 Stuttgart.
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
Permissions for the use of these publications is granted subject to the following terms and conditions.
Personal Use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative works of these publications, or any portion thereof, without the express consent of the manufacturer.
Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of the manufacturer.
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any data, software or other intellectual property contained therein.
The manufacturer reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by the manufacturer, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.
THE MANUFACTURER MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THESE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.