DS8000 Service Documentation Version 8.5.7

(B1xxxxxx) Service processor firmware reference codes

A B1xxxxxx reference code indicates that an exception occurred in a service processor firmware-detected operation.

To determine if the SRC requires a service action or if it is for tracking purposes only, see (B1xxxxxx) Service processor firmware reference codes for instructions.

Note: See (B1xxxxxx) Service processor firmware reference codes for a list of B1xx SRCs and descriptions.

B1xxyyyy where:

xx=: Indicates the subsystem where the event or error occurred. See Table 1.
yyyy=: The reason for the event or error (reason code). See Table 3.

A B1xx reference code indicates that an event or exception occurred in a service processor firmware-detected operation. The following tables describe the B1xx SRCs.

Table 1 lists ranges of B1xx Service processor subsystem IDs and gives a general description of the associated event or error.
Table 2 lists B1xx SRCs and descriptions.
Table 3 lists ranges of B1xx SRCs in the format B1xx yyyy, where yyyy refers to a series of characters (called the reason code). This table includes the reason code and a more detailed description of the exception in the firmware or in a firmware operation.

If you do not find an SRC in the table that follows, contact your next level of support for assistance.

Notes:

The SRCs on this page are from the Power Systems hardware documentation, and the Descriptions apply to a single CEC enclosure or I/O enclosure. The Action and Failing Item fields are modified as appropriate for DS8000® architecture and repair methods.
SRCs missing from the following tables might be found on the Power Systems online documentation. You can use the SRC description as is to define the problem. Do not use the Action and Failing Item without contacting the next level of support first.
To display the Power Systems hardware online documentation, go to the Web site http://www-01.ibm.com/support/knowledgecenter/.
- In the IBM Systems Hardware Information right content pane, click POWER6 reference codes listing.

Table 1. (B1xx) Service processor subsystem IDs
Subsystem ID	Description
10	Processor subsystem event or error reported by the service processor.
11	Processor FRU event or error reported by the service processor.
12	Processor chip (including internal cache) event or error reported by the service processor.
13	Processor unit (CPU) event or error reported by the service processor.
14	Processor/system bus controller and interface event or error reported by the service processor.
20	Memory subsystem event or error reported by the service processor.
21	Memory controller event or error reported by the service processor.
22	Memory bus interface event or error reported by the service processor.
23	Memory DIMM event or error reported by the service processor.
24	Memory card/FRU event or error reported by the service processor.
25	External cache event or error reported by the service processor.
30	I/O subsystem event or error reported by the service processor.
31	I/O hub (Remote I/O) event or error reported by the service processor.
32	I/O bridge event or error reported by the service processor.
33	I/O bus interface event or error reported by the service processor.
34	I/O processor event or error reported by the service processor.
35	SMA hub event or error reported by the service processor.
36	Remote I/O loop and associated I/O hub event or error reported by the service processor.
37	Remote I/O loop and associated I/O bridge event or error reported by the service processor.
38	Processor Host Bridge (PHB) event or error reported by the service processor.
39	EADS/EADS-X global event or error reported by the service processor.
3A	EADS/EADS-X slot event or error reported by the service processor.
40	I/O adapter event or error reported by the service processor.
46	I/O device event or error reported by the service processor.
50	System unit hardware event or error reported by the service processor.
51	Service processor event or error reported by the service processor.
55	VPD device and interface event or error reported by the service processor.
56	I2C device and interface event or error reported by the service processor.
57	JTAG device and interface event or error reported by the service processor.
58	Clock and control event or error reported by the service processor.
59	Control panel event or error reported by the service processor.
5A	Time-of-day hardware (including the battery) event or error reported by the service processor.
5B	Storage/memory device on service processor event or error reported by the service processor.
60	Power/cooling subsystem and control event or error reported by the service processor.
61	Power supply event or error reported by the service processor.
62	Power control hardware event or error reported by the service processor.
63	Fan or other air moving device event or error reported by the service processor.
70	Other event or error reported by the service processor.
71	HMC subsystem and hardware event or error reported by the service processor.
72	Test tool event or error reported by the service processor.
73	Removal media event or error reported by the service processor.
74	Multiple subsystems event or error reported by the service processor.
75	Unknown, invalid event or error reported by the service processor.
76	Informational event reported by the service processor.
7B	Connection monitoring error: service processor lost communication with the server firmware.
7C	Connection monitoring error: service processor lost communication with the HMC.
7D	Connection monitoring error: HMC lost communication with a logical partition.
80	Platform firmware event or error reported by the service processor.
81	Service processor firmware event or error reported by the service processor.
82	Server firmware event or error reported by the service processor.
85	SPCN firmware event or error reported by the service processor.
86	Bulk power firmware event or error reported by the service processor.
87	HMC code or firmware event or error reported by the service processor.
90	Software event or error reported by the service processor.
A0	External environment event or error reported by the service processor
A1	Input power source (AC) event or error reported by the service processor.
A2	Room (ambient) temperature event or error reported by the service processor.
A3	User error reported by the service processor.

Table 2. (B1xx) SRC Descriptions
Reference Code	Description	Action
B103F684	Xscoms are not supported	See Note.
B104FAA9	Failed trying to get pointer to functional unit group for type	See Note.
B110E500	Bad hardware	See Note.
B110F138	Scom attention detected on the current chip	See Note.
B110F139	Master Attention Alone detected	See Note.
B110F141	Indicates a potential problem with clock card	See Note.
B110F7B0	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B1	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B2	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B3	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B4	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B5	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B6	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B110F7B7	The interposer plug count for the MCM in the callout has exceeded the limit	See Note.
B111E500	Bad hardware	See Note.
B111F64B	Fabric latency calculation packet not received on processor	See Note.
B111F658	Invalid fabric rotation length	See Note.
B111F665	Processor's POR State Machine not at idle after free running logic reset	See Note.
B112E500	Bad hardware	See Note.
B112F64E	PLL Health check failed on Trimaran	See Note.
B112F65B	Invalid L2 Slice Configuration	See Note.
B112F66E	Handling CE detected by the fabric firs and the L3 firs	See Note.
B112F66F	Handle errors detected by L3 firs and the ebist engine	See Note.
B112F670	Handle CE detected by L3 firs	See Note.
B113E500	Bad hardware	See Note.
B114E500	Bad hardware	See Note.
B114F2DF	Fatal IAP Error	See Note.
B114F663	Fabric initialization failed on processor	See Note.
B114F66C	Clock period from Fabric out of calculated range	See Note.
B114F66D	Operation attempted on nonfunctional Functional unit	See Note.
B114F66E	Handling CE detected by the Fabric firs and the L3 firs	See Note.
B114F6A1	Processor chip didn't have all zeros in the ring scanned	See Note.
B114F6A2	Processor chip didn't have all ones in the ring scanned	See Note.
B114F6C1	Actual Processor chip lbist signature didn't match the expected values	See Note.
B114F6D0	Processor chip abist timeout	See Note.
B114F6D1	Processor chip abist fail	See Note.
B114F6D2	Processor chip missing fusemap data in VPD	See Note.
B114F6D3	No repairs found for pending array repair	See Note.
B114F7A4	Processor gets clock errors with each clock input	See Note.
B114FB53	Wiretest has detected an EST error	See Note.
B120E500	Bad hardware	See Note.
B120F228	A memory block trying to be referenced is out of range	See Note.
B120F667	Fir bit UE (uncorrectable error) during maintenance scrub or L3 connections test display	See Note.
B120F685	Single-shot command never completed	See Note.
B121E500	Bad hardware	See Note.
B121F2DF	Undetermined failure on IAP	See Note.
B121F666	Fir bit indicates problem with memory controller	See Note.
B121F66A	Cache line write buffer CEs after a flush if Manufacturing mode set	See Note.
B121F66B	No fir bits on. Maintenance command timed out	See Note.
B121F66E	Handling CE detected by the Fabric firs and the L3 firs	See Note.
B121F684	This level of hardware does not support 8GB DIMMs that require ranks 8-15	See Note.
B121F690	Fir bit indicates MC CE	See Note.
B121F7A5	The memory controller gets clock errors with both clock inputs	See Note.
B123E500	Bad hardware	See Note.
B123F642	The DIMMs in the callout list are part of an incomplete group because of missing DIMMs	See Note.
B123F643	The DIMMS in the callout list don't match, so they form an invalid memory group	See Note.
B123F667	Fir bit UE (uncorrectable error) during maintenance scrub or L3 connections test display	See Note.
B123F669	Maintenance CE threshold exceeded during maintenance scrub or L3 connections test display	See Note.
B123F688	The DIMMS in the callout list are on a processor card that only allows quad stacked DIMMs	See Note.
B123F7BB	The system resource(s) in the callout list failed a system configuration test	See Note.
B124E500	Bad hardware	See Note.
B124F622	Failed JTAG function call	See Note.
B124F62A	POR Complete not reached on SMI2. Chip is most likely locked up	See Note.
B124F64E	PLL Lock Failure (PLL is unlocked)	See Note.
B124F65F	SMI didn't exit power down mode after Exit Power Down maintenance command executed	See Note.
B124F66C	Clock period from SMI out of calculated range	See Note.
B124F68D	Fir bit indicates problem with SP code or SMI	See Note.
B124F68E	Fir bit indicates interface problem with DIMMs	See Note.
B124F68F	Fir bit indicates interface CEs with DIMMs	See Note.
B124F690	Fir bit indicates MC CE	See Note.
B124F691	SMI Masked Fir Bit On	See Note.
B124F6C7	SMI2 lbist signature didn't match the expected values	See Note.
B125E500	Bad hardware	See Note.
B125F622	Failed JTAG function call	See Note.
B125F62A	Timed out waiting for Trimaran LBIST to complete	See Note.
B125F66C	Clock period from Trimaran out of calculated range	See Note.
B125F66E	Handling CE detected by the Fabric firs and the L3 firs	See Note.
B125F66F	Handle errors detected by L3 firs and the ebist engine	See Note.
B125F670	Handle CE detected by L3 firs	See Note.
B125F671	Trimaran not ready for ebist Command	See Note.
B125F6A7	Trimaran didn't pass setting the ring to all zeros	See Note.
B125F6A8	Trimaran didn't pass setting the ring to all ones	See Note.
B125F6C4	Trimaran lbist signature didn't match the expected values	See Note.
B125FAA1	Ebist engine timed out	See Note.
B125FAA5	L3 Address to be deleted	See Note.
B125FAA7	Error detected by EBIST engine	See Note.
B130E500	Bad hardware	See Note.
B130F2DF	Fatal IAP Error	See Note.
B131F138	Scom attention detected on the current chip	See Note.
B131E500	Bad hardware	See Note.
B131F242	The part found in RID location is not supported in this configuration	See Note.
B131F2DF	Fatal IAP Error	See Note.
B131F64B	Auto TLAR calculation failed. Acknowledge never received	See Note.
B131F64E	PLL Lock Failure (PLL is unlocked)	See Note.
B131F657	Galaxy scom operation did not complete	See Note.
B131F66C	Clock period from chip out of calculated range	See Note.
B131F6A3	Enterprise scanned ring to all 0 test failed	See Note.
B131F6A4	Enterprise scanned ring to all 1 test failed	See Note.
B131F6AF	P5IOC scanned ring to all 0 test failed	See Note.
B131F6B0	P5IOC scanned ring to all 1 test failed	See Note.
B131F6C2	Actual Enterprise chip lbist signature didn't match the expected values	See Note.
B131F6C9	Actual P5IOC chip lbist signature didn't match the expected values	See Note.
B131F6D4	Enterprise failed abist test	See Note.
B131F6DA	P5IOC failed abist test	See Note.
B132E500	Bad hardware	See Note.
B132F6A5	Winnipeg didn't pass the scan test of all zeros	See Note.
B132F6A6	Winnipeg didn't pass the scan test of all ones	See Note.
B132F6C3	Actual Winnipeg chip lbist signature didn't match the expected values	See Note.
B132F6D5	Winnipeg didn't pass abist test	See Note.
B132F7A8	Failed to enable host PCI	See Note.
B132F7A9	Failed to verify host PCI	See Note.
B133E500	Bad hardware	See Note.
B135E500	Bad hardware	See Note.
B135F62A	We timed out waiting for the PLLs to lock	See Note.
B135F6C6	CanopusPlus didn't pass setting the ring to all zeros or ones ring	See Note.
B135F6C8	LDC lbist signature didn't match the expected values	See Note.
B135F6D8	CanopusPlus abist test failed	See Note.
B1431583	Failed to get input buffer from SCED	See Note.
B1503517	Failed to determine system type	See Note.
B150355A	Error in determining FSP-A/B position	See Note.
B150355B	Error in determining FSP-A/B position	See Note.
B15035D5	Failed to close I2C ADAL	See Note.
B15035D5	Failed to close I2C ADAL	See Note.
B150B110	The P5IOC2 was not functional.	See Note.
B150D133	Server process failed	See Note.
B150E500	Bad hardware	See Note.
B150E670	Error in determining system type. We cannot determine system type because gpio read gave unsupported values	See Note.
B150E675	Failed to open I2C ADAL	See Note.
B150E676	Failed to transmit data using I2C ADAL	See Note.
B150E678	Failed to obtain control of MUX	See Note.
B150E679	Failed to setup I2C ADAL configuration	See Note.
B150E67A	Failed to obtain control of MUX	See Note.
B150E67B	Failed to close I2C ADAL	See Note.
B150E67C	Failed to receive data from I2C ADAL	See Note.
B150E67D	Failed to transmit data using I2C ADAL	See Note.
B150E67E	Failed to transmit data using I2C ADAL	See Note.
B150E67F	Failed to receive data from I2C ADAL	See Note.
B150E680	Failed to setup GPIO pins	See Note.
B150E681	Failed to read GPIO pins	See Note.
B150E691	Failed to close I2C ADAL	See Note.
B150F12C	Unmatched CRC	See Note.
B150F206	There is a card in the system that is missing or has corrupted VPD data	See Note.
B150F207	Detected a card in the system without chips	See Note.
B150F20A	Failed to create daughter card object	See Note.
B150F22A	There was not enough functional nodes found in the system to continue IPLing.	See Note.
B150F2C2	Fabric bus lost synchronization, IPL cannot continue	See Note.
B150F2DE	Elastic Interface Alignment Procedure never completed	See Note.
B150F2DF	Fatal IAP Error	See Note.
B150F2E0	Non-fatal IAP Error/Warning	See Note.
B150F2E7	There is a checkstop present prior to running FOCR Sync	See Note.
B150F239	Detected a missing chip	See Note.
B150F244	It seems that both clock cards, which should be present in the system, are not present in the system	See Note.
B150F620	Invalid bits set	See Note.
B150F627	Error detected while waiting for Trimaran display to complete	See Note.
B150F62A	Timeout while waiting for display to complete	See Note.
B150F66D	Handle errors detected by the Fabric firs and the L3 firs	See Note.
B150F805	Functional Unit procedure error	See Note.
B150F806	Procedure error	See Note.
B150F80e	Error while stopping Core clocks	See Note.
B150F80f	Error while stopping Fabric clocks	See Note.
B150F810	Error while starting Core clocks	See Note.
B150F811	Error while starting Fabric clocks	See Note.
B150F819	Error while reading data in from ring buffer or alias	See Note.
B150F81a	Error while writing ring buffers or alias to hardware	See Note.
B150F81c	Error reading from register	See Note.
B150F81d	Error writing to register	See Note.
B150FAA2	Data Miscompare found in L3 Connections test but no Fir bit on	See Note.
B150FB53	Wiretest has detected an EST error	See Note.
B150FB54	RDT has detected a hardware error	See Note.
B150FB55	Processor group pointer is NULL	See Note.
B150FB61	Processor group pointer is NULL	See Note.
B150FB64	Processor group pointer is NULL	See Note.
B150FD00	GARD Actions were performed on all items that were marked to be gard'd by the system that are not resource recoverable	See Note.
B150FD01	GARD Actions were performed on all items that were marked as gard'd manually via the menus or system gard'd items that can be resource recovered	See Note.
B1513598	Garding out FSPA due to communication fail	See Note.
B151E40A	Detected DRAM Recovered Errors	See Note.
B151E40B	Detected NVRAM Recovered Errors	See Note.
B1523592	Sibling FSP is expected but not present	See Note.
B1523599	Garding out FSPB due to communication fail	See Note.
B1551300	First level of basic input parameter validation failed	See Note.
B1551301	Second level of basic input parameter validation failed	See Note.
B1551304	Machine model invalid	See Note.
B1551305	Invalid offset type received in structure	See Note.
B1551306	Number of devices is less than or equal to zero	See Note.
B1551307	Can't open device list file	See Note.
B1551308	Data pointer is NULL	See Note.
B1551310	Failed to read root path from registry	See Note.
B1551311	Failed to read device path from registry	See Note.
B1551312	Read sink path failed	See Note.
B1551313	Read check value failed	See Note.
B1551320	No data returned from ADAL	See Note.
B1551321	Maximum arbitration retries exceeded	See Note.
B1551322	Error from the ADAL trying to set the device Master timeout	See Note.
B1551323	Write to old hub failed	See Note.
B1551324	Failed VPD dataport read	See Note.
B1551325	Failed VPD dataport write	See Note.
B1551326	Pass through to open file	See Note.
B1551330	Failed to release I2C lock	See Note.
B1551331	Failed to unlock I2C hub	See Note.
B1551332	Error unlocking hub	See Note.
B1551333	Error from ADAL trying to unlock the device behind the hub	See Note.
B1551334	Error unlocking CHUNKY device	See Note.
B1551340	Invalid operation type received in structure	See Note.
B1551341	Invalid number of nodes received in structure	See Note.
B1551342	Busy condition	See Note.
B1551343	Lock on first address of the chunky device failed	See Note.
B1551344	Error locking CHUNKY device	See Note.
B1551345	Error from ADAL trying to set the Master timeout	See Note.
B1551346	Failed to get hub type	See Note.
B1551350	Could not get the bus to start the transaction	See Note.
B1551351	Error trying to close the bus	See Note.
B1551352	Error from the ADAL trying to park the I2C mux	See Note.
B1551353	Error from ADAL trying to set Master timeout value	See Note.
B1551354	Error from ADAL trying to set device timeout value	See Note.
B1551355	Error from ADAL trying to lock the device behind the hub	See Note.
B1551356	Attempt to lock this device failed	See Note.
B1551357	Failed to set I2C lock	See Note.
B1551358	Error trying to set the bus speed in preparation for a retry	See Note.
B1551359	Error trying to read the maximum memory size of the device from the ADAL	See Note.
B155135A	Error trying to read the bus speed to see if it can be lowered for a retry	See Note.
B155135B	Write to set new hub failed	See Note.
B1551360	Write to new hub failed	See Note.
B1551361	Write to set the device failed	See Note.
B1551362	Write to set old hub failed	See Note.
B1551363	Retry at lower bus speed also failed	See Note.
B1551364	Retry after the bus reset still failed	See Note.
B1551365	Retry after bus busy condition still failed	See Note.
B1551366	Retry after loss of arbitration failed	See Note.
B1551370	Receive from device failed	See Note.
B1551371	Read from device failed	See Note.
B1551372	Failed to receive data from hub	See Note.
B1551373	Failed to receive data	See Note.
B1551380	Error trying to write register to device	See Note.
B1551381	Error trying to do the read	See Note.
B1551390	Error trying to reset bus	See Note.
B1551392	Error while closing an I2C bus or unlocking an I2C device or parking an I2C MUX	See Note.
B1551393	Failed to create network client address	See Note.
B1551394	Failed network connection between client and server	See Note.
B1551395	Communication error while trying to send or receive	See Note.
B1551396	Failed to unflatten server error log	See Note.
B1551397	Failed to close network client	See Note.
B1551398	Invalid input received from the caller	See Note.
B1551399	Error while trying to unflatten the server error log	See Note.
B155139A	Error while trying to unflatten the server error log	See Note.
B155139B	Failed to turn on FRONT light strip	See Note.
B155139C	Failed to turn on BACK light strip	See Note.
B155B006	Failed to update the Module VPD	See Note.
B155B017	Keyword can not be found in the VPD buffer	See Note.
B155B028	We failed trying to read smart chip block	See Note.
B155B02C	There was a failure trying to update one of the smart chip blocks	See Note.
B155B036	We failed trying to get smart chip block size	See Note.
B155B03D	Failed to write to I2C device	See Note.
B155B03E	Error reading from the device	See Note.
B155B03F	Reading thermal sensor data or RIO cable id failed for the given FRU	See Note.
B155B048	ECC check failed on the given FRU	See Note.
B155B04D	Checksum in the VPD data does not match calculated checksum	See Note.
B155B058	The VPD data which describes the wiring path of a FRU is invalid	See Note.
B155B05E	No valid copy of System VPD was found on this system	See Note.
B155B060	There was a mismatch in VINI record for primary and redundant root node VPD	See Note.
B155B061	Unable to use either VPD Chip because we could not reach them or they are garded out	See Note.
B155B065	Reading all blocks from smart chip failed	See Note.
B155B06D	Failed to process VPD chip	See Note.
B155B06F	No valid copy of Enclosure VPD was found on this system	See Note.
B155B070	Invalid/Un-Programmed System Serial Number (SE)	See Note.
B155B071	Invalid/Un-Programmed Serial Number in Enclosure	See Note.
B155B072	Invalid/Un-Programmed System Storage Serial Number (SG)	See Note.
B155B073	Invalid/Un-Programmed System Type Model (TM)	See Note.
B155B074	Invalid/Un-Programmed System Storage Type Model (TN)	See Note.
B155B075	Invalid/Un-Programmed System Manufacturing ID (MN)	See Note.
B155B076	Invalid/Un-Programmed System ID (ID)	See Note.
B155B077	Invalid/Un-Programmed System Unique ID (SU)	See Note.
B155B078	Invalid/Un-Programmed World Wide Node Name (NN)	See Note.
B155B079	Invalid/Un-Programmed System Brand (BR)	See Note.
B155B07D	Invalid/Un-Programmed Feature Code in Enclosure	See Note.
B155B083	Pin failure failed after root node mismatch	See Note.
B155B086	A device did not respond to an I2C or smartchip request but using other logic we found in firmware that the FRU is actually present on the system	See Note.
B155B087	We had an error in trying to detect if this FRU was actually present or not on the system	See Note.
B155B08F	We failed trying to configure bits for 9555/9554 controllers	See Note.
B155B090	We failed trying to create smart chip block	See Note.
B155B091	Error occurred while locking/unlocking DASD device	See Note.
B155B096	Unsupported bit definition found in the VPD data for record_99	See Note.
B155B0AA	Error reading from the device	See Note.
B157E500	Bad hardware	See Note.
B157F131	Last bits of chip command status are not 0x01	See Note.
B157F20D	The JTAG chain pointer was initialized to NULL and maybe do to an invalid input	See Note.
B157F244	A chip has been found to be missing	See Note.
B158E500	Bad hardware	See Note.
B158F7A3	Clock failure during test	See Note.
B158F7A4	Processor gets clock errors with each clock input	See Note.
B158F7A5	The memory controller gets clock errors with both clock inputs	See Note.
B159A070	Indicates that the Panel is being deactivated	See Note.
B15A5000	There is a hardware problem with the RTC	See Note.
B15A5002	One-time log stating that the FSP time is invalid and needs to be reset	See Note.
B15A5004	The FSP battery needs replacing	See Note.
B1701001	DMA driver has encountered an error	See Note.
B1701002	DMA driver has encountered an error	See Note.
B1701003	DMA driver has encountered an error due to hardware checkstop during a read operation in the IPL mode	See Note.
B1701004	DMA driver has encountered an error due to a target abort in the IPL mode during a read operation	See Note.
B1701005	DMA driver has encountered an unknown error in TCE mode during read operation	See Note.
B1701006	DMA driver has encountered an error due to hardware checkstop during a write operation in the IPL mode	See Note.
B1701007	DMA driver has encountered an error due to a target abort in the IPL mode during a write operation	See Note.
B1701008	DMA driver has encountered an unknown error in IPL mode during write operation	See Note.
B1701009	DMA driver has encountered an error due to hardware checkstop during a read operation in the TCE mode	See Note.
B170100A	DMA driver has encountered an error due to a target abort in the TCE mode during a read operation	See Note.
B170100D	DMA driver has encountered an error due to a target abort in the TCE mode during a write operation	See Note.
B170100F	DMA driver returned a zero	See Note.
B1701010	User given data length doesn't match with the amount of data being DMA'd	See Note.
B1701012	User given data length doesn't match with the amount of data being DMA'd	See Note.
B1701018	Failed to verify host PCI	See Note.
B1701019	Failed to enable host PCI	See Note.
B1701029	Data which is written via DMA does not match with the data being read from the same address using JTAG	See Note.
B170102A	Data which is written via DMA does not match with the data being read from the same address using DMA	See Note.
B170102B	DMA verification failed while writing random data at the host address	See Note.
B1701040	Error occurred in code	See Note.
B170901F	SPIRA does not have sufficient space for the data structure	See Note.
B1709029	Data read from mainstore is not the same as what was written to mainstore	See Note.
B170E500	Bad hardware	See Note.
B170F668	Maintenance SUE during memory preserving or exit/error state IPL	See Note.
B1748812	A Fatal system attention was received so the Service Routine failed to complete	See Note.
B175E019	Communication with the IPAP failed	See Note.
B175E01A	This entry is to record a successful communication with RETAIN, contains the PMH number and the response from retain regarding the call packet.	See Note.
B175E01B	We sent the 20 record to RETAIN, for some reason they did not ask for the first call data packet, we log this error and move on, since we did not send the error data to RETAIN it's not a success.	See Note.
B175E01C	We sent the logon record and did not get a successful response	See Note.
B175E01D	We sent the user record and did not get a successful response the machine may not be entitled	See Note.
B175E500	Bad hardware	See Note.
B1764020	Invalid data was found in the registry entry	See Note.
B1764024	The Hyperboot capability value is being changed from ENABLED to CAPABLE due to the value of Service Processor IPL type.	See Note.
B176501F	Invalid data was found in the rtim registry entry	See Note.
B1765020	The system time was changed	See Note.
B1765023	The Timed Power On was disabled due to invalid system time	See Note.
B1765024	The rtiminit daemon received an invalid command in a socket message	See Note.
B176E500	Bad hardware	See Note.
B176F687	Bit 2 set in Interrupt Register on Winnipeg	See Note.
B176F7BC	The user specified LMB size is not valid for this system's memory size, so the system will use the default LMB size for this configuration	See Note.
B17BE434	PHYP failed to send its heartbeat message within the stipulated time	See Note.
B17CE433	Hardware Management Console failed to send its heartbeat message within the stipulated time	See Note.
B1806003	Unable to complete fork operation	See Note.
B1806006	Failed to allocate memory for object	See Note.
B1806007	Error receiving message	See Note.
B1806009	Invalid state set for State Manager	See Note.
B180600A	Invalid state set for State Manager	See Note.
B180600C	Error in the size of the registry value	See Note.
B180600D	Bad size of registry value	See Note.
B180600E	Could not read the registry	See Note.
B180600F	Failed to write to the registry	See Note.
B1806010	Invalid current and next state	See Note.
B1806011	Invalid file state	See Note.
B1806013	Invalid state set for State Manager	See Note.
B180601A	Failed to reset the file open	See Note.
B180601C	Failed to decode reset values	See Note.
B180601D	Failed to allocate memory for object	See Note.
B1806021	Failed to write to message in queue	See Note.
B1806022	Failed to read from message in queue	See Note.
B1806023	Failed to look up file from required type	See Note.
B1806025	Failed to reboot	See Note.
B1806026	Failed to open map file	See Note.
B180602B	Failed to read Manufacturing flag for reset/reload	See Note.
B1806030	Invalid character	See Note.
B1806031	Error receiving log from client library	See Note.
B1806033	Failed to synchronize with the State Manager server	See Note.
B1806035	Failed IPL type	See Note.
B1806036	Validation of PCS failed	See Note.
B1806037	Tool reset occurred	See Note.
B180E500	Bad hardware	See Note.
B1811013	Failed to open DMA driver	See Note.
B1811016	Could not retrieve debug configuration information from the DMA driver	See Note.
B1811017	Could not retrieve debug configuration information from the DMA driver	See Note.
B181101A	User asking to do a zero length DMA	See Note.
B181101B	User asking to do a zero length DMA	See Note.
B181101C	Invalid FSP address received from user	See Note.
B181101D	Invalid FSP address received from user	See Note.
B181101E	Bad tag data	See Note.
B181101F	Bad tag data	See Note.
B1811020	Bad tag data	See Note.
B1811021	Cannot DMA when FSP state is between Instruction Start and OLC	See Note.
B1811022	Invalid value for bus controller	See Note.
B1811026	There has been a power off just before or during the DMA	See Note.
B1811027	Could not open file	See Note.
B1811028	Could not open file	See Note.
B181102C	Client thread that was supposed to collect DMA error data timed out	See Note.
B181102D	Event Manager constructor failed	See Note.
B181102F	Could not query the CHIC reserve identity	See Note.
B1811030	DMA event listener deleted by another DMA thread	See Note.
B1811031	Failed to wait for thread conditional	See Note.
B1811032	Failed to join with thread	See Note.
B1811033	Client thread that was supposed to collect DMA error data encountered some error	See Note.
B1811035	TCE mode shouldn't have been set before PHYP lids are loaded	See Note.
B1811036	No useful DMA error data returned	See Note.
B1811037	No HOM ID for the enterprise chip found was returned	See Note.
B1811038	Maximum number of Service Processor resource identities returned was zero	See Note.
B1811039	Service Processor resource identities is zero	See Note.
B181103A	No identity match for current FSP	See Note.
B181103B	No corresponding DMA path was returned for the current resource identity	See Note.
B181103D	No resource id for the enterprise chip found was returned	See Note.
B181103E	No HOM ID for the node found was returned	See Note.
B181103F	User gave an invalid TCE address. The upper 32 bits of the TCE token is non zero which is not a valid token.	See Note.
B1811040	Failed to get processor state	See Note.
B1811041	Current power state is undefined	See Note.
B1811044	Timeout waiting for CEC debug data	See Note.
B1811045	The MainStore address being written to is within a range which produces unpredictable results	See Note.
B1811101	Bad command given when trying to send on I2C	See Note.
B1811103	Failed to receive on slave I2C	See Note.
B1811104	Failed to send on I2C	See Note.
B1811109	Panel display line 1 data truncated	See Note.
B1811110	Panel display line 2 data truncated	See Note.
B1811112	Checksum failure	See Note.
B1811114	Failed to open I2C	See Note.
B1811115	Failed to close I2C	See Note.
B1811117	Button press/release sequence violated	See Note.
B1811118	Failed to configure I2C	See Note.
B1811119	Failed to receive on slave I2C	See Note.
B1811401	Invalid parameter passed to function	See Note.
B1811402	Failed to open I2C	See Note.
B1811403	Failed to close I2C	See Note.
B1811404	Failed to transmit on I2C	See Note.
B1811405	Failed to configure I2C	See Note.
B1811406	Message received from RPC was bigger than buffer	See Note.
B1811501	Failed to set reset	See Note.
B1811502	Failed chip select	See Note.
B1811503	Failed to set wrap enable	See Note.
B1811504	Failed to get present device	See Note.
B1811505	Failed to set GPIO lines	See Note.
B1811506	Failed to setup UART hardware to wrap	See Note.
B1811507	Failed to open UART	See Note.
B1811508	Failed to set timeout for UART	See Note.
B1811509	Failed to set automatic transmit for UART	See Note.
B181150a	Failed to set normal transmit for UART	See Note.
B181150b	Failed to set received for UART	See Note.
B181150c	Failed to write UART buffer	See Note.
B181150d	Failed to read UART buffer	See Note.
B181150e	Wrap test data compare failed	See Note.
B181150f	Failed to set functioning device	See Note.
B1811510	Failed to close UART	See Note.
B1811511	Failed to get present device	See Note.
B1811512	Failed to set reset	See Note.
B1811513	Failed to receive input deglitch from SPCN via UART	See Note.
B1811514	Failed to set present device	See Note.
B1811515	Failed to set device unit representation	See Note.
B1811516	Failed to set GPIO driver type to PUSHPULL	See Note.
B1811517	Failed to set GPIO pin	See Note.
B1811518	Failed to reset pins	See Note.
B1811519	Failed to reset pin polarity	See Note.
B181151a	Failed to set baud rate for UART	See Note.
B181151b	Failed to set parity mode for UART	See Note.
B181151c	Failed to set check mode for UART	See Note.
B181151d	Failed to set stop bit length for UART	See Note.
B181151e	Failed to set end of transmit timeout for UART	See Note.
B181151f	Failed to set end of message timeout for UART	See Note.
B1811520	Failed to select chip pins	See Note.
B1811521	Failed to get chip pins	See Note.
B1811522	Timeout waiting to receive message on UART	See Note.
B1811523	Timeout waiting to receive message on UART	See Note.
B1811524	Failed to write to UART	See Note.
B1811525	Failed to select pins for function	See Note.
B1811526	Failed to select pins for function	See Note.
B1811527	Failed to select pins for function	See Note.
B1811528	Failed to get address line setting	See Note.
B1811529	Failed to get address pins polarity	See Note.
B181152a	Failed to set address GPIO value	See Note.
B181152b	Failed to set address GPIO driver type to PUSHPULL	See Note.
B181152c	Registry Read call returned an error	See Note.
B181152d	Failed to set function line	See Note.
B181152e	Failed to close UART	See Note.
B181152f	Failed to open UART	See Note.
B1811531	A non-present device was accessed	See Note.
B1811532	Failed to prep for read/write	See Note.
B1811533	Failed to get sequence retry count	See Note.
B1811534	Failed to set next send/receive flag	See Note.
B1811535	Failed to get next send/receive flag	See Note.
B1811536	Requested transaction size too large	See Note.
B1811537	Failed to set next send sequence bit	See Note.
B1811538	Failed to set next receive sequence bit	See Note.
B1811539	Received message from smart chip is invalid	See Note.
B181153a	Failed to set next receive sequence bit	See Note.
B181153b	Failed to set next send sequence bit	See Note.
B181153c	Failed to set next send receive flag	See Note.
B181153d	Failed to set next send sequence bit	See Note.
B181153e	Failed to set next receive sequence bit	See Note.
B181153f	Failed to set next send receive flag	See Note.
B1811541	Failed to set next send sequence bit	See Note.
B1811542	Failed to set next receive sequence bit	See Note.
B1811543	Failed to execute wrap reset test	See Note.
B1811544	Failed to execute transaction	See Note.
B1811545	Failed to reset VPD devices	See Note.
B1811546	Failed reset test	See Note.
B1811547	Failed to zero all device sequence bits	See Note.
B1811548	Failed to set valid configuration flag	See Note.
B1811549	Failed to get next receive sequence bit	See Note.
B181154a	Failed to get next send sequence bit	See Note.
B181154b	Failed to reset devices	See Note.
B181154c	Failed to get valid configuration flag	See Note.
B181154d	Failed reading the configuration id from GPIO	See Note.
B181154e	The configuration id read from the GPIO pins on this system is invalid	See Note.
B181154f	Configuration registry read back test failed	See Note.
B1811550	Failed to get reserve for sced	See Note.
B1811551	Failed to reset	See Note.
B1811552	Failed to release reserve for sced	See Note.
B1811553	Non-zero response code returned	See Note.
B1811554	The number of bytes read doesn't match the bytes requested	See Note.
B1811555	Failed to send command	See Note.
B1811556	No sender id detected in call	See Note.
B1811557	Failed to get mux information from VPD	See Note.
B1811558	Failed any bytes in or out	See Note.
B1811559	Failed zero bytes in or out	See Note.
B181155a	Registry write call returned an error	See Note.
B181155b	Registry Read call returned an error	See Note.
B181155c	Failed to get file name for GPIO configuration parser	See Note.
B181155d	Failed to open file	See Note.
B181155e	Failed to read number of entries from file	See Note.
B181155f	Failed to read pin information from file	See Note.
B1811560	Invalid pointer	See Note.
B1811561	Received a undefined command type	See Note.
B1811562	Received a undefined command type	See Note.
B1811563	GPIO pin file not loaded yet	See Note.
B1811564	Bad value in pin group	See Note.
B1811565	Registry Read call returned an error	See Note.
B1811566	Failed to set device present flag to false	See Note.
B1811567	GPIO pin file not loaded yet	See Note.
B1811568	Bad value in pin group	See Note.
B181156a	Error from sced internals	See Note.
B181156b	Error from network server address	See Note.
B181156e	Failed message control	See Note.
B181156f	Failed to get message	See Note.
B1811570	Failed to create thread for sced	See Note.
B1811571	Failed to create thread for event handling	See Note.
B1811572	Failed to get path from registry for synchronization	See Note.
B1811573	Failed to bind socket for network server	See Note.
B1811574	Failed to listen on socket for network server	See Note.
B1811575	Failed to synchronize with server for sced	See Note.
B1811576	Invalid pointer returned from synchronization	See Note.
B1811577	Failed to connect to network server	See Note.
B1811578	Failed to receive from network server	See Note.
B1811579	Failed to send message	See Note.
B181157a	Reached maximum number of failures for attempts with network server	See Note.
B181157b	Message Processing Request has an unknown operation	See Note.
B181157c	Failed to get path from registry	See Note.
B181157d	Invalid current packet number	See Note.
B181157e	Failed to reset type in and zero out	See Note.
B181157f	Failed to zero single device sequence bits	See Note.
B1811580	Failed to reset single device	See Note.
B1811581	Failed to reset single VPD device	See Note.
B1811590	Failed to get reserve for sced	See Note.
B1811591	Maximum number of pin failures has been reached	See Note.
B1811596	Failed to get reserve for sced	See Note.
B1811597	Failed to get reserve for sced	See Note.
B181159A	Parsing of return packet failed	See Note.
B181159D	Received an unexpected signal	See Note.
B1812000	Unexpected signal received	See Note.
B1812001	Failed to open file	See Note.
B1812002	Failed to initialize trace	See Note.
B1812003	No name for thread in trace	See Note.
B1812004	Error reading from registry	See Note.
B1812005	Error setting up iterator for SRCs	See Note.
B1812006	Failed to get SRC from SRC iterator	See Note.
B1812007	Invalid pointer	See Note.
B1812008	Failed to lock the mutex	See Note.
B1812009	Failed to unlock the mutex	See Note.
B181200a	Error from event manager constructor	See Note.
B181200b	Error from event management monitor	See Note.
B181200c	Error from event management signal	See Note.
B1812017	Could not initialize queue mutex	See Note.
B1812018	The condition variables could not be initialized	See Note.
B1812019	The condition variables could not be destroyed	See Note.
B181201a	Could not destroy queue mutex	See Note.
B181201b	A power fault has been detected	See Note.
B181201c	Failed to wait on thread conditional	See Note.
B181201d	Failed to write to registry	See Note.
B181201e	Failed to signal on thread conditional	See Note.
B181201f	Failed to create notify thread	See Note.
B1812020	Failed to cancel the threads	See Note.
B1812021	Failed to set cancel state of thread	See Note.
B1812023	Failed to join to thread created	See Note.
B1812024	Failed to communicate with SPCN	See Note.
B1812025	Failed to stop communication with SPCN	See Note.
B1812026	Thread is being canceled while in the middle of sending a command to SPCN	See Note.
B1812027	Server has routed an acknowledgment message to the command queue	See Note.
B1812028	The command was rejected by SPCN	See Note.
B1812029	Could not send a message through the interface to SPCN	See Note.
B181202a	Could not read a message from the interface to SPCN	See Note.
B181202b	Failed to create network server object	See Note.
B181202c	Failed to listen to socket for network server	See Note.
B181202d	Failed process synchronization with client	See Note.
B181202e	Failed to close network server	See Note.
B181202f	Failed to connect to network server	See Note.
B1812030	Failed to receive from network server	See Note.
B1812031	Failed to bind to socket for network server	See Note.
B1812032	Incorrect data received	See Note.
B1812033	The delayed response has been aborted and the caller is prohibited from attempting to update the socket value	See Note.
B1812034	Failed to get configuration ID from SPCN	See Note.
B1812035	Failed to set configuration ID	See Note.
B1812036	Failed to deattach thread	See Note.
B1812037	Error getting subfunction ranges for SPCN panel function	See Note.
B1812038	The notification cannot be sent to state manager because the fsp is not in a particular state	See Note.
B1812039	Error from state manager power off notification	See Note.
B181203a	Error from state manager power on notification	See Note.
B181203b	The condition was not satisfied before specified interval	See Note.
B181203c	Failed to wait for thread conditional	See Note.
B181203d	Server queue is full	See Note.
B181203e	Server queue is empty	See Note.
B181203f	Already started server	See Note.
B1812040	Unrecognized command	See Note.
B1812041	Failed to get path from registry	See Note.
B1812042	Failed direct command to SPCN	See Note.
B1812043	Failed to get maximum number of RIDs from SVPD	See Note.
B1812044	Unexpected SVPD data	See Note.
B1812045	Failed to get RIDs from SVPD	See Note.
B1812046	Failed to figure out which FSP running on	See Note.
B1812047	Timed out waiting for an acknowledgment	See Note.
B1812048	Failed to set UPS status for SPCN	See Note.
B1812049	Error from SPCN when trying to power off I/O	See Note.
B181204A	Error from SPCN command line handler	See Note.
B1812100	Failed to initialize	See Note.
B1812102	Failure creating thread	See Note.
B1812103	Pipe system call failed	See Note.
B1812104	System call failed	See Note.
B1812105	Select system call failed	See Note.
B1812106	Invalid parameter passed to function	See Note.
B1812107	Could not create message queue	See Note.
B1812108	Received invalid command from RPC device	See Note.
B1812109	Invalid function ID from message	See Note.
B181210A	Timeout receive though no timeout was given	See Note.
B181210B	Expected file descriptor not set after select call	See Note.
B181210C	Failed to do an I2C slave address change on a redundant FSP failover	See Note.
B181210D	Could not insert initial events into queue	See Note.
B181210E	Error removing message from queue	See Note.
B181210F	Failed to get power state	See Note.
B1812110	Failed IPL lock function	See Note.
B1812111	Failed to close network server	See Note.
B1812112	Error from Event Manager	See Note.
B1812113	Could not create token queue	See Note.
B1812114	Could not insert tokens into token queue	See Note.
B1812115	Over total thread threshold	See Note.
B1812201	Failed to open and lock the IPL Lock data file	See Note.
B1812202	Failed to unlock and/or close the IPL Lock data file	See Note.
B1812203	Failed to initialize the header of the IPL Lock data file	See Note.
B1812204	Failed to read from registry	See Note.
B1812205	Failed to position the cursor in the file or read the header from the file	See Note.
B1812206	Failed to position the cursor in the file or write the lock information to the file	See Note.
B1812207	Failed to read lock information	See Note.
B1812208	Failed to write the new lock information to the IPL Lock data file	See Note.
B1812209	Failed to read the header in the IPL Lock data file	See Note.
B181220A	Failed to update new header in IPL Lock data file	See Note.
B181220B	Invalid parameter passed into function	See Note.
B181220C	Invalid power state for IPL requested	See Note.
B181220D	Failed to get current power state of system	See Note.
B181220E	Failed to open and lock the IPL Lock data file	See Note.
B181220F	Failed to close and/or unlock the IPL Lock data file	See Note.
B1812210	No locks exist or the requested lock exceeds the total number of locks that exist	See Note.
B1812211	A lock by the requesting component still exists and is active	See Note.
B1812212	An error occurred trying to find the lock for the component	See Note.
B1812213	Failure to allocate memory for timer thread structure	See Note.
B1812214	Failure to create timer thread for lock	See Note.
B1812215	Failure to remove requested lock	See Note.
B1812216	Component requesting refresh does not have a lock in the IPL Lock data file	See Note.
B1812218	IPL requested is blocked due to an IPL lock	See Note.
B1812219	Value passed in to set Power IPL in Progress to was out of range	See Note.
B181221A	Emergency IPL was received and locks were bypassed	See Note.
B181221B	IPL was rejected by State Manager or the acknowledge was not accepted	See Note.
B181221C	A Power IPL has already been requested and queued	See Note.
B181221D	Failed to send Power On event to Panel for requested IPL	See Note.
B181221E	Failed to send Power Off event to Panel	See Note.
B181221F	Failed fork system call	See Note.
B1812220	Failed to start IPL Power process due to not being able to replace current executable with IPL Power process	See Note.
B1812221	Invalid argument was passed into the timer thread	See Note.
B1812222	Invalid signal received	See Note.
B1812223	Failure to detach timer thread so memory resources will not be freed upon termination of the timer thread	See Note.
B1812224	A Power IPL is in progress	See Note.
B1812225	Failed to get Power IPL in Progress indicator	See Note.
B1812226	Failed to write to Power IPL in Progress registry variable	See Note.
B1812227	Failed to indicate that a Power IPL will be in progress	See Note.
B1812228	Failed to get current and next state	See Note.
B1812229	Failed to read current FSP Role from registry	See Note.
B181222A	An invalid pointer was passed into the function	See Note.
B181222B	Failed to determine the size of the IPL Lock data file	See Note.
B181222C	An error occurred trying to get current ticks	See Note.
B1812300	Unexpected signal received	See Note.
B1812301	Failed fork operation	See Note.
B1812304	Error while querying for CEC termination	See Note.
B1812305	Synchronization with State Manager failed	See Note.
B1812306	Failed to read maximum size of error	See Note.
B1812307	Failed to write to registry	See Note.
B1812308	Error creating termination iterator	See Note.
B1812309	Failed to read termination SRC	See Note.
B181230B	Failed to read path from registry	See Note.
B181230C	Error from event monitor	See Note.
B181230D	Server not ready or daemon is not running	See Note.
B181230E	Failed to synchronize with client	See Note.
B181230F	Error returned from IPL lock function	See Note.
B1812311	Error from event manager constructor	See Note.
B1812401	Failed to write WOL Policy to registry	See Note.
B1812402	Failed to read WOL Policy from registry	See Note.
B1812403	Failed to HIGH-LOW-HIGH the Wake on LAN reset line	See Note.
B1812404	Failure to setup Wake on LAN reset line	See Note.
B1812405	Failed to get current power state, so we were not able to activate the Wake on LAN hardware	See Note.
B1812406	Invalid signal received	See Note.
B1812407	Failed to activate Wake on LAN hardware	See Note.
B1812408	Failed to IPL the system via Wake on LAN	See Note.
B1812409	Failed to get Wake on LAN Policy	See Note.
B181240A	The value for the Wake on LAN Policy is out of range for what is acceptable	See Note.
B181240B	Failed fork system call	See Note.
B181240C	An error was returned as we tried to wait for the Wake on LAN interrupt line	See Note.
B181240D	An error occurred processing the Wake on LAN interrupt	See Note.
B181240E	Failed to get root path from the registry.	See Note.
B181240F	A daemon is already up and running	See Note.
B1812410	Failed to create the daemon synchronization file	See Note.
B1812411	Due to the type of machine, the Wake on LAN functionality is not supported	See Note.
B1812412	Failed to read current state data from registry	See Note.
B1812413	Failed to read FSP Role from registry	See Note.
B1812414	Failed to read machine model type from registry	See Note.
B1812415	Failed to read operational mode from registry	See Note.
B1813001	Someone is already updating code	See Note.
B1813002	Registry read fails	See Note.
B1813003	Registry write fails	See Note.
B1813006	Lid Entry is not found. The specified Lid number is not in the specified Masterlid file	See Note.
B1813007	Invalid Lid number	See Note.
B1813008	Lid is not valid	See Note.
B1813009	Request to update the wrong lid	See Note.
B181300A	Requestor did not start the update	See Note.
B181300C	Type of code update is already set	See Note.
B181300D	Invalid flash side	See Note.
B181300E	In correct flash side	See Note.
B181300F	Header has invalid magic number	See Note.
B1813010	System command fails to remove a file	See Note.
B1813011	File open error	See Note.
B1813012	Lid does not exist	See Note.
B1813013	Someone is currently updating the specified lid	See Note.
B1813014	Request IPL lock or unlock fails	See Note.
B1813015	Lid class is invalid	See Note.
B1813016	Specified buffer is too small for the requesting data	See Note.
B181301F	Updating on the running side is not allowed	See Note.
B1813020	Update good flash side, when other side is invalid	See Note.
B1813022	CRC miscompare	See Note.
B1813025	Invalid data size is detected	See Note.
B1813028	IPL lock refresh fails	See Note.
B1813029	Invalid component id	See Note.
B181302A	Lid is currently being modified by someone	See Note.
B1813030	Invalid code type	See Note.
B1813031	Invalid Marker Lid version	See Note.
B1813034	Invalid operation state	See Note.
B1813035	Offset is exceeding the file size	See Note.
B1813036	Someone requests code update termination	See Note.
B1813038	Unable to create event	See Note.
B1813039	Unable to create thread to monitor the power lock timeout	See Note.
B181303a	Lid does not belong to FSP	See Note.
B181303b	The power log flag is not set	See Note.
B181303d	Invalid data	See Note.
B181303e	Function call fails	See Note.
B181303f	Reading offset to partition table failed	See Note.
B1813040	Write the partition name to a specific partition table entry failed	See Note.
B1813041	Seek file from the end of file failed	See Note.
B1813042	The status of the MTD device failed	See Note.
B1813043	Invalid Genus size	See Note.
B1813044	Incorrect file for update	See Note.
B1813045	Unable to find keyword that indicate bank id	See Note.
B1813047	The system has redundant FSP	See Note.
B1813048	The specified arguments for major/minor number are out of range	See Note.
B1813049	The filename that is passed in does not start with a '/'	See Note.
B181304a	The status of the MTD device failed	See Note.
B181304f	Invalid operation	See Note.
B1813050	Unknown signal	See Note.
B1813501	Error in call to other component interface	See Note.
B1813503	Error received from sibling FSP	See Note.
B1813509	Error setting network parameters for various Ethernet interfaces	See Note.
B181350B	Error creating network client object	See Note.
B181350C	We detected a sibling but the communication broke down in between	See Note.
B181350D	Error configuring various Ethernet interfaces	See Note.
B181350F	Error in call to other component interface	See Note.
B1813511	Error sending data to sibling	See Note.
B1813515	Error obtaining mux information	See Note.
B1813516	Error in interface call to other component	See Note.
B1813519	Bad command received from sibling FSP	See Note.
B181351A	Communication to sibling failed	See Note.
B181351B	Error reading FSP State	See Note.
B181351C	Error waiting for an event	See Note.
B181351E	Error getting time of day	See Note.
B181351F	Error setting time of day	See Note.
B1813520	Error indicating that sibling FSP was already garded	See Note.
B1813521	Error creating a event object	See Note.
B1813523	Error creating network client object	See Note.
B1813524	We detected a sibling but the communication broke down in between	See Note.
B1813525	We detected a sibling but the communication broke down in between	See Note.
B1813527	Failed to read from registry	See Note.
B1813528	Failed to read size from registry	See Note.
B1813529	We detected a sibling but the communication broke down in between	See Note.
B181352A	Error reading registry entry size	See Note.
B181352B	Error writing pass phrase to registry entry	See Note.
B181352C	Error reading sibling Ethernet port 0 registry entry	See Note.
B181352D	Error writing to sibling Ethernet port 0 registry entry	See Note.
B181352E	Error reading sibling Ethernet port 1 registry entry.	See Note.
B181352F	Error writing to sibling ethernet port 1 registry entry.	See Note.
B1813531	Error writing MTMS to file	See Note.
B1813532	Error reading registry entry size	See Note.
B1813533	Error reading registry entry	See Note.
B1813534	Error reading/writing from file	See Note.
B1813535	Error reading/writing from file	See Note.
B1813536	Error reading/writing from file	See Note.
B1813537	Error reading/writing from file	See Note.
B1813538	Error reading/writing from file	See Note.
B1813539	Error reading/writing from file	See Note.
B181353A	Error reading/writing from file	See Note.
B181353B	Error reading/writing from file	See Note.
B181353C	Error in network operation	See Note.
B181353D	Error in network operation	See Note.
B181353E	Error in network operation	See Note.
B181353F	Error in network operation	See Note.
B1813540	Error in network operation	See Note.
B1813541	Error in network operation	See Note.
B1813542	Error in network operation	See Note.
B1813543	Error in network operation	See Note.
B1813544	Error in network operation	See Note.
B1813545	Error in network operation	See Note.
B1813546	Error in network operation	See Note.
B1813547	Error in network operation	See Note.
B181354A	Error in network operation	See Note.
B181354B	Error in call to other component interface	See Note.
B181354C	Error in network operation	See Note.
B181354D	Error in call to other component interface	See Note.
B1813550	Error in network operation	See Note.
B1813551	Error in call to other component interface	See Note.
B1813552	Error in network operation	See Note.
B1813553	Error in call to other component interface	See Note.
B1813554	Error in network operation	See Note.
B1813555	Error in call to other component interface	See Note.
B1813556	Error in network operation	See Note.
B1813557	Error in network operation	See Note.
B1813558	Error in reading FSP Role registry	See Note.
B1813559	Error in call to other component interface	See Note.
B181355C	Error in call to other component interface	See Note.
B181355D	Error in call to other component interface	See Note.
B181355E	Error in call to other component interface	See Note.
B181355F	Error in call to other component interface	See Note.
B1813560	Error in call to other component interface	See Note.
B1813561	Error in call to other component interface	See Note.
B1813562	Error in network operation	See Note.
B1813563	Error in call to other component interface	See Note.
B1813564	Error in call to other component interface	See Note.
B1813569	Error in network operation	See Note.
B181356A	Error writing MTMS to file	See Note.
B181356F	Error reading/writing from file	See Note.
B1813570	Error reading/writing from file	See Note.
B1813579	Error setting network parameters for various ethernet interface	See Note.
B181357A	Error in interface call to other component	See Note.
B181357B	Error trying to setup initial communication between FSP's	See Note.
B181357C	Error in call to other component interface	See Note.
B181357D	Error in call to other component interface	See Note.
B181357E	Error in interface call to other component	See Note.
B181357F	Error starting Surveillance	See Note.
B1813580	Error in call to other component interface	See Note.
B1813581	Error in network operation	See Note.
B1813582	Error in network operation	See Note.
B1813583	Error in interface call to other component	See Note.
B1813584	Error sending data to sibling	See Note.
B1813585	Error sending data to sibling	See Note.
B1813586	Error sending data to sibling	See Note.
B1813587	Error sending data to sibling	See Note.
B1813588	Error sending data to sibling	See Note.
B1813589	Error sending data to sibling	See Note.
B181358A	Error in call to other component interface	See Note.
B181358B	Error in call to other component interface	See Note.
B181358C	Error in interface call to other component	See Note.
B181358D	Error while making open call to I2C adal	See Note.
B181358F	Error while making open call to I2C adal	See Note.
B1813591	Error while making open call to I2C adal	See Note.
B1813592	Sibling FSP is expected but not present	See Note.
B1813593	Error in call to other component interface	See Note.
B1813594	Error in call to other component interface	See Note.
B1813595	Discovery abort was requested	See Note.
B1813596	Error in call to other component interface	See Note.
B1813597	Error in putting message in message queue	See Note.
B181359A	Error while making open call to I2C adal	See Note.
B181359B	Error while making open call to I2C adal	See Note.
B181359E	Error setting up passwords	See Note.
B181359F	Error closing client socket	See Note.
B18135A0	Error closing server socket	See Note.
B18135A1	Invalid request to Discovery thread	See Note.
B18135A2	Eth0 IP address on FSP-B was set to default	See Note.
B18135A3	Eth1 IP address on FSP-B was set to default	See Note.
B18135A4	Error while making open call to I2C adal	See Note.
B18135A5	Exceeded maximum number of retries for communication errors between FSP's in various states	See Note.
B18135A6	Error in interface call to other component	See Note.
B18135A7	Error in interface call to other component	See Note.
B18135A8	Error in interface call to other component	See Note.
B18135A9	Both FSPs were reset	See Note.
B18135AA	Both FSPs were reset	See Note.
B18135AB	Both FSPs were reset	See Note.
B18135AC	Error sending data to sibling	See Note.
B18135AD	Error reading registry	See Note.
B18135AE	Error exchanging data with sibling	See Note.
B18135AF	Error receiving data from sibling	See Note.
B18135B0	Error writing registry	See Note.
B18135B1	Error receiving data from sibling	See Note.
B18135B2	Error exchanging data to/from sibling	See Note.
B18135B3	Error in data received from sibling	See Note.
B18135B4	Error receiving data from sibling	See Note.
B18135B5	Error in call to other component interface	See Note.
B18135B6	Error in call to other component interface	See Note.
B18135B7	Error in call to other component interface	See Note.
B18135B8	Error receiving data from sibling	See Note.
B18135B9	Error receiving data from sibling	See Note.
B18135BA	Error sending data to sibling	See Note.
B18135BB	Error writing registry	See Note.
B18135BC	Error receiving data from sibling	See Note.
B18135BD	Error sending data to sibling	See Note.
B18135BE	Error receiving data from sibling	See Note.
B18135BF	Error receiving data from sibling	See Note.
B18135C0	Error receiving data from sibling	See Note.
B18135C1	Eth1 IP address on FSP-B was set to default	See Note.
B18135C2	Eth1 IP address on FSP-B was set to default	See Note.
B18135C3	Reset of both FSPs. Possible new role assigned to FSP-A	See Note.
B18135C4	Reset of both FSPs. Possible new role assigned to FSP-A	See Note.
B18135C5	Reset of both FSPs. Possible new role assigned to FSP-A	See Note.
B18135C8	Gard did not return back a status but indicated a failure in the output parameter of their routine	See Note.
B18135C9	Error in call to other component interface	See Note.
B18135CA	Error in call to other component interface	See Note.
B18135CB	Error in call to other component interface	See Note.
B18135CC	Error in call to other component interface	See Note.
B18135CD	Error in putting message in message queue	See Note.
B18135CE	Error from network client gateway	See Note.
B18135CF	Error from network client gateway	See Note.
B18135D0	Registry entry indicates that a serial communication error is to be simulated	See Note.
B18135D1	Error reading serial error injection registry	See Note.
B18135D2	Error in putting message in message queue	See Note.
B18135D3	Error in putting message in message queue	See Note.
B18135D4	Error in call to other component interface	See Note.
B18135D7	Error while making open call to I2C adal	See Note.
B18135D8	Error in interface call to other component	See Note.
B18135D9	Error in interface call to other component	See Note.
B18135DA	Error in interface call to other component	See Note.
B18135DB	Error indicating that sibling FSP was already garded	See Note.
B1814000	Invalid command	See Note.
B1814001	Missing argument	See Note.
B1814002	Invalid argument	See Note.
B1814003	Invalid data received for process message operation number	See Note.
B1814004	Wrong number of arguments given to command	See Note.
B1814005	An error occurred reserving the semaphore	See Note.
B1814006	Received unexpected signal	See Note.
B1814006	Receive unexpected signal	See Note.
B1814007	A side switching IPL is not allowed for the given type of CEC IPL	See Note.
B1814008	A side switching IPL is needed, but the code is not valid on that side	See Note.
B1814008	A side switch reboot could not be performed because the code is not valid on the new next side	See Note.
B1814016	Invalid data was received for next system operation mode	See Note.
B1814016	Invalid data was received for system click to accept state	See Note.
B1814017	Invalid data was received for next platform IPL side	See Note.
B1814018	Invalid data was received for next system IPL mode	See Note.
B1814019	Invalid data was received for next platform IPL speed	See Note.
B181401A	Invalid data was received for next platform IPL speed override	See Note.
B181401B	Invalid data was received for next Hypervisor IPL state	See Note.
B181401C	Invalid data was received for next RPA partition IPL mode	See Note.
B181401D	Invalid data was received for next CEC LMB size	See Note.
B1814021	The daemon could not get the lock	See Note.
B1814022	Failed fork system call	See Note.
B1814023	The daemon rebooted the FSP to Standby because the P2 registry data that controls labeling of Permanent and Temporary Flash images was replaced with P3 registry backup data.	See Note.
B1814025	Called interface not supported in context	See Note.
B1815001	Received unexpected signal	See Note.
B1815005	Invalid data received	See Note.
B1815006	An attempt was made to write to the system clock without proper user authority	See Note.
B1815007	The GPIO ADAL returned an error while reading the battery alert pin	See Note.
B1815008	A registry read error occurred	See Note.
B181501B	An undefined operation was requested	See Note.
B181501C	Error reading using Time of Day ADAL	See Note.
B181501D	Error writing using Time of Day ADAL	See Note.
B181501E	Error writing using Time of Day ADAL	See Note.
B1815021	The daemon could not get the lock	See Note.
B1815022	Failed fork system call	See Note.
B1815025	Failed to create thread	See Note.
B1815026	The elapsed time since IPL Parameters time data was built was calculated with the RTC and TOD counter. The two results are off by more than 8 seconds.	See Note.
B1815027	The TOD counter was checked after writing, and was off by more than 65536 ticks (0.524 sec).	See Note.
B1815029	Failed to create RMGR synchronization thread	See Note.
B1816009	Invalid state set for State Manager	See Note.
B1816010	Invalid current and next state	See Note.
B181601C	Failed to decode reset values	See Note.
B1817000	Failure to create thread	See Note.
B1817003	Failed network server connection	See Note.
B1817004	Failed to receive message from network	See Note.
B1817005	Failed to close network connection	See Note.
B1817006	Failure to establish communications pipe	See Note.
B1817007	PHYP was not ready to be communicated with	See Note.
B1817008	Failed to write data	See Note.
B1817009	Failure reading data	See Note.
B181700A	Load SRC failed	See Note.
B181700D	Failed to read from or write to registry	See Note.
B1817010	Error reading data from server communications pipe	See Note.
B1817011	Data size mismatch	See Note.
B1817012	Error/Event notification throughout the system has failed for the given platform event log	See Note.
B1817013	Failed to scan for error/event logs	See Note.
B1817015	Error while attempting to change state	See Note.
B1817016	Corrupt input data	See Note.
B1817018	A log was picked up and the unique id assigned to it is zero	See Note.
B1817019	Error received while attempting to turn on virtual platform service indicator	See Note.
B181701A	The section identifier read from the data does not match the section id of the current object	See Note.
B181701B	Invalid section size detected	See Note.
B181701C	Section version mismatch	See Note.
B181701D	Section count mismatch	See Note.
B181701E	Failed to send or receive on network	See Note.
B181701F	Unhandled signal received	See Note.
B1817020	Invalid input or data	See Note.
B1817021	File system failure	See Note.
B1817022	FSP call home attempt has failed	See Note.
B1817024	Failed to initialize the history log, logging cannot continue if the physical file cannot be initialized	See Note.
B1817025	Request to clear error/event logs has been processed	See Note.
B1817026	Error/Event logging server started	See Note.
B1817028	Error/Event log created from system log message	See Note.
B1817029	Linux system call failed	See Note.
B181702A	Error unloading virtual headers due to lack of file allocation space	See Note.
B181702B	Timeout waiting for sibling FSP command to complete	See Note.
B181703E	Unknown failure	See Note.
B1817102	Failed to setup process error recovery	See Note.
B1817107	Host driver or registry failure	See Note.
B181710B	Event manager failed	See Note.
B181710D	Event detection failed	See Note.
B1817112	Software failure resulted in a signal	See Note.
B1817113	Event loop exited	See Note.
B1817114	Failed to change directory	See Note.
B1817115	Failed to set session identity	See Note.
B1817200	User requested to boot from a side that is marked invalid	FSPSP02
B1817201	FSP had a kernel panic during last boot	FSPSP02
B1817202	Both FSP code banks are marked invalid	FSPSP02
B1817203	Error writing to Persistent Control Store (PCS)	FSPSP02
B1817204	Error reading from PCS	FSPSP02
B1817205	FSP Boot code failed during last boot causing the FSP to reset again	FSPSP02
B1817206	FSP had a Unit check timer reset	FSPSP02
B1817209	FSP had a Watchdog timeout reset	FSPSP02
B181720A	FSP had an internal hardware error	FSPSP02
B1818103	Failed to write to registry	See Note.
B1818106	Invalid bus owner argument	See Note.
B1818107	Invalid number of command line arguments	See Note.
B1818108	No argument value for --r option	See Note.
B1818109	Multiple -c arguments	See Note.
B181810A	-s option specified with -c	See Note.
B181810B	Multiple -s arguments	See Note.
B181810C	-c options specified with -s	See Note.
B181810D	Invalid command line option	See Note.
B181810E	Non-option element(s)	See Note.
B181810F	Null input numeric string	See Note.
B1818110	Empty input numeric string	See Note.
B1818111	Invalid character encountered in conversion	See Note.
B1818114	Failed to stop instructions	See Note.
B1818115	Failed to send signal for event manager	See Note.
B1818116	Failed to get processor state	See Note.
B1818203	Requested index is out of range	See Note.
B1818204	Failed to open given directory	See Note.
B1818211	Could not understand operation requested	See Note.
B1818212	Unexpected result	See Note.
B1818213	Invalid data	See Note.
B1818214	Incorrect input size (too small or too large)	See Note.
B1818215	A generic stream failure has been detected	See Note.
B1818216	Failed to write to file	See Note.
B1818217	The Callout substructure cannot be identified	See Note.
B1818218	Unhandled signal received	See Note.
B1818301	Already in the terminate state	See Note.
B1818302	Already in the power off state	See Note.
B1818303	Currently processing a power off request from SPCN	See Note.
B1818304	Currently processing an FSP terminate request from another component	See Note.
B1818305	Failed state manager termination request	See Note.
B1818307	Failed power transition request	See Note.
B1818309	Too many client connections	See Note.
B181830B	Thread timed out while waiting for another busy thread to complete	See Note.
B181830D	Client request thread started with invalid pointer	See Note.
B181830E	Another instance of the server is already running	See Note.
B1818310	Timed out waiting for thread conditional	See Note.
B1818312	Failed to receive on network	See Note.
B1818313	Failed to connect to server over network	See Note.
B1818316	Failed to trace SRC on termination trace	See Note.
B1818317	Failed to read the registry	See Note.
B1818318	Could not update the CEC termination state	See Note.
B181831A	No log passed in. Will use default log to terminate system.	See Note.
B181831C	Couldn't retrieve the embedded SRC from error log	See Note.
B181831D	Failed to initialize thread attributes	See Note.
B181831E	Failed to set deattach state for thread	See Note.
B1818320	Failed to bind socket	See Note.
B1818321	Failed to lock the mutex	See Note.
B1818322	Could not cancel all the client request processing threads	See Note.
B1818323	Unknown error	See Note.
B1818328	Could not unflatten log object from the received byte stream	See Note.
B1818329	Log size maximum is less than the client data length	See Note.
B181832A	Zero data length	See Note.
B181832C	Failed to construct event manager	See Note.
B1818330	Failed to bind socket	See Note.
B1818331	Failed to create thread	See Note.
B1818333	Cannot reset CEC termination in the middle of a power fault request	See Note.
B1818336	Unknown FSP role returned	See Note.
B1818337	Already in the terminated state with force failover option	See Note.
B1818338	Currently processing an FSP terminate request with force failover option from another component	See Note.
B1818341	Failed to flatten log	See Note.
B1818344	Bad length on flattened log	See Note.
B1818345	Server aborted or failed to connect to network	See Note.
B1818346	Server aborted or failed to send or receive on the network	See Note.
B1818347	Server not running	See Note.
B181834A	P0 root path not defined	See Note.
B1818500	Incorrect number of arguments	See Note.
B1818501	The caller wanted to get event related data but the buffer pointer is invalid	See Note.
B1818502	The daemon received a message with an invalid function field	See Note.
B1818503	Error returned from another component	See Note.
B1818504	Failed system call	See Note.
B1818505	Failed fork system call	See Note.
B1818507	Error trying to forward an event to 1 or more subscribers	See Note.
B1818508	The id of a tool request is invalid	See Note.
B1818509	Unexpected signal received	See Note.
B181850E	The user specified a time limit to wait for an event and limit was reached	See Note.
B181850F	Another thread is waiting	See Note.
B1818600	Application has received an unexpected signal	See Note.
B181860D	Application has not setup process error recovery	See Note.
B181860E	Killing process without having process error recovery setup	See Note.
B181860F	Process continues to get killed. Caught in a loop.	See Note.
B1818610	Application has received an unexpected signal	See Note.
B1818700	Error in selecting communicating socket	See Note.
B1818701	Failed to listen to socket for network server	See Note.
B1818702	Failed to bind to socket for network server	See Note.
B1818703	Failed to bind for TCP/IP	See Note.
B1818704	Error in accepting socket	See Note.
B1818705	Error in processing message from serial	See Note.
B1818706	Error in accepting socket	See Note.
B1818708	Error creating unique key for message queue	See Note.
B1818709	Error in creating message queue	See Note.
B181870A	Error in queueing messages	See Note.
B181870B	Error in receiving message from queue when processing message	See Note.
B181870C	Failed to read registry	See Note.
B181870D	Error in creating inbound thread	See Note.
B181870F	Error in inbound connection	See Note.
B1818711	Error in receiving messages	See Note.
B1818714	Error processing message	See Note.
B1818718	Error in send message in DVS	See Note.
B181871B	Failed to destroy old message queue	See Note.
B181871E	Error in IPC address creation	See Note.
B181871F	Error in closing inbound socket	See Note.
B1818728	Can't remove the previous mount	See Note.
B181872A	Failed in registry read	See Note.
B181872C	Failed in file write	See Note.
B181872E	Can't activate user configuration setup file	See Note.
B1818730	Error in writing system name	See Note.
B1818731	Invalid user	See Note.
B1818736	Failed to set user password	See Note.
B1818737	Failed to validate password	See Note.
B1818738	Error in initial outbound remote thread setup	See Note.
B1818739	Failed to kill thread in outbound	See Note.
B181873A	Failure from remote message object	See Note.
B181873B	Failed to requeue message	See Note.
B181873C	Error in operation should not kill	See Note.
B181873D	Failed to destroy old message queue	See Note.
B181873F	Failed to create thread	See Note.
B1818740	Failed to create thread	See Note.
B1818748	Failed to read from registry	See Note.
B181874C	Serial message is invalid	See Note.
B1818752	Failed to open port for connection	See Note.
B1818753	Failed to configure baud for UART	See Note.
B1818755	Failed to set status field to failure for PHYP	See Note.
B1818756	Failed to verify dynamic password	See Note.
B1818759	Failed to write password signature	See Note.
B1818760	Failed to write Manufacturing password signature	See Note.
B1818762	Failed to configure parity for UART	See Note.
B1818763	Failed to configure UART to transmit normal	See Note.
B1818764	Failed to auto receive on UART	See Note.
B1818765	Failed to configure UART to transmit automatically	See Note.
B1818767	Error from perc	See Note.
B1818768	Error in getting machine type VPD	See Note.
B1818769	Error in getting machine serial number	See Note.
B181876A	Error in reading machine brand name	See Note.
B181876B	Error initializing network serial server daemon	See Note.
B181876C	Failed to get a file descriptor	See Note.
B181876D	Error from status of file	See Note.
B181876E	Improper error path	See Note.
B181876F	Failed to write Manufacturing password signature	See Note.
B1818770	Illegal socket descriptor selected	See Note.
B1818771	Improper error path	See Note.
B1818772	Failed to get registry key status information	See Note.
B1818773	Failed to get registry key status information	See Note.
B1818776	Failed to configure UART	See Note.
B1818777	Failed to configure UART for loop back	See Note.
B1818778	Failed to configure UART	See Note.
B1818780	Failed to read registry	See Note.
B1818781	Failed to open file	See Note.
B1818782	Failed to get file handle	See Note.
B1818783	Socket creation failed	See Note.
B1818785	Socket bind error	See Note.
B1818786	Failed in socket listen	See Note.
B1818787	Failed in file write	See Note.
B1818788	Invalid client name length	See Note.
B181878A	Failure to get free entry	See Note.
B181878C	Failed in registry read	See Note.
B181878D	Update session entry failure	See Note.
B181878E	Session entry read failed	See Note.
B181878F	Invalid lookup entry for maximum entry	See Note.
B1818791	Failed to seek file offset	See Note.
B1818792	Session entry not found	See Note.
B1818793	Session entry read failed	See Note.
B1818795	Failed to seek session entry	See Note.
B1818796	Update session write failed	See Note.
B1818797	Invalid process id value	See Note.
B1818799	Invalid constructor area	See Note.
B181879A	Failed in socket creation	See Note.
B181879B	Failed to read path for socket from registry	See Note.
B181879D	Failed to construct network client	See Note.
B181879E	Failed to allocate memory for a message	See Note.
B181879F	Failed to allocate memory for a message	See Note.
B18187A0	Length of the message buffer is incorrect	See Note.
B18187A1	Invalid pointer	See Note.
B18187A2	Invalid pointer	See Note.
B18187A3	Invalid pointer	See Note.
B18187A4	Invalid pointer	See Note.
B18187A5	Failed to get channel string id to server	See Note.
B18187A7	Failed to connect using UNIX	See Note.
B18187A8	Error in network connection using UNIX	See Note.
B18187AB	Failed to receive data from the network client	See Note.
B18187AC	Failed to connect using TCP/IP	See Note.
B18187AD	Failed to connect using UNIX	See Note.
B18187AF	Timed out waiting on connection	See Note.
B18187B0	Failed to get socket options	See Note.
B18187B1	Connection failed	See Note.
B18187B2	Failed to select socket	See Note.
B18187B3	Eth0 connection failure	See Note.
B18187B4	Failed to connect for network client serial connection to CMS	See Note.
B18187B6	Failed to send serial connection message to eth0 gateway	See Note.
B18187B7	Error in sending connection message	See Note.
B18187B8	Error in sending connection message to serial connection to CMS	See Note.
B18187B9	Failed to send data	See Note.
B18187BA	Error in opening port number	See Note.
B18187BC	Error writing to port	See Note.
B18187BD	Failed to close UART	See Note.
B18187BE	No object created	See Note.
B18187C0	Failed to receive data	See Note.
B18187C1	Failed to reset UART	See Note.
B18187CA	Failed to close	See Note.
B18187CB	Failed to close serial	See Note.
B18187CC	Error closing eth0 connection	See Note.
B18187CD	Error closing eth1 connection	See Note.
B18187D0	Unexpected signal received	See Note.
B18187D1	Error setting password	See Note.
B18187D6	Failed to send sdata	See Note.
B18187D7	Failed to send sdata	See Note.
B18187D8	Failed to configure UART	See Note.
B18187D9	Failed to configure UART	See Note.
B18187DA	Failed to configure UART	See Note.
B18187DB	Failed to configure UART	See Note.
B18187DC	Failed to configure UART	See Note.
B18187DE	Error receiving on serial interface	See Note.
B18187E5	Failed to read registry for network client	See Note.
B18187E6	Failed to connect for TCP/IP	See Note.
B18187E7	Socket error on select	See Note.
B18187E8	Timed out on select call	See Note.
B18187E9	Connect failed	See Note.
B18187EA	Failed to close	See Note.
B18187EC	Error in write operation	See Note.
B18187ED	Error in select while waiting for data	See Note.
B18187EE	Timeout in select while waiting for data	See Note.
B18187EF	Error in receive operation	See Note.
B18187F0	Bad eyecatcher detected in the data packet	See Note.
B18187F1	Timeout in select while waiting for data	See Note.
B18187F2	Error in select while waiting for data	See Note.
B18187F3	Error in select	See Note.
B18187F5	Error in sending connection message to serial connection to CMS	See Note.
B18187F6	Error processing message for gateway	See Note.
B18187F7	Error sending or receiving message	See Note.
B18187FA	Data sent in through constructor is bad	See Note.
B1818801	Invalid Service Routine	See Note.
B1818802	Requested processor core is not functional	See Note.
B1818803	Failed to get selected processor core functionality	See Note.
B1818806	Failed to restore the Attention Area into MainStore	See Note.
B1818807	Failed to restore the SPRs	See Note.
B1818808	Failed to restore the GPRs	See Note.
B1818809	Failed to create shared memory for Attention Area	See Note.
B181880A	Failed to invalidate the I-Cache and Instruction buffers for all processors	See Note.
B181880B	Failed to read path from registry	See Note.
B181880C	Failed to start instructions to run the Service Routine	See Note.
B181880D	Failed to write to Service Routine State in registry to indicate that a Service Routine is running	See Note.
B181880E	Timed out waiting for the Service Routine to finish	See Note.
B181880F	Failed to write to Service Routine State in registry to indicate that a Service Routine is not running	See Note.
B1818810	Failed to attach to shared memory area for Attention Area	See Note.
B1818813	Failed to set bit for SPR register setup	See Note.
B1818814	Failed to read GPRs for thread in User Data 2 of SRC so they could be saved	See Note.
B1818815	Failed to set bits in setup map buffer to indicate what register we wanted to set	See Note.
B1818816	Failed to read SPRs for thread in User Data 4 of SRC so they could be saved	See Note.
B1818817	Failed to read Attention Area from MainStore	See Note.
B1818818	Failed to get CPU Control Area from Host Data Area	See Note.
B1818819	Failed to get Service Routine structure from Host Data Area	See Note.
B181881A	Failed to initialize Service Routine address buffer	See Note.
B181881B	Failed to write Service Routine address to GPR3 for thread in User Data 2 of SRC	See Note.
B181881C	Failed to read the current SPR values	See Note.
B181881D	Failed to initialize NIA buffer	See Note.
B181881E	Failed to setup SPR to run Service Routine	See Note.
B181881F	Failed to set NIA for Service Routine	See Note.
B1818820	Failed to initialize MSR buffer	See Note.
B1818821	Failed to set MSR for Service Routine	See Note.
B1818822	Failed to set LPCR for Service Routine	See Note.
B1818823	Failed to clear RMI bit in LPCR for Service Routine	See Note.
B1818824	Failed to get LPCR from SPR object	See Note.
B1818825	Invalid attention area pointer was passed into function	See Note.
B1818826	Failed to get shared memory area for Attention Area	See Note.
B1818827	Failed to deattach from shared memory area for Attention Area	See Note.
B1818828	Failed to create file to signify that the system attention has been handled	See Note.
B1818829	Failed to destroy file	See Note.
B181882A	Failed to destroy shared memory for Attention Area	See Note.
B181882B	Failed to get status of thread requested	See Note.
B181882C	No threads are alive on the requested processor core	See Note.
B181882D	Failed to get proper fabric identity so we could read MainStore	See Note.
B181882E	Failed to get Attention Area data from MainStore object	See Note.
B181882F	Timed out waiting for Attention Handler to begin running	See Note.
B1818830	Failed to start Attention Handler	See Note.
B1818831	Failed to unmap memory	See Note.
B1818901	Failed to read from the registry	See Note.
B1818902	The Server file does not exist and we have timed out	See Note.
B1818903	The Server file exists, but is not locked and we have timed out	See Note.
B1818904	The file failed to open	See Note.
B1818905	The Server file failed to be created and opened	See Note.
B1818906	The Server file that was created/opened failed to lock	See Note.
B1818907	The Server file that was opened is already locked by another Server process	See Note.
B1818908	The Server file failed to be unlinked (destroyed)	See Note.
B181890A	The List file is at the end of file	See Note.
B181890B	The List file failed to read a line due to a reading error	See Note.
B181890C	The List file is in an invalid format	See Note.
B181890D	Failed to read the base path from the List file	See Note.
B181890E	The timeout value read from the List file was too small or too large	See Note.
B181890F	Failed to read the relative path of the file to be checked from the List file	See Note.
B1818910	Failed to read the timeout of the file to be checked from the List file	See Note.
B1818911	Failed to synchronize with a file from List file	See Note.
B1818912	Failed to synchronize with requested file in time allotted	See Note.
B1818913	A line was read from the List file, but it had invalid characters	See Note.
B1818914	The command was passed improper arguments	See Note.
B1818915	We have exceeded the maximum number of files that are allowed to be created and opened using Process Synchronization	See Note.
B1818916	The Server file descriptor could not be found	See Note.
B1818917	Failed to synchronize with requested file in time allotted	See Note.
B1818A01	Registry read or write failure due to an invalid key	See Note.
B1818A02	Registry read or write failure due to a size mismatch	See Note.
B1818A03	Building Block registry write failure	See Note.
B1818A04	Failed to determine the platform extension for the given write key	See Note.
B1818A05	Redundant write failed for the given key	See Note.
B1818A06	Event signal failure for the given write key	See Note.
B1818A08	Redundant registry write failure due to stream failure	See Note.
B1818A09	Building Block registry failure	See Note.
B1818A0A	Error forming the registry path	See Note.
B1818A0D	Requested system operation failed	See Note.
B1818A0E	File not open	See Note.
B1818A0F	Reached end of file	See Note.
B1818A10	Bad memory receive pointer	See Note.
B1818A11	Stream is at end of file	See Note.
B1818A12	File removal failed in the underlying layer	See Note.
B1818A13	File lock failure with given parameters	See Note.
B1818A15	Semaphore initialization cannot complete due to failure getting semaphore	See Note.
B1818A16	Semaphore initialization cannot complete due to control failure of semaphore	See Note.
B1818A17	Semaphore operation failed	See Note.
B1818A18	Semaphore initialization cannot complete due to failure getting file token	See Note.
B1818A19	Loading of a shared library has failed	See Note.
B1818A1A	Loading of a shared library symbol has failed	See Note.
B1818A1B	Failed to execute the synchronization immediate platform extension during a registry operation	See Note.
B1818A1D	Building Block registry read failure	See Note.
B1818A1E	Error reading platform extension for the given registry key	See Note.
B1819002	Invalid number of arguments were passed	See Note.
B1819003	Incorrect number of arguments	See Note.
B1819004	Failed trying to make a directory	See Note.
B1819008	Failed trying to get status of a file	See Note.
B1819009	Failed attempting to allocate memory	See Note.
B181900A	Failed trying to allocate memory	See Note.
B181900B	Failed trying to allocate memory	See Note.
B181900C	Failed trying to memory map a file	See Note.
B181900E	Failed trying to memory map a file	See Note.
B181900F	Failed trying to unmap a file	See Note.
B1819010	Failure from memory unmap	See Note.
B1819011	Unexpected signal received	See Note.
B1819014	Size of registry entry is not correct	See Note.
B1819018	LID's file size is too large	See Note.
B181901A	Failed trying to add another entry to an array	See Note.
B181901B	Attempted to add a RAM FRU for an invalid mainstore area	See Note.
B181901C	Failed trying to get status of primary LID's file	See Note.
B181901F	More PHYP LIDs have been added to the build for FSP to load and an array is not large enough to accommodate the new LIDs	See Note.
B1819020	Size of file cannot contain the amount of memory we want to map	See Note.
B1819021	VPD says a required FRU does not exist	See Note.
B1819022	Attempted to allocate memory but it failed	See Note.
B1819023	No resource ids were returned for a required FRU	See Note.
B1819026	VPD collection was not complete and it did not complete in a reasonable time	See Note.
B1819027	An error occurred trying to DMA a LID to mainstore	See Note.
B1819028	The number of I/O paths to the primary FSP is not valid	See Note.
B181904F	Another component had a failure	See Note.
B1819200	I/O control failed trying to set the DTR pin	See Note.
B1819202	HVSI received a response to the version query but did not get any data	See Note.
B1819203	OS protocol version does not match currently supported FSP version	See Note.
B1819206	The open on the requested device failed	See Note.
B1819207	HVSI was asked to open a port that did not exist	See Note.
B1819209	Invalid action requested or invalid data passed	See Note.
B181920A	Request for modem control signal status but the port is not open	See Note.
B181920B	Error trying to read status register data	See Note.
B181920D	We failed reading data from the serial port	See Note.
B181920E	Write to the serial port failed	See Note.
B181920F	Failed to close	See Note.
B1819211	Stuck trying to write to serial port for more than 2 seconds	See Note.
B1819502	Unable to unlock an HMC queue mutex	See Note.
B1819505	Unable to post semaphore to wake up processing thread	See Note.
B1819506	Couldn't create the thread	See Note.
B1819509	The wrong number of bytes were written on mailbox interface	See Note.
B181950A	No bytes were returned on mailbox read	See Note.
B181950B	Failed to send message to PHYP	See Note.
B181950D	The size of data being sent exceeds the TCE size or the TCE's have never been allocated and written to the registry	See Note.
B181950E	Unable to start timer to block code update on DPO	See Note.
B1819510	Bad status in network response message	See Note.
B1819516	Got a socket message that doesn't belong to this sender	See Note.
B1819517	Unable to receive the error/event log from the daemon	See Note.
B1819518	Failed operating system call	See Note.
B1819519	Bad parameter for function	See Note.
B181951A	IPL handshake failed	See Note.
B181951B	Dump other than platform or FSP is being invalidated	See Note.
B1819520	State manager never made it to desired state in time we waited	See Note.
B1819521	HMC ID is too big	See Note.
B1819522	Daemon is down	See Note.
B1819524	Unable to clear bits in DSISR so PHYP may stop talking to the FSP, if the bits are actually set	See Note.
B1819525	Unable to display SRC for PHYP	See Note.
B1819526	On redundant FSPs, there are times when messages to PHYP are blocked and this is one of those times	See Note.
B1819527	On redundant FSPs, there are times when messages from PHYP are blocked and this is one of those times	See Note.
B1819902	Invalid signal received	See Note.
B1819903	An error occurred reading a registry variable	See Note.
B1819904	Failure to write to registry variable	See Note.
B1819905	Unrecognized power off IPL type	See Note.
B1819906	Invalid value read from registry variable	See Note.
B1819907	Invalid value trying to set registry variable to	See Note.
B1819908	An error occurred writing to the registry	See Note.
B1819909	Failure to write to registry for Controlled Power Off	See Note.
B181990A	Failure to write to registry for Loss of AC Power	See Note.
B181A000	Input parameter is incorrect	See Note.
B181A001	Socket connect failure	See Note.
B181A004	Send system call has failed	See Note.
B181A005	Send length not equal to the message length	See Note.
B181A006	Received length not equal to the server message length	See Note.
B181A007	Invalid parameter	See Note.
B181A008	Socket system call failed for server socket	See Note.
B181A009	Bind system call has failed for server socket	See Note.
B181A00A	Listen system call has failed for server socket	See Note.
B181A00B	Failed to accept socket	See Note.
B181A00E	Failed to receive message	See Note.
B181A00E	Failed to receive message	See Note.
B181A00F	Socket connect failure	See Note.
B181A010	Send system call failure	See Note.
B181A012	An error occurred reading the P0 root path from the registry	See Note.
B181A013	Trying to set invalid power state	See Note.
B181A015	Response doesn't match request	See Note.
B181A016	Incorrect mode	See Note.
B181A017	Function requested is disabled	See Note.
B181A018	Invalid subfunction number	See Note.
B181A019	Function range is disabled	See Note.
B181A01C	Sequence error	See Note.
B181A01D	Timer creation error	See Note.
B181A01E	Resetting timer has failed	See Note.
B181A01F	Resetting scroll lock has failed	See Note.
B181A021	Error in starting process as a daemon	See Note.
B181A024	Failure to start thread	See Note.
B181A025	Type undefined for given function. Probably invalid function number	See Note.
B181A027	Unexpected signal received	See Note.
B181A028	An unsupported event id was received	See Note.
B181A029	Failed to select socket	See Note.
B181A02A	Timed out waiting for select	See Note.
B181A02B	Failed to select socket	See Note.
B181A02C	Timed out waiting for select	See Note.
B181A02E	The client has gone away	See Note.
B181A02F	The server has gone away	See Note.
B181A031	Failure building the display	See Note.
B181A032	Error while attempting to program panel buttons or displaying to Panel	See Note.
B181A033	Failed to read path from registry	See Note.
B181A036	Failed to remove an old message queue	See Note.
B181A038	Event message queue send failed	See Note.
B181A039	Event message queue receive failed	See Note.
B181A03A	Failed to allocate memory for event	See Note.
B181A040	Failed thread conditional broadcast	See Note.
B181A041	Failed to create thread	See Note.
B181A042	Failed to synchronize with server process	See Note.
B181A043	An error occurred while reading a Registry value	See Note.
B181A044	Failed to synchronize with client process	See Note.
B181A049	VPNL returned error while executing the specified function	See Note.
B181A050	Error getting function state	See Note.
B181A051	The caller has elected to NOT wait for VPD collection to complete	See Note.
B181A054	The specified RID does not correspond to a physically present op-panel	See Note.
B181A055	An op-panel is currently active, and therefore the 'activate' request cannot be performed	See Note.
B181A056	Another concurrent maintenance operation is in progress	See Note.
B181A057	Failure to lock a mutex	See Note.
B181A058	Failure to unlock a mutex	See Note.
B181A059	An op-panel is not currently active, and therefore the 'deactivate' request cannot be performed	See Note.
B181A05A	This event indicates that the panel will not be activated for the system because it is a Redundant FSP, MLx system with the new FSP cables	See Note.
B181A061	Failure to initialize thread attribute variable	See Note.
B181A062	Failure to set thread attribute variable	See Note.
B181A063	Failure to cancel thread	See Note.
B181A064	Failed to get VPD state	See Note.
B181A065	Failed to get the maximum number of RIDs from VPD	See Note.
B181A066	Failed to get RID number from VPD	See Note.
B181A069	More than one op-panel is physically present in the system	See Note.
B181A071	The caller's array is too small to contain all the data	See Note.
B181A072	Experienced a problem while trying to detect old message queue	See Note.
B181A073	Timed out waiting for the thread to exit	See Note.
B181A074	Error while waiting for thread to exit	See Note.
B181A075	Error waiting on the 'CCM complete' condition	See Note.
B181A076	Only the primary FSP can activate an op-panel	See Note.
B181A077	Failed to get power state	See Note.
B181A078	An error occurred trying to extract the Display SRC function symbol from the panel client library	See Note.
B181A079	An error occurred trying to setup the environment to have the correct library path for finding the panel client library	See Note.
B181A07A	Error reading VPD	See Note.
B181A07B	Invalid RID count	See Note.
B181A07C	No sibling FSP found	See Note.
B181A201	Invalid field update specified in request	See Note.
B181A203	An unsupported operation was requested	See Note.
B181A204	Failed IPL request	See Note.
B181A206	Error returned from IPL lock function	See Note.
B181A207	Failed lamp test	See Note.
B181A208	Error returned while reading registry	See Note.
B181A209	Registry write failure	See Note.
B181A20A	The operation request is not allowed because it was requested on the backup FSP	See Note.
B181A20B	Invalid request from caller	See Note.
B181A20C	This request has NULL output data pointer	See Note.
B181A20D	Error returned from dump function	See Note.
B181A20E	The requested function is not within the valid range or it is an unsupported function	See Note.
B181A20F	Error from mailbox	See Note.
B181A211	Rejected specified function/ subfunction request	See Note.
B181A214	The requested function is not within the valid range or it is an unsupported function	See Note.
B181A215	SPCN Panel function (07) is disabled	See Note.
B181A216	FSP dump failed	See Note.
B181A217	Requested subfunction is outside the valid range	See Note.
B181A219	Invalid signal received by process	See Note.
B181B000	Invalid parameter passed by the user	See Note.
B181B001	Update for the given keyword not allowed for second time	See Note.
B181B004	Cannot find given record	See Note.
B181B005	VTOC record not found	See Note.
B181B006	Failure reading / finding the module VPD file	See Note.
B181B009	RLCA Index greater than number of RLCA entries	See Note.
B181B00A	Invalid length of parameter	See Note.
B181B00B	Failure to read VPD File Path registry	See Note.
B181B00C	Error reading NVRAM entry	See Note.
B181B00E	We had an error opening the file for the given resource ID	See Note.
B181B00F	We were unable to gain a lock on a VPD file	See Note.
B181B010	We had an error reading the VPD file	See Note.
B181B011	We were unable to unlock the file	See Note.
B181B012	Unable to build location code for the FRU	See Note.
B181B013	Error trying to locate the file	See Note.
B181B014	Invalid format for the VPD	See Note.
B181B015	Error renaming file	See Note.
B181B016	We had an error closing and/or unlocking the file	See Note.
B181B017	Cannot find given keyword in the block	See Note.
B181B01B	Cannot read VPD node for the given RID	See Note.
B181B01C	Cannot find PT keyword in the VTOC record	See Note.
B181B01D	Invalid input buffer length	See Note.
B181B01E	Error while writing to the registry	See Note.
B181B01F	Failure reading configurated id of machine model registry	See Note.
B181B020	Invalid parameter passed by the user	See Note.
B181B024	Error reading ECC for VHDR block	See Note.
B181B027	Invalid VTOC record length	See Note.
B181B028	We failed trying to get smart chip block size	See Note.
B181B02A	Error initializing smart chips	See Note.
B181B02C	There was a failure trying to update one of the smart chip blocks	See Note.
B181B030	Unable to find input resource ID in the RID table	See Note.
B181B031	Cannot find rlca index for the given location code	See Note.
B181B032	We were trying to generate a FRU callout because we had an error in one of the external interface and in process of generating that error we ran into another error	See Note.
B181B033	Cannot find MF tag for 1002 slotmap	See Note.
B181B035	Error writing Machine Brand registry	See Note.
B181B036	We failed trying to get smart chip block size	See Note.
B181B037	Invalid length for the keyword in the VPD	See Note.
B181B038	Invalid Block id passed by the user	See Note.
B181B03A	Unable to find input resource ID in the RID table	See Note.
B181B03B	Cannot find data port node for VRM information	See Note.
B181B03C	Error initializing I2C devices	See Note.
B181B03D	Writing to I2C device failed	See Note.
B181B03E	Error trying to read the module VPD from the I2C Chip	See Note.
B181B03F	Reading thermal sensor data failed for the given FRU	See Note.
B181B040	Invalid controller type for frequency controller	See Note.
B181B041	Someone has requested the SMP cable ID on a non MLx system	See Note.
B181B043	Invalid RID or invalid FSP ID	See Note.
B181B044	The Input RID does not have a redundant resource associated with it	See Note.
B181B045	Invalid bit definition for 9551 controllers	See Note.
B181B046	Invalid bit definition for 9552 controllers	See Note.
B181B049	Invalid data	See Note.
B181B04A	Invalid keyword format VPD	See Note.
B181B04B	Invalid description length for keyword format VPD	See Note.
B181B04C	Invalid offset found in the keyword format VPD	See Note.
B181B04E	Invalid offset	See Note.
B181B04F	No 0x84 tag found	See Note.
B181B050	Invalid offset for the PT keyword in VTOC record	See Note.
B181B051	Invalid VTOC record offset	See Note.
B181B052	Invalid VHDR record size	See Note.
B181B053	Error reading "PR" keyword from the VINI record for the given RID	See Note.
B181B054	Invalid IN keyword size. Found zero number of VSRC entries	See Note.
B181B055	Zero plug count found for the given RID	See Note.
B181B056	Unsupported Resource Type	See Note.
B181B057	Unsupported Record Type	See Note.
B181B059	Offset is greater than buffer size	See Note.
B181B05A	Invalid 200A Slotmap	See Note.
B181B05B	Cannot find rlca index for the given slca index	See Note.
B181B05C	Cannot find rlca index	See Note.
B181B05D	Failure to write Registry with Raw VPD data	See Note.
B181B061	Unable to use either VPD Chip because we could not reach them or they are garded out	Ensure the little VPD card with the blue handle (to the upper right of the service processor card) is properly installed. The VPD card may need to be replaced. See Note.
B181B063	Incorrect size passed in by user	See Note.
B181B064	Caller has asked us to update an invalid type of FRU	See Note.
B181B065	Failed to read anchor card VPD	See Note.
B181B067	Error converting to multiple stanza format converged VPD	See Note.
B181B068	Error converting to multiple stanza format keyword format VPD	See Note.
B181B06D	Failed to process VPD chip	See Note.
B181B06E	Failed to get RLCA index for a resource ID	See Note.
B181B073	We read an invalid Machine Type Model from the VPD	See Note.
B181B07A	Legacy SC buffer greater than original buffer	See Note.
B181B07C	Cannot find old file in directory	See Note.
B181B07E	Failed to write RLCA table	See Note.
B181B080	No valid Service Processor VPD was found on this system	See Note.
B181B082	No VPD collected for given processor card	See Note.
B181B083	Pin failure failed after root node mismatch	See Note.
B181B084	Pin failure is successful after root node mismatch	See Note.
B181B085	Invalid FRU Detect Data Port Type Found in VPD	See Note.
B181B086	We failed when trying to read the SMP cable ID from the 9552 controller on this MLx system	See Note.
B181B087	VPD Firmware had an error in trying to detect if this FRU was actually present or not on the system	See Note.
B181B088	No plug detect node found for this RID but the RLCA table said there should be	See Note.
B181B089	Error in finding out which FSP it is	See Note.
B181B08A	We were unable to determine the maximum number of Resource ID's for the input FRU type	See Note.
B181B08B	Failed trying to determine the Resource ID's associated with the given FRU type	See Note.
B181B08C	We had a failure finding the LED node for this processor card	See Note.
B181B08D	We had a failure reading the SMP cable ID on a processor card	See Note.
B181B08E	We had a mismatch in the cable ID between two processor cards	See Note.
B181B08F	There was a failure trying to configure 9555/9554 controller	See Note.
B181B090	There was a failure trying to create smart chip blocks	See Note.
B181B091	Error occurred while locking/unlocking DASD device	See Note.
B181B092	VPD Firmware had an error in trying to read the size of a registry key	See Note.
B181B093	Failed to open source directory while copying a directory	See Note.
B181B094	Locking the VPD file has failed	See Note.
B181B095	Unlocking the VPD file has failed	See Note.
B181B097	Cannot find DR keyword in the given record while updating legacy smart chip VPD	See Note.
B181B098	TM field is already updated once. Second update for the given keyword not allowed because TYPE part of MTM does not match	See Note.
B181B099	Firmware needs to add support for an additional resource to the given FRU type	See Note.
B181B09A	Failed to get FRU status for the given RID in registry update function	See Note.
B181B09B	Failed to read the VPD and update the registry entry for the input RID	See Note.
B181B09C	Error writing NVRAM to VPD	See Note.
B181B09D	Mismatch in VPD vs NVRAM	See Note.
B181B09E	Failed to write System NVRAM values out to VPD	See Note.
B181B09F	Failed to write Enclosure NVRAM values out to VPD	See Note.
B181B0A0	Unable to add FRU to the rlcaTable because instanceTable shows no more FRU addition allowed	See Note.
B181B0A1	Invalid algorithm type found in the VPD node for the given RID in the rlcaTable	See Note.
B181B0A2	Failed to update GARD with a resource ID	See Note.
B181B0A3	Failed to GARD out a resource ID	See Note.
B181B0A4	Failed to determine if chip is garded out or not	See Note.
B181B0A5	A chip on the Anchor card has been garded out	See Note.
B181B0A7	Failure to write registry for update status	See Note.
B181B0A8	Failure attempting to read the system configuration file	See Note.
B181B0A9	Failed to input line from system file	See Note.
B181B0AA	Mismatch SN or PN between primary and redundant fsp recollect during VPD verification	See Note.
B181B0AB	Error reading smart chip legacy block size	See Note.
B181B0AD	Error reading Raw Machine type model registry	See Note.
B181B0AF	Failed to process message for VPD	See Note.
B181B0B5	Cannot find RID for FRU_SP for this FSP	See Note.
B181B0B6	Error synchronizing file to the other FSP	See Note.
B181B0B7	Error reading system type registry	See Note.
B181B0B8	Error converting FRU type	See Note.
B181B0B9	Error converting FRU type	See Note.
B181B0BB	Sibling FSP state is set to NOT working	See Note.
B181B0BC	Unable to locate string in file	See Note.
B181B0BD	Invalid number of processor cards are present	See Note.
B181B0BE	Checksum in the VPD data does not match calculated checksum	See Note.
B181B0BF	Someone tries to read/write a keyword in corrupt VPD	See Note.
B181B0C0	Failure in getting the other RID from the system configuration file	See Note.
B181B0C1	Error in updating CCMM registry with the new primary RID	See Note.
B181B0C2	VPD is not collected both for primary RID and redundant RID or its child RID	See Note.
B181B0C4	Failed to read GPIO pin value from FSP extender	See Note.
B181B0C5	Invalid number rlcaTable entries	See Note.
B181B0C6	New value has been written to the hyperboot capability registry	See Note.
B181B0C7	Error while getting the hyperboot capability registry value	See Note.
B181B0C8	VPD could not collect more Oppanel VPD for ASMI	See Note.
B181B0C9	No Oppanels present in system	See Note.
B181B0CA	Invalid raw brand name	See Note.
B181B0CB	Failed to copy or rename directory	See Note.
B181B0CC	Failed to remove directory	See Note.
B181B101	VPD indicates that no VPD headers are available	See Note.
B181B102	Location code for the associated resource ID not found in the VPD header array	See Note.
B181B103	Location code for the associated resource ID is not NULL terminated	See Note.
B181B104	Parent location code of resource ID being processed is not null terminated	See Note.
B181B105	The length of the location code being built is going to exceed the maximum allowed	See Note.
B181B106	Call made to read location code for a resource ID of zero	See Note.
B181B107	Call made to read location code, but the buffer provided is not large enough to hold a maximum length location code	See Note.
B181B108	Location code for the associated resource ID has a length mismatch	See Note.
B181B109	Call made to read location code, but the buffer reference provided was a NULL pointer	See Note.
B181B10B	Failed to get number of headers from VPD	See Note.
B181B10C	Failed to get all headers from VPD	See Note.
B181B10D	Failed to process a resource ID	See Note.
B181B10E	Failed to get maximum number of RIDs for enclosure	See Note.
B181B10F	Failed to get RID numbers for enclosure	See Note.
B181B110	Failed to get enclosure number and index using RID	See Note.
B181B111	Error reading enclosure Feature Code and model data	See Note.
B181B112	Error reading system Type/Model data	See Note.
B181B113	Error reading system serial number data	See Note.
B181B114	Error updating location code	See Note.
B181B115	Failed to get RID number of children	See Note.
B181B116	Maximum number of RIDs returned is zero	See Note.
B181B117	Data length mismatch while reading enclosure Feature Code and model data	See Note.
B181B118	Data length mismatch while reading enclosure serial number data	See Note.
B181B119	Data length mismatch while reading system type/model data	See Note.
B181B11A	Data length mismatch while reading system serial number data	See Note.
B181B11B	Failed to read rlca table from VPD	See Note.
B181B11C	The rlca was searched for a FRU_ID of "VV" which is the starting point of the VPD tree. However, no "VV" entry was found in the rlca	See Note.
B181B11D	An FRU_ID "VV" root was being processed and an error was returned	See Note.
B181B11E	An enclosure was being processed and an error was returned	See Note.
B181B11F	User input invalid parameter	See Note.
B181B120	Error returned from reading VPD registry	See Note.
B181B121	Could not find VPD registry entry	See Note.
B181B201	Call was made to read location codes, but a NULL buffer pointer was provided	See Note.
B181B202	Call was made to read location codes, but the input buffer provided is not large enough to hold all the LED location codes	See Note.
B181B204	Call was made to get LED access data, but the input location code pointer was NULL	See Note.
B181B205	Call was made to get LED access data, but the input location code was not NULL terminated	See Note.
B181B207	Call was made drive an LED to a specific state but the class controller type is invalid or not supported	See Note.
B181B208	Failed to open I2C bus	See Note.
B181B209	Failed to close I2C bus	See Note.
B181B20A	Failed to transmit data on I2C bus	See Note.
B181B20B	Failed to transmit data to the LED lightstrip controller	See Note.
B181B20C	Failed to lock the I2C hub	See Note.
B181B20D	The specified LED state is not valid	See Note.
B181B20E	Failed to get GMNOL from VPD	See Note.
B181B20F	Failed to get GAL from VPD	See Note.
B181B210	Call was made to read the number of enclosure LEDs, but none was found	See Note.
B181B211	Failed to read LED location codes	See Note.
B181B212	Failed to drive LED to specified state	See Note.
B181B213	Failed to drive LED to specified state	See Note.
B181B214	Failed to transmit data to the I2C hub	See Note.
B181B215	Failed to transmit park data to the I2C hub	See Note.
B181C000	VPD failure	See Note.
B181C001	Session entry failure	See Note.
B181C002	Failed network client call	See Note.
B181C003	Invalid authentication level or requestor was set	See Note.
B181C004	PHyp returned an error when attempting to open a PHyp session	See Note.
B181C005	Data buffer error	See Note.
B181C006	Failed Mailbox function call	See Note.
B181C007	Failed to read from or write to a registry entry	See Note.
B181C008	Internal event error	See Note.
B181C009	Internal file error	See Note.
B181C00A	Internal VTTY error	See Note.
B181C00B	Failed to signal a broadcast event	See Note.
B181C00C	Failed to successfully create a virtual serial object while running the virtual serial open command	See Note.
B181C00D	A virtual serial client attempted to open a virtual serial session before PHYP reached standby/runtime state	See Note.
B181C00E	The DMA component returned an error log while attempting to read the VTTY buffer	See Note.
B181C00F	Received an error while trying to access the leds file	See Note.
B181C010	Received an error while accessing the semaphore object for the leds table during the lock table command	See Note.
B181C011	API error	See Note.
B181C012	Failure to calculate the timestamp stored in the session entry object	See Note.
B181C013	Failed to acknowledge surveillance	See Note.
B181C014	Internal lock error	See Note.
B181C015	Failed to obtain file lock	See Note.
B181C016	Failed to release file lock	See Note.
B181C017	Failed to access a file through the utility	See Note.
B181C018	Unable to authenticate password for an authorized virtual serial session	See Note.
B181C019	Failed to reset reload	See Note.
B181C01A	PHYP status error	See Note.
B181C01B	HMC/FSP interface protocol violation	See Note.
B181C01C	Internal error	See Note.
B181C01D	Protocol error	See Note.
B181C01E	Failed to get the cage and frame number	See Note.
B181C01F	Did not receive a valid data length or ack value	See Note.
B181C020	MP command cannot be executed since MP state is incorrect	See Note.
B181C021	Failed to write partial lid for code update	See Note.
B181C022	Internal error	See Note.
B181C023	Precondition failure	See Note.
B181C024	Request to open a PHyp connection was denied because the tool type is not allowed to perform that operation	See Note.
B181C025	Concurrent maintenance lock access failure	See Note.
B181D101	Failed to write to file	See Note.
B181D102	Failed to read breakpoint attention	See Note.
B181D103	File write operation failed	See Note.
B181D107	Failed to initialize the Hypervisor service routine flag	See Note.
B181D108	Failed to read from registry	See Note.
B181D10A	Null pointer while trying to enable attentions	See Note.
B181D10C	Failure in Unmask attentions interface	See Note.
B181D10D	JTAG failed while waiting for attention	See Note.
B181D10E	Failed to write to MainStore	See Note.
B181D10F	JTAG read failure while reading the Interrupt Status Register	See Note.
B181D110	Fail to get the Hardware level in the JTAG controller	See Note.
B181D111	Failed to enable attentions	See Note.
B181D112	Timeout while waiting for JTAG lock	See Note.
B181D113	Request for system dump failed after getting attention	See Note.
B181D115	Utility read failure on a breakpoint attention	See Note.
B181D116	Utility write failure while writing the terminate flag	See Note.
B181D117	Failure while trying to open a file on a breakpoint attention	See Note.
B181D118	Phyp wrote an invalid SRC in the attention area in MainStore	See Note.
B181D119	Master FSP Communications failure	See Note.
B181D11A	Utility write failure while writing the terminate flag	See Note.
B181D11C	Spurious attention detected after attempt to clear all attentions for ISR	See Note.
B181D11D	Failed to get the reserve	See Note.
B181D11E	Failed while attempting to release the reserve	See Note.
B181D11F	No error created on a processor checkstop	See Note.
B181D120	Failed to read mainstore after a breakpoint attention	See Note.
B181D121	Failed to write to mainstore after a breakpoint attention	See Note.
B181D122	Failed to write the ISR back to the JTAG controller	See Note.
B181D123	Failed to release the JTAG lock	See Note.
B181D124	Failure when getting functional group	See Note.
B181D125	Failure while mapping mainstore to get attention area	See Note.
B181D126	Failed while reading the mainstore area	See Note.
B181D127	Get data failure	See Note.
B181D128	Failure to instantiate an object	See Note.
B181D129	Attentions not found exceeded threshold	See Note.
B181D12A	Server process failed	See Note.
B181D12B	Interface failure	See Note.
B181D12C	Interface failure	See Note.
B181D12D	Interface failure	See Note.
B181D12E	Disable attentions failed	See Note.
B181D130	Interface failure on an asset protection attention	See Note.
B181D131	A trace trigger attention was detected	See Note.
B181D132	Detected a clock stop on error attention	See Note.
B181D133	Server process failed	See Note.
B181D134	Failed to synchronize with client process	See Note.
B181D135	Utility read failed to read the current state of the State Manager	See Note.
B181D136	Invalid type of attention	See Note.
B181D137	A TI was detected during either dump, power off or dump transition	See Note.
B181D138	Manufacturing interface to read the policy flag failed	See Note.
B181D139	Call to generate event failed during a Non IO checkstop	See Note.
B181D13A	Utility read failed to read the current role of the FSP	See Note.
B181D13B	FSP Dump event timed out	See Note.
B181D13C	Reset reload while handling P5IOC recovered error	See Note.
B181E001	Call home enabled but no destination phone numbers programmed	See Note.
B181E002	Failed to receive message	See Note.
B181E003	Pager data was not programmed	See Note.
B181E004	Error writing to serial port	See Note.
B181E005	The customer AGN account information is missing	See Note.
B181E006	Missing data from setup	See Note.
B181E007	Failed fork system call	See Note.
B181E008	Failed to rebuild the error log during call home	See Note.
B181E009	Failed fork system call	See Note.
B181E00A	Child process failed	See Note.
B181E00B	Child process failed	See Note.
B181E00C	Child process died due to unhandled signal	See Note.
B181E00D	Child process died due to unhandled signal	See Note.
B181E00E	Failed trying to put the symptom string together	See Note.
B181E010	Serial port open failed	See Note.
B181E011	The file descriptor was is not valid	See Note.
B181E012	Failed select system call	See Note.
B181E015	Sending message on socket failed	See Note.
B181E016	Failed to get socket	See Note.
B181E017	Failed to get socket	See Note.
B181E01E	Call home test	See Note.
B181E01F	User issued a call home test	See Note.
B181E025	Failed serial port echo	See Note.
B181E026	Failed serial port echo	See Note.
B181E027	Trying to do call home test on same port that ASMI is active on	See Note.
B181E028	Trying to do call home test on same port that ASMI is active on	See Note.
B181E101	String was found in the input data and the system reIPL has been requested	See Note.
B181E201	Received an error and did not attempt a reboot	See Note.
B181E202	Received an error waiting for the backup FSP to terminate	See Note.
B181E303	Invalid modifier	See Note.
B181E30B	Cannot Query for LED Table	See Note.
B181E30D	The request sent in is not a valid request type for this function	See Note.
B181E310	Invalid request type	See Note.
B181E315	Failed on retry for SPCN command	See Note.
B181E31B	Failed to get LED state control	See Note.
B181E31C	SPCN PRS command to collect LED data did not return any data	See Note.
B181E31D	SPCN command to control the physical attention LED has failed	See Note.
B181E31E	Failed to get location code table from PHYP	See Note.
B181E400	Attempt to open file failed	See Note.
B181E401	Attempt to open file failed	See Note.
B181E402	Attempt to open file failed	See Note.
B181E403	Attempt to close file failed	See Note.
B181E404	Attempt to close file failed	See Note.
B181E405	Attempt to open file failed	See Note.
B181E406	Attempt to open file failed	See Note.
B181E407	Attempt to open file failed	See Note.
B181E408	Attempt to close file failed	See Note.
B181E409	Attempt to close file failed	See Note.
B181E40A	Detected DRAM Recovered Errors	See Note.
B181E40B	Detected NVRAM Recovered Errors	See Note.
B181E40C	Failed to get statistics	See Note.
B181E40D	Attempt to open directory failed	See Note.
B181E40E	Attempt to open file failed	See Note.
B181E40F	File system corrupted	See Note.
B181E411	Failed to get the maximum number of RIDs from VPD	See Note.
B181E412	Failed to get the RID from VPD	See Note.
B181E425	Failed to initialize thread attributes	See Note.
B181E426	Failed to set thread to deattached state	See Note.
B181E427	Attempt to accept a client request failed	See Note.
B181E428	Attempt to receive client message failed	See Note.
B181E429	Failed to send response to client	See Note.
B181E42A	Unknown client command received	See Note.
B181E42F	Another instance of the process is already running	See Note.
B181E430	Failed thread call	See Note.
B181E432	System call for mutex failed	See Note.
B181E436	Client failed to send its heartbeat message within the stipulated time	See Note.
B181E437	Error while trying to connect to the daemon	See Note.
B181E438	Error while trying send or receive data with the daemon	See Note.
B181E439	Failed to synchronize with server	See Note.
B181E43A	Failed fork system call	See Note.
B181E43B	Could not close the client socket	See Note.
B181E43C	Error while attempting to close server address socket	See Note.
B181E43D	Failed to read path from registry	See Note.
B181E43E	Error while trying to signal event to notify HMC of the change in the HMC Surveillance Flag	See Note.
B181E43F	Error returned while attempting to write to the registry	See Note.
B181E440	Error returned when attempting to read the registry	See Note.
B181E441	Error trying to notify PHYP of the change in HMC flag	See Note.
B181E443	Invalid type	See Note.
B181E444	Could not flatten log to send to client	See Note.
B181E445	Error while attempting to extract flattened log sent from the daemon	See Note.
B181E446	Client gateway was not able to talk to the master FSP	See Note.
B181E448	Gateway address creation to send surveillance heart beat to master FSP failed	See Note.
B181E449	Failed to connect to client gateway	See Note.
B181E44A	Failed to kill the Common Message Server of a failed HMC client	See Note.
B181E44F	Error while trying to reset the watchdog timer	See Note.
B181E451	Failed to query managed information	See Note.
B181E453	Attempt to bind to the listening address failed	See Note.
B181E454	Attempt to listen in server address failed	See Note.
B181E455	Attempt to open directory failed	See Note.
B181E457	The mux id requested to ping is not valid	See Note.
B181E458	Another component had an error	See Note.
B181E45B	Error while attempting to create listening socket	See Note.
B181E45C	Invalid Response Interval sent	See Note.
B181E45D	Error while trying to create server address	See Note.
B181E460	Failed to set thread schedule policy	See Note.
B181E462	Failed to get the maximum allowed thread priority	See Note.
B181E463	Failed to get the scheduling parameter	See Note.
B181E464	Failed to set scheduling parameter to thread	See Note.
B181E500	Bad hardware	See Note.
B181E601	Error while attempting to read registry	See Note.
B181E602	Another process is already running	See Note.
B181E604	Network client failed to send or receive	See Note.
B181E606	Invalid major operation received	See Note.
B181E607	Error while attempting to create listening socket	See Note.
B181E608	Failed to send from network server	See Note.
B181E609	Failed fork system call	See Note.
B181E60A	Error returned while initializing a thread attribute	See Note.
B181E60B	Error returned while setting a thread attribute	See Note.
B181E60C	Error returned while creating a thread	See Note.
B181E60F	Received an invalid component type while attempting to create handler thread	See Note.
B181E610	Network client failed to connect	See Note.
B181E611	Network client failed to send or receive	See Note.
B181E612	Network client failed to close	See Note.
B181E613	Failed to synchronize with server	See Note.
B181E614	Failed to bind to socket	See Note.
B181E615	Failed to listen to socket	See Note.
B181E616	Network server failed to connect	See Note.
B181E618	Failed to initialize mutex	See Note.
B181E619	Error encountered while locking mutex	See Note.
B181E61A	Error encountered while unlocking mutex	See Note.
B181E61B	Network server failed to close	See Note.
B181E61C	Failed to return log	See Note.
B181E61D	Unknown minor operation id received	See Note.
B181E620	Invalid operation requested to data correlation handler	See Note.
B181E621	Failed to create object	See Note.
B181E622	Network client failed to close	See Note.
B181E623	Network client failed to send or receive	See Note.
B181E625	No file name sent in by client	See Note.
B181E627	Non existent registry variable sent	See Note.
B181E628	File does not exist	See Note.
B181E629	Error attempting to open file for reading or writing	See Note.
B181E62A	Error while reading file	See Note.
B181E62B	Error while attempting write registry	See Note.
B181E62C	Error while writing to the file	See Note.
B181E62D	Backup is not running from the same flash side as primary FSP	See Note.
B181E62F	Sibling returned error on the requested operation	See Note.
B181E633	Error returned while attempting to create event handler object	See Note.
B181E634	Invalid event id was received	See Note.
B181E635	Error while attempting to signal Fsp Role Change event	See Note.
B181E64A	Backup FSP has a different level that the primary FSP	See Note.
B181E64B	Primary and backup FSP have different lid levels loaded	See Note.
B181E64C	Error returned when a flattened log was attempted to be restored	See Note.
B181E64D	Error unflattening the log sent by primary FSP	See Note.
B181E64F	Invalid role in the FSP	See Note.
B181E650	Invalid fail-over type requested	See Note.
B181E656	MUX control could not be taken	See Note.
B181E657	Unrecognized routing type received	See Note.
B181E659	Requested IPL failed	See Note.
B181E65B	Failed to determine fail-over type	See Note.
B181E65C	Surveillance failure of primary FSP detected at pre-standby state	See Note.
B181E65F	Error attempting to determine if the current platform can support redundant FSP	See Note.
B181E660	The system is in a state where fail-over operation cannot be initiated	See Note.
B181E661	Sibling returned error on the requested operation	See Note.
B181E663	Fail-over operation is not allowed	See Note.
B181E664	Force Terminate and fail-over operation is requested	See Note.
B181E665	Failed to terminate and force a fail-over	See Note.
B181E666	Requested FSP IPL failed	See Note.
B181E667	Invalid IPL type	See Note.
B181E669	Failed to determine fail-over type	See Note.
B181E66D	AFO request received from primary FSP	See Note.
B181E66E	EFO operation is being performed by backup to take control of the host system	See Note.
B181E66F	Non I/O Path fail EFO operation is being performed by backup to take control of the host system	See Note.
B181E678	Error while obtaining mux control	See Note.
B181E67B	Failed to close I2C ADAL	See Note.
B181E683	Error while attempting to read Fsp Role registry	See Note.
B181E684	Sibling returned error on the requested operation	See Note.
B181E686	Error in connecting to address to talk to the Common Message Server of a failed HMC client	See Note.
B181E687	Failed to kill the Common Message Server of a failed HMC client	See Note.
B181E689	Sibling returned error on the requested operation	See Note.
B181E68A	The fail-over enable key has been changed by HMC	See Note.
B181E68B	Sibling has requested to initiate reset/reload operation	See Note.
B181E68C	Powering off primary FSP to get the hardware muxes released	See Note.
B181E68F	Backup FSP is not at Runtime	See Note.
B181E690	Fail-over cannot be enabled at runtime without having a backup that has not IPLed the system even once	See Note.
B181E692	Error trying to get FSP alpha version key	See Note.
B181E693	Failed check for fail-over capable	See Note.
B181E699	Unknown HMC command received	See Note.
B181E69D	Attempt to restart discovery command received	See Note.
B181E801	Failure to read from or write to registry	See Note.
B181E802	Failed to synchronize with client	See Note.
B181E803	Failure with network server	See Note.
B181E804	Thread failure	See Note.
B181E805	Client failure	See Note.
B181E806	Failure when calling Code Update	See Note.
B181E807	Failure from Mailbox function	See Note.
B181E808	Failure to read or write using DMA for SMA Dump Header	See Note.
B181E809	The SMAs that were selected to perform an MP Fatal Dump did not all complete successfully	See Note.
B181E80A	System Type was not recognized	See Note.
B181E80B	Failure in Load IPC Bootstrap execution	See Note.
B181E80C	Null pointer while iterating through the SMAs	See Note.
B181E80D	Received invalid initialization type input	See Note.
B181E80E	The MP reset procedure failed	See Note.
B181E80F	The MP reset procedure failed	See Note.
B181E810	The MP reset procedure failed	See Note.
B181E811	The MP reset procedure failed	See Note.
B181E812	Failure to find a matching SMA Handle for the inputted SMA id	See Note.
B181E813	Received a command to invalidate an SMA Dump when no SMA Dump was present	See Note.
B181E814	Failure in dump utility that reads and formats System Type, Model, and Feature Code	See Note.
B181E815	Failure in attempting to signal event	See Note.
B181E81F	Test of log failed	See Note.
B181E901	Reset/reload occurred	See Note.
B181E902	No SRC in log	See Note.
B181E90a	Unable to clear bits in the DISR	See Note.
B181E90d	No routine for reset/reload call	See Note.
B181E90e	Invalid routine for reset/reload call	See Note.
B181E90f	Received unexpected signal	See Note.
B181E910	Unable to set bits in the DISR	See Note.
B181E911	Reset/reload occurred	See Note.
B181EA00	Unable to create a session entry object for the specified HMC index	See Note.
B181EA01	Error while packaging outbound payload data for the HMC	See Note.
B181EA02	Failure occurred with another component API	See Note.
B181EA03	Failed to read from or write to registry	See Note.
B181EA04	No Concurrent Maintenance lock found	See Note.
B181EA05	Unable to convert location code to RID	See Note.
B181EA06	Failure occurred with another component API	See Note.
B181EA07	Failure occurred with another component API	See Note.
B181EA08	Failure occurred with another component API	See Note.
B181EA09	Invalid RID for Concurrent Maintenance request	See Note.
B181EA0A	Machine type or state incorrect for Concurrent Maintenance operations	See Note.
B181EA0B	Node or GX resource failed during hot add	See Note.
B181EA0C	Failure occurred with another component API	See Note.
B181EA0D	Sequencing failure or cannot write checkpoint because system is transitioning	See Note.
B181EA0E	Not enough memory to reserve a GX adapter	See Note.
B181EA0F	Failed to read path from registry	See Note.
B181EA10	Detected corruption of the GX reservation area	See Note.
B181EA11	Failed to send activation asynchronization message	See Note.
B181EA12	Failed to create session entry object	See Note.
B181EA13	Unable to gard the FSP	See Note.
B181EA14	Failed to unlock file mutex	See Note.
B181EA15	FSP aborted the transition file	See Note.
B181EA16	Failed to send progress code	See Note.
B181EA17	Unable to read sibling FSP state data	See Note.
B181EA18	Failed to activate power domain	See Note.
B181EA19	Abort detected	See Note.
B181EA1A	The system has new FSP cables attached to the system, but they are not the appropriate ones	See Note.
B181EA1E	Concurrent Maintenance operation started	See Note.
B181EA1F	Concurrent Maintenance operation stopped	See Note.
B181EF01	Only one active object is allowed per process	See Note.
B181EF02	Failed to detect error in normal path	See Note.
B181EF03	Check for valid FSP dump failure	See Note.
B181EF0A	External failure writing registry	See Note.
B181EF0C	Inconsistency in saved data header	See Note.
B181EF0D	Failure reading or writing a file	See Note.
B181EF0F	Notify PHYP failure	See Note.
B181EF11	Failed to update headers	See Note.
B181EF12	Failed to update headers	See Note.
B181EF13	Failed to update headers	See Note.
B181EF17	Failed to seek correct position in file	See Note.
B181EF1A	Failed to display status to Panel	See Note.
B181EF1F	Failed to enable FSP dump	See Note.
B181EF28	I/O controller error	See Note.
B181EF2D	Failed to signal for HMC notification	See Note.
B181EF2E	Internal HMC notify failure	See Note.
B181EF2F	HMC notify failure	See Note.
B181EF32	Failed to initialize I/O controller	See Note.
B181EF33	Failed to close I/O controller	See Note.
B181EF34	Failed to check inputs	See Note.
B181EF35	Failed to check inputs	See Note.
B181EF36	Failed to setup for command	See Note.
B181EF37	Failed to setup for command	See Note.
B181EF38	Failed to trace command	See Note.
B181EF39	Failed to trace command	See Note.
B181EF3D	Failed to display status to Panel	See Note.
B181EF3E	Failed to read registry	See Note.
B181EF3F	Failed to write registry	See Note.
B181EF40	Failed to trace command	See Note.
B181EF41	Failed to trace command	See Note.
B181EF42	NULL command specified	See Note.
B181EF44	Failed default command	See Note.
B181EF45	Failed to zip memory	See Note.
B181EF46	Failed to collect data	See Note.
B181EF4A	Failed to read registry	See Note.
B181EF4B	Failed to write registry	See Note.
B181EF4C	Failed to complete headers	See Note.
B181EF4D	Failed to complete dumped headers	See Note.
B181EF52	Invalid input for FSP dump	See Note.
B181EF53	No data to gather for FSP dump specified	See Note.
B181EF54	Not enough room left on flash	See Note.
B181EF55	Not enough room left on flash	See Note.
B181EF56	Moving backwards in the FSP dump file caused error	See Note.
B181EF57	Moving backwards in the FSP dump file caused error	See Note.
B181EF5A	Failed to get FSP dump id	See Note.
B181EF5B	Failed to get FSP dump length	See Note.
B181EF5C	Failed to read registry	See Note.
B181EF5D	Failed to read registry	See Note.
B181EF5E	Failed to execute Panel function 20	See Note.
B181EF5F	Failed to read registry	See Note.
B181EF62	Failed to execute FSP dump	See Note.
B181EF63	Failed to execute FSP dump	See Note.
B181EF64	Failed to execute FSP dump	See Note.
B181EF65	Out of flash failure	See Note.
B181EF66	FSP dump controller failure acknowledged, must continue	See Note.
B181EF67	FSP dump controller failure acknowledged, terminate FSP dump sequence	See Note.
B181EF69	FSP dump controller failure	See Note.
B181EF6C	Failed I/O boundary device	See Note.
B181EF6D	Failed to write FSP dump	See Note.
B181EF71	Failed to check for valid FSP dump	See Note.
B181EF73	Failed to start FSP dump due to not finding FSP dump file	See Note.
B181EF75	Failed to start FSP dump due to not finding FSP dump file	See Note.
B181EF79	Failed to start FSP dump	See Note.
B181EF7A	Failed to increment device bank	See Note.
B181EF7B	Failed opening FSP dump device for initial navigation	See Note.
B181EF7C	Failed to lock FSP dump device	See Note.
B181EF7D	Failed to close FSP dump device	See Note.
B181EF7E	Failed initial device navigation	See Note.
B181EF7F	Failed to close device navigation	See Note.
B181EF80	Code updated forced clear of all pending and existing FSP dumps	See Note.
B181EF81	Failed FSP dump cancellation checking	See Note.
B181EF82	Cancelled dump due to Code update	See Note.
B181EF83	Failed to invalidate FSP dump	See Note.
B181EF84	Failed to retrieve FSP dump	See Note.
B181EF85	A FSP Dump occurred	See Note.
B181EF86	Failed to read registry	See Note.
B181EF87	Failed to set lid for FSP dump	See Note.
B181EF88	A user or surveillance initiated a FSP dump	See Note.
B181EF8B	Failed to set header value	See Note.
B181EF8D	Failed to check boot watchdog sideswitch	See Note.
B181EF8F	Failed to get dynamic MTD sizing	See Note.
B181EF90	Failure in creating a buffer about a critical FSP dump operation	See Note.
B181EF91	FSP dump was invalidated	See Note.
B181EF93	Cannot enable degraded mode as FSP dump device is locked	See Note.
B181EF94	Temporarily disabled function due to code update	See Note.
B181EF95	Code update deallocated part of FSP dump data and user is trying to access them	See Note.
B181EF96	Can't enable degraded mode because there are FSP dumps pending	See Note.
B181EF97	Degraded partition interface error	See Note.
B181EF98	Inconsistency in the persistent storage area in flash was detected	See Note.
B181EF99	Multiple FSP dump support logic failure	See Note.
B181EF9A	Out of FSP dump storage	See Note.
B181EF9B	Failed to open file	See Note.
B181EF9C	Failed to read registry	See Note.
B181EF9D	Confirm bank enablement failure	See Note.
B181EF9E	Persistent storage area was reinitialized	See Note.
B181EF9F	General failure during initialization of FSP dump	See Note.
B181F000	Failed to remove directory	See Note.
B181F003	Not able to create directory	See Note.
B181F004	Error return from file open command	See Note.
B181F005	Error return trying to read from a file	See Note.
B181F006	Error returned trying to write to a file	See Note.
B181F007	Failed to get status of file	See Note.
B181F009	Error returned trying to seek offset file	See Note.
B181F00E	Error returned from a DMA Write attempt	See Note.
B181F00F	Failed to get next file space	See Note.
B181F010	Illegal MDRT section size detected	See Note.
B181F012	Failed to determine size of registry variable	See Note.
B181F013	Error return trying to read from the registry	See Note.
B181F014	Error returned trying to write to the registry	See Note.
B181F015	Error returned from thread function	See Note.
B181F017	Error return from another function	See Note.
B181F018	Received an unexpected signal	See Note.
B181F019	Object not found or returned	See Note.
B181F01A	The requested Policy value is not in the bounds	See Note.
B181F01B	Unable to stop Clocks within the dump hardware collection	See Note.
B181F01C	Control Block not valid size or invalid flattened control block	See Note.
B181F01E	Status failure in call to create SRC object	See Note.
B181F022	No file spaces left to store dump memory on	See Note.
B181F029	System busy or there is no dump pending flag set	See Note.
B181F02C	Override Content has change dump type to NO DUMP	See Note.
B181F02D	A No Dump request was made	See Note.
B181F02E	Manufacturing Policy Flag has set NO DUMP policy	See Note.
B181F02F	No dump correctable error file present	See Note.
B181F030	Mainstore dump not taken	See Note.
B181F031	A correctable error was encountered while invalidating dump	See Note.
B181F038	Termination of the system to occur	See Note.
B181F039	Requested to invalidate the dump on the system	See Note.
B181F03B	It was determined that no exit error state IPL would be needed because no mainstore dump is required	See Note.
B181F03C	Mainstore dump not taken	See Note.
B181F03D	Non-user requested dump and the dump policy is set to NO DUMP	See Note.
B181F03E	Dump pending. Must invalidate dump before another dump can be called	See Note.
B181F100	Invalid position on chain	See Note.
B181F101	No chips in chain	See Note.
B181F102	Commands added exceed chain command size	See Note.
B181F104	Chip not found	See Note.
B181F105	Invalid Ring buffer size	See Note.
B181F10A	Failure to release lock	See Note.
B181F110	Failure with controller device driver	See Note.
B181F111	Invalid device number	See Note.
B181F118	Abort signaled	See Note.
B181F11A	Failure to release lock	See Note.
B181F11B	Attempt to release lock that is not held	See Note.
B181F125	Invalid command ID	See Note.
B181F126	Invalid use of get scom JTAG interface	See Note.
B181F127	Invalid use of put scom JTAG interface	See Note.
B181F128	Invalid use of flush JTAG interface	See Note.
B181F12C	Unmatched CRC	See Note.
B181F12D	Chip detected CRC miscompare on scan-in	See Note.
B181F12E	Detected scom attentions	See Note.
B181F12F	Bad parity or invalid command	See Note.
B181F130	Invalid flush operation code	See Note.
B181F131	Last bits of chip command status are not 0x01	See Note.
B181F132	Invalid ring selection	See Note.
B181F133	Clocks did not start	See Note.
B181F134	Could not stop clocks	See Note.
B181F135	Invalid call to enable drivers	See Note.
B181F136	Invalid call to disable drivers	See Note.
B181F138	Scom attention detected on the current chip	See Note.
B181F139	Master Attention Alone detected	See Note.
B181F13A	Unrecognized attention type condition	See Note.
B181F13B	Invalid function call to attentions	See Note.
B181F13D	Prohibited command found during initialize scom IPL step	See Note.
B181F13E	Unable to find CEC cage	See Note.
B181F140	Data shows invalid ECID value	See Note.
B181F141	Indicates a potential problem with clock card	See Note.
B181F142	Could not get valid hom id of active clock card	See Note.
B181F200	Configuration failure	See Note.
B181F201	The HOM unit ID is not present in this system	See Note.
B181F202	The mainstore memory size has not been properly initialized	See Note.
B181F206	There is a card in the system that is missing or has corrupted VPD data	See Note.
B181F208	Avoid following the NULL rule facade pointer	See Note.
B181F209	The specified card object was not found	See Note.
B181F20A	The call to create a card returned a NULL pointer	See Note.
B181F20B	An error occurred while creating a system domain and returned a NULL pointer	See Note.
B181F20C	There was an error while attempting to create a group and the function returned a NULL group pointer	See Note.
B181F20D	There is an inconsistency between the size of the JTAG chain and the number of JTAG chains counted	See Note.
B181F20E	The chip rule facade pointer created was returned as NULL	See Note.
B181F211	Creation of a cage pointer failed	See Note.
B181F212	The cage rule facade pointer was not found	See Note.
B181F217	An error occurred while attempting to create the JTAG controller object and returned a NULL instance pointer	See Note.
B181F21C	The instance variable for the JTAG chains is NULL even after successful creation of the chains	See Note.
B181F21D	The FRU was not found or does not exist	See Note.
B181F21E	The MRU or FRU was not found or does not exist	See Note.
B181F21F	Invalid input	See Note.
B181F220	The functional unit for a JTAG operation was not found	See Note.
B181F222	The functional unit has experienced a hardware monitor error	See Note.
B181F225	Attempting to write an invalid frequency to a clock card	See Note.
B181F227	An invalid VPD port number was encountered	See Note.
B181F228	A memory block trying to be referenced is out of range	See Note.
B181F22A	There was not enough functional hardware found in the system to continue IPLing	See Note.
B181F22B	A memory controller group pointer was initialized to NULL by the cvMapper	See Note.
B181F22C	Got an invalid unit id	See Note.
B181F239	Detected a missing chip	See Note.
B181F23E	There is a mismatch between the number of nodes present and the type of SMP cable being used	See Note.
B181F23F	The mainstore configuration changed from the previous IPL, mainstore cannot be preserved	See Note.
B181F241	Light strips have not been plugged correctly	See Note.
B181F242	The slot specified should NOT be turned on	See Note.
B181F243	PRS data returned indicates that the Light Strip attempting to be powered off was not powered off	See Note.
B181F244	It seems that both clock cards, which should be present in the system, are not present in the system	See Note.
B181F245	This is an unrecognized cable state for this machine	See Note.
B181F25E	Cannot get a pointer to the System Fabric Group	See Note.
B181F2C0	Function pointer from dynamic load is NULL	See Note.
B181F2C1	Functional Unit of wrong type	See Note.
B181F2CC	Invalid parameter passed in to function	See Note.
B181F2CD	Failed trying to release JTAG Controller lock after reading the JTAG Controller's interrupt registers	See Note.
B181F2DC	Received an empty list of Chips at attention	See Note.
B181F2DE	Elastic Interface Alignment Procedure never completed	See Note.
B181F2DF	Fatal IAP Error	See Note.
B181F2E0	Non-fatal IAP Error/Warning	See Note.
B181F2E3	Couldn't get pointer object	See Note.
B181F2E4	Selected elastic interface is Non-functional	See Note.
B181F2E5	One or more lines are stuck low for the ISR because the value read back does not match FF's	See Note.
B181F2E6	The attention line stuck high test failed to clear all the FSP attention lines	See Note.
B181F301	Object not initialized	See Note.
B181F304	Object attributes not set	See Note.
B181F305	Failed to set scom register attributes	See Note.
B181F306	Attributes are not set	See Note.
B181F308	Attributes not yet set	See Note.
B181F309	Could not find a Functional Unit that used the specified ring or register	See Note.
B181F30A	Data not extracted	See Note.
B181F30B	Data not inserted	See Note.
B181F30F	Incorrect buffer size	See Note.
B181F310	Incorrect buffer size	See Note.
B181F311	Required register or ring not present	See Note.
B181F312	File open error	See Note.
B181F401	Illegally calling this function	See Note.
B181F405	Could not create cage rule facade for this cage	See Note.
B181F407	Could not find a unique or default entry for this combination of inputs	See Note.
B181F408	Could not read card slot table - end of file or file failure	See Note.
B181F409	End of file reached before row number found	See Note.
B181F40a	Size of array needed exceeds size of array passed in	See Note.
B181F40b	Number exceeded maximum number allowed	See Note.
B181F40c	Could not open library for the object to create or unflatten	See Note.
B181F40d	Could not open class for the object to create or unflatten	See Note.
B181F500	File IO error occurred	See Note.
B181F501	The specified HOM Object was not found	See Note.
B181F502	Specified HOM Object does not exist	See Note.
B181F504	The requested function is invalid	See Note.
B181F505	User attempted to save a HOM signature into a data buffer that was too small for the amount of data to be saved	See Note.
B181F506	Got an invalid unit id	See Note.
B181F507	A thread failed to start	See Note.
B181F620	Failure with functional unit	See Note.
B181F621	Scom bus busy after timeout	See Note.
B181F625	Timed out waiting for instructions to stop	See Note.
B181F62A	Timeout reached on scom poll	See Note.
B181F62B	Tried a clock operation which isn't supported on this functional unit	See Note.
B181F62E	Trying to instruction step while they are still running	See Note.
B181F630	I2C lock counter is a negative number, it should always be positive or zero	See Note.
B181F633	Failure while trying to open the attention handler data file for write operation	See Note.
B181F634	The bits active in the Special Attention register are not supported	See Note.
B181F636	Object pointer returned NULL	See Note.
B181F638	Clocks need to be on or off but mode says not to change state	See Note.
B181F639	Bad parameter passed into function	See Note.
B181F63B	Instructions failed to start	See Note.
B181F63C	Instructions failed to step	See Note.
B181F63D	Unexpected NULL pointer for Fabric Functional unit	See Note.
B181F647	An attention is active from a thread which is not alive	See Note.
B181F648	Cannot process special attention since Memory controller object is null	See Note.
B181F649	XScom is busy or has errors	See Note.
B181F64A	FOCR state machine wasn't idle after clearing	See Note.
B181F64B	The GR GX auto TLAR calculation failed	See Note.
B181F64C	Failed to complete self synchronization	See Note.
B181F64D	Error encountered during self synchronization	See Note.
B181F64F	Address + entries exceeds maximum SMA External SRAM size	See Note.
B181F653	Service buffer timed out while writing data	See Note.
B181F654	An attention not supported has been detected in SMA hardware	See Note.
B181F658	Invalid data	See Note.
B181F659	Not able to find master or slave target time data for a chip	See Note.
B181F65A	GS Figtree database not loaded for this object or Functional Unit	See Note.
B181F65D	Memory queues are not idle	See Note.
B181F65E	Maintenance command timed out	See Note.
B181F65F	Maintenance command failed	See Note.
B181F660	Command in progress while trying to send maintenance command	See Note.
B181F661	Instruction start or stop attempted on non alive thread	See Note.
B181F662	Fabric initialization failed on processor	See Note.
B181F663	Fabric initialization failed on processor	See Note.
B181F664	Fabric Quiesce failed	See Note.
B181F67B	Got an invalid unit id or NULL pointer	See Note.
B181F67C	Calling function on invalid object	See Note.
B181F67D	Operation attempted on nonfunctional Functional unit	See Note.
B181F686	Can't get the associated FRU ID	See Note.
B181F689	Could not find associated Chip	See Note.
B181F68C	Unsupported bit(s) set in the local special attention register	See Note.
B181F68D	Fir bit indicates problem with SP code or SMI	See Note.
B181F6F2	Microcode failed to execute	See Note.
B181F6F3	Microcode failed to execute	See Note.
B181F6F6	Bootstrap executed successfully, but FSP was not permitted to set MP Available latch	See Note.
B181F7A0	The dump file contains a dump and cannot be read by the saved configuration for fast boot feature to examine the previous system configuration	See Note.
B181F7A1	Figtree library call failed	See Note.
B181F7A2	No TCE region found for GX Controller	See Note.
B181F7A7	No valid MC PLL Multiplier found when MC uses internal clock source	See Note.
B181F7A8	Host PCI enable failed	See Note.
B181F7A9	Host PCI verify failed	See Note.
B181F7AB	Memory Sharing Group is an invalid configuration	See Note.
B181F7AC	A chip is in Bus Trace Mode, but doesn't have any attached memory	See Note.
B181F7AD	Memory group contains chip in Bus Trace Mode, but base address is zero	See Note.
B181F7AE	No system EI table found for bus	See Note.
B181F7AF	No entry in system EI data table for bus and master chip position	See Note.
B181F7B8	Resource pointer was NULL	See Note.
B181F7B9	The passed in buffer pointer was NULL	See Note.
B181F7BA	Couldn't find frequency data type requested	See Note.
B181F7BB	The system resource(s) in the callout list failed a system configuration test	See Note.
B181F7BC	The user specified LMB size is not valid for this system's memory size, so the system will use the default LMB size for this configuration	See Note.
B181F801	NULL Functional Unit Pointer	See Note.
B181F802	Not enough space	See Note.
B181F803	Not enough space	See Note.
B181F804	Index out of bounds	See Note.
B181F805	Failed to read the number of memory chips	See Note.
B181F806	Procedure error using display/alter	See Note.
B181F807	Invalid thread selected for FPSCR	See Note.
B181F809	Unable to associate array ID for address	See Note.
B181F80a	Invalid operation specified	See Note.
B181F80b	Unable to Create or remap Logical to Physical Mapper	See Note.
B181F80c	Could not create server object instance	See Note.
B181F814	Invalid address. Does not map to any memory location	See Note.
B181F815	Invalid Data Length specified	See Note.
B181F816	NULL Rule Chip Facade Pointer	See Note.
B181F817	Error encountered while reading array entry	See Note.
B181F818	Error encountered while writing array entry	See Note.
B181F81b	Mismatch data error	See Note.
B181F81e	Unable to allocate buffer or NULL pointer detected	See Note.
B181F950	received an unexpected signal	See Note.
B181F951	Error from abort message	See Note.
B181F952	Buffer is NULL or is too small to hold information	See Note.
B181F953	Failed to receive message	See Note.
B181F954	Error creating serial thread in cec server	See Note.
B181F955	Error creating listener thread in cec server	See Note.
B181F956	Failed to get token in cec server	See Note.
B181F957	Invalid command received	See Note.
B181F958	Failure obtaining mutex lock in serial thread	See Note.
B181F959	Error while sending message	See Note.
B181F95A	Error while sending message	See Note.
B181F95B	Error receiving message in serial thread	See Note.
B181F95E	Error initializing cec server daemon	See Note.
B181F95F	Invalid arguments	See Note.
B181F966	Error while unflattening HOM data	See Note.
B181F968	Error writing to bit buffer	See Note.
B181F96A	Not enough parameters	See Note.
B181F96B	No function specified	See Note.
B181F96C	Specified function not found	See Note.
B181F96D	Too many parameters supplied	See Note.
B181F96E	Unknown option specified	See Note.
B181F96F	Some value required for these options is missing	See Note.
B181F970	Unknown parameter type	See Note.
B181F971	Input value out of range	See Note.
B181F972	Invalid input character	See Note.
B181F973	String not found in lookup table	See Note.
B181F974	Buffer too small	See Note.
B181F975	Unknown output type	See Note.
B181F978	An HMC requested operation is not supported	See Note.
B181FAA3	Invalid parameter to function	See Note.
B181FAA4	Number of packets sent does not equal number received or CRC not zero	See Note.
B181FAA9	Can't get the sharing group for this Chip	See Note.
B181FAB0	Physical Status registers not set to link up; test can not proceed	See Note.
B181FAB1	Number of packets sent does not equal number received or CRC not zero	See Note.
B181FAB2	RIO test failure	See Note.
B181FAB3	Galaxy test failed during communication stage	See Note.
B181FB51	Maximum number of wire test errors has been reached	See Note.
B181FB54	RDT has detected a hardware error	See Note.
B181FD00	An FSP or DMA path was GARDed out	See Note.
B181FD01	The command line was used to manually configure or deconfigure a resource	See Note.
B181FD02	GARD Data did not exist because either it was the first IPL on this machine or NVRAM had been cleared	See Note.
B181FD03	GARD detected a new version of the gard data area	See Note.
B181FD04	GARD detected corrupt gard date	See Note.
B181FD05	GARD could not open the Gard Memory File	See Note.
B181FD06	Error trying to read a file	See Note.
B181FD07	Error trying to write IO Data to the Gard file	See Note.
B181FD0A	Failed setting the rank status in the HOM	See Note.
B181FD0B	Failed setting functional status of a non-rank unit	See Note.
B181FD0D	Failed to read registry	See Note.
B181FD0E	Failed to read the VPD data for a given resource id	See Note.
B181FD10	The input Resource ID is not an FSP that can have its GARD state changed	See Note.
B181FD11	Manual deconfiguration of FSP is not allowed because FSP is already System Deconfigured or because we are at runtime	See Note.
B181FD12	This interface was called with more than the allowed number of DMA Paths	See Note.
B181FD13	The input DMA path did not match any stored in VPD	See Note.
B181FD14	Ungarding the sibling FSP is not allowed at Runtime	See Note.
B1828811	Incorrect command in Attention Area memory as it does not match up with the requested Service Routine	See Note.
B182901C	Failed trying to get status of the LID file	See Note.
B182901D	Failed to get OLC or CONTINUE ACK response from PHYP	See Note.
B182901F	SPIRA does not have sufficient space for the data structure	See Note.
B1829025	Event id which satisfied the monitor was incorrect	See Note.
B1829503	The FSP has queued its maximum number of messages to the send queue	See Note.
B1829504	There is nobody waiting on the message we just received from PHYP	See Note.
B1829507	Unable to write error\event log that PHYP wanted	See Note.
B1829508	PHYP passed the FSP a zero TCE or a TCE with something in the top 4 bytes	See Note.
B182950C	Indicates that PHYP sent the FSP a bad size, modifier or HMC index	See Note.
B182950D	PHYP didn't provide enough data to write the LID or the first TCE is too small to contain the LID header (although the latter is less likely)	See Note.
B1829511	Warning that HMC message has reached timeout limit	See Note.
B1829512	PHYP tried adding an existing HMC buffer to the list	See Note.
B1829513	PHYP is garding the anchor card and since we don't get any SRC from them, we make this one up	See Note.
B182951A	Wrong modifier received on OLC command	See Note.
B182951C	PHYP didn't acknowledge the message that the FSP sent to it within the architected timeout value	See Note.
B182951D	PHYP tried to use a HMC buffer that they haven't defined or they don't own	See Note.
B182951E	PHYP returned non-zero status in the acknowledge message	See Note.
B1829523	Failed on setup for reset/reload	See Note.
B182D004	Failed to get enclosure list	See Note.
B182D005	Failed to set drawer information	See Note.
B182E500	Bad hardware	See Note.
B182F023	Bad TCE returned	See Note.
B1878707	Error function not available	See Note.
B187E500	Bad hardware	See Note.
B1A3E500	Bad hardware	See Note.
Note: Repair the serviceable event that sent you here. If the FRU list is empty, call the next level of support.

Table 3. (B1xx) Service processor reason codes' ranges
Reason codes for	Range	Description
End Device Abstraction Layer (EDAL) ranges
DMA EDAL	'1000'x through '10FF'x	The direct memory access EDAL component (DMAE ) is a shared library that allow applications to transfer data between system memory and the service processor's address space. DMAE is normally used by the Hypervisor data initialization (HDAT) component during boot. The dump component also uses DMAE for collecting dumps.
Control Panel I2C EDAL	'1100'x through '111F'x	IPNL provides an interface to the control panel hardware and handles all of the internal communication details. The PANL component uses IPNL extensively.
VPD I2C EDAL	'1300'x through '13FF'x	IVPD collects and reports vital product data (VPD) found in the system unit hardware. Data collected from the hardware is analyzed and stored file system of the service processor. Hardware VPD update facilities are also provided. VPD collection and reporting provides a system-wide view of the current hardware configuration.
RPC I2C EDAL	'1400'x through '141F'x	IRPC manages the low-level IIC bus interface to remote power controllers (RPCs) on some types of servers.
Smart Chip VPD EDAL	'1500'x through '15AF'x	SCED collects and reports VPD found in the system unit hardware. Data collected from the hardware is analyzed and stored in the file system of the service processor. Hardware VPD update facilities are also provided. VPD collection and reporting provides a system-wide view of the current hardware configuration.
Power control code ranges
Power Control Interface	'2000'x through '204F'x	The system power interface (SPIF) component provides a communication interface between service processor components and the system power control network (SPCN). The server uses SPIF to obtain the system power state and other data.
Remote Power Control	'2100'x through '211F'x	REMP manages the high-level communication protocol between the service processor and the RPCs on some types of servers.
IPL Lock	'2200'x through '222F'x	The IPL lock component synchronizes dependent operations with boot transition requests. It performs this synchronization by evaluating the system when a boot is requested. Note: A dependent operation is an operation that requires that no boot transition request of a certain type be allowed while the operation is being performed. Writing to flash memory is an example of a dependent operation.
Auto Power On Restart	'2300'x through '231F'x	This component's functionality is configured by the customer. If enabled, this component automatically performs a power-on reboot following an unexpected loss of power.
Remote Platform Power On	'2400'x through '241F'x	The remote platform power on component allows a user to remotely power on a system using the wake on LAN capability (which is accessed via the ASMI) when the system is powered off.
Thermal Management	'2600'x through '261F'x	The thermal management component is responsible for reading processor thermal calibration data, for providing an interface which firmware uses to read processor temperatures, and for handling thermal alerts generated by the processor's thermal sensors.
System infrastructure ranges
Code Update	'3000'x through '305F'x	CUPD controls the updating of firmware on the service processor. You might see this code when the error occurs: During the code update (flash) process. During the code promotion process. After the code updates successfully and the system reboots from the new code side, a user might use the code promote command to copy the new code from the temporary (or T side) to the permanent (or P) side. When the service processor reboots after a code update, which is when the service processor makes the redundant boot code. During the booting of the managed system, which is when the code update process attempts to verify flash image during the power on process for the system unit. The error can be caused by: A bad or invalid system firmware image A service processor failure, which leads to the firmware being unable to perform the code update Corruption of the update file, which occurs when the file is sent from the management console (HMC) or the Hypervisor An internal code problem A problem with the network issue A user error. which might occur when a user does not follow the update process
Discovery	'3500'x through '35FF'x	The DSCV component manages dual service processors in those systems that can have a primary and a secondary service processor. DSCV exchanges the required information between the service processors to establish the various communication links between them.
IPL Parameters	'4000'x through '402F'x	The IPLP component manages some of the service processor registry data that is transferred to the Hypervisor at boot time, such as IPL speed, logical memory block size, and so on.
RTC Application	'5000'x through '503F'x	The RTIM component manages the battery-backed real time clock hardware on the service processor, which is the source of the system-level time-of-day (TOD) clock.
State Manager	'6000'x through '603F'x	The SMGR component is responsible for supervising the IPL. It determines the validity of an IPL request and attempts to IPL the system.
State Transition Manager	'6500'x through '651F'x	The STTR component contains the various transition files that the system uses to make the transition from one state to another (for example, powering on or powering off the system unit, performing a platform dump, and so on).
Error Logging	'7000'x through '703F'x	The ERRL component provides data logging, entry management, and the reporting of application errors to the operating system.
Primary PCI bus Initialization	'7100'x through '711F'x	The PPIN component monitors for power events, such as power on and power off.
Boot Plug-in	'7200'x through '721F'x	The BOOT component reads user preferences and determines which service processor flash side to boot from.
Service processor firmware utilities ranges
Switch BCU utility	'8100'x through '811F'x	The SBCU component manages the PCI bus switch state in the registry. Note: Two switch states are possible: The service processor owns the PCI bus The system unit owns the PCI bus
SRC Interface	'8200'x through '821F'x	The SRCI component is a service processor utility that allows the user to do the following: Create, display, and trace SRCs Retrieve SRC entries from an SRC trace
CEC Termination	'8300'x through '834F'x	The CTRM (CEC Termination) component terminates the service processor. When an application encounters a fatal error (that the application determines should lead to system termination), the application uses its error log to call CTRM. After being called, CTRM displays the terminating SRC on the panel and records the error.
NVRAM Initialization	'8400'x through '841F'x	The NVRI component used to initialize and configure the service processor.
Event Notification	'8500'x through '853F'x	The EVEN component provides the facilities to signal and monitor for the occurrence of specified events. It is one way of performing interprocess communication within the service processor firmware.
Process Error Context	'8600'x through '861F'x	The PERC component allows a service processor application to collect some flight recorder information (FFDC) when the service processor receives an unexpected signal.
Network Server	'8700'x through '877F'x	The NETS code component dynamically loads libraries for the operations and functions that it services.
Network Client	'8780'x through '87FF'x	The NETC component is the client interface plug-in that applications running on the service processor, manufacturing and the HMC use to talk to the servers and other applications running on the service processors. NETC provides wrappers for the TCP/IP and sockets API and serial traffic APIs. It also provides a common message format for communication and data packets.
Hypervisor Service Routine	'8800'x through '883F'x	The HYSR component allows the user to run a Hypervisor service routine from the service processor. Typical uses of a Hypervisor service routine include validating a system storage address and performing a system storage dump for a platform dump.
Process Synchronization	'8900'x through '891F'x	The SINK component synchronizes the time when a server process is ready to interact with a client process.
Utility Component	'8A00'x through '8A1F'x	The UTIL component provides common functionality throughout the service processor environment, such as common file, registry, and semaphore manipulation.
External firmware interfaces ranges
Hypervisor Data Initialization	'9000'x through '904F'x	The HDAT component does the following: Loads the Hypervisor code into system storage Gathers various pieces of information that describe the hardware configuration and various boot parameters and loads that data into the main storage Starts the execution of the processors that run the Hypervisor and the partition firmware
Host Virtual Serial Interface	'9200'x through '921F'x	The HVSI component provides the host virtual serial interface, which allows the host operating system to use the serial ports of the service processor as if they were the native serial ports.
Mailbox Handling	'9500'x through '952F'x	The MBOX component handles certain hardware on the service processor (called the mailbox) that is accessible to both the operating system and the service processor. The mailbox enables the system to transfer small amounts of data between the service processor and operating system, so that they can communicate to each other at runtime.
Service Processor Capacity Upgrade on Demand	'9900'x through '991F'x	The SCOD component provides information about the state of the previous power off and whether the system lost AC power after the power off.
Panel	'A000'x through 'A07F'x	The PANL component processes the pressing of control panel buttons and updates the control panel display appropriately.
Virtual Panel	'A200'x through 'A21F'x	The VPNL component implements the virtual control panel functions in the firmware.
Vital Product Data (VPD)	'B000'x through 'B0FF'x	The SVPD component collects and reports VPD found in the hardware of the system unit, which provides a system-wide view of the current hardware configuration. Data collected from the hardware is analyzed and stored in file system of the service processor. SVPD also provides hardware VPD update facilities.
VPD Location Codes	'B100'x through 'B11F'x	The VLOC component builds the location code table that the Hypervisor uses.
VPD LED Access	'B200'x through 'B21F'x	The VLED component provides library routines to drive the LEDs of the system unit. VLED uses the SVPD component to provide the bus mapping information. Other components can use the VLED routines to drive the LEDs to the desired state.
HMC Interface	'C000'x through 'C03F'x	The HMCX component provides the communications interface between the HMC and the service processor of the managed system.
Power Management	'C100'x through 'C1FF'x	The POWR component controls the power supplies, regulators and blowers and collects and reports power status, power VPD, and temperatures of the system unit and I/O towers and drawers.
Service Processor Menus	'D000'x through 'D03F'x	The MENU component provides both a Web browser interface and a legacy TTY (text based) interface (both are known as the Advanced System Management Interface, or ASMI). The ASMI enables users to configure the service processor, change selected system-level settings, and access certain service processor resources.
Attention Handler	'D100'x through 'D13F'x	The ATTN component processes the checkstops, recovered errors, and special attentions that come from the hardware. ATTN also makes appropriate calls to components like processor runtime diagnostics (PRD) so that the system properly handles attentions.
Reliability, Availability, and Serviceability (RAS) ranges
Call-in/Call-out	'E000'x through 'E02F'x	The CALL component provides remote service functions (like call home, call in, and call out) and SRC display on serial ports.
Snoop/Wrap	'E100'x through 'E11F'x	The SNOP component provides the serial port snoop function. SNOP can be used only when the system is in single partition mode. This component also detects the legacy iSeries UPS, if present, and reports the number of serial ports available to the operating system.
CEC Reboot	'E200'x through 'E21F'x	The RBOT component determines if an system unit re-IPL needs to occur after a termination.
LED Management	'E300'x through 'E31F'x	The LEDS component supports the service indicators (used by to identify failing FRUs) and controls the system attention indicator.
Surveillance	'E400'x through 'E460'x	The SURV component detects the failures of critical components, such as the Hypervisor or the HMC, and takes the appropriate actions.
Processor Runtime Diagnostics	'E500'x through 'E51F'x	When the service processor receives an attention from system hardware, PRDF examines the error registers in the system to determine what happened and creates an error log entry that calls out one or more failing items. Note: The E500 code denotes a hardware error, or an error in software other than processor runtime diagnostics. The E501 code is reserved for PRD code errors.
Redundancy Manager	'E600'x through 'E6A0'x	The RMGR component controls the interactions between the primary and the secondary service processors on a model 550, 590, or 595 system.
Synchronization of Redundant Service Processors	'E700'x through 'E71F'x	The SYNC component, which is part of the RMGR component, performs data synchronization between the primary and the secondary service processors on a model 550, 590, or 595 system.
SMA Dump	'E800'x through 'E81F'x	The SDMP component controls the sequencing of the initialization of SMA adapters to the message passing available state.
Reset/Reload	'E900'x through 'E91F'x	The RSRL component saves the most recent critical error log in the event of a reset or reload event (on the assumption that this log best explains the reason for the reset). In cases where the reset or reload event terminates the system, RSRL sends its error log to the administrator.
Concurrent Maintenance	'EA00'x through 'EA1F'x	The CCMM component provides the interface between the concurrent maintenance program (which is part of Service Focal Point) on the HMC and the service processor of the managed system.
Service Processor Dump (Belly-up DuMP)	'EF00'x through 'EFCF'x	The BDMP component dumps data that the system can use to debug a failure that occurs when the service processor and bulk power subsystems encounter an error on servers that are housed in 24-inch racks. The following service processor or bulk power subsystem errors might cause this type of dump: An application failure that leads to a core dump A panic of the service processor kernel An unexpected reset of the service processor or bulk power subsystem A user-injected dump on the service processor or bulk power subsystem that captures the state of the entire subsystem at a given moment in time
Dump	'F000'x through 'F03F'x	After the system detects a checkstop or other hardware error condition, the DUMP component gathers required hardware and possibly system memory contents to facilitate error recreation and analysis.
Hardware Object Model (HOM) ranges
HOM JTAG Interface	'F100'x through 'F16F'x	The HJTG component provides an interface for scanning data from firmware into the actual chips or from the chips into the firmware. The JtagInterface object represents the physical JTAG interface that is internal to each hardware chip. Firmware uses this piece of chip logic to communicate with the chip, and it is used anytime a JTAG operation is performed.
HOM Packaging Units	'F200'x through 'F25F'x	The HPKU component is a package management class that holds and manages the system hardware object model.
HOM Groups	'F2C0'x through 'F2FF'x	The HFUG component provides procedural support for chip functionality.
HOM Scan Rings	'F300'x through 'F31F'x	The HREG (HOM register) component provides a firmware object that represents a scan ring, SCOM register, or an alias, with its unique characteristics (address, length, etc.) in order to scan chips. HREG also provides the data storage area (called a bit buffer) that holds the data to be scanned as well as the algorithms the system uses to manipulate the data stored in the buffer.
HOM Rules	'F400'x through 'F41F'x	The RULE component provides access to certain configuration and engineering data that is stored in the esw_rtbl component. The system uses the data stored in the edw_rtbl component to model the system and to read from the hardware.
HOM Rules Tables	'F450'x through 'F46F'x	The RTBL component holds data.
HOM Utilities	'F500'x through 'F51F'x	The HUTL component provides common utility functions used by all of the hardware access code. HUTL also handles error logging and recovery actions for the system unit hardware during booting and execution of high-level boot steps related to initializing the system unit.
HOM Functional Units	'F620'x through 'F6FF'x	The HFUS component provides internal access to the chip functionality.
Central Electronics Complex (CEC) ranges
CEC Chip Initialization	'F700'x through 'F7FF'x	The CINI component initializes the chips in the system unit, based on the system configuration. These actions include configuring system memory and address ranges, chip modes, and communicating from chip to chip. CINI also determines and sets the processor and bus frequencies.
Display/Alter	'F800'x through 'F81F'x	The DADA component accesses (reads) and manipulates (writes) user information inside the system unit hardware by using the JTAG interfaces. Several hardware components use this functionality, including the certain CPU chips, L3 cache devices, and I/O controllers.
Hardware Interface Commands	'F950'x through 'F98F'x	The CHIC component provides the mechanism that allows a call made in an external service processor application to execute inside the system unit server application.
Automated Built-in Self-Test (ABIST)	'FA00'x through 'FA1F'x	The ABST component runs internal chip diagnostics as part of the system boot process. ABST tests the logic and arrays in each chip (as applicable) and peforms array repair (bit sparing) for processor chips, if necessary.
Logic Built-in Self-Test (LBIST)	'FA50'x through 'FA6F'x	The LBST component runs internal chip diagnostics as part of the system IPL process. LBST tests the logic and arrays in each chip (as applicable) and performs array repair (bit sparing) for processor chips, if necessary.
Memory Diagnostics	'FAA0'x through 'FABF'x	The MDIA component performs diagnostics on the system memory and L3 cache during the boot process by writing patterns into and reading the patterns back from system storage and L3 cache.
SIBATS	'FB00'x through 'FB1F'x	The SBAT component is part of the LBIST component.
Wiretest	'FB50'x through 'FB6F'x	The WIRE component, a diagnostic routine used when the system is booted in slow mode, verifies the continuity and independence of interconnections in the system unit. WIRE checks for open and short circuits on the testable nets between chips.
Ring API (CEC Utility)	'FC00'x through 'FC1F'x	The RAPI component does not display reason codes.
Resource Guard	'FD00'x through 'FD1F'x	The GARD component provides the repeat GARD functionality for all "gardable" items (memory and processors) that are deconfigured and then marked "garded out" either at IPL or runtime. GARD also provides system configuration information to the menu system about system configuration.