HPIPFTRAP-MIB

NOTIFICATION-TYPE

The OS has registered an OS_INIT vector, but is has not passed the checksum

NOTIFICATION-TYPE

The OS has registered an OS_MCA vector, but it has not passed the checksum

NOTIFICATION-TYPE

The BMC has failed testing and has been disabled.

NOTIFICATION-TYPE

SFW failed to launch EFI

NOTIFICATION-TYPE

Monarch selection has failed. Data: 0x11 = Calibration Failure 0x22 = Select Code Failure

NOTIFICATION-TYPE

Monarch Collision has occurred

NOTIFICATION-TYPE

SFW attempted to virtualize EFI and failed

NOTIFICATION-TYPE

SFW was unable to virtualize PAL

NOTIFICATION-TYPE

SFW was unable to virtualize SAL

NOTIFICATION-TYPE

SFW was unable to virtualize SALPROC

NOTIFICATION-TYPE

SFW has failed initializing the CPU Struct. Data: Physical location of CPU that produced failure

NOTIFICATION-TYPE

A CPU has failed early config.

NOTIFICATION-TYPE

A CPU has failed early self test. Data: PAL Test State.

NOTIFICATION-TYPE

SFW has detected that a CPU has failed. Data: The Physical Location of the CPU that failed

NOTIFICATION-TYPE

SFW has determined a CPU or Memory has failed late test. This could be related to a CPU error or a Correctable Single Bit Memory error. Data: Physical location of CPU See Cause/Action.

NOTIFICATION-TYPE

The CPU late test has failed because of insufficient memory

NOTIFICATION-TYPE

Could not allocate memory for EFI image

NOTIFICATION-TYPE

EFI image is corrupted

NOTIFICATION-TYPE

EFI fit error

NOTIFICATION-TYPE

EFI NVM has failed testing. The cell or system will now halt.

NOTIFICATION-TYPE

EFI Image Error

NOTIFICATION-TYPE

EFI Image Error.

NOTIFICATION-TYPE

The IVT interrupting nesting depth has been exceeded. This processor will be halted. Data: Number of the offending vector.

NOTIFICATION-TYPE

An external interrupt has been requested and not serviced. Data: Number of the vector

NOTIFICATION-TYPE

An external interrupt has been taken. Data: Number of the vector taken.

NOTIFICATION-TYPE

Access to the FPL has failed.

NOTIFICATION-TYPE

SFW was unable to read the CPU PSR. Data: Physical location of CPU

NOTIFICATION-TYPE

SFW has halted the cell or system

NOTIFICATION-TYPE

SFW has determined that PAL is not compatible with the current processors.

NOTIFICATION-TYPE

SFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor.

NOTIFICATION-TYPE

Interrupt clear failed during cell config

NOTIFICATION-TYPE

SFW has determined that an IPMI event failed.

NOTIFICATION-TYPE

Data: interrupt vector table (IVT) Offset

NOTIFICATION-TYPE

LDB state bad

NOTIFICATION-TYPE

Interrupt context was lost. Data: interrupt number.

NOTIFICATION-TYPE

Registering of the processor min state save area with PAL has failed.

NOTIFICATION-TYPE

SFW has determined the monarch has timed out. SFW is deconfiguring the CPU. Data: Physical Location of CPU

NOTIFICATION-TYPE

A PAL_B FIT error has occurred

NOTIFICATION-TYPE

A SAL_B FIT error has occurred

NOTIFICATION-TYPE

NVM has failed test. The system will halt

NOTIFICATION-TYPE

A interrupt vector has been requested out of the acceptable range. Data: Vector Number.

NOTIFICATION-TYPE

The PAL Copy Info call has failed.

NOTIFICATION-TYPE

Error copying PAL to memory

NOTIFICATION-TYPE

A PAL Proc has failed. This will halt the processor. Data: Physical Location of CPU

NOTIFICATION-TYPE

A console device has failed. Data: Physical Addr of device that failed.

NOTIFICATION-TYPE

A console device has failed. Data: Physical Addr of device that failed.

NOTIFICATION-TYPE

Platform Scratch RAM has failed the test.

NOTIFICATION-TYPE

A CPU has failed to enter rendezvous. Data: Local CPU Number

NOTIFICATION-TYPE

SFW could not extract SAL_B from the ROM

NOTIFICATION-TYPE

Platform Scratch RAM has failed test.

NOTIFICATION-TYPE

IPMI SEL full

NOTIFICATION-TYPE

No wakeup vector registered for processor Data: Physical location of CPU

NOTIFICATION-TYPE

Slave Rendezvous handler has failed. Data: Physical Location of CPU

NOTIFICATION-TYPE

SFW failed to build the SMBIOS tables

NOTIFICATION-TYPE

The trap nesting limit has been exceeded. Data: Vector Number

NOTIFICATION-TYPE

A trap has been requested and not serviced. Data: Vector Number

NOTIFICATION-TYPE

A trap has been taken. Data: Number of the vector taken.

NOTIFICATION-TYPE

At least one interrupt was not cleared. Data: The highest pending interrupt number

NOTIFICATION-TYPE

An unexpected external interrupt has occurred. Data: External Interrupt Number

NOTIFICATION-TYPE

An interrupt has occurred before setting up the Interrupt Vector Table. Data: Interrupt Number

NOTIFICATION-TYPE

An unexpected MCA has occurred before MCAs are unmasked. Data: Local CPU Number.

NOTIFICATION-TYPE

An unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number

NOTIFICATION-TYPE

SFW has detected an unknown error.

NOTIFICATION-TYPE

SFW has detected a PAL Failure

NOTIFICATION-TYPE

Expected Machine Check Vector not registered

NOTIFICATION-TYPE

This is the equivalent of a TOC event in the PA RISC Architecture. On IPF systems, this event is called an INIT. This event can be triggered by the 'tc' command from the MP, or from the button labeled 'TOC' :wor 'Transfer of Control' on the Management card or bezel of the system. There are also other causes of an INIT generated by software. Data: Local CPU Number

NOTIFICATION-TYPE

An I/O host bridge is missing. Firmware will continue boot and display the following EFI warning, 'Unexpected hardware I/O configuration.' Data Field: Physical location of the missing I/O host bridge.

NOTIFICATION-TYPE

Firmware detected an unexpected number of I/O slots connected to an I/O host bridge. Firmware display the following EFI warning message, 'Unexpected hardware I/O configuration.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

Firmware found an I/O controller rope of unexpected width. Firmware will configure the I/O host bridge connected to the rope and display the following EFI warning message, 'Unexpected hardware I/O configuration.' Data Field: Physical location of the I/O host bridge connected to the rope.

NOTIFICATION-TYPE

Firmware found an unexpected I/O host bridge. Firmware will configure the I/O host bridge and display the following EFI warning message, 'Unexpected hardware I/O configuration.' Data Field: Physical location of the unexpected I/O host bridge.

NOTIFICATION-TYPE

An I/O host bridge's bus frequency DLL circuit failed. Firmware will deconfigure the failed I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

An I/O host bridge's hot-plug controller has failed. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

Firmware attempts to configure an I/O controller rope to an unsupported width. Firmware will deconfigure any I/O host bridge connected to the rope. Data Field: Physical location of the failed rope.

NOTIFICATION-TYPE

During I/O host bridge configuration, firmware found a persistent error condition. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

An I/O host bridge is inaccessible because an I/O controller rope reset failed to complete. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

There is insufficient power. Firmware will not power on a hot-plug I/O slot. In addition, firmware will display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Date Field: Physical location of the I/O slot.

NOTIFICATION-TYPE

Firmware encountered an unexpected error while attempting to configure an I/O host bridge's I/O devices. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

The total resource requirement from the I/O devices connected to an I/O host bridge exceeds the resource limit of the I/O host bridge. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. In addition, firmware will display the following EFI warning message, 'Insufficient resources to assign to one or more I/O devices.' Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

Firmware encountered an unexpected error while attempting to clear resource allocations on an I/O host bridge's I/O devices. Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

An I/O host bridge failed to determine the appropriate PCI[X] mode and frequency (PCI, PCI-X 66 MHz, PCI-X 133 MHz, etc.) for its bus. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the failed I/O host bridge.

NOTIFICATION-TYPE

Firmware is unable to access the power monitor. Firmware will assume that there is sufficient power and proceed to power on an I/O slot. Data Field: Physical location of the I/O slot.

NOTIFICATION-TYPE

An I/O controller rope reset did not complete within the expected time limit. Firmware will deconfigure the I/O host bridge attached to the rope. Data Field: Physical location of the deconfigured I/O host bridge.

NOTIFICATION-TYPE

During I/O chipset configuration, firmware found a persistent error condition. Firmware will attempt to continue the boot. Data Field: Physical location of the I/O chipset.

NOTIFICATION-TYPE

During boot, firmware has found a hot-plug I/O slot with an incorrect default power state. The slot power should be off by default. Data Field: Physical location of the I/O slot.

NOTIFICATION-TYPE

Firmware encountered an error while attempting to power on an I/O slot. Firmware will deconfigure the I/O slot and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O slot.

NOTIFICATION-TYPE

An I/O slot's standby (Vaux) power has failed. Firmware will deconfigure the I/O slot and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the failed I/O slot.

NOTIFICATION-TYPE

An I/O host bridge or hot-plug controller reported an illegal PCI[X] bus mode for its bus or slot, respectively. Firmware will deconfigure the I/O host bridge or I/O slot and display the following EFI warning, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the failed I/O host bridge or the failed I/O slot.

NOTIFICATION-TYPE

Firmware attempted to configure an I/O controller rope to an unsupported frequency. Firmware will deconfigure any I/O host bridge connected to the rope and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the failed rope.

NOTIFICATION-TYPE

Firmware has found an unsupported I/O host bridge type. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the I/O host bridge.

NOTIFICATION-TYPE

A Machine Check has been initiated

NOTIFICATION-TYPE

There has been a problem building the Memory Data Table (MDT).

NOTIFICATION-TYPE

There has been a problem building the Memory Data Table (MDT).

NOTIFICATION-TYPE

Memory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt.

NOTIFICATION-TYPE

There has been a problem building the Memory Data Table (MDT).

NOTIFICATION-TYPE

There has been a media failure.

NOTIFICATION-TYPE

Indicates that the chipset register test has failed. The data field contains the physical address of the failing register.

NOTIFICATION-TYPE

After FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written.

NOTIFICATION-TYPE

A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.

NOTIFICATION-TYPE

The DIMM specified by the physical location has an SPD EEPROM that has a bad checksum. The Data field is the physical location of the DIMM.

NOTIFICATION-TYPE

Detected a error in DIMM SPD

NOTIFICATION-TYPE

A DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform.

NOTIFICATION-TYPE

The DIMM type of this DIMM is not the same as the other DIMMs in the same group. The group of DIMMs is deallocated. If this is the last active group of DIMMs in the system, the system is halted.

NOTIFICATION-TYPE

The DIMM type table is full

NOTIFICATION-TYPE

An entry for the DIMM was not found in the DMT table. The data field contains the DMT entry that the caller wanted to find (in Dimm number format, which is 2 bytes, upper byte is the extender number, lower byte is the chip select of the rank caller is looking for.)

NOTIFICATION-TYPE

The FW selftest of CEC multi-bit error (MBE) detection has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.

NOTIFICATION-TYPE

The FW selftest of CEC multi-bit error (MBE) signaling has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.

NOTIFICATION-TYPE

The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.

NOTIFICATION-TYPE

The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.

NOTIFICATION-TYPE

Memory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest.

NOTIFICATION-TYPE

Memory FW could not figure out which rank maps to the physical address specified in the data field.

NOTIFICATION-TYPE

Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.

NOTIFICATION-TYPE

Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.

NOTIFICATION-TYPE

The Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear.

NOTIFICATION-TYPE

A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.

NOTIFICATION-TYPE

An error occurred that memory FW does not know how to handle.

NOTIFICATION-TYPE

The memory interleaving code failed.

NOTIFICATION-TYPE

FW was unable to create a memory configuration with no errors in low memory to hand off to EFI.

NOTIFICATION-TYPE

A series of MEM_MBE_IN_RANK chassis code will be sent when an error is detected by firmware. The data fields will contain information on the error based on the data type as follows: Physical Location - location of dimm(s) in error; Physical Address - address affect by error; Syndrome - Firmware generated ECC syndrome that can be used to further isolate the error.

NOTIFICATION-TYPE

The chipset's memory controller failed the register test. The data field contains the address of the register that failed selftest.

NOTIFICATION-TYPE

Memory Discovery could not detect any DIMMs installed.

NOTIFICATION-TYPE

FW could not continue because there are no valid memory ranks loaded.

NOTIFICATION-TYPE

The PDT has been disabled, and FW found memory errors during selftest. This is a stopboot condition. Also, the PDT will never be disabled in customer systems, so this event should never be seen in the field.

NOTIFICATION-TYPE

An event indicating that the user has the PDT disabled on this boot. The PDT will never be disabled in customer systems, so this event should never be seen in the field.

NOTIFICATION-TYPE

Error writing entry into the PDT.

NOTIFICATION-TYPE

An attempt was made to add an entry to a full PDT. The entry is not added, and this event is sent.

NOTIFICATION-TYPE

Memory FW was unable to save or restore the original error configuration (including CEC error log and signal enable and CPU ECC detection). This event should never be seen in the field unless there is a FW problem

NOTIFICATION-TYPE

The rank structure that corresponds to the rankID in the data field could not be found in the Rank table. The Data field is the rankID of the structure it is looking for. This error event should never be seen.

NOTIFICATION-TYPE

More than one error type was detected when only one error type was expected.

NOTIFICATION-TYPE

The forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field.

NOTIFICATION-TYPE

The memory error status has bits set in it that indicate another non-memory error occurred. The data field contains the CEC's error status.

NOTIFICATION-TYPE

The memory test summary bits are invalid. The data field is the test summary bits.

NOTIFICATION-TYPE

Memory rank shadowing has been selected but is not supported by the revision of the memory controller.

NOTIFICATION-TYPE

The control bit to skip the DIMM distribution check is set and the DIMM distribution check was skipped. This bit should only be done in the factory and not in the field.

NOTIFICATION-TYPE

The control bit to skip the DIMM loading order check is set and the DIMM loading order check was skipped. This bit should only be done in the factory and not in the field.

NOTIFICATION-TYPE

The control bit to loop on destructive memory test is set and the destructive memory tests are run continuously. This bit should only be done in the factory and not in the field.

NOTIFICATION-TYPE

The control bit to skip the DIMM set check is set and the DIMM set check was skipped. This bit should only be done in the factory and not in the field.

NOTIFICATION-TYPE

The control bit to skip the DIMM SPD check is set and the checking of the DIMM SPD was skipped. This bit should only be done in the factory and not in the field.

NOTIFICATION-TYPE

The control bit to load an alternate memory configuration is set and an alternate memory configuration has been loaded. This bit should only be set in the factory and not in the field.

NOTIFICATION-TYPE

The OS_INIT vector has not been registered

NOTIFICATION-TYPE

The OS_MCA vector has not been registered

NOTIFICATION-TYPE

An Uncorrected Machine Check has occurred

NOTIFICATION-TYPE

A PDH register has failed.

NOTIFICATION-TYPE

The handler for SAL_CHECK has failed for an unknown reason.

NOTIFICATION-TYPE

The handler for SAL_INIT has failed for an unknown reason.

NOTIFICATION-TYPE

Indicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call.

NOTIFICATION-TYPE

Unexpected return to SAL_CHECK.

NOTIFICATION-TYPE

The SFW TOC vector (SAL_INIT) has been unexpectedly returned to.

NOTIFICATION-TYPE

Firmware is adding a device tree node for a CPU that is degraded in functionality. The cpu should not be trusted and will not be active in the system.

NOTIFICATION-TYPE

Firmware was unable to locate a required element in the device tree and cannot create a partition. The resource that cannot be located is listed as an ansi string in the data field.

NOTIFICATION-TYPE

The currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with.

NOTIFICATION-TYPE

The current cell could not read a remote cells CSR. The remote cell number is displayed in the data field. These cells will not be able to rendezvous.

NOTIFICATION-TYPE

The currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with.

NOTIFICATION-TYPE

The currently executing cell detected CPUs that are incompatible with it to be installed on a cell that the current cell is trying to rendezvous with.

NOTIFICATION-TYPE

The current cell was too slow creating the local rendezvous set and the other cells have left it behind. It will not be able to participate in the remainder of the rendezvous. The data field is unused, but the cell emitting this event is the one too late to rendezvous.

NOTIFICATION-TYPE

The reporting cell was not included in the final global set that was agreed upon. This means that another cell either could not reach the reporting cell or the reporting cell was too late arriving to a required state.

NOTIFICATION-TYPE

No cells in the PD can be a core cell. This is fatal.

NOTIFICATION-TYPE

System Firmware was unable to notify utilities of the selected core cell number.

NOTIFICATION-TYPE

The fabric code is unable to find a service provider for a required banyan service.

NOTIFICATION-TYPE

The fabric port specified in the data field had an error.

NOTIFICATION-TYPE

An error occurred reading a CSR. The CSR address is displayed in the data field.

NOTIFICATION-TYPE

Error writing to Fabric. CSR data in data field.

NOTIFICATION-TYPE

Incompatible crossbar slices are installed The data field is the two revisions reported by slice1 and slice0 of the CSR data. Bits [31:0] slice0 revision Bits [63:32] slice1 revision

NOTIFICATION-TYPE

Crossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data.

NOTIFICATION-TYPE

A CPU has taken over as the monarch CPU.

NOTIFICATION-TYPE

SRAM cannot be accessed on the cell board. Execution cannot continue.

NOTIFICATION-TYPE

The PDH Arbiter component/chip cannot be located or used.

NOTIFICATION-TYPE

A required piece of PDH bus hardware cannot be contacted.

NOTIFICATION-TYPE

The physical location of the PCI controller with mixed speeds is displayed in the data field.

NOTIFICATION-TYPE

During walking of the IO busses, the maximum depth was exceeded. This is a hardware configuration problem. The data field contains the physical location.

NOTIFICATION-TYPE

A Timeout occurred during RI initialization. The CSR is in the data field. The alert level will vary.

NOTIFICATION-TYPE

SuperIO has been detected in the PCI slot displayed in the data field.

NOTIFICATION-TYPE

IO Link Software error was corrected.

NOTIFICATION-TYPE

Parity error in Reg FIFO Internal parity error.

NOTIFICATION-TYPE

TLB Fetch timeout.

NOTIFICATION-TYPE

Link presence goes away, FE.

NOTIFICATION-TYPE

LBA to SBA parity error on command, rope will go fatal.

NOTIFICATION-TYPE

Access to invalid TLB entry Requesting rope fatal.

NOTIFICATION-TYPE

Memory Fetch Timeout.

NOTIFICATION-TYPE

An error was encountered when initing the rope number specified in the data field.

NOTIFICATION-TYPE

LBA correctable timeout error was encountered.

NOTIFICATION-TYPE

LBA uncorrectable Function Error was encountered.

NOTIFICATION-TYPE

LBA uncorrectable Timeout Error was encountered.

NOTIFICATION-TYPE

Misc uncorrectable error discovered on LBA.

NOTIFICATION-TYPE

LBA encountered an uncorrectable parity error.

NOTIFICATION-TYPE

LBA misc. Fatal Error encountered.

NOTIFICATION-TYPE

LBA Fatal function error encountered.

NOTIFICATION-TYPE

LBA Fatal Parity error encountered.

NOTIFICATION-TYPE

LBA Fatal timeout error encountered.

NOTIFICATION-TYPE

Misc Uncorrectable Error encountered on the card specified in the data field.

NOTIFICATION-TYPE

Misc fatal error was discovered on the PCI card specified in the data field.

NOTIFICATION-TYPE

The calculated and compared Checksums of the SPD EEPROM don't match.

NOTIFICATION-TYPE

The Options component encountered a header checksum error. The actual data is in the data field of the chassis code.

NOTIFICATION-TYPE

The Options service data had a bad checksum. Actual data is in the data field.

NOTIFICATION-TYPE

Internal inconsistency in the interleave tables.

NOTIFICATION-TYPE

The CellInfoList is not null and was expected to be. There has been an error in interleaving.

NOTIFICATION-TYPE

Error in constructing the Memory Descriptor.

NOTIFICATION-TYPE

Unable to update the local memory layout.

NOTIFICATION-TYPE

A required address was not found within a mapped address in the PDT.

NOTIFICATION-TYPE

Failure to install a partition level PDT. Errors prevented it.

NOTIFICATION-TYPE

A critical resource that is required early in the initialization process either could not be found, or was unusable. The specific resource is specified in the data field as follows: Platform Parameters Component not found in FIT: 0xdead0001; SRAM_BASE not found in platform parms: 0xdead0002; SRAM_SIZE not found in Platform Parms: 0xdead0003; firmware framework not found in the fit: 0xdead0004; Framework Segment not usable: 0xdead0005; bad NVRAM: 0xdead0006; PDH Arbiter unusable: 0xdead0007; SRAM unusable: 0xdead0008; CPU unusable: 0xdead0009; Options Component Unusable: 0xdead000a; Real Time Clock unusable: DEAD_RTC; Unknown: 0xdead0086

NOTIFICATION-TYPE

An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the IP address of the function that encountered the error.

NOTIFICATION-TYPE

NVRAM failed with a data compare error. 3 chassis codes will be sent. The first one will have the expected data and the second the actual data and the third one will be the address.

NOTIFICATION-TYPE

An NVRAM CRC Error was detected. There will always be 2 chassis codes sent. The first one will give the expected data and the second the actual data.

NOTIFICATION-TYPE

Get Error Response Mode has been called. The first 8 bytes of the response mode string are displayed in the data field and must be converted to ASCII from the hex values.

NOTIFICATION-TYPE

The required semaphore could not be obtained due to errors. The data field contains the IP of the routine trying to obtain the semaphore. A request was placed for more NVRAM to be allocated but NVRAM was full.

NOTIFICATION-TYPE

The NVRAM block requested has an unexpected revision. This chassis code will be emitted in pairs. The first one will contain the expected revision number, the second will contain the actual revision number.

NOTIFICATION-TYPE

The requested NVRAM block was not found. The ID that was not found is displayed in the data field.

NOTIFICATION-TYPE

The block id specified in the data field is locked.

NOTIFICATION-TYPE

Firmware tried to unlock a NVRAM block that was already unlocked. Data field contains the block ID.

NOTIFICATION-TYPE

The header in the NVRAM space was not found.

NOTIFICATION-TYPE

The Freelist used vor Non-Volatile Memory allocation is corrpt.

NOTIFICATION-TYPE

System firmware has detected a condition that requires the cell to be reset for reconfiguration. The function has been called and is now executing. Data field contains the cell number being reset.

NOTIFICATION-TYPE

During PD rendezvous, system firmware encountered a problem sending commands to the utilities system. This will prevent a fully functional PD from being created.

NOTIFICATION-TYPE

System Firmware has determined that cell or system progress must be halted. The data field contains the Instruction Pointer of the function that called for the halt. The second instance of this code being emitted indicates the major state in system change. This code must be emitted in pairs.

NOTIFICATION-TYPE

The DUI (Developers User Interface) was entered, but there is no console available for the interface.

NOTIFICATION-TYPE

During Error processing and reporting, an error was detected that prevented further processing of errors. The data field contains an ASCII message indicating the problem.

NOTIFICATION-TYPE

System firmware is unable to complete the request to reset the cell for reconfiguration. Typically, are required step has not been performed yet or a needed resource is unavailable.

NOTIFICATION-TYPE

The cell was not able to reach all the other cells in its configured set through the fabric. The data field contains the bitmask of actual cells that were reached.

NOTIFICATION-TYPE

Firmware detected a PCI-to-PCI bridge that exceeds the maximum supported bridge depth. Firmware will not configure I/O devices below the maximum bridge depth. Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: PCI function address of the bridge that exceeded the maximum depth limit. Bits 24..31: segment number Bits 16..23: bus number Bits 11..15: device number Bits 8..10: function number Bits 0..7: reserved (0)

NOTIFICATION-TYPE

Debugging event, not for release. This event is no longer used on Everest/xPeak systems but its event ID is still contained in the code base.

NOTIFICATION-TYPE

This event is unused

NOTIFICATION-TYPE

The reporting cell read an unknown state from a remote cell. This chassis code will be emitted in pairs. The first one indicating the cell number in the data field and the second code indicating the state read in the data field.

NOTIFICATION-TYPE

The reporting Cell thinks that it should be the core cell but has discovered another cell in the same PD that thinks it should be the core cell. This is a serious problem.

NOTIFICATION-TYPE

The utilities system firmware component received an error response from the SINC in response to a command being sent. The exact error is displayed in the data field. Typically, this can occur when the SINC cannot talk to the MP.

NOTIFICATION-TYPE

System Firmware issued the Retrieve Cell Slot State command to the Sync and got an error back. See related chassis code or the specifics of the error.

NOTIFICATION-TYPE

This denotes the fact that all the cpus in the cell did not rendezvous.

NOTIFICATION-TYPE

This chassis code indicates that the cell does not have any access to a PD.

NOTIFICATION-TYPE

This indicates the cell would not be able to join the other cells in the PD level rendezvous. The data portion represents the cell id of the cell that incurred the loss of lockstep.

NOTIFICATION-TYPE

This indicates that some of the cells did not show up during the PD level rendezvous.

NOTIFICATION-TYPE

This indicates that catastrophic errors have been found in the PIN block of the cell controller. The cell needs to be reset/ halt.

NOTIFICATION-TYPE

This means that the cell monach cpu has not completed the assigned task within the timeout and hence it will be deconfigured.

NOTIFICATION-TYPE

This indicates that the cell is too late for the PD level rendezvous. And hence it will not join the other PD cells.

NOTIFICATION-TYPE

This indicates the state where the PD monarch was not able to complete the task within a certain time. It failed.

NOTIFICATION-TYPE

System firmware on the Core cell was unable to update a slave cell with the location of the root of the partition tree. The CPU that was unable to be contacted is printed in the data field.

NOTIFICATION-TYPE

Read test on a CSR failed and the CSR contents were not updated. This chassis code will be emitted in 3's, with the CSR Address, expected data, and actual data given.

NOTIFICATION-TYPE

This chassis code reports the failure in collecting the ICM parameters needed for the cell interleaving.

NOTIFICATION-TYPE

This chassis code indicates that the cell interleaving routine could not get the information on the cell memory.

NOTIFICATION-TYPE

This chassis code is used to represent the failure in updating the GNI information of the cell with the CLM ( cell local memory) information obtained from the Complex Profile.

NOTIFICATION-TYPE

This represents the failure in adjusting the memory information with the minimum ZI requirements.

NOTIFICATION-TYPE

Complex Profile A (Stable Profile) stored checksum does not match the calculated checksum. The expected data and actual data are displayed in the 2 reporting event Ids.

NOTIFICATION-TYPE

The Dynamic Complex Profile (Group B) stored checksum did not equal the calculated checksum. The Expected Data and Actual date are displayed in successive chassis codes.

NOTIFICATION-TYPE

The stored value of the complex profile Group C does not match the calculated value. Expected data and actual data are stored in successive chassis codes.

NOTIFICATION-TYPE

The Complex Profile Group A sequence ID is invalid. Booting cannot continue. The actual data is in the chassis code data field.

NOTIFICATION-TYPE

The Dynamic Complex Profile (Group B) sequence ID is invalid. The invalid Sequence ID is displayed in the data field.

NOTIFICATION-TYPE

The Group C Partition Complex Profile Sequence ID is invalid. The value read is displayed in the data field.

NOTIFICATION-TYPE

An internal EFI firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc, corrupt firmware tree or something similar. The data field contains the IP address of the function that encountered the error.

NOTIFICATION-TYPE

The Complex Profile Group A PD assignment for this cell does not match the PD or Partition number in Group C of the complex profile. This is a fatal condition for the cell. The PD number from group A will be emitted first, followed by a subsequent code for the PD assigned in group C.

NOTIFICATION-TYPE

The Partition (PD) assigned to this cell in the complex profile group A and C is larger than the maximum allowed number of PDs as specified by Group A.

NOTIFICATION-TYPE

Tried to obtain the port semaphore but GetPortSemaphore returned an ERROR. Could be a failed write to the port semaphore crossbar CSR or another cell owned the semaphore. Data field bits 32:63 contain the crossbar ID and bits 0:31 contain the port number for which the semaphore was being obtained.

NOTIFICATION-TYPE

Currently owned the port semaphore but could not release the semaphore. Data field bits 32:63 contain the crossbar ID and bits 0:32 contain the port number.

NOTIFICATION-TYPE

There was an error reading from the BMC token when attempting to write to SAL NVM. This is a stop boot condition. Data: Lower 32 bits, BMC Token Number. Upper 32 bits, bmc return status.

NOTIFICATION-TYPE

The read from SAL NVM has failed. This is a stop boot condition. Data: The token number on which the read failed

NOTIFICATION-TYPE

There was an error when trying to write to a BMC Token. This is a boot warning condition. Data: lower 32 bits are BMC token number, upper 32 bits is the status return from the BMC.

NOTIFICATION-TYPE

There has been an error writing the BMC_FIRST_BOOT token. This is a stop boot condition.

NOTIFICATION-TYPE

The read of a FRU has failed. Data: Device ID of device that failed the FRU read.

NOTIFICATION-TYPE

The read of a FRU has failed the checksum test. Data: Device ID of device that failed the FRU read.

NOTIFICATION-TYPE

The read of a FRU has failed due to a version problem. Data: Device ID of device that failed the FRU read.

NOTIFICATION-TYPE

A ROM Rev and FIT Rev do not match. Data: Code for what didn't match: 0x1 = PAL_A, 0x2 = PAL_B, 0x4 = SAL_A, 0x8 = ACPI, 0xA = EFI

NOTIFICATION-TYPE

A ROM Rev and Rev Block do not match. Data: Code for what didn't match: 0x3 = PAL, 0x5 = SAL_A, 0x7 = SAL_B, 0x9 = ACPI, 0xB = EFI, 0xC = BMC

NOTIFICATION-TYPE

The FIT is bad.

NOTIFICATION-TYPE

The FIT is bad.

NOTIFICATION-TYPE

PAL_A_ROM has generated a warning.

NOTIFICATION-TYPE

PAL_B_ROM has generated a warning.

NOTIFICATION-TYPE

Firmware tried to default the Dynamic (Group B) complex profile and encountered an error.

NOTIFICATION-TYPE

An I/O device (or host bridge) detected a bus parity error. An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Data Field: Physical location of the I/O device (or host bridge).

NOTIFICATION-TYPE

An I/O device (or host bridge) detected an internal error. An I/O device (or host bridge) detected a bus error. Data Field: Physical location of the I/O device (or host bridge).

NOTIFICATION-TYPE

Firmware has deconfigured an I/O host bridge due to an error (see earlier error event). Firmware will display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the deconfigured I/O host bridge.

NOTIFICATION-TYPE

Firmware tried to default the Partition (Group C) complex profile and encountered an error.

NOTIFICATION-TYPE

The Reporting Cell is not configured to be in a PD, according to Complex Profile Group A.

NOTIFICATION-TYPE

DIMMs are not loaded on the extender in a thermally optimal way. Boot is still possible, but the DIMM arrangement should be changed to the loading order recommended in the users manual. The data field indicates the number of the extender with incorrectly loaded DIMMs.

NOTIFICATION-TYPE

Not enough cells made the Rendezvous for boot to continue. The rules are listed in the cause action section.

NOTIFICATION-TYPE

SFW's INIT handler failed to rendezvous the processors.

NOTIFICATION-TYPE

SFW's Machine Check Handler was unable to log or clear I/O error registers.

NOTIFICATION-TYPE

Cannot escalate an MCA to BERR

NOTIFICATION-TYPE

Cannot escalate an MCA to BINIT.

NOTIFICATION-TYPE

SFW failed to get the feature set from PAL.

NOTIFICATION-TYPE

PAL Failed to rendezvous the processors during a MCA.

NOTIFICATION-TYPE

SFW failed to get the feature set from PAL.

NOTIFICATION-TYPE

SFW's MCA Handler has failed to rendezvous all the slaves Data: Return from the rendezvous call.

NOTIFICATION-TYPE

A bad rendezvous vector has been registered.

NOTIFICATION-TYPE

No Machine Check Monarch exists, exiting MC Rendezvous.

NOTIFICATION-TYPE

The OS has not registered a wake-up mechanism for rendezvous.

NOTIFICATION-TYPE

PAL call failed to set the BINIT escalation bit

NOTIFICATION-TYPE

The PAL call PAL_GET_FEATURES has failed.

NOTIFICATION-TYPE

The PAL call PAL_SET_FEATURES has failed.

NOTIFICATION-TYPE

An internal SAL_ABI firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc, corrupt firmware tree or something similar. The data field contains the IP address of the function that encountered the error.

NOTIFICATION-TYPE

The Memory extenders have not been loaded in the correct order.

NOTIFICATION-TYPE

The length field within the ESI (Extensible SAL Interface) table does not agree with the product of the entry_count field and the size of each entry. Data Field: computed value of the length based on entry_count and size of the entries.

NOTIFICATION-TYPE

The computed checksum for the ESI (Extensible SAL Interface) table is not zero as expected. EFI is halting. Data Field: the computed checksum.

NOTIFICATION-TYPE

EFI found an unsupported entry type within the ESI (Extensible SAL Interface) Table. Data Field: unknown type.

NOTIFICATION-TYPE

EFI was attempting to output a GUID in the EFI_GUID_HALF1 and EFI_GUID_HALF2 events which was larger than 128 bits. The data field contains the actual length of the GUID in bytes.

NOTIFICATION-TYPE

EFI is halting. Look for the cause of the halt in preceding events. Data Field: the 'halt' (0x0F) major change in system state code.

NOTIFICATION-TYPE

This code will be sent when FW detects a rank installed in the system that doesn't support chipspare. The data field is used to indicate the rank that the x8 DIMMs are installed. It is in the format 0x00000000XDXCXBXA or 0x00000000YBYAXBXA where X and Y are the number of the rank.

NOTIFICATION-TYPE

EFI has detected an internal error. The actual error is unspecified by this event. Examine previous events and console output for possible explanations.

NOTIFICATION-TYPE

EFI has executed the 'break' shell command. EFI is halting. The 'break' command is currently implemented as an infinite loop to halt EFI.

NOTIFICATION-TYPE

The EFI USB interrupt service has detected the host controller is hung. EFI is halting.

NOTIFICATION-TYPE

The EFI/SAL handoff structure's version does not match EFI expectations. EFI is halting. Look for EFI_SAL_HANDOFF_VER_EXPECTED to provide EFI's expected value. Data Field: Actual value of the version in the structure.

NOTIFICATION-TYPE

EFI is unable to obtain access to all the RTC (Real Time Clock) SAL services. This means that EFI is unable to fully interact with the RTC. EFI is halting. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

EFI is unable to obtain access to all the SAL timer services. This means that EFI is unable to fully interact with the timer. EFI is halting. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

EFI is unable to start the periodic timer. This timer interrupts EFI periodically to process time sensitive events. EFI is halting. Data Field: Return status for internal EFI function.

NOTIFICATION-TYPE

EFI did not find an I/O port space region in the MDT. EFI is halting.

NOTIFICATION-TYPE

EFI reached an unimplemented section of code. EFI is halting. Data Field: Unique identifier indicating the location reached within the code.

NOTIFICATION-TYPE

EFI was unable to read the current speedy boot settings. The speedy boot settings are stored within the BMC. EFI will use a default value of 0 and continue booting. The speedy boot functionality is also accessed via the boot test EFI shell command and via the OS. These other accesses will likely fail. Data Field: Return status from internal EFI function..

NOTIFICATION-TYPE

A SAL Callback was attempted. This is not permitted. EFI is halting. Data Field: index of the function that was being called.

NOTIFICATION-TYPE

While attempting to calibrate the EFI stall timer, system firmware is unable to determine the frequency of the CPU interval timer. System firmware will assume 800 MHz for the purpose of the stall timer calibration and continue boot. Data Field: error status code (should be 0xFFFFFFFD).

NOTIFICATION-TYPE

The EFI system events have already been initialized. This is unexpected. EFI is continuing. Data Field: the current value of the system event entry point.

NOTIFICATION-TYPE

EFI was unable to create an internal virtualization event while initializing EFI's System Events (IPMI events). This internal event is not an IPMI event; rather it serves as a trigger for EFI to virtualize the System Event facility when going virtual. EFI will likely halt. Data Field: return status from internal EFI function.

NOTIFICATION-TYPE

An error was detected while initializing the FPGA node and services associated with the PDH.

NOTIFICATION-TYPE

Firmware encountered an error when creating the ioconfig node as a child of the pdh node.

NOTIFICATION-TYPE

System firmware was unable to correctly set up the pdh arbiter node as a child of the pdh node, or was unable to locate and attach the pdh arbiter service to the node. The status is returned in the data field.

NOTIFICATION-TYPE

The PDH service was unable to either get or set the property specified in the data field as an ASCII message.

NOTIFICATION-TYPE

PDH encountered an error creating the ACPI Hardware Node in the device tree or installing its properties.

NOTIFICATION-TYPE

The PDH service encountered an error while creating the ipmi node or adding properties to it. The status is in the data field.

NOTIFICATION-TYPE

Installed processors are not of compatible models or families

NOTIFICATION-TYPE

Processors with different cache sizes are installed

NOTIFICATION-TYPE

SFW is selecting a new monarch processor due to compatibility problems.

NOTIFICATION-TYPE

The monarch stepping is not equal to the lowest installed CPU stepping.

NOTIFICATION-TYPE

A CPU's FSB frequency is overclocked. Data: Local CPU Number.

NOTIFICATION-TYPE

There was an error reading the info ROM area of the CPU. Data: CPU Physical location

NOTIFICATION-TYPE

PAL_A has not been executed and control has been transferred back to SAL_B.

NOTIFICATION-TYPE

PAL_B has not been executed and control has been transferred back to SAL_B.

NOTIFICATION-TYPE

Data: Lower 32 bits have Local CPU Number

NOTIFICATION-TYPE

Data: Monarch's Local CPU Number

NOTIFICATION-TYPE

Supplemental tests have been run on the cpus in the node and an error was encountered. If this event id is only emitted once, then the cpu detected that it failed on its own and the offending CPU id is in the data field. If the event is emitted three times, then the monarch CPU on the cell detected the error and the offending CPU id, expected data and actual data are reported in the data field of the three events.

NOTIFICATION-TYPE

While reading a XBC CSR, a multi-bit error was found. Data field includes the CSR data that includes the error. A previous event, FABRIC_READ_ERROR, details the CSR address that failed.

NOTIFICATION-TYPE

The return value from a function was an unknown value. Data field is the unknown status that was returned.

NOTIFICATION-TYPE

EFI queries the BMC on the system board for the status of a system ID. The BMC could not complete the request successfully or on time. Data Field: Internal EFI function status.

NOTIFICATION-TYPE

BMC reported a system ID status as inaccessible, reported invalid status or cannot return the current value of a system ID. Data Field: uuid status or internal EFI function status. System ID status: a 1 byte value 0 extended to 64bits: 0x00 -> primary and secondary values are valid 0x01 -> primary and secondary values are magic 0x02 -> primary and secondary values are inaccessible 0x04 -> primary and secondary values are invalid 0x08 -> primary and secondary values are null (UUID only) 0x10 -> primary and secondary values are different, value (primary or secondary) is valid 0x11 -> primary and secondary values are different, value (primary or secondary) is magic 0x12 -> primary and secondary values are different, value (primary or secondary) is inaccessible 0x14 -> primary and secondary values are different, value (primary or secondary) is invalid 0x18 -> primary and secondary values are different, value (primary or secondary) is null (UUID only)

NOTIFICATION-TYPE

Firmware tried to write a primary or secondary system ID as requested by the user during the boot sequence. The write failed. Data Field: Internal EFI function status.

NOTIFICATION-TYPE

The system ID(s) currently in the system is either invalid or, if the EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR or EFI_SYSID_BMC_WRITE_ERROR events are also present, inaccessible to the system firmware. A stop boot condition will be generated and software license will probably be invalid. Data Field: 64-bit value. If preceded by 0xbad00000000000 the following valid values are possible: 0000 -> valid UUID (should never see this one) 0001 -> magic UUID 0002 -> inaccessible UUID 0004 -> invalid (bad CRC) UUID If zero, then one of the following conditions occurred: Invalid combination of primary and secondary system ID values User declined copying/entering system ID values when prompted by firmware All other values indicate failure during attempt to update system IDs.

NOTIFICATION-TYPE

EFI is unable to find the SAL services for installing interrupt handlers. EFI was trying to install the run-time handlers that are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

NOTIFICATION-TYPE

EFI is unable to find the SAL service to install run-time interrupt handlers. These handlers are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

NOTIFICATION-TYPE

EFI is unable to find the SAL services for installing interrupt handlers. EFI was trying to install the boot-time handlers that are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

NOTIFICATION-TYPE

EFI is unable to find the SAL service to install boot-time interrupt handlers. These handlers are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

NOTIFICATION-TYPE

Too many parameters were passed in a request for the utilities system to perform an operation. No more data is provided.

NOTIFICATION-TYPE

A crossbar port is expected to be present, but its presence detect bit is not set. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

NOTIFICATION-TYPE

A crossbar port is expected to have its HW_LINK_OK bit set, but it is not. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

NOTIFICATION-TYPE

A connected crossbar port was found to have its FE bit set. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

NOTIFICATION-TYPE

There was an error while initializing the Cell Controller-Xbc interface. The data field contains the address of the Cell Controller CSR for which the error occurred.

NOTIFICATION-TYPE

The CC - XBC link failed to initialize.

NOTIFICATION-TYPE

EFI is unable to determine current system mode. The EFI/SAL interface is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing.

NOTIFICATION-TYPE

The BMC has returned an invalid system mode. Data Field: the invalid mode. Expected values are 0 or 1.

NOTIFICATION-TYPE

EFI is unable to specify a new system mode. The EFI/SAL interface point is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing in the current mode.

NOTIFICATION-TYPE

EFI is unable to enter normal system mode. The EFI/SAL interface is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing in the current mode.

NOTIFICATION-TYPE

EFI is unable to initialize part of the SAL/EFI interface. This crucial service provides access to certain BMC functionality such as the security system. EFI will halt. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

A needed tree node was not found. The data field contains the ASCII name of the tree node that was not found.

NOTIFICATION-TYPE

EFI is unable to modify the system state from 'booting' to 'running'. This is done as part of Exit Boot Services. The system will not be able to enter a sleep mode. Data Field: For errors, this data is zero. For warnings, this data indicates the current system state as: 0 Error 1 booting 2 running 3 attention 4 fault 5 booting + attention

NOTIFICATION-TYPE

CPUBusConfigValue setting in options as been compared with what is reported by PAL as settable and CPUBusConfigValue is specifying at least one bit that is not supported by this version of PAL using the Get Processor Bus Dependent Configuration Features. This chassis code is emitted in pairs, the first data field contains the PAL expected values; the second data field contains the requested setting from options.

NOTIFICATION-TYPE

Firmware was unable to correctly issue the Get Processor Bus Dependent Configuration Features command.

NOTIFICATION-TYPE

A pair of DIMMs installed in the system are mismatched, and that pair of DIMMs will not be used. The data field indicates which pair of DIMMs are mismatched in the format 0x000000000000XBXA where X is the number of the rank that is mismatched.

NOTIFICATION-TYPE

EFI is unable to initialize internal library. This collection of internal services is required for much of EFI's functionality. EFI is halting.

NOTIFICATION-TYPE

EFI is unable to initialize the security level. The privilege level of the system may or may not be Admin. It is likely certain EFI facilities will be unavailable. EFI will continue booting but security may be compromised. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

EFI detected an invalid value for its internal privilege level. This value is stored within SAL. EFI will continue but system security may be compromised. Data Field: The invalid privilege level.

NOTIFICATION-TYPE

EFI detected an invalid privilege level when setting a BMC password. Only the levels of Admin (0x30) and User (0x20) are permitted. Data Field: the invalid privilege level.

NOTIFICATION-TYPE

SFW has determined that the Memory Data Table (MDT) table is invalid.

NOTIFICATION-TYPE

Processor has incompatible fixed core ratio. Data: Local CPU Number.

NOTIFICATION-TYPE

Data: A bitmask for which CPUs are slated to be deconfigured

NOTIFICATION-TYPE

An error occurred while reading a crossbar remote route table, or an unexpected/invalid value was read from the table. The data field consists of the crossbar ID (32:43), the port number of which the table was read (44:55), and the return status of the read call (0:32).

NOTIFICATION-TYPE

An error occurred while trying to read the PORT[n]_NEIGHBOR_INFO crossbar CSR. The data field consists of the crossbar ID (32:43) and port number (44:55) for which the CSR was read.

NOTIFICATION-TYPE

A quad of DIMMs installed in the system are mismatched, and that quad of DIMMs will not be used. The data field indicates which quad of DIMMs are mismatched in the format 0x00000000XDXCXBXA where X is the number of the rank that is mismatched.

NOTIFICATION-TYPE

The DIMM at the physical location given by the data field had excessive errors and has been marked as 'FAILED' by firmware.

NOTIFICATION-TYPE

A XBC port was expected to be functional, but its OE bit was not set. The data field consists of the contents of the port_status CSR (0:31), the XBC number (32:43), and the port number (44:55).

NOTIFICATION-TYPE

Unable to read the PORT_STATUS CSR for a XBC port. The data field consists of the contents of the PORT_STATUS CSR (0:31), the XBC number (32:43), and the port number (44:55).

NOTIFICATION-TYPE

A XBC port was unexpectedly found to be landmined. The data field consists of the XBC number (32:43) and the port number (44:55).

NOTIFICATION-TYPE

Reporting cell tried to rendezvous with a cell with processors that are running at a different speed. The data field lists the offending cell

NOTIFICATION-TYPE

The link between the local CC and the local XBC is unexpectedly not initialized. The data field is the XIN_LINK_STATE CC CSR value.

NOTIFICATION-TYPE

A value that was expected to be a XBC number was found to be an invalid XBC number. The data field is the invalid XBC number.

NOTIFICATION-TYPE

A value that was expected to be a valid XBC port number was found to be invalid. The data field is the XBC number (33:44) and the invalid XBC port number (44:55).

NOTIFICATION-TYPE

A bad parameter was passed to the utilities function that manipulates the LED on replaceable parts. The offending parameter is displayed in the data field.

NOTIFICATION-TYPE

A neighbor type read from a XBC PORT_NEIGHBOR_INFO CSR was different than the expected neighbor type. This event is emitted twice, first with expected data and second with actual data. Data field 1: XBC number (43:32), XBC port number (55:44), expected type (31:0) Data field 2: XBC number (43:32), XBC port number (55:44), actual neighbor type (31:0).

NOTIFICATION-TYPE

A XBC port number was unexpectedly found to not be a valid XBC-CC port. The data field consists of the XBC number (32:43) and the port number (44:55).

NOTIFICATION-TYPE

A XBC port was unexpectedly found to be an invalid XBC-XBC port. The data field consists of the XBC number (32:43) and the port number (44:55).

NOTIFICATION-TYPE

The XBC neighbor chip number does not match the expected value for this topology. The data field contains the expected neighbor chip number (32:63) and the actual neighbor chip number (0:31).

NOTIFICATION-TYPE

The XBC neighbor port number does not match the expected value for this topology. The data field contains the expected neighbor port number (32:63) and the actual neighbor port number (0:31).

NOTIFICATION-TYPE

A write to a BMC token has failed. This is a boot warning condition. Data: Upper 32 bits, BMC failure return code. Lower 32 bits, BMC token number that failed.

NOTIFICATION-TYPE

The utilities system reported an error while trying to carry out the command to turn on, flash or turn off the LED. The status returned by the command is displayed in the data field.

NOTIFICATION-TYPE

2 cpus think that they have the same ID within the cell. Typically this would mean that PAL reported the same cpu id for more than 1 cpu on a bus. The cpuid is in the data field.

NOTIFICATION-TYPE

OS crashdump started (D700)

NOTIFICATION-TYPE

OS legacy PA hex fault code (Bxxx). Possible I/O error or system panic

NOTIFICATION-TYPE

A memory dump occurred on the system, or on one partition in a cellular system. The dump occurred due to either a non-recoverable error or by user request. EFxx is the OS dump status (the success/failure of the writing of the dump). EF00 = success (followed by either EF0A = successful dump with sync, or EF09 = successful dump without sync), EFFF = a general error, EFFE = dump path assertion failure, EFFD = no dump was taken by default, choice or failure, EFFC = dump was aborted by user.

NOTIFICATION-TYPE

SFW has failed to set the processor timeout value via a PAL call. Data: PAL call return value.

NOTIFICATION-TYPE

During EFI security initialization, the attempt to determine what privilege level a blank password provides, failed. Most likely this indicates the BMC has failed. EFI assumes that the BMC has failed and will attempt to continue booting. Some EFI functionality may be unavailable. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

As part of normal security initialization, EFI attempted to issue a close session to the BMC (I.e. force the BMC to GUEST mode). This attempt failed. EFI is unable to initialize the security system. EFI will continue but security may be compromised. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

As part of normal security initialization, EFI attempted to issue an open session to the BMC in order to raise the privilege level to the highest permitted by a blank password. This attempt failed. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

As part of normal security initialization, EFI attempted to record the current privilege level. This attempt failed. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

As part of normal security initialization, EFI attempted to record the current privilege level. This attempt failed with a privilege violation error. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

OS dump, error writing image area to disk (E055)

NOTIFICATION-TYPE

Early in bootstrap, the coherency controller (CC) registers are checked for Deadlock Recovery Reset. This chassis code indicates that CC logs will be stored to NVRAM.

NOTIFICATION-TYPE

SFW detected a memory address parity error. The data field contains the physical location of DIMM that saw the parity error.

NOTIFICATION-TYPE

The loading order of the DIMMs is incorrect. The cell is halted.

NOTIFICATION-TYPE

Timeout Waiting for SDRAM parts to become ready - mem_status[0] Refresh Control Register

NOTIFICATION-TYPE

The version of Memory extender installed in the system has not been qualified to work with the version of the baseboard installed in the system.

NOTIFICATION-TYPE

There is a fabric topology mismatch with the XBCs in the complex. Data Field: (Topology of XBC << 32) | Topology of destination XBC 0x00 Topology not yet determined 0x30 Domelight 0x40 U-Turn (Left cabinet) 0x41 U-Turn (Right cabinet) 0x42 Cross-Flex 0x43 U-Turn

NOTIFICATION-TYPE

While routing the XBC to XBC ports, an invalid port was encountered. The data field is the crossbar number (32:43) and the port number (44:55).

NOTIFICATION-TYPE

The XBC could not get neighbor information. Data Field: XBC # << 32 | internal port attempting to access neighbor

NOTIFICATION-TYPE

For the XBC being routed, routing has already been attempted, but an error occurred. Inspect chassis codes from other cells for more details regarding the nature of the problem. The data field consists of the XBC number (32:63)

NOTIFICATION-TYPE

This means that the error event log cannot be logged to the persistent storage. The data field gives the event type that was supposed to be logged.

NOTIFICATION-TYPE

An XBC port was found to have an unexpected error. The data field consists of the crossbar number (32:63) and the current port errors (0:31)

NOTIFICATION-TYPE

During fabric routing a port on a XBC was found in error or had been previously marked as in error. PDC will route around this XBC port. Data Field: XBC number (32:63) and external XBC port number (0:31)

NOTIFICATION-TYPE

Data field: the unexpected forward progress state (0:31) XBC number (32:44) Cell number (56:63)

NOTIFICATION-TYPE

A crossbar was found to be in an unexpected forward progress state during fabric routing. This crossbar stayed in the unexpected state until Fabric Discovery timed out. Data field: unexpected forward progress (0:31) XBC number (32:44) Cell number (56:63)

NOTIFICATION-TYPE

An XBC port was found that is not healthy. This indicates at least one of the following about the port: - Hardware link is not okay - Presence detect is false - Fatal error detected - SBE detected - LPE detected - Port landmined The data field of the chassis code indicates which port is unhealthy, as well as the fabric routing state before the problem was encountered.

NOTIFICATION-TYPE

The CC to XBC link is not viable.

NOTIFICATION-TYPE

There was a problem performing remote routing on the local XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The data field consists of the XBC number that failed routing (32:63)

NOTIFICATION-TYPE

Two or more XBC-XBC links were found to be broken. The data field is the XBC number (32:63) and a bit map of the ports broken (0:31)

NOTIFICATION-TYPE

After unlocking the XBC Global Semaphore for a takeover, this cell did not get the semaphore.

NOTIFICATION-TYPE

When a cell holds an XBC semaphore for an extended period of time, fabric will attempt to takeover the semaphore so that the rest of the cells will have access to it. Fabric will attempt to take the SM4 for a period of time. If it is unable to unlock the SM4 within the timeout period, it will send this chassis code and halt the cell. Data field: XBC number (32:63) and current owner (cell) of the semaphore (0:31)

NOTIFICATION-TYPE

During Fabric Discovery, the cell will wait until it gets the XBC's Global Semaphore. It waits for a very long time. This chassis code indicates that the wait has timed out.

NOTIFICATION-TYPE

The XBC Release Semaphore timeout is designed to fail last. The semaphore could not be released. Any other cell (even outside the PD) may be blocked because the XBC is a global resource. Data field: current semaphore owner (0:31) XBC number (32:43) port number (44:55) cell number (56:63)

NOTIFICATION-TYPE

Management Processor Firmware detected improper data in NVRAM (bad checksums.) Either the NVRAM layout changed, or the Management Processor Battery may not be maintaining the data through A/C power cycles.

NOTIFICATION-TYPE

Management Processor Firmware detected a software error and is logging an event. The data represents data associated with the error seen.

NOTIFICATION-TYPE

An I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset.

NOTIFICATION-TYPE

A stored CRC value did not match the calculated CRC value for the specified address.

NOTIFICATION-TYPE

See Summary.

NOTIFICATION-TYPE

2 cpus in the system are reporting different revisions. This event will be emitted in groups of 3 with the two revisions reported in the first 2 data fields and the cpu number in the 3rd data field.

NOTIFICATION-TYPE

This chassis code will be emitted in pairs. 2 cpus are reporting that they are running at different frequencies. The two frequencies are reported in the data fields.

NOTIFICATION-TYPE

The rating for the cpu and the actual speed will be emitted in 2 sequential event data fields.

NOTIFICATION-TYPE

The complex profile is stored in NVRAM on the MP and each cell. All copies must match. For this error to be generated, not only is the MP's copy of the complex profile invalid, but not all of the cell's copies match.

NOTIFICATION-TYPE

The MP detected 2 or more cabinets with the same cabinet number.

NOTIFICATION-TYPE

The complex identification information in group A of the complex profile is invalid. The MP (Manageability Processor) command 'ID' must be run. The SSKEY hardware is required.

NOTIFICATION-TYPE

The battery on the SBCH is below the safe threshold. The battery can be replaced online.

NOTIFICATION-TYPE

The partition is being reset because its watchdog timer expired and automatic restart is enabled.

NOTIFICATION-TYPE

The processor dependent hardware controller (PDHC) on the cell board had its watchdog timer expire. The PDHC will reset the watchdog as the main program runs. If the watchdog does not get reset within 7 seconds the timer will expire, resetting the PDHC.

NOTIFICATION-TYPE

The Cabinet Power Up request was aborted due to ambient air over temperature.

NOTIFICATION-TYPE

The power requirements for the cabinet exceeds the capabilities of the available Bulk Power Supplies. The PM3 section of the Utilities Subsystems keeps a tally of the power requirements for all installed entities in a cabinet. The power available from the Bulk Power Supplies does not meet the requirements of the installed entities, according to the Cabinet Power Tally.

NOTIFICATION-TYPE

When given a power up request, the cabinet had to abort the start up due to less than the required number of Cabinet Blowers installed.

NOTIFICATION-TYPE

When given a power up request, the cabinet had to abort the start up due to less than the required number of IO fans present.

NOTIFICATION-TYPE

The AC power connected to the PDCA (Power Distribution Control Assembly) was removed. The data field contains the physical location of the PDCA. The PDCA source that was deleted can be identified by the implementation dependent field (data byte 3) of the physical location: data byte[3]: 0 for PDCA 0, 1 for PDCA 1.

NOTIFICATION-TYPE

A cabinet main blower has failed. Depending on the number of blowers still operating, the cabinet may or may not shut down. View the Error Log entries to determine if the cabinet is operating. If many log entries call out entities powering off during the same time frame as this BLOWR_FAIL, the cabinet has probably shutdown. Carefully review the log for the first few events within the same time frame for the root cause of the problem. The GSP command, PS, will show a detailed power status for a cabinet. If the +48V LED on the Front Panel Board is not lit, power is not enabled to the cabinet. This is an indication the cabinet blowers have probably gone from N to N - 1 status requiring an immediate cabinet shutdown.

NOTIFICATION-TYPE

A 48 Volt DC Converter powered by the specified PDCA failed on the designated Bulk Power Supply. The PDCA powering the converter on the BPS that failed can be identified by the implementation dependent field (data byte 3) of the BPS' physical location: data byte[3]: 0 for PDCA 0, 1 for PDCA 1.

NOTIFICATION-TYPE

The designated Bulk Power Supply is reporting its fan has failed.

NOTIFICATION-TYPE

The 48 Volt DC Converter powered by the specified PDCA in the designated Bulk Power Supply, is in over temp condition. The PDCA powering the converter on the BPS that failed can be identified by the activity status (last byte of chassis code): e = PDCA 1 f = PDCA 0

NOTIFICATION-TYPE

The number of functioning Bulk Power Supplies has decreased to where the Cabinet Power supplied (number of available Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed is greater than 0, but less than the output of one Bulk Power Supply.

NOTIFICATION-TYPE

The PM has detected the value of +48V power, as measured on the UGUY board, has exceeded an upper threshold.

NOTIFICATION-TYPE

The PM has detected the value of +48V power, as measured on the UGUY board, has fallen below a lower threshold.

NOTIFICATION-TYPE

A cabinet fan has failed. Depending on the number of cabinet fans still operating, the cabinet may or may not shut down. View the Error Log entries to determine if the cabinet is operating.

NOTIFICATION-TYPE

Housekeeping power has exceeded expected levels.

NOTIFICATION-TYPE

Housekeeping power has fallen below expected levels.

NOTIFICATION-TYPE

Through failures or reconfiguration, the BPS for the cabinet named are illegally configured. There must be a BPS connected to each phase of the power. Phase 1 feeds BPS slots 0 & 1, phase 2 feeds slots 2 & 3, and phase 3 feeds 4 & 5. There must be a BPS connected to each phase. If 4 BPS are installed in a cabinet in slots 0 - 3 and 4 & 5 were empty, this would be an illegal configuration. They should be installed in 0,1,2,and 4 or 0,1,3,and 5 or some combination thereof. The PDCA physical location determines which phase is configured incorrectly. Data Byte 3 (implementation dependent field) indicates the PDCA number used when the configuration error occurred:

NOTIFICATION-TYPE

A Bulk Power Supply is reporting an unknown BPS ID. The Bulk Power Supply will not be powered up and added to the Power Available tally. If cabinet is not powered up, it will refuse to power up until this fault is corrected.

NOTIFICATION-TYPE

The cabinet's Ambient Air Sensor detected a change in air temperature entering the over-temp-high range. The Cabinet will be shutting itself down to prevent component damage.

NOTIFICATION-TYPE

The cabinet's Ambient Air Sensor detected a change in air temperature crossing to the low range. The air temperature may be rising or falling. This is just a reporting of entering the over-temp-low range.

NOTIFICATION-TYPE

The cabinet's Ambient Air Sensor detected a change in air temperature crossing to the mid range. The air temperature may be rising or falling. This is just a reporting of entering the over-temp-mid range..

NOTIFICATION-TYPE

An IO Chassis cooling fan has failed. Depending on the number of fans still operating, the cabinet may or may not shut down. View Error Log entries to determine if the cabinet is operating. If many log entries call out entities powering off during the same time frame as this IOFAN_FAIL, the cabinet has probably shutdown. Carefully review the log for the first few events within the same time frame for the root cause of the problem. The Guardian Service Processor command, PS, will show a detailed power status for a cabinet. The +48V LED on the Front Panel Board not lit, power is not enabled to the cabinet, indicating the cabinet IO Chassis fans have probably gone from N to N - 1 status requiring an immediate cabinet shutdown.

NOTIFICATION-TYPE

This code is issued when the Cabinet Power supplied (number of Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed drops below 0. Utilities firmware will not allow a cabinet in this state to power up (see ABORT_PWRUP_BPS). Utilities firmware will not shut down a cabinet in this state. However, there is a possibility of a cabinet brownout, making the cabinet unreliable.

NOTIFICATION-TYPE

After a BLOWR_FAIL, there were N-1 blowers functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.

NOTIFICATION-TYPE

After a IOFAN_FAIL, there were N-1 fans functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.

NOTIFICATION-TYPE

One of two fans in the Utility chassis of the IO Expansion Cabinet has failed.

NOTIFICATION-TYPE

The Watchdog Timer checks for inactivity, or hung state, of the Cabinet Level Utilities (CLU) portion of the UGUY. During activity, the timer is continually reset. If the timer expires, it will automatically reset the CLU microprocessor. This will not affect running partitions.

NOTIFICATION-TYPE

An invalid checksum was received when reading the FRUID EEPROM for the device named in the chassis code. If this is a single error, the fault lies with the named FRU. If there are many INVALID_CKSM entries in the Event Log, there is probably a problem with the I2C bus.

NOTIFICATION-TYPE

One or more of the System Backplane Power Boards is reporting a DC Fault through the System Backplane Local Power Monitor. The physical location of the failing power board is in the Data Field of the event.

NOTIFICATION-TYPE

An attempt to read the EEPROM (FRUID) on the IO Backplane Board failed.

NOTIFICATION-TYPE

An attempt to read the EEPROM (FRUID) on the IO Backplane Power Board failed.

NOTIFICATION-TYPE

An attempt to read the Local Power Monitor Fault register on the IO Backplane Power Board failed.

NOTIFICATION-TYPE

The Local Power Monitor of the named IO Chassis is reporting a Power Brick over temperature condition.

NOTIFICATION-TYPE

The Local Power Monitor on the named IO Chassis has reported a power fault condition.

NOTIFICATION-TYPE

The Local Power Monitor on the named IO Power Board failed to properly margin the power as commanded.

NOTIFICATION-TYPE

Either by command or as part of initialization, the data from a FRUID EEPROM failed a read command. This does not necessarily mean the FRU has failed, just that the FRUID data cannot be read.

NOTIFICATION-TYPE

Either by command or as part of initialization, the data from a FRUID EEPROM failed a read command. This does not necessarily mean the FRU has failed, just that the FRUID can't be read.

NOTIFICATION-TYPE

An attempt to read the EEPROM (FRUID) on the System Backplane failed

NOTIFICATION-TYPE

A read command on the system backplane I2C bus failed.

NOTIFICATION-TYPE

A write command on the system backplane I2C bus failed. The type of command that failed can be identified by the activity status field (last byte) of the encoded field. B = RC Cable Configuration Register write C = Backplane Voltage Margin Register write 9 = Flex circuit configuration register write

NOTIFICATION-TYPE

The Local Power Monitor on the named System Backplane has detected a power fault. The failing Backplane Power Board status is read from the Backplane LPM I2C interface register and the value is placed in the data field of the event (bits 15-8).

NOTIFICATION-TYPE

Margining voltage to the System Backplane has failed.

NOTIFICATION-TYPE

An attempt to write data to the FRUID EEPROM by the MFG level MP command WF failed. The FRU handle of the failing FRUID is embedded in the two uppermost bytes of the data field.

NOTIFICATION-TYPE

The fan on a CPU is not operating in a manner that provides enough air flow to cool the processor

NOTIFICATION-TYPE

The fan on a CPU is operating in a manner that provides enough air flow to cool the processor but is not at normal operation

NOTIFICATION-TYPE

The fan on a CC chip is not operating in a manner that provides enough air flow to cool the processor

NOTIFICATION-TYPE

The fan on a CC chip is operating in a manner that provides enough air flow to cool the processor but is not at normal operation

NOTIFICATION-TYPE

System FW and the PDHC have incompatible shared memory interface revisions. Data byte 0 is the PDHC's supported ICM revision number. Data byte 1 is System FW's supported ICM revision number.

NOTIFICATION-TYPE

The MP checked the FW revision of the PDHC identified in the physical location data field and discovered that it did not recognize the revision as one that it has been qualed with. This is an unsupported configuration.

NOTIFICATION-TYPE

The local Power Monitor is reporting a fault with the named Cell Power Board. The data field of this event can be decoded as follows where a bit set in any of the status fields indicates a fault: data byte 0: (power_good << 1) | (power_fault) data byte 1: Cell Power Board converters status bits[0:2] - memory power bricks 0-2 status bits[3:5] - power i/f bus bricks 0-2 status bits[6:7] - JAB core power bricks 0-1 status data byte 2: Cell converters status bit 0 - clock power status bit 1 - cache power status bit 2 - link power status bit 3 - CC core power status bit 4 - FSB power status bit 5 - 48-V status data byte 3: CPU module converters status bit 0 - CPU module 0 core power status bit 2 - CPU module 1 core power status bit 4 - CPU module 2 core power status bit 6 - CPU module 3 core power status

NOTIFICATION-TYPE

The CPU node retuned an error when calling its initialize node function. The specific status is displayed in the data field.

NOTIFICATION-TYPE

ExecuteCommand issues commands that execute on remote CPUs via IPI interrupts. If the command failed to execute, this event is printed and the data field contains the status.

NOTIFICATION-TYPE

A remote CPU is in a state where it cannot receive and execute a new command. The current status of the CPU is provided in the data field.

NOTIFICATION-TYPE

An error was encountered when executing a PAL_PROC. This code will be emitted in pairs. The Proc INDEX will be in the data of the first chassis code. The status is in the second data field.

NOTIFICATION-TYPE

CPUs not loaded in correct order. Correct loading order is CPU 0, 1, 2, 3.

NOTIFICATION-TYPE

The XBC logged a SBE or LPE after they should have been cleared. Either the clear failed, or a new error was logged immediately. Data field: XBC number (32:43), port number (44:55), port status information (0:31)

NOTIFICATION-TYPE

The CC to XBC Link pattern test failed. Data Field: This event will be emitted three times 1st event: XBC number (32:43), port number (44:55) 2nd event: expected pattern (0:63) 3rd event: actual data read (0:63)

NOTIFICATION-TYPE

System firmware was unable to complete a platform storage read command from the utilities system. The exact status printed in the data field.

NOTIFICATION-TYPE

System firmware was unable to complete a platform storage write command. The actual status is returned in the data field.

NOTIFICATION-TYPE

The Sequencer was unable to find the tree node it needed to complete an operation. The tree node is in the ASCII in the data field.

NOTIFICATION-TYPE

System firmware attempted to read a partition variable from the GSP and store it in options. An error was encountered during this process. The data field contains the partition variable element ID that was being processed.

NOTIFICATION-TYPE

One or more power converters on the Cell or Cell Power Board has reported a fault. However, because of redundancy in the power system, the power to the Cell is still good. The data field contains detailed power fault location information that is specific to each platform.

NOTIFICATION-TYPE

CPUProcConfigValue setting in options as been compared with what is reported by PAL as settable and CPUProcConfigValue is specifying at least one bit that is not supported by this version of PAL using the Get Processor Dependent Features. This chassis code is emitted in pairs, the first data field contains the PAL expected values; the second data field contains the requested setting from options.

NOTIFICATION-TYPE

System firmware was unable to successfully issue the PAL_GET_PROC_FEATURES PAL proc. The data field is unused

NOTIFICATION-TYPE

This event is a tool to aid in the debugging and testing of firmware.

NOTIFICATION-TYPE

The CLU has encountered an undefined case in its control flow.

NOTIFICATION-TYPE

The Cell voltage margin settings do not match the Normal, +5%, or -5% values.

NOTIFICATION-TYPE

For debug purposes, many assumptions made by the PDHC developer(s) are checked at run-time. If this event log is seen, it indicates that the hardware or software is in an unknown state. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

NOTIFICATION-TYPE

An unknown error has been detected by the PDHC firmware. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

NOTIFICATION-TYPE

An attempt to write to a device on the PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A converters, and, if they are accessible, the CPU Module Power Pods' FRU EEPROMs. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

An attempt to read from a device on the PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A converters, and, if they are accessible, the CPU Module Power Pods' FRU EEPROMs. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

An attempt to write to a device on the PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules' thermal sensors. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

An attempt to read from a device on the PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules' thermal sensors. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

The PDHC did not read valid frequency information from the CPU modules' or Cell's FRU EEPROMs, or the frequency registers would not update properly. Following this event, the Cell will not boot until the problem is corrected and Cell Power has been turned off, then on again, using the PE command.

NOTIFICATION-TYPE

An error has occurred while updating System FW. More details about the update failure may be available as displayed by the Firmware Update Utility (FWUU).

NOTIFICATION-TYPE

The PDHC firmware was reset for some unknown reason.

NOTIFICATION-TYPE

A hardware fault prevented the PDHC from configuring the thermal sensor(s) on one or more of the CPU modules. Following detection of this fault condition, the Cell will be prevented from booting until the Cell is powered 'off', then 'on', using the PE command.

NOTIFICATION-TYPE

A CPU module's temperature has exceed the high temperature threshold. As a result of this event, an irrevocable 2 minute timer will begin. At the end of 2 minutes, the offending CPU module will be powered off by the Cell hardware. The Cell must be powered off then on using the MP's PE command before the CPU module will be powered again.

NOTIFICATION-TYPE

An error occurred while updating the PDHC firmware. More specific details of the update error may be displayed by the Firmware Update utility running on the MP.

NOTIFICATION-TYPE

The cell type (IPF or PA) does not match System FW type. The cell type is detected based on information stored in CPU modules' FRUID EEPROMs. The System FW type is determined based on data that is embedded in the System FW ROM image. This is checked each time Cell power transitions from off to on, and each time the System FW is updated. Following the detection of this mismatch, the Cell will not be allowed to boot until the problem has been resolved.

NOTIFICATION-TYPE

This event is emitted after the PDHC has waited longer than a maximum expected time for the PDH arbiter to grant it control of the PDH bus. The PDHC will continue waiting for control of the PDH bus until the arbiter grants it control, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink.

NOTIFICATION-TYPE

This event is emitted after the PDHC has waited longer than a maximum expected time to obtain control of the PDH bus semaphore. The PDHC will continue waiting for control of the PDH bus semaphore until System FW relinquishes control of the semaphore, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus semaphore, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink. The data field contains debug data that may be useful for developers. Data_byte[0] = last value read from PDHC's address for the microSemaphore register. Data_byte[1] = boolean indicator (1=set,0=not_set) of whether the PDHC's flag is set. Data_byte[2] = boolean indicator (1=set,0=not_set) of whether the System FW's flag is set.

NOTIFICATION-TYPE

This event indicates that an error occurred while transmitting an IPMI message in the BMC2HOST direction. The data field contains more detailed information about the source of the error. Data Bytes 0 & 1 form a 16-bit IPMI error indicator that has the following values and meanings: 1 - IPMI_HOST_BUSY_TIMEOUT - The PDHC could not put a message in the BMC2HOST hardware message queue for over 10 seconds, so the pending message(s) were dropped. 2 - IPMI_INVALID_MSG_SIZE - The MP sent an IPMI message response that has an embedded size indicator that is less than 4 bytes or greater than the size of the message data. The poorly formed message response will be dropped. 3 - IPMI_BMC2HOST_Q_FULL - The BMC2HOST message queue in the PDHC is full, so a message response from the MP has been dropped.

NOTIFICATION-TYPE

EFI was unable to read the initial debug level from the BMC token. EFI will continue with an unknown value for the debug level. Data Field: Return status from internal EFI function.

NOTIFICATION-TYPE

A XBC port was unexpectedly found to not be landmined. The data field consists of the XBC number (32:43) and the port number (44:55).

NOTIFICATION-TYPE

The number of landmined XBC ports was not within the allowable range. There is a minimum number of landmined ports because some ports are always unused. There is a maximum number of landmined ports because there is a limit to the number of broken links allowed in a system. The data field shows the number of landmined ports found

NOTIFICATION-TYPE

Data field contains the backplane type found. During Intra SKD Routing, the backplane type detected was either a Medel backplane or was unrecognized. The backplane could therefore not be routed. This is a firmware sanity check. Data Field: system type

NOTIFICATION-TYPE

Prior to initializing the CC to XBC link, the XIN error mask should be zeroed out to prevent spurious errors from interfering with the link initialization. This write to zero out the error mask failed. Data Field: (cell << 56) | return status

NOTIFICATION-TYPE

The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the return status from an attempted read of the CC Primary Error Mode CSR. (0 = SUCCESS)

NOTIFICATION-TYPE

The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Primary Error Mode CSR.

NOTIFICATION-TYPE

The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the return status from an attempted read of the CC Primary Error Mode CSR. (0 = SUCCESS)

NOTIFICATION-TYPE

The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Error Mask CSR.

NOTIFICATION-TYPE

The neighbor's port connected to the link being crossed is not routable. This was the first attempt to cross the link, PDC will now look for another link it can cross. DATA: (xbcNum << 32 ) | (port << 44)

NOTIFICATION-TYPE

Fabric read error. Data field: (XBC number << 32 | return status)

NOTIFICATION-TYPE

Too many crossbar links are broken. Cell cannot boot, halting. Data field: XBC number << 32

NOTIFICATION-TYPE

For debug purposes, many assumptions made by the PM developer(s) are checked at run-time. If this event log is seen, it will either indicate that the hardware is in a unknown state that is not handled by the PM, or that a programming bug has been found. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

NOTIFICATION-TYPE

An unknown error has been detected by the PM firmware. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

NOTIFICATION-TYPE

This event is a tool to aid in the debugging and testing of firmware.

NOTIFICATION-TYPE

Failed link testing to ensure that SBE and LPE errors are detected properly by the XBC. The XBC did not detect any errors. Data field indicates the return status: (1 = err detected, 0 = no err detected, -1 = XBC accesses failed)

NOTIFICATION-TYPE

The data field contains the cabinet number that is invalid

NOTIFICATION-TYPE

The cell indicated in the data field is at a different firmware revision than the reporting cell. This is determined by evaluating the checksums of the 2 rom images.

NOTIFICATION-TYPE

An attempt to write to a device on the PM's I2C bus has failed. The Data field contains information that can identify the exact device that has failed. Refer to the UGUY ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

An attempt to read from a device on the PM's I2C bus has failed. This event is only emitted when the PM is reading a BPS's. The Data field contains information that can identify the exact device that has failed. Refer to the UGUY ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address (to convert to BPS slot number subtract 1 and divide by 2) Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

NOTIFICATION-TYPE

An error was encountered trying to obtain the data required for the cell information structure in ICM. The data field is an ASCII message that indicates the information that was not found.

NOTIFICATION-TYPE

An error was encountered establishing the slave cells use of the diva console.

NOTIFICATION-TYPE

An error was encountered trying to relocate the registry on a slave cell to point to the core cells main memory structures.

NOTIFICATION-TYPE

The Calculated CRC for the group C Partition Profile did not match the stored value. The expected value and the actual value will be emitted in 2 sequential chassis codes.

NOTIFICATION-TYPE

Not able to find a core cell in the PD during a global MCA error processing.

NOTIFICATION-TYPE

An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.

NOTIFICATION-TYPE

An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the IP address of the function that encountered the error.

NOTIFICATION-TYPE

During the on line addition of a cell the partition adding the cell has determined inconsistent data as to which cell is being added. The cell addition will be aborted and the partition will resume execution without the new cell.

NOTIFICATION-TYPE

An error occurred while reading the routing from the source cell's port on the source XBC. Data Field: (source cell << 56 | source XBC << 32)

NOTIFICATION-TYPE

OLA cell cannot be added because it has resources that are not compatible with those already in the partition. Data field specifies the physical location of the cell which is incompatible and on which the OLA was attempted. The preceding chassis code or codes should already have been emitted specifying what the actual incompatibility was. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.

NOTIFICATION-TYPE

Root Cell attempted to OLA a cell which hung somewhere in the OLA process - the cell released from BIB but never made it to its final rendezvous state. Data field contains physical location of the hung OLA cell. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.

NOTIFICATION-TYPE

Root cell attempted to OLA a cell that was never released from BIB. Data field contains the physical location of the cell that is being OLAD.

NOTIFICATION-TYPE

Partition attempted to OLA a cell in an unexpected Cell state. Data Field contains the unexpected cell state of the OLA cell. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.

NOTIFICATION-TYPE

Root cell will emit this chassis code indicating the OLA cell could reach all cells in the alive set of the existing partition. Data field will contain the physical location of the OLA cell. This chassis code should immediately follow a chassis code indicating exactly which cell the OLA cell could not reach. The OLA cell will not be added to the partition and the partition will be unaffected.

NOTIFICATION-TYPE

CPU's of mixed maximum core frequencies are installed

NOTIFICATION-TYPE

The Cell Controller-XBC link initialization is having an intermittent failure. The data field contains the number of initialization sequences that failed before being successful.

NOTIFICATION-TYPE

PDC failed clearing the OLA steering bit in the PDH FPGA microstatus register. Data field contains the physical location of the cell with the failure. This can only happen on an OLA cell and will cause that cell to reset and not to join the existing partition.

NOTIFICATION-TYPE

The attempt to update the PD Addr Map to include OLA cell failed.

NOTIFICATION-TYPE

Attempt to update the partition PDT with OLA cell PDT data has failed.

NOTIFICATION-TYPE

Attempt to update the cell map to include the OLA Cell failed

NOTIFICATION-TYPE

Fabric Discovery's final attempt to initialize the local cell's CC to Crossbar Chip (XBC) link has failed. This cell cannot talk to the fabric. Data: link init state bit read from the CC Link State register

NOTIFICATION-TYPE

An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the physical address that failed mapping to a virtual address

NOTIFICATION-TYPE

Failure while writing the XBC CSR containing the link status

NOTIFICATION-TYPE

Failure while reading the XBC CSR containing the link status

NOTIFICATION-TYPE

Fabric Discovery's attempt to initialize the local cell's CC to XBC link has failed. The link initialization sequence has an intermittent problem.

NOTIFICATION-TYPE

An error was encountered while attempting to create and initialize a PCI device node

NOTIFICATION-TYPE

An error was encountered while scanning the PCI bus

NOTIFICATION-TYPE

An error was encountered while attempting to initialize a P2P bridge

NOTIFICATION-TYPE

Insufficient IO Port space to support the PCI card

NOTIFICATION-TYPE

Insufficient MMIO space to support the PCI card requirements

NOTIFICATION-TYPE

An error was encountered while attempting to initialize the SBA node

NOTIFICATION-TYPE

An error was encountered while attempting to discover SBA hardware

NOTIFICATION-TYPE

An error was encountered while attempting to reset the SBA

NOTIFICATION-TYPE

An error was detected in the link between the CC and the I/O controller.

NOTIFICATION-TYPE

An SBA cable error has been detected

NOTIFICATION-TYPE

Identified the cell number that is connected to the chassis.

NOTIFICATION-TYPE

An error occurred while attempting to create or initialize an LBA node

NOTIFICATION-TYPE

An error was encountered while attempting to configure LBA rope bundling width

NOTIFICATION-TYPE

error code

NOTIFICATION-TYPE

An error occurred while attempting to clear an LBA error log register

NOTIFICATION-TYPE

An error was encountered while attempting to generate LBA error logs

NOTIFICATION-TYPE

An error was encountered while attempting to discover LBA hardware

NOTIFICATION-TYPE

An error occurred while attempting to configure the LBA hardware

NOTIFICATION-TYPE

An error was encountered while attempting to scan the PCI bus

NOTIFICATION-TYPE

An error was encountered while attempting to configure PCI config space

NOTIFICATION-TYPE

The OLA cell failed accessing the complex profile. Cell will send Failed to OLA message back to partition and then reboot itself. Existing partition will not be affected.

NOTIFICATION-TYPE

A Firmware tries to find a main memory block large enough meeting alignment requirements.

NOTIFICATION-TYPE

Cell started OLA but is not configured in the complex profile of the partition. Cell will reboot to SINC_BIB. Existing partition will not be affected.

NOTIFICATION-TYPE

The Options service received an error when attempting to allocate an NVRAM storage block. Either an error was returned from the call, or the call returned successfully yet an invalid address was returned.

NOTIFICATION-TYPE

A failure occurred on the OLA cell during the attempt to synchronize its real time clock with the clock(s) in the existing partition. Data field contains physical location of OLA cell.

NOTIFICATION-TYPE

Access to SAL error log procedure timed out because the log facility was busy processing a request from another CPU. Data field indicates the SAL procedure ID.

NOTIFICATION-TYPE

The PDH FPGA IPR is not cleared after a MAX_RD_CLR_IPR_TRIES on a cell. The Data Filed in the Cell number. See the next Chassis Code to see the MAX_RD_CLR_IPR_TRIES

NOTIFICATION-TYPE

Indicated the PDH FPGA IPR is not cleared after a number of PDC attempts. The Data Field contents the MAX_RD_CLR_IPR_TRIES. Please look at the previous Chassis Code to see the Cell number.

NOTIFICATION-TYPE

attempt to synchronize the Real-Time Clock of the OLA cell with the existing partition failed because the RTC on the core cell could not be read.

NOTIFICATION-TYPE

One or more dimms are missing from the echelon given in the data field. The dimms may not be installed or firmware was not able to detect the dimms.

NOTIFICATION-TYPE

The code that reads the port state (landmine vs. healthy) expects a XBC internal port number, it received bogus data. The port state cannot be read. Data Field: (port << 44) | (xbc num << 32)

NOTIFICATION-TYPE

The code that writes the port state (landmine vs. healthy) expects a XBC internal port number, it received bogus data. The port state cannot be read. Data Field: (port << 44) | (xbc num << 32)

NOTIFICATION-TYPE

The main backplane is reporting the LPM status as fault.

NOTIFICATION-TYPE

The IO backplane has reported a local power monitor fault.

NOTIFICATION-TYPE

System firmware was unable to default the complex profile

NOTIFICATION-TYPE

Firmware call to set processor feature resulted in an error.

NOTIFICATION-TYPE

This chassis code shows that the error log space in the NVRAM has not been allocated for the current error event. This will be emitted out whenever a error section is attempted to be logged without allocation of log space in NVRAM

NOTIFICATION-TYPE

This indicates that the error logs for a particular event type have reached the maximum allowed to be stored in the NVRAM. The event type is indicated in the data field.

NOTIFICATION-TYPE

System firmware has been invoked to perform a cell delete operation but no cell in the system appears to be ready for deletion.

NOTIFICATION-TYPE

The bulk power supply is overcurrent

NOTIFICATION-TYPE

Data: Bulk location.

NOTIFICATION-TYPE

Error Response Mode code attempted a malloc of heap space that failed.

NOTIFICATION-TYPE

The dimm in the physical location given by the data field is not supported on this platform. The dimm may not be supported by the hardware, or the dimm may not have been properly qualified for this platform.

NOTIFICATION-TYPE

The OPTIONS component was unable to allocate NVRAM memory in order to store a non-volatile variable. The storage area for NVRAM options may be full, or there may be undetected corruption.

NOTIFICATION-TYPE

A dimm or CPU has failed and is not operational for the system. This event is emitted prior to determining if the cell should be integrated into the Partition.

NOTIFICATION-TYPE

A cpu or dimm error has been detected, and the Complex Profile, Cell Integration Table, Cell integration policy says to not integrate the cell into the PD. The data field is unused, but the cell that emitted this event is the one that did not get integrated.

NOTIFICATION-TYPE

The IO error context is corrupt. This will impair IO error reporting.

NOTIFICATION-TYPE

A rope went fatal from the SBA to the LBA. If all the ropes go fatal the IO subsystem is dead. Any I/O below the rope will not be accessible. The data field gives the physical location of the rope that went fatal. Some ROPE_FATAL conditions will not cause the system to go down. For Example, a rope that has gone fatal during an OLAR operation will only cause warnings to the user, not bring the partition down.

NOTIFICATION-TYPE

A PCI bus on the system is fatal. Any device on this bus is unavailable. Firmware was unable to complete card initialization due to an error. Data field contains physical location of failed bus.

NOTIFICATION-TYPE

One of the rope units in the SBA failed. If all of the rope units fail, then IO will not be available on this cell.

NOTIFICATION-TYPE

The System Flash Write Enable bit is incorrectly set and now clearing by PDC. The Data field contains the value of PDH Miscellaneous Signal Register read before System Flash bit is cleared.

NOTIFICATION-TYPE

System firmware encountered an error while trying to perform an operation during system initialization. This event ID will always be emitted before an event ID that describes the status of the operation that failed.

NOTIFICATION-TYPE

This means that all the cpus in the cell did not show up.

NOTIFICATION-TYPE

This means that all the cells did not rendezvous during the PD rendezvous. The data part will contain the Expected data and the actual mask of the cells that rendezvoused.

NOTIFICATION-TYPE

The FW tree sanity check failed during the MCA error processing.

NOTIFICATION-TYPE

This means that the registry sanity check failed during MCA error handling.

NOTIFICATION-TYPE

This means that MCA occurred while OS_MCA was performing error recovery.

NOTIFICATION-TYPE

This means that memory dump will be abandoned due to work-around for CN2272. This happens when one of the Blocking timeout in the Processor input block of the Cell Controller occurs.

NOTIFICATION-TYPE

The firmware tree is not complete and hence there will be no PD rendezvous.

NOTIFICATION-TYPE

The firmware parameter that defines the ACPI configuration is inconsistent in at least one of the cells in the partition.

NOTIFICATION-TYPE

Writing the XIN_ERR_ORDER_STATUS register of the CC failed. This is some sort of a hardware failure. Data Field: return status

NOTIFICATION-TYPE

An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.

NOTIFICATION-TYPE

A value read by the PDHC from a CPU module's Processor Information ROM was not within acceptable limits.

NOTIFICATION-TYPE

An invalid parameter was specified when trying to set the cpu bus config register, cpu frequencies ratio field. Valid range is 0xe - 0x17

NOTIFICATION-TYPE

The overhead structure of the OPTIONS block in NVRAM has a checksum error.

NOTIFICATION-TYPE

During a cell OLA, the link on the local cell failed to initialize. Data Field: (my cell << 32) | XIN Link State

NOTIFICATION-TYPE

An attempt to disable the fabric link failed because writing the CC CSR failed. Data Field: (cell << 56) | return status

NOTIFICATION-TYPE

Could not determine the system type in order to write the appropriate error mask for the fabric link. Data Field: system type

NOTIFICATION-TYPE

Failed writing the XIN error mask for CC's fabric link. Data Field: (cell << 56) | return status

NOTIFICATION-TYPE

Could not read the XIN Link error mask register. Data Field: (cell << 56) | return status

NOTIFICATION-TYPE

The CC to CC link initialization sequence has failed. Data Field: link init status

NOTIFICATION-TYPE

An error occurred while trying to notify the MP that a reset is about to occur (QPartitionReleaseBIB command). The status is in the data field.

NOTIFICATION-TYPE

A fabric access error occurred while trying to disable the CC to CC link on a single cell Medel system. This cell will halt. Data field: error status

NOTIFICATION-TYPE

While updating the Port State register, the cell could not get the XBC semaphore. Data field is: (Port Num << 44 | XBC num << 32 | return status). Where return status is: (0 Success; -1 Access Failure; -2 Semaphore Owned By Another, -3 Semaphore Already Owned; -4 XBC Key Contention)

NOTIFICATION-TYPE

While updating the Port State register, the cell could not get the XBC semaphore. Data field is: (Port Num << 44 | XBC num << 32 | return status). Where return status is: (0 Success; -1 Generic Failure)

NOTIFICATION-TYPE

An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.

NOTIFICATION-TYPE

While attempting to initialize the XIN link, it was found to already be initialized. A firmware assertion has failed. The link will not be re-initialized and processing should continue as normal. However, the system could be confused at this point.

NOTIFICATION-TYPE

The PDHC FW could not detect any CPU modules on its Cell board, so it is holding the Cell in reset.

NOTIFICATION-TYPE

The Cell has been disabled by PDHC FW because the CPU modules are not compatible. Compatibility is determined based on data stored in the Scratch/FRUID EEPROM on each CPU module. The CPU module partition compatibility byte for each CPU module must be identical.

NOTIFICATION-TYPE

The Cell has been disabled because of invalid data in a CPU module Scratch EEPROM. PDHC FW checksums the FRUID data stored in each CPU module's Scratch EEPROM. If a checksum fails, the Cell is held in reset and will not boot. The data field identifies the CPU module that failed.

NOTIFICATION-TYPE

The battery voltage level is low for the cell. This indicates that the NVRAM will not be saved if the power is removed.

NOTIFICATION-TYPE

There was an error while copying the routing for the XBC to the local XBC port. The cell will reset. Data: (XBC port << 44) | (XBC num << 32) | return status

NOTIFICATION-TYPE

The read immediately after a write while copying routing registers failed. Data: whether or not the XBC Key was enabled

NOTIFICATION-TYPE

Failed to release a XBC Semaphore while marking each XBC in the complex to indicate that routing has completed. Data: (XBC num << 32) | return value

NOTIFICATION-TYPE

Writing this XBC's forward progress register failed. Data: (XBC num << 32) | return value

NOTIFICATION-TYPE

Failed to get a XBC Semaphore while marking each XBC in the complex to indicate that routing has completed. Skipping this XBC. Data: (XBC num << 32) | return value

NOTIFICATION-TYPE

Reading this XBC's topology register failed. Data Field: (xbc num << 32) | return status

NOTIFICATION-TYPE

Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)

NOTIFICATION-TYPE

Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)

NOTIFICATION-TYPE

While checking traversability of a 2 cell back to back system, there was an error reading the local cell's XIN block. Data Field: return status (1 or -1)

NOTIFICATION-TYPE

While checking traversability of a 2 cell back to back system, there was an error reading the local cell's XIN block. Data Field: return status (1 or -1)

NOTIFICATION-TYPE

Could not traverse to the target cell. The XIN link is either not initialized, or is not connected to the target cell. However, the target cell is designated to be within the partition. Data Field: target cell << 56 | XIN link state register

NOTIFICATION-TYPE

Could not traverse to the target cell. The XIN link is either not initialized, or is not connected to the target cell. However, the target cell is designated to be within the partition. Data Field: target cell << 56 | XIN link state register

NOTIFICATION-TYPE

Error reading the XIN_LINK_STATE register of the CC. This occurred while verifying that the link had been disabled. Data Field: cell being read << 56 | return status from the CSR read.

NOTIFICATION-TYPE

Failure while reading the XBC CSR containing the link status. This occurred while attempting the retry process to get XBC to CC link initialized. Data Field: link init status

NOTIFICATION-TYPE

An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.

NOTIFICATION-TYPE

The CPU that just completed self tests is functionally or performance restricted. The data field contains the Self Test State Parameter. The 2-bit state field (bits 1..0) can have the following values when this event is displayed: 01 - Performance Restricted - cpu still functions 10 - Functionally Restricted - cpu doesn't function properly

NOTIFICATION-TYPE

The RTC was found to be invalid and has been cleared

NOTIFICATION-TYPE

System firmware requested that Late Self Tests be run by PAL, but PAL returned that the tests did not actually run on the processor. The data field indicates the status word returned by PAL.

NOTIFICATION-TYPE

An attempt to update the cell state has failed due to a fabric crossbar failure. The cell number being updated in bits 63:56, while the traversable cell set (those cells connected to the fabric) is returned in bits 31:0

NOTIFICATION-TYPE

Failed to reset a cell due to an error setting the cell's state. The cell will not be reset with the other cells in the PD. The cell number is reported in the data field.

NOTIFICATION-TYPE

SFW has detected that a DRAM is failing on the DIMM specified by the physical location. The rank the failing DIMM is part of will be deallocated.

NOTIFICATION-TYPE

Internal CPU clocks are not valid when compared with the real time clock. The data field contains the hex value of the elapsed time. If this value is off a small percentage from the expected value (which is given in the next chassis code), the event is emitted.

NOTIFICATION-TYPE

Could not traverse the fabric to the cell being added. Data field: (chosen cell << 56) | return status, where -1 = failure

NOTIFICATION-TYPE

A XBC port was found to be unhealthy on this reboot. This cell will attempt to route around it. Data field: (local Cell << 56) | (local internal Port << 44) | (local XBC << 32) | XBC internal port number being routed around.

NOTIFICATION-TYPE

Error getting the XBC port's expected neighbor from a firmware table. Data field: 0 (SUCCESS) or -1 (FAILURE)

NOTIFICATION-TYPE

Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function IsHCellCpuDeconfig().

NOTIFICATION-TYPE

Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function SleepAndWakeupCountersGet().

NOTIFICATION-TYPE

Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function PdhGetHCellStructAddr().

NOTIFICATION-TYPE

Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function HasCpuCompletedWakeupTask().

NOTIFICATION-TYPE

Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function PdhGetHCellStructAddr().

NOTIFICATION-TYPE

There is a need to reset the cell for reconfiguration, but it cannot be done yet because the cell has not reported at BIB. The Reset is being scheduled to be performed later.

NOTIFICATION-TYPE

When processing the complex profile, the an unexpected 'Architecture Type' was specified in the PA/IA Arch field. The actual data found is displayed.

NOTIFICATION-TYPE

While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the deconfig byte information about the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from IsHCellCpuDeconfig().

NOTIFICATION-TYPE

While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's sleep and wakeup counters for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from SleepAndWakeupCountersGet().

NOTIFICATION-TYPE

While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's forward progress state (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().

NOTIFICATION-TYPE

While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's Forward Progress State (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().

NOTIFICATION-TYPE

At a certain point in PDC boot, all of the processors in the partition except the PD monarch are put into a sleep, and they remain there until they are awakened by the PD monarch, at which time they read an architected location in Page Zero to find out where to branch to. This gives the OS a mechanism by which to bring processors under its control and have it executing OS code. This chassis log is sent if and when a problem is detected by PDC regarding the contents in the Page Zero location. This means that PDC cannot branch to the location logged in the Page Zero location. So, PDC sends this chassis log and then the processor returns to sleep. The data field is unused.

NOTIFICATION-TYPE

The Data Field contains the value used to determine a valid order.

NOTIFICATION-TYPE

While trying to get the sleep counter and the wakeup counter for a particular processor, which is kept in a data structure in PDH memory, PDC was unable to determine the address to the data structure on the remote cell. PDC is supposed to be able to calculate addresses to anything in PDH memory on other cells in the partition. The data field contains the PDC error return status from a function called PdhGetHCellStructAddr().

NOTIFICATION-TYPE

Error occurred accessing a PDC data structure. Depending upon the situation the cell or entire partition will be reset. The data field contains the return status for the function that encountered the error.

NOTIFICATION-TYPE

PDC is about to halt the cell because PDC was unable to determine the GNI address of the SlaveDispatcher function of PDC relocated to memory by PDC. The data field contains the error return value from the function GetGniCodeAddrFromRomCodeAddr().

NOTIFICATION-TYPE

PDC is about to halt the cell because at least one of the processors didn't complete the task for which they were awakened and then return to sleep. The data field contains an error return status.

NOTIFICATION-TYPE

PDC is about to halt the cell because PDC was unable to determine the GNI address of the CpuFpSet() function of PDC relocated to memory by PDC. The data field contains the error return value from the function GetGniCodeAddrFromRomCodeAddr().

NOTIFICATION-TYPE

PDC is about to halt the cell because one or more of the slaves were unable to change their CPU FP state in PDH memory on the local cell. The data field contains an error return status.

NOTIFICATION-TYPE

PDC was trying to move the cell monarchs on each of the non-core cells into the Dispatcher, but in order to do that, the PD monarch needs to be able to read the CPU number of the cell monarch on each of the non-core cells, which is kept in a data structure on each of the cells. PDC was unable to get the address to the CELL_CPU_STATE structure in PDH memory in a cell in the partition. The data field is the error return status from the PDC function called PdhGetHCellStructAddr().

NOTIFICATION-TYPE

PDC is about to reset the partition because at least one of the processors didn't complete the task for which they were awakened and then return to sleep. The data field contains the error return status from the PDC function CheckSingleSlave().

NOTIFICATION-TYPE

PDC is about to reset the partition because it is unable to determine the GNI address for the CpuFpSet() function for one or more of the cells in the partition. The data field contains the error return status from GetGniCodeAddrFromRomCodeAddr().

NOTIFICATION-TYPE

PDC is about to reset the partition because one or more of the processors were unable to successfully modify their CPU FP State (aka their PST state). The data field contains the error return status from the CpuFpSet() function.

NOTIFICATION-TYPE

MX2 initialization failed.

NOTIFICATION-TYPE

A cpu that is attached to a cpu that is slated for deconfiguration is being deconfigured as well.

NOTIFICATION-TYPE

FW failed to virtualize the mx2 interposer.

NOTIFICATION-TYPE

FW has failed to virtualize the mx2 interposer.

NOTIFICATION-TYPE

Installation of the FW PMI handler has failed.

NOTIFICATION-TYPE

Cell and or cpus have failed compatibility checks.

NOTIFICATION-TYPE

PDH space not available after release from reset.

NOTIFICATION-TYPE

MPON failed to release.

NOTIFICATION-TYPE

Dillon failed to reset.

NOTIFICATION-TYPE

DMD clock is not running.

NOTIFICATION-TYPE

All possible CPUs on a cell have been scheduled for deconfiguration.

NOTIFICATION-TYPE

A read error occurred while dumping the XBC port routing registers during boot. This cell will attempt fabricless boot. Data field: (XBC port << 48) | (XBC num << 32) | error status reg

NOTIFICATION-TYPE

After cell rendezvous for a 2 cell Medel, only one cell made it into the partition. Disabling the link failed. The cell will reset for reconfig. Data Field: return status

NOTIFICATION-TYPE

Power is no longer being supplied to input A0 on the cabinet specified in the data field.

NOTIFICATION-TYPE

Power is no longer being supplied to input A1 on the cabinet specified in the data field.

NOTIFICATION-TYPE

Power is no longer being supplied to input B0 on the cabinet specified in the data field.

NOTIFICATION-TYPE

Power is no longer being supplied to input B1 on the cabinet specified in the data field.

NOTIFICATION-TYPE

Failed to disable the XIN link init CSR on a XBCless system. Cell will halt. Data field: return status (0 = SUCCESS, -1 = FAILURE), -1 is expected for this event.

NOTIFICATION-TYPE

Error writing the XBC port's routing registers. The cell will reboot. Data Field: XBC port << 44 | XBC num << 32 | return status

NOTIFICATION-TYPE

Could not read the XIN error mask register on the CC. Data Field: cell number and return status

NOTIFICATION-TYPE

Could not write the XIN error mask register on the CC. Data Field: cell number and return status

NOTIFICATION-TYPE

While testing link traversability, a XBC CSR could not be read. Data Field: Port Number << 44 | XBC Number << 32 | return value

NOTIFICATION-TYPE

The Battery-Low interrupt was signaled in the Interrupt Pending Register in Dillon (PDH) by the hardware. PDHC is merely reporting the problem.

NOTIFICATION-TYPE

This means that the system FW MCA handler is not going to handoff to the OS_MCA handler.

NOTIFICATION-TYPE

When returning from other software, like when returning from ISL, PDC is trying to make sure that all of the slave processors in the partition are asleep; however, this event ID indicates that we were unable to access PDH memory of a cell that is supposed to be part of our partition. The data field contains the error return status from a function called SleepAndWakeupCountersGet().

NOTIFICATION-TYPE

When returning to PDC from other software, like returning from ISL, PDC tries to verify that all the slave processors are in the expected state (i.e. that all slave processors are asleep); however, this event ID indicates that at least one processor active in the partition was not asleep. So, PDC is going to reset the partition. The data field of this Event ID is the global CPU number of the first CPU in the partition not found in the expected state.

NOTIFICATION-TYPE

PDC could not access one of its own data structures on the local cell. The cell will be halted. The data field contains the return status from the PDC function that encountered the error.

NOTIFICATION-TYPE

The NVRAM-based descriptor for System Firmware NVRAM blocks is corrupt.

NOTIFICATION-TYPE

The cell will be reset because it was unable to access PDH memory on its own cell. While trying to move all the slave processors on the cell to the 'late boot sleep', the monarch tried to write the sleep timeout to PDH memory on its own cell, but encountered an error in doing so. The data field contains a PDC return status.

NOTIFICATION-TYPE

All CPUs have been determined to be manually deconfigured in NVM during boot. This may only happen when switching from single core CPU deconfiguration to multi-core CPU deconfiguration in product qualification testing. As a recovery, NVM settings have been changed to reconfigure all CPUs.

NOTIFICATION-TYPE

A failure has occurred trying to determine the number of CPU cores per module. Depending upon the situation, either the cell will be halted or the entire partition will be reset.

NOTIFICATION-TYPE

While writing the remote routing, the local XBC could not be accessed to determine the topology. Look for additional chassis codes to determine what will happen as a result of this failure. Data field: return status, either SUCCESS (0) or (-1)

NOTIFICATION-TYPE

Failed to route around a broken link on cell reboot. Data Field: PDC return status

NOTIFICATION-TYPE

Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Too many broken crossbar links were found. This cell will have no connectivity to other cells in the complex. It will attempt a fabricless boot, except in a few configurations. Data Field: (XBC Num << 32) | number of broken links

NOTIFICATION-TYPE

Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: PDC return status

NOTIFICATION-TYPE

Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not read the XBC register that marks the ports that have been routed around. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

The PIOB route to the remote XBC was not traversable. The cell will halt. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Could not release the remote XBC's semaphore. Cell will halt. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Failed to complete a broadcast write to an XBC. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Failed to complete a read to the built-in port of a XBC. Data Field: (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

Failed to complete a write to the local cell's port of the XBC. Data Field: (XBC Port << 44) | (XBC Num << 32) | PDC return status

NOTIFICATION-TYPE

The link between the CC and SBA failed meaning that I/O is not available to the reporting cell.

NOTIFICATION-TYPE

An error was detected in the SBA and the reporting cell has no I/O.

NOTIFICATION-TYPE

The structured exception handling within the system firmware failed during I/O initialization.

NOTIFICATION-TYPE

There is not enough malloc resources for the I/O structure exception handling. I/O on the reported cell is not available.

NOTIFICATION-TYPE

Error creating the structure for housing the I/O structured exception handling services and data. I/O is lost on the reporting cell.

NOTIFICATION-TYPE

Unable to bind the I/O structure exception handling to the internal data structures.

NOTIFICATION-TYPE

Error detected while initializing the I/O structure exception handling services.

NOTIFICATION-TYPE

Error initializing the I/O structure exception handling data structures.

NOTIFICATION-TYPE

The structured I/O exception handling data structures have an error. All I/O on the reporting cell is not available.

NOTIFICATION-TYPE

While setting up the internal SBA data and service an error was detected. All I/O for the reporting cell is not available.

NOTIFICATION-TYPE

An error attaching firmware services to the internal structures was detected. All I/O on the reporting cell is not available.

NOTIFICATION-TYPE

System firmware detected an error initializing internal SBA data structures and services. This is usually an error with unavailable resources.

NOTIFICATION-TYPE

The SBA type is unknown to the system firmware. The I/O on the reporting cell is not available.

NOTIFICATION-TYPE

An expected I/O device cannot be detected by the system firmware.

NOTIFICATION-TYPE

Too many broken links! The XBC port route around failed because the route-around port was bad too. Data field: (XBC port << 44) | (XBC num << 32) | port state

NOTIFICATION-TYPE

ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.

NOTIFICATION-TYPE

Server Agents SNMP branch is not responding due to a portion of the IPMI Management Subsystem being locked by another entity.

NOTIFICATION-TYPE

A non-hot plug I/O slot's power consumption increases the total I/O power consumption beyond the supported limit. Firmware will display the following EFI error message, 'I/O configuration exceeds power limit' and disallow O/S boot. Data Field: Physical location of the I/O slot.

NOTIFICATION-TYPE

This is a warning that the system is running in a degraded mode. It will only be emitted in MFG mode when Memory SBE Seeding is enabled. This is only for testing of SBE seeding for LAB and possibly MFG use ONLY. It should NEVER be seen in the field.

NOTIFICATION-TYPE

Read failure while writing the number of failed links to the XBC. Data Field: Return Status (SUCCESS = 0, FAILURE = -1)

NOTIFICATION-TYPE

PDC could not access a complex profile. The partition will be reset because the available complex profile is not valid. Data field contains the return status from the function that encountered the error.

NOTIFICATION-TYPE

An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.

NOTIFICATION-TYPE

PDC could not access a complex profile. The partition will be reset. Data field contains the return status from the function that encountered the error.

NOTIFICATION-TYPE

Before attempting a fabricless boot, the cell's link to the fabric should be disabled to provide isolation and stability. The link could not be disabled, so the cell will halt.

NOTIFICATION-TYPE

Configuration information on the processor was invalid. The cell will be halted. Data field contains the return value from the function that encountered the error.

NOTIFICATION-TYPE

The clock ratio that the processor is running at does not match the clock ratio that manageability is reporting.

NOTIFICATION-TYPE

The user has manually bypassed a stop boot condition (caused by an error during boot) and continued to boot an O/S. The system might experience unpredictable failures.

NOTIFICATION-TYPE

Firmware was unable to relocate the VGA BIOS to the hardcoded VGA BIOS region in main memory (physical address range 0xc0000 - 0xdffff). VGA routing has been disabled by firmware. No VGA device will be accessible on this boot.

NOTIFICATION-TYPE

The component compatibility matrix stored in NVRAM and used by system firmware has a checksum error. The stored value does not equal the calculated value. The data field will contain first the expected value, and the subsequent code will contain the actual data.

NOTIFICATION-TYPE

PDC could not read an internal CPU register. The partition will be reset. Data field is the return status from the function that encountered the error.

NOTIFICATION-TYPE

PDC could not read an internal CPU register. The partition will be reset. Data field is the return status from the function that encountered the error.

NOTIFICATION-TYPE

PDC failed reading a value out of its own copy of the internal CPU register settings. Data field is a status return indicating the type of failure.

NOTIFICATION-TYPE

PDC failed reading a value out of its own copy of the internal CPU register settings. Data field is a status return indicating the type of failure.

NOTIFICATION-TYPE

PDC attempted to update CPU registers to match their respective settings in the complex profile, but a failure was returned from the call to accomplish the update. Data field contains the failure.

NOTIFICATION-TYPE

PDC could not access a complex profile. The partition will be reset.. Data field contains the return status from the function that encountered the error.

NOTIFICATION-TYPE

PDC could not access a complex profile. The cell will be reset. Data field contains the return status from the function that encountered the error.

NOTIFICATION-TYPE

Could not find a potential core cell for the partition in the configured set. This cell will reset for reconfiguration. Data Field: return status from failing function

NOTIFICATION-TYPE

The potential core cell was not viable (i.e. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set

NOTIFICATION-TYPE

The potential core cell was not viable (i.e. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set

NOTIFICATION-TYPE

The potential core cell did not rendezvous with the rest of the partition. This cell cannot talk to the selected core cell. This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set

NOTIFICATION-TYPE

The local cell is disconnected from the rest of the system due to the main backplane configuration. While the partition is only configured to contain a single cell, the local cell is not a viable core cell. The cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set

NOTIFICATION-TYPE

This cell has booted without the main backplane, probably due to prior main backplane errors. The partition it is in is configured with 3 or more cells. The combination of these two configurations is not allowed. The cell will reset for reconfiguration. Data Field: configured set

NOTIFICATION-TYPE

While validating the internal RTC data the data is read twice and compared. If the comparison fails to match the read is performed again up a maximum of 50 times. If we cannot get a match in 50 retries we issue this event.

NOTIFICATION-TYPE

PDC attempts to make sure that all of the cells in a partition are installed in the same processor architecture. PDC failed to read the architecture for another cell. PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell reporting the event.

NOTIFICATION-TYPE

The buffer size passed in to the XBC error logging routine through SAL_GET_STATE_INFO, SAL_CLEAR_STATE_INFO, or MCA logging is too small for the XBC error log Data field consists of: XBC number (32:43)

NOTIFICATION-TYPE

System firmware was unable to clear an XBC error. The data field contains: XBC number (32:43) port number (44:55) error type (0:31)

NOTIFICATION-TYPE

Error encountered while collecting PCI error logs. The result is some or all PCI error logs will be unavailable.

NOTIFICATION-TYPE

Error encountered while collecting SBA error logs. The result is some or all SBA error logs will be unavailable.

NOTIFICATION-TYPE

During fabric initialization, if a crossbar is found to be in an unexpected state, the number of retries is incremented. If the number of retries exceeds the maximum, then something is wrong and there is no way to initialize the fabric. Data field: number of retries (0:31), crossbar number (32:63)

NOTIFICATION-TYPE

ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.

NOTIFICATION-TYPE

ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.

NOTIFICATION-TYPE

A error occurred on the bus connecting the PCI card to the system bus.

NOTIFICATION-TYPE

A PCI card has been marked as 'fatal' by the operating system due to a bus error. The LBA has been isolated by the operating system due to an error which occurred in a device(s) connected to that LBA.

NOTIFICATION-TYPE

A PCI card has been marked as 'fatal' by the operating system due to a device error.

NOTIFICATION-TYPE

Firmware tried to read the first boot token an got a failure. The data field contains the token number that FW tried to read. This is a stop boot condition

NOTIFICATION-TYPE

monarch PA cell has detected that a cell it is attempting to rendezvous into its PD is not a PA cell and is thus incompatible.

NOTIFICATION-TYPE

A XBC error could not be cleared due to a write failure. The data field indicates the type of error: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Failed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

The XBC CSR Low Severity error was not cleared or more errors remain. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | contents of the XBC CSR Error Status Register

NOTIFICATION-TYPE

The XBC CSR High Severity error was not cleared or more errors remain. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | contents of the XBC CSR Error Status Register

NOTIFICATION-TYPE

Failed to read the XBC Port Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Failed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | error status

NOTIFICATION-TYPE

Firmware failed to copy the XBC CSR Error symbol 01 registers into a data structure on the stack. Data Field: address where the register contents are being copied

NOTIFICATION-TYPE

Firmware failed to copy the XBC CSR Error symbol 23 registers into a data structure on the stack. Data Field: address where the register contents are being copied

NOTIFICATION-TYPE

Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

The XBC Low Severity error logs were not cleared. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | number of failed clear attempts

NOTIFICATION-TYPE

Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Failed to read a XBC Global scratch register that indicates if new, unlogged errors have been encountered. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

Failed to read a XBC Global scratch register that indicates if new, unlogged errors have been encountered. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status

NOTIFICATION-TYPE

An error occurred while enabling hashing in the platform cache. The data field contains the status.

NOTIFICATION-TYPE

A write to an invalid XBC CSR address was attempted. The write will not be allowed. The severity of this result will be determined by the calling function. Data Field: XBC CSR address that was attempted

NOTIFICATION-TYPE

It indicates loss of cell connectivity in the partition during a global MCA processing.

NOTIFICATION-TYPE

Error status of building the cell-level firmware device tree

NOTIFICATION-TYPE

An error has occurred during CPU FSB interface initialization. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error has occurred while obtaining CPU parameters from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while getting CPU icache parameters from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if this error occurs during system boot.

NOTIFICATION-TYPE

An error occurred while obtaining CPU dcache parameters from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if error occurs during system boot.

NOTIFICATION-TYPE

An error occurred while initializing the CPU cache to a known state. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while enabling CPU cache error monitoring. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while enabling some machine error check traps on a CPU. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while disabling marching error check traps on a CPU. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred during the serialized CPU late selftests. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while enabling the CPU L2 shared cache. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error while getting default values for programmable CPU internal registers from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while getting an address for a CPU internal register within a buffer from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

An error occurred while programming CPU internal registers with final configuration values. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.

NOTIFICATION-TYPE

There was not enough error free memory in the system to run the late selftests.

NOTIFICATION-TYPE

The left cell ejector on the specified cell is open.

NOTIFICATION-TYPE

The right ejector latch on the specified cell board is open.

NOTIFICATION-TYPE

The optical emitters on the cell latch sensors are not functioning.

NOTIFICATION-TYPE

The specified vrm is reporting a fault.

NOTIFICATION-TYPE

The specified vrm is reporting a fault.

NOTIFICATION-TYPE

The specified rail is reporting a fault.

NOTIFICATION-TYPE

The specified pci vrm is reporting a voltage fault.

NOTIFICATION-TYPE

The specified pci power brick is reporting a voltage fault.

NOTIFICATION-TYPE

The specified vrm is reporting a temperature fault.

NOTIFICATION-TYPE

The specified pci power brick is reporting a temperature fault.

NOTIFICATION-TYPE

The specified vrm rail is reporting a fault.

NOTIFICATION-TYPE

The specified pci brick is reporting a fault.

NOTIFICATION-TYPE

The specified system backplane vrm is reporting a module voltage fault.

NOTIFICATION-TYPE

The specified system backplane vrm is reporting a temperature fault.

NOTIFICATION-TYPE

The specified system backplane rail is reporting a fault

NOTIFICATION-TYPE

The master mp has failed. The slave has taken over management of the cabinet.

NOTIFICATION-TYPE

The NVRAM service was unable to satisfy an NVRAM allocation request.

NOTIFICATION-TYPE

The RTC seems to not be updating its internal time registers. The cell cannot boot without the RTC.

NOTIFICATION-TYPE

An uncorrectable Power Aware Architecture (PAA) fault has occurred on the MX2 module and PAA firmware has halted. The system will continue to run without PAA firmware.

NOTIFICATION-TYPE

fabric API is about to open the a link going out of the local cell

NOTIFICATION-TYPE

An Arches fabric CSR read was unsuccessful because of a timeout.

NOTIFICATION-TYPE

An Arches fabric CSR write was unsuccessful

NOTIFICATION-TYPE

The event data details the error return status from Phase3BackToBackPrep. Internal debug only, this refers to an unexpected firmware error or data corruption.

NOTIFICATION-TYPE

The maximum memory supported by this system has been exceeded. The data field contains the amount of memory supported by the system.

NOTIFICATION-TYPE

Failed to delete a bad port while routing the fabric. Data field indicates return status

NOTIFICATION-TYPE

failed to delete an edge that was found to be bad during routing

NOTIFICATION-TYPE

A command to the memory buffer chip failed to complete.

NOTIFICATION-TYPE

The Arches Fabric function ArfIsCsrRouteTraversable was called for a back-to-back system. This is unsupported, ArfIsCsrRouteTraversable should only be called for systems with crossbars. No data.

NOTIFICATION-TYPE

An invalid port number was given as an input to an Arches Fabric Traversability function. The port is expected to be an internal XBC num (8-15), but the actual port was not. Data field: (XBC number << 32) | (port number << 48)

NOTIFICATION-TYPE

Unable to read XBC port neighbor information. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

XBC port with an unexpected neighbor chip type. Data field: (expected chip type) | (actual chip type << 16) | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC port was found to have an unexpected neighbor ID. Data field: (expected NID) | (actual NID << 16) | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC was found to have an unexpected neighbor port connection. Data field: (expected port) | (actual port << 16) | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

The expected data was not found in the Arches Fabric expected edge list. Data field is unused

NOTIFICATION-TYPE

An XBC port has an unexpected neighbor chip type. Data field: neighbor type found, bits [7:0], other bits unused

NOTIFICATION-TYPE

A previously good XBC-XBC link was found to be down. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC port was found to have a Fatal Error during traversability test. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Unable to read the local cell's LINK_SEL_FABRIC CSR Data field: unused

NOTIFICATION-TYPE

Unable to read the XBC route table. Data field: (route index) | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC link was found to be not connected while testing CSR traffic traversability. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Error reading Skyline ALREC_ALB_ID CSR Data field: (Skyline port) | (Cell number << 56)

NOTIFICATION-TYPE

A circular route was found while testing XBC CSR traffic traversability. Data field: (target XBC << 32) | (cellNum << 56)

NOTIFICATION-TYPE

Error reading ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC-XBC port had an invalid chip type connection. Data field: (expected chip type) | (actual chip type << 32)

NOTIFICATION-TYPE

ArfIsXbcRouteTraversable was called on a back-to-back system which is an improper use of the function. Data field: unused

NOTIFICATION-TYPE

In ArfIsXbcRouteTraversable, an XBC-XBC link was found to have fatal errors. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Unable to read the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Error reading an XBC ROUTE_TABLE CSR. Data field: route index | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Error reading ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC port was found with an unexpected neighbor chip. Data field: expected chip type | (actual chip type << 32)

NOTIFICATION-TYPE

A cell/port pair was not found in the expected graph data. Data field: (cellNum << 32) | CC portNum

NOTIFICATION-TYPE

Arches Fabric Traversability code unexpectedly found the local cell link not connected. Data field: linkState (0 = connected, 1 = link pending, 2 = not connected, -1 = error)

NOTIFICATION-TYPE

Error reading the ROUTEx CSR on the XBC. Data field: route index | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Unable to read the ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

An XBC port has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32)

NOTIFICATION-TYPE

A Cell-Cell link has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32)

NOTIFICATION-TYPE

The cell/port pair does not exist in the Arches Fabric expected graph data. Data field: CC port | (cellNum << 32)

NOTIFICATION-TYPE

A Cell-Cell link is connected to an unexpected neighbor port. Data field: expected neighbor port | (actual neighbor port << 32)

NOTIFICATION-TYPE

A Cell-Cell link is connected to an unexpected cell. Data field: expected neighbor ID | (actual neighbor ID << 16) | (target cell << 32) | (local cell << 48)

NOTIFICATION-TYPE

An EFI Driver may be corrupt.

NOTIFICATION-TYPE

VM_FindAllRoutes returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (source cell << 32) | (target cell << 48)

NOTIFICATION-TYPE

In SetupNCTable, a write to the GLOBAL_LINK_SEL_NONCOH CSR failed. Data field: (data written to CSR) | (actual CSR data read << 32)

NOTIFICATION-TYPE

SetupNCTable failed in ArfPhase3. Data field: cell set passed in to SetupNCTable

NOTIFICATION-TYPE

A failure occurred while prepping a back-to-back system for post-rendezvous Arches Fabric setup. Data field: return value from Phase4BackToBackPrep

NOTIFICATION-TYPE

ArfPhase4 was unable to set up the Non-Coherent link select to at least one cell in its alive/gsm sharing set. Data field: bitmap of unreachable cells

NOTIFICATION-TYPE

Unable to set the Non-Coherent route. Data field: (sourceCell << 32) | (cell set passed in to SetupNCTable)

NOTIFICATION-TYPE

Unable to setup the Coherent route table for a cell in our partition. Data field: (sourceCell << 32) | (cell set passed in to SetupCohTable)

NOTIFICATION-TYPE

Error writing the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (route set to disable) | (xbcNum << 32) | (xbc port << 48)

NOTIFICATION-TYPE

The Arches Fabric vertex module returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (sourceCell << 32) | (dest cell << 48)

NOTIFICATION-TYPE

A write to a Skyline Global LINK_SEL_COHx CSR failed. Data field: cell number of the Skyline that failed, bits [7:0]. Other bits unused

NOTIFICATION-TYPE

Unable to write the XBC port scratch CSR with the routing state. Data field: (routing state) | (xbcNum << 32) | (portNum << 48)

NOTIFICATION-TYPE

Couldn't get the configured set during Fabric Init

NOTIFICATION-TYPE

Error while running the Arches Fabric API part of Fabric Init.

NOTIFICATION-TYPE

Failure while running the Fabric API part of Fabric Init.

NOTIFICATION-TYPE

An error was encountered while running the Fabric API to optimize the fabric.

NOTIFICATION-TYPE

Input power to the specified UPS has failed.

NOTIFICATION-TYPE

Input power to the specified UPS has been restored.

NOTIFICATION-TYPE

The system is being powered down as UPS power is exhausted.

NOTIFICATION-TYPE

During SAL Machine Check handling, SAL fail to round up all the processor entering SAL Machine check handler.

NOTIFICATION-TYPE

Sal failed to clear the CEC logs during Machine check handling. The data field return an ASCII name of the CEC that failed to clear.

NOTIFICATION-TYPE

An error occurred while getting the XBC semaphore.

NOTIFICATION-TYPE

An error occurred while releasing the XBC Global Semaphore.

NOTIFICATION-TYPE

An error occurred while checking the owner of the XBC Global Semaphore.

NOTIFICATION-TYPE

An error occurred while forming the XBC semaphore address. Data Field: (xbc << 32) | (cell << 56)

NOTIFICATION-TYPE

Error reading the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failure to get the XBC Global Semaphore address. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failed to write the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failed to read the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failed to get the address of the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failed to write the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Failed to release the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)

NOTIFICATION-TYPE

Fabric phases have been executed in an invalid order

NOTIFICATION-TYPE

Fabric phases have been executed in an invalid order. Data field indicates the expected phase.

NOTIFICATION-TYPE

Failed to get an address when opening XBC to XBC links. Data field is return value from GetAlbAddrBlk function. Internal debug only.

NOTIFICATION-TYPE

Failed to open a fabric link. Data field: [31:0] - error status from OpenFabricLink [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error when writing the XBC return route. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error enabling the XBC return route. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

failed to disperse the routes across links. Data field: [31:0] - error status from GetDispersedOutboundPort [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error setting up XBC-XBC link for routing across it. Data field: [31:0] - error status from SetupXbcToXbcLinks [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error while routing the remote side of a route. Data field: [31:0] - error status from RouteRemoteXbcPort [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number:

NOTIFICATION-TYPE

Error getting address while routing the remote XBC. Data field: [31:0] - error status from GetAlbAddrBlk [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error getting the neighbor info. Data field: [31:0] - error status from AlbGetNeighborInfo [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error finding the shortest route. Most likely a firmware error or data corruption. Data field: [31:0] - error status from VM_FindShortestRoute [39:32] - Destination XBC ID [59:52] - Destination Cell number

NOTIFICATION-TYPE

error writing the remote XBC routing register. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number

NOTIFICATION-TYPE

error enabling the routes on the remote XBC. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number

NOTIFICATION-TYPE

Error writing the routing register on the local XBC. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error writing the local XBC routing registers to reach a remote cell. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

Error enabling the local XBC routes. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number

NOTIFICATION-TYPE

SynchGraphs() failed during Arches Fabric Phase 4. Data field: return value from SynchGraphs()

NOTIFICATION-TYPE

VM_DeleteVertex() failed in SynchGraphs(). Data field: (vertex id << 32) | (vertex type << 56) | (return value from VM_DeleteVertex())

NOTIFICATION-TYPE

VM_DeleteEdge() failed in the Arches Fabric function SynchGraphs(). Data field:(vertex id1 << 32) | (vertex port1 << 48) | (vertex type1 << 56) | (vertex id2 << 0) | (vertex port2 << 16) | (vertex type2 << 24)

NOTIFICATION-TYPE

Unexpected error when calling an Arches Fabric vertex module function. Data field: return value from vertex module function

NOTIFICATION-TYPE

Unexpected return from an Arches Fabric vertex module function while copying a cell's graph. Data field: return value from vertex module function

NOTIFICATION-TYPE

The checksum update for the PDT has failed.

NOTIFICATION-TYPE

The checksum in the memory area of NVM is bad. Memory NVM will be cleared.

NOTIFICATION-TYPE

Checksum calculation failed.

NOTIFICATION-TYPE

The BMC copy and SAL copy of the token specified in the data field has been initialized from the default value for the token due to an IPMI error and SAL NVM error.

NOTIFICATION-TYPE

Detected incompatibility between the cell board and the I/O backplane and/or I/O backplane cables.

NOTIFICATION-TYPE

The fPar identified by the event detail will be unusable. Other events may preceded this event which will help to diagnose the failure. A possible cause is that the system exhausted unused NVRAM.

NOTIFICATION-TYPE

Firmware is out of NVRAM and cannot built the ILM memory slice device map

NOTIFICATION-TYPE

The NVRAM for the CPU map is corrupt and cannot be trusted. It appears that there are more CPUs in the map than the size of the map can hold.

NOTIFICATION-TYPE

The NVRAM for the IO device ownership map is corrupt and cannot be trusted. It appears that there are more IO devices in the map than the size of the map can hold.

NOTIFICATION-TYPE

The NVRAM for the cell local memory map is corrupt and cannot be trusted. It appears that there are more memory slices in the map than the size of the map can hold.

NOTIFICATION-TYPE

An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for a CPU device in the partition. Either of these conditions is fatal.

NOTIFICATION-TYPE

An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for an IO device in the partition. Either of these conditions is fatal.

NOTIFICATION-TYPE

An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for a CLM device in the partition. Either of these conditions is fatal.

NOTIFICATION-TYPE

Firmware has run out of NVRAM and cannot create the needed variable(s)

NOTIFICATION-TYPE

The call to the IOC firmware component method 'LbaReconfig' failed, probably a low-level hardware error. The fPar BSP is identified in bits 63..32 of the event detail, the fPar owning this CPU and LBA is identified in bits 31..16 and the number of the Rope is identified in bits 15..0.

NOTIFICATION-TYPE

The CPU modules have been installed in an illegal configuration on the cell board.

NOTIFICATION-TYPE

An invalid CPU terminator card is installed on the cell board. The data field indicates the physical location of the offending socket.

NOTIFICATION-TYPE

Invocation of the soft reset code from an interrupt or similar vector, or improper locking/releasing of semaphores.

NOTIFICATION-TYPE

Data field is count of cpus held by the sm4 which issues the event (and is trying to reset itself). Indicates invocation of the SoftResetCpu code from an interrupt or similar vector where the processor was modifying critical resources, or improper locking/releasing of semaphores.

NOTIFICATION-TYPE

A reset of an fPar discovered that an fPar failed to release critical resources within a reasonable time.

NOTIFICATION-TYPE

Significant numbers of corrected memory errors have been detected on the memory subsystem

NOTIFICATION-TYPE

Over-temperature condition detected on a processor

NOTIFICATION-TYPE

Cache errors detected on a processor

NOTIFICATION-TYPE

Corrected errors detected in the cache portion of the memory for a processor module

NOTIFICATION-TYPE

Corrected errors detected on the system bus for a processor module

NOTIFICATION-TYPE

Corrected errors detected on the processor bus for a processor module

NOTIFICATION-TYPE

Corrected errors detected in the tag portion of the memory for a processor module

NOTIFICATION-TYPE

fPars-mode EFI variable is set to enable fPars operation but no fPars are actually enabled to boot. So the server boots in hard partition mode.

NOTIFICATION-TYPE

An fPar was directed to reset using the ESIT DirectedfParResetAndMigrate() service but the target (recipient) fPar of the resources is in a state that cannot receive ownership of these resources.

NOTIFICATION-TYPE

Firmware error setting the NVRAM value of preferred-bsp for the vPars monitor. The partition will boot using the PD monarch, but the value of preferred-bsp may not match this CPU.

NOTIFICATION-TYPE

Unable to write to an XBC port ROUTE_TABLE_ENABLE_MASK CSR in Arches Fabric Phase3. Data field: (XBC port << 48) | (XBC ID < 32) | (route)

NOTIFICATION-TYPE

An unrecoverable processor interrupt occurred. IPF firmware owned the processor interrupt vector table (IVT) at the time of the interrupt.

NOTIFICATION-TYPE

SBA call to LBA SetDeviceMask method fails.

NOTIFICATION-TYPE

LBA slot device scan error

NOTIFICATION-TYPE

There is none (or inadequate) memory slice resource assigned to the fPar so it cannot boot its instance. The fPar will be disabled (enter a spinloop) because it cannot boot, or if in vPars mode will return control to the monitor.

NOTIFICATION-TYPE

Couldn't collect vertex information during Fabric Info call. Data Field: return status

NOTIFICATION-TYPE

Couldn't collect the vertices during the Fabric Info call. Data Field: number of vertices returned

NOTIFICATION-TYPE

Couldn't find all the edges during a procedure call. Data Field: return status

NOTIFICATION-TYPE

Couldn't find an appropriate number of edges during a procedure call. Data Field: the number of edges found

NOTIFICATION-TYPE

Too many edges were encountered during a procedure call. Data Field: link count

NOTIFICATION-TYPE

Failed to get an address during a procedure call. Data Field: return status

NOTIFICATION-TYPE

An unexpected state was encountered during a procedure call. Data Field: state returned

NOTIFICATION-TYPE

Unable to get the link health state during a procedure call. Data Field: (cell num << 56) | (port << 44) | (xbc << 32)

NOTIFICATION-TYPE

The fabric data failed a CRC check. Data Field: (xbc port << 44 ) | (xbc << 32) | return status)

NOTIFICATION-TYPE

VM_CollectVertices failed unexpectedly. Could possibly be a data corruption problem. Data field: (cell number << 56) | (return value from VM_CollectVertices)

NOTIFICATION-TYPE

Unable to generate an ALB address in Arches Fabric ArfSetDefaultCSRs() function. Data field:(cell number << 56) | (port number << 48) | (xbc ID < 32) | (return value)

NOTIFICATION-TYPE

SetDefaultCSRs function failed unexpectedly. Arches Fabric was unable to set XBC CSRs to default values. Data field: return value from SetDefaultCSRs

NOTIFICATION-TYPE

A problem was encountered while routing which prevented an appropriate route from being chosen. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status

NOTIFICATION-TYPE

An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status

NOTIFICATION-TYPE

An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status

NOTIFICATION-TYPE

An invalid port number was returned when selecting a route for the XBC-CC link. Data Field: (destination cell 56) | (xbc port 44) | (xbc # 32) | port selected

NOTIFICATION-TYPE

An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | switch fabric

NOTIFICATION-TYPE

The second flash part is not programmed with a valid image

NOTIFICATION-TYPE

System backplane power has reported a 1.2v LDO fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 2.5v LDO fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 3.3v house keeping power fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 12v power fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 3.3v power fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 1.5v power fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

System backplane power has reported a 2.5v power fault. The data field contains the physical location of the fault.

NOTIFICATION-TYPE

One or more power rails is providing insufficient power to the backplane.

NOTIFICATION-TYPE

Clock fault for clocks supplied from the Redundant Clock Source (RCS) board to the system backplane. RCS board is no longer providing clocks to the backplane. The data field contains the physical location of the RCS.

NOTIFICATION-TYPE

Clock fault for clocks supplied from the Hot Swap Oscillator (HSO) board to the system backplane. HSO has reported a fault or has been removed. The data field contains the physical location of the HSO.

NOTIFICATION-TYPE

The operational clock frequencies do not match between the Redundant Clock Source (RCS) and the Hot Swap Oscillator (HSO). The data field contains the physical location of the HSO.

NOTIFICATION-TYPE

The clock margin of the system backplane failed.

NOTIFICATION-TYPE

System backplane Hot Swap Oscillator (HSO) boards are NOT redundant.

NOTIFICATION-TYPE

System backplane Hot Swap Oscillator (HSO) boards are insufficient.

NOTIFICATION-TYPE

Failure reading Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device.

NOTIFICATION-TYPE

Failure writing Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device

NOTIFICATION-TYPE

Failure reading the Reset and Power Monitors (RPM) EEPROM. Data field contains the physical location of the device.

NOTIFICATION-TYPE

Failure writing the Reset and Power Monitors (RPM) EEPROM. Datafield contains the physical location of the device

NOTIFICATION-TYPE

Failure reading the Onboard System Programmers (OSP) EEPROM. Datafield contains the physical location of the device

NOTIFICATION-TYPE

Failure writing the Onboard System Programmers (OSP) EEPROM. Datafield contains physical location of the device

NOTIFICATION-TYPE

Serial Bit Stream (SBS) fault on startup. An SBS fault results in the MOAB's not being configured correctly.

NOTIFICATION-TYPE

Failure reading IO backplane LPM. Datafield contains the physical location of the device.

NOTIFICATION-TYPE

Failure writing IO backplane LPM. Datafield contains physical location of device.

NOTIFICATION-TYPE

The system software violated one of the 'well-behavedness' rules of soft partitions and tried to call a firmware procedure within the firmware instance of a sibling. This is an access violation and firmware rejects the call

NOTIFICATION-TYPE

AlbInitPrep was unable to read the ALREC_CONFIG CSR to determine whether the link is up or not. Data field: unused

NOTIFICATION-TYPE

The fPar whose ID is identified in the event detail is disabled from booting because it has no bootable, healthy CPU. It may not own any CPU or the CPUs it owns are Unhealthy (or deconfigured)

NOTIFICATION-TYPE

Non-critical event announces that an fPar is enabled to boot but has inadequate memory resources to instantiate the firmware for the fPar. The configuration is modified to disable but not delete this fPar.

NOTIFICATION-TYPE

The fPar has been enabled to boot, and contains at least one CPU and adequate memory but has not been given any IO resources. The soft partition (fPar) may therefore only boot as far as the EFI shell. It must be reconfigured and reset before it may boot an operating system.

NOTIFICATION-TYPE

All CPUs were scheduled to be deconfigured

NOTIFICATION-TYPE

All CPUs have been auto reconfigured

NOTIFICATION-TYPE

IO Backplane 3.3V power fault

NOTIFICATION-TYPE

IO Backplane 5.0V power fault

NOTIFICATION-TYPE

IO Backplane -12V power fault

NOTIFICATION-TYPE

IO Backplane +12V power fault

NOTIFICATION-TYPE

IO Backplane 1.5V temperature fault

NOTIFICATION-TYPE

IO Backplane 3.3V temperature fault

NOTIFICATION-TYPE

IO Backplane -12.0V temperature fault

NOTIFICATION-TYPE

IO Backplane +12.0V temperature fault

NOTIFICATION-TYPE

The local cell was unable to clear the link_off bit on at least one CC-CC link. Data field: return value of Phase3BackToBackPrep()

NOTIFICATION-TYPE

ArfOLAPreRendez() was unable to reach the added cell. Data field: bitmap of unreachable cells

NOTIFICATION-TYPE

An unexpected error occurred in SetupNCTable(). Data field: return value from SetupNCTable()

NOTIFICATION-TYPE

Phase4BackToBackPrep() unexpectedly failed. Data field: return value of Phase4BackToBackPrep()

NOTIFICATION-TYPE

Data field: (master cell number << 56) | (bitmap of cells to synch)

NOTIFICATION-TYPE

Data field: bitmap of unreachable cells.

NOTIFICATION-TYPE

Data field: return value from SetupNCTable() or SetupCohTable()

NOTIFICATION-TYPE

Data field: (local cell number << 56) | (bitmap of routes to enable)

NOTIFICATION-TYPE

Data field: (bitmap of cells << 32) | (bitmap of routes to disable)

NOTIFICATION-TYPE

Data field: (bitmap of source cells << 32) | (bitmap of routes to disable)

NOTIFICATION-TYPE

Memory allocation failed. The data is the size of the memory block which could not be allocated.

NOTIFICATION-TYPE

Memory locking failed. The data is the size of the memory block which could not be locked.

NOTIFICATION-TYPE

The minimum number of processors required is more than the number available. The data is the number of available processors.

NOTIFICATION-TYPE

The guest operating system performed an operation which could not be handled by the virtual machine. The virtual machine could not continue running the guest so it stopped.

NOTIFICATION-TYPE

Kernel driver failed to lock memory

NOTIFICATION-TYPE

The code which initializes the MMIO/IOP map found that the table already contained information.

NOTIFICATION-TYPE

An attempt was made to add a PCI bus with a number greater than the maximum allowed.

NOTIFICATION-TYPE

The configured CPU generation is not supported

NOTIFICATION-TYPE

An ISA UART was created without a data structure. A PCI UART structure exists

NOTIFICATION-TYPE

A TCGETS or TCSETS IOCTL failed. The errno status will be in a subsequent event.

NOTIFICATION-TYPE

A stat call on the PMAN failed. The next event contains the failure errno.

NOTIFICATION-TYPE

The virtual machine driver could not be opened

NOTIFICATION-TYPE

The virtual machine driver could not create a virtual machine

NOTIFICATION-TYPE

Could not create a file system node for communication between the vmm driver and the virtual machine. The next event contains the error from the Unix system call.

NOTIFICATION-TYPE

The vm device was created but cannot be opened

NOTIFICATION-TYPE

The virtual machine driver has not been loaded

NOTIFICATION-TYPE

An attempt to create a thread on the PMAN has failed. The next event contains the Unix error number.

NOTIFICATION-TYPE

VM Driver was unable to communicate with virtual machine

NOTIFICATION-TYPE

The configuration file could not be read

NOTIFICATION-TYPE

Memory allocation for a firmware table has failed. The data contains the name of the firmware table.

NOTIFICATION-TYPE

Driver was unable to build map tables

NOTIFICATION-TYPE

Reboot failed. The virtual machine will exit.

NOTIFICATION-TYPE

Data field: (cell set << 32) | (return value from SetupInitialCohTables())

NOTIFICATION-TYPE

Stable store read or write to flash failed.

NOTIFICATION-TYPE

Error reading or writing the stable store NVM area

NOTIFICATION-TYPE

SFW has detected an illegal memory config using 4GB DIMMs. The system will be halted

NOTIFICATION-TYPE

SFW component NVM space is not big enough to store all it data. Check the ASCII data field to determine which component caused the error.

NOTIFICATION-TYPE

SFW component does not allocate enough SCR ram space to store it data.

NOTIFICATION-TYPE

Data field: cell set [63:32], return value [31:0]

NOTIFICATION-TYPE

Data field: cell ID [63:56], port num [55:44], XBC ID [43:32]

NOTIFICATION-TYPE

Data field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0]

NOTIFICATION-TYPE

The OS being booted is not supported in a partition containing a mix of processor stepping revisions.

NOTIFICATION-TYPE

Data field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0]

NOTIFICATION-TYPE

Data field: cell num [63:56] | link sel coh CSR (0 or 1) [0:0]

NOTIFICATION-TYPE

The OS suitable for booting in this mode does not support booting in the current configuration due to the existence of cpus of differing revisions.

NOTIFICATION-TYPE

System firmware experienced an error while updating the link sel value. Data field indicates return status

NOTIFICATION-TYPE

Fabric was unable to generate a Skyline CSR address Data field: cell number [63:56] and return value from address function [31:0]

NOTIFICATION-TYPE

Firmware was unable to generate a Skyline CSR address. Data field: cell number [63:56] | return value [31:0]

NOTIFICATION-TYPE

Target CPU receives wakeup interrupt to join the OS but the OS_BOOT_RENDEZ entry point is invalid or none-existent

NOTIFICATION-TYPE

The entry point for OS_BOOT_RENDEZ exists, but fails the checksum test performed by firmware

NOTIFICATION-TYPE

The System Firmware call to PAL_COPY_INFO failed.

NOTIFICATION-TYPE

The System Firmware call to PAL_COPY_PAL failed.

NOTIFICATION-TYPE

The System Firmware call to PAL_CACHE_FLUSH failed.

NOTIFICATION-TYPE

Cell on line add/delete is not initialized and cannot be used.

NOTIFICATION-TYPE

In FPARs mode, cell on line add/delete depends on functionality in the FPARs component. This is either broken or missing.

NOTIFICATION-TYPE

Cell on line add/delete in FPARs mode failed to get the FPARs semaphore.

NOTIFICATION-TYPE

More than one processor from an FPAR called into cell on line add/delete

NOTIFICATION-TYPE

All FPARs processors failed to rendezvous during a cell on line add/delete op

NOTIFICATION-TYPE

Unable to setup Skyline LINK_SEL_COHx CSRs on the running partition to the newly added cell. Data field: cell set [63:32] | return val [31:0]

NOTIFICATION-TYPE

This indicates an MCA happening before a previous MCA was not completely handled.

NOTIFICATION-TYPE

This indicates an MCA event happening before a previous INIT event was not completely processed.

NOTIFICATION-TYPE

Firmware was unable to find a bad edge in an untraversable route. Data Field: (destCell << 56 | port num < 44 | xbc num << 32 | return status)

NOTIFICATION-TYPE

Some entity that is not known to the firmware, is drawing power from the bus bars.

NOTIFICATION-TYPE

Rebooting the partition to nPars because a soft partition could not be booted.

NOTIFICATION-TYPE

Firmware was unable to find a replacement route for the broken link. Data field contains: port << 44, chip id << 32, and number of attempts to find an alternate route

NOTIFICATION-TYPE

Data field details the cell that failed to set its bit

NOTIFICATION-TYPE

Indicates that an uncorrectable ECC error has been encountered, and gives the physical location of the DIMM that had the error.

NOTIFICATION-TYPE

System firmware experienced an error while retrieving the expected neighbor fabric chip for distributing traffic over crossbarl inks. Data Field: (xbc port # << 44) | (xbc # << 32) | return status

NOTIFICATION-TYPE

Could not read crossbar neighbor information during routing. Data Field: (xbc port << 44) | (xbc << 32) | error status

NOTIFICATION-TYPE

Could not establish route for local crossbar during route around routing. Data Field: (xbc port << 44) | (xbc << 32) | error status

NOTIFICATION-TYPE

An invalid TPM has been detected in the system and is being use. Security might be compromised. Data field unused.

NOTIFICATION-TYPE

Invalid or unsupported TPM detected in the system. TPM is disabled. Data filed unused

NOTIFICATION-TYPE

Firmware cannot initialize the TPM. TPM related security feature are disabled Data field unused

NOTIFICATION-TYPE

A CPU module's temperature has exceed the high temperature threshold or a CPU power module fault has occurred. As a result of this event, the CPU has been inhibited. The Cell must be powered off then on using the MP's PE command before the CPU module will be powered again.

NOTIFICATION-TYPE

An error occurred while writing to stable store flash. Data field is unused.

NOTIFICATION-TYPE

PCI interlock has been opened with PCI slot power on. The datafield can be decoded as follows (where byte 0 is the rightmost byte): byte offset 2:PCI slot number byte offset 5: IO Chassis number byte offset 6: IO Bay number byte offset 7: Cabinet number

NOTIFICATION-TYPE

The specified low dropout regulator on the IO backplane is reporting a fault. The specified power rail is reporting a fault. The number in the slot field of the physical location is the rail number that caused the fault. Rails are: 4 = LDO 2.5v for Esca 0, 5 = LDO 2.5v for Esca 1, 1.5v, 7 = Other backplane 2.5v, 8 = Other backplane 1.2v

NOTIFICATION-TYPE

The specified low dropout regulator on the main backplane is reporting a fault. The number in the slot field of the physical location is the rail number that caused the fault. Rails are: 0 = SysBP xb0 1.5v, 1 = SysBp xb1 1.5v, 2 = SysBp switched 3.3v, 3 = SysBp LDO xb0 2.5v, 4 = SysBp xb1 LDO 2.5v, 5 = SysBp LDO 1.5v br0, 6 = SysBp LDO 1.5v br1

NOTIFICATION-TYPE

The hot swap controller for the specified core IO is reporting fault.

NOTIFICATION-TYPE

An error occurred while retrieving the crossbar chip number. Data Field: cell number << 56 | port number << 44 | return status

NOTIFICATION-TYPE

For most workloads, the system performance may be degraded if CLM mode is not enabled for all of the cells in a partition. Windows Server 2003 contains additional support to optimize for CLM systems, increasing the performance compared to an interleaved configuration.

NOTIFICATION-TYPE

Corrected memory errors have been detected. Double DRAM chip sparing events have been invoked.

NOTIFICATION-TYPE

A error occurred in the crossbar controller and was corrected by the hardware.

NOTIFICATION-TYPE

A platform error was detected by the firmware/hardware, and corrected by using a spare channel. The error occurred between the crossbar chips on the backplane(s).

NOTIFICATION-TYPE

A platform error was detected by the firmware/hardware, and corrected by using a spare channel. The error occurred between the cell controller and the IO controller.

NOTIFICATION-TYPE

Multiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the backplane.

NOTIFICATION-TYPE

Multiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the crossbar chips on the backplane(s).

NOTIFICATION-TYPE

Multiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the IO controller.

NOTIFICATION-TYPE

The server identification information does not match the cabinet type. The server will not power on until this condition is resolved.

NOTIFICATION-TYPE

Duplicate DIMM serial numbers have been detected. Data field gives physical location of DIMM. Check for other events specifying other DIMMs with same serial number.

NOTIFICATION-TYPE

The MP has lost communications with the UPS via SNMP over the LAN

NOTIFICATION-TYPE

The MP lan communications with the UPS have been restored.

NOTIFICATION-TYPE

An unrecoverable processor interrupt occurred while in IPF firmware. The data value is the processor IFA.

NOTIFICATION-TYPE

An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor ISR.

NOTIFICATION-TYPE

System firmware has detected and corrected memory errors. Double chip sparing has been invoked to help mitigate this condition.

NOTIFICATION-TYPE

External clock cable has been removed from the CPU cabinet. The data field contains the physical location of the cabinet.

NOTIFICATION-TYPE

System Fabric encountered a link error after opening up the fabric link

NOTIFICATION-TYPE

Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32) | 1

NOTIFICATION-TYPE

System firmware encountered fabric problems. Data Field: (crossbar port << 44) | (crossbar << 32)

NOTIFICATION-TYPE

Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32)

NOTIFICATION-TYPE

A PCI error occurred, but the OS recovered.

NOTIFICATION-TYPE

A PCI error occurred, but the operating system recovered.

NOTIFICATION-TYPE

A PCI error occurred, but the operating system recovered

NOTIFICATION-TYPE

The request to power on, either via MP user interface, power button, or other, was denied by the Onboard Administrator.

NOTIFICATION-TYPE

The blade has been forced to power-on, either via the MP user interface or the power button. The blade did not negotiate with the Onboard Administrator to insure that there was sufficient power for this action.

NOTIFICATION-TYPE

The MP has repeatedly tried to communicate with the Onboard Administrator and has not received any response

NOTIFICATION-TYPE

This is an internal SW error

NOTIFICATION-TYPE

This is an internal SFW error

NOTIFICATION-TYPE

This is an internal SFW error

NOTIFICATION-TYPE

This is an internal SFW error

NOTIFICATION-TYPE

There are miscompares in the complex profiles between cells in a partition. Data field is unused, earlier events will give more detail.

NOTIFICATION-TYPE

An I/O device is missing from the Core I/O. Internal peripherals may be not accessible.

NOTIFICATION-TYPE

An fPar's GPE_EN bits are not set up to handle receiving a CPU migrate. This event is emitted 2 times, the Data field is different each time. 1. Data field: Address of GPE block 2. Data field: bits 31:0 Virtual GPE_EN register (lower byte) bits 63:32 Enable bits needed for successful migrate

NOTIFICATION-TYPE

FSHWA was unable to notify the new owner of a CPU migrate. This event is emitted 2 times: 1. Data field: IOSAPIC Address 2. Data field: Virtual IOSAPIC SCI redir

NOTIFICATION-TYPE

The operating system set the watchdog timer to time out if it was not reset within a specified time. It was not reset and has timed out. The management processor will now take the action specified when the timer was set.

NOTIFICATION-TYPE

An OS is shutting down due to an MCA (Machine Check Abort) or INIT.

NOTIFICATION-TYPE

An OS is shutting down due to a panic.

NOTIFICATION-TYPE

Following an in-the-box system type upgrade, or after a UGUY board was replaced, the CLU FW may not have been updated to an appropriate revision for the system type.

NOTIFICATION-TYPE

Diagnostics running under the OS have detected a problem with the identified hardware.

NOTIFICATION-TYPE

The processor temperature has exceeded normal limits. HP's Enhanced Thermal Management (ETM) feature has been employed to cool the processor. If the temperature problem persists, this will have an adverse impact on the performance of this processor.

NOTIFICATION-TYPE

An error occurred while checking the fabricless boot state

NOTIFICATION-TYPE

System firmware was unable to clear the link error masks

NOTIFICATION-TYPE

System firmware could not determine a link's address

NOTIFICATION-TYPE

System firmware was unable to turn a bad link off

NOTIFICATION-TYPE

The Wiindows watchdog timer has expired. The nPartition will either be reset or powered off. The data field contains the following information: byte 2 - cell slot number of the cell that generated the timeout event byte 3 - nPartition number (SX2000 superdome only) byte 4 - timeout action (0 = Reset, 1 = Power off) byte 7 - cabinet number

NOTIFICATION-TYPE

An MP Bus communications device is reporting a hardware revision that is known to cause MP Bus communications failures. The value in the data field indicates the physical location of the PM, CLU, or PDHC device that is failing.

NOTIFICATION-TYPE

Main power at the PCI slot located on the IO Chassis has faulted.

NOTIFICATION-TYPE

A failure was encountered while running the Fabric API to optimize the fabric.

NOTIFICATION-TYPE

A critical failure occurred during a cell online add or delete call.

NOTIFICATION-TYPE

A cell being added is not compatible with the partition.

NOTIFICATION-TYPE

The Firmware revision of the cell being added is different from the nPar.

NOTIFICATION-TYPE

The OpenVMS system has failed and will reboot

NOTIFICATION-TYPE

Bad cell board (on cellular system), or bad processor board (on non-cellular system).

NOTIFICATION-TYPE

CPU performance degraded due to excessive errors in third level cache.

NOTIFICATION-TYPE

The alternate ROM failed to authenticate. The current (primary) ROM will continue to be used

NOTIFICATION-TYPE

The alternate ROM was successfully authenticated but the primary and alternate ROM could not be swapped. The current primary will still be used

NOTIFICATION-TYPE

PCI/PCIX/PCIe card/slot error detected during IO bus scan

NOTIFICATION-TYPE

A CC to CC link failed to train in a 2-cell system. The partition can still boot, but with less redundancy and bandwidth. Data field: Cell number [63:56] Link number [32:0]

NOTIFICATION-TYPE

An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor status register.

NOTIFICATION-TYPE

The 'e-keying error' only occurs during the power-up if the SVB must be left off due to an electronic keying problem.

NOTIFICATION-TYPE

The 'location error' only occurs during power-up if the SVB must be left off due to being installed in an improper location in the enclosure (SVBs must be installed in specific positions relative to fans or other components.

NOTIFICATION-TYPE

The 'ccoling error' occurs during the power-up if the SVB must be left off due to insufficient cooling; more fans may be needed.

NOTIFICATION-TYPE

Data field: return value from internal firmware function.

NOTIFICATION-TYPE

OA is Busy: The Powe-on request cannot be completed.

NOTIFICATION-TYPE

The IO backplane in the specified cabinet is reporting a non-redundant PCI power condition.

NOTIFICATION-TYPE

This trap is sent when a USB storage device has been attached.

NOTIFICATION-TYPE

This trap is sent when a attached USB storage device is removed.

NOTIFICATION-TYPE

The migration source could not connect to the target.

NOTIFICATION-TYPE

A migration has failed.

NOTIFICATION-TYPE

A migration was not successful. This contains the migration phase when it was terminated.

NOTIFICATION-TYPE

A virtual machine was not able to obtain memory for an I/O device.

NOTIFICATION-TYPE

HP PFM service has detected HP unsupported DIMM(s) on this partition.

NOTIFICATION-TYPE

OS run-time critical shutdown has occurred.

NOTIFICATION-TYPE

The amount of power expected to be drawn by the currently operating hardware is greater than the rating of the currently operating Bulk Power Supplies (BPS). It is very likely that partitions may be powered down with no further warning to eliminate the excess power load.

NOTIFICATION-TYPE

Bulk power supply (BPS) redundancy has been lost on one or more row(s) of power supplies in the complex. The further loss of a single BPS or an AC grid will most likely result in the shutdown of partitions using the chassis that lost redundancy.

NOTIFICATION-TYPE

AC redundancy has been lost on one or more row(s) of power supplies in the complex. The further loss of a single Bulk Power Supply (BPS) or the other AC grid will most likely result in the shutdown of partitions using the chassis that have lost redundancy.

NOTIFICATION-TYPE

The fans that cool a region of the system are not redundant. If an additional fan fails in or is removed from this cooling domain, the partitions on this system will be automatically shut down to prevent an over temperature condition.

NOTIFICATION-TYPE

An insufficient number of fans are working in a cooling domain to permit system operation. Running partitions will be shut down immediately to prevent system damage due to excessive heat. (If the situation is corrected immediately, it is possible to prevent system shutdown).

NOTIFICATION-TYPE

Operating system is not using all available processors for the current system.

NOTIFICATION-TYPE

A Fabric Message Processor (FMP) has unexpectedly reset. The system has recovered from the problem.