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