HPIPFTRAP-MIB
File:
HPIPFTRAP-MIB.mib (566082 bytes)
Imported modules
Imported symbols
Defined Values
hp |
1.3.6.1.4.1.11 |
OBJECT IDENTIFIER |
|
|
|
nm |
1.3.6.1.4.1.11.2 |
OBJECT IDENTIFIER |
|
|
|
hpnsa |
1.3.6.1.4.1.11.2.23 |
OBJECT IDENTIFIER |
|
|
|
hpIpfEvtDetailStr |
1.3.6.1.4.1.11.2.23.35.1 |
This string provides a detailed description of the Event along with variable information. |
Status: mandatory |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
|
|
hpevtBadOsInitChecksum |
5001 |
The OS has registered an OS_INIT vector, but is has not passed the checksum |
TRAP-TYPE |
|
|
|
hpevtBadOsMcaChecksum |
5002 |
The OS has registered an OS_MCA vector, but it has not passed the checksum |
TRAP-TYPE |
|
|
|
hpevtBootCellMonSelFailure |
5011 |
Monarch selection has failed. Data: 0x11 = Calibration Failure 0x22 = Select Code Failure |
TRAP-TYPE |
|
|
|
hpevtBootCpuConfigFail |
5030 |
SFW has failed initializing the CPU Struct. Data: Physical location of CPU that produced failure |
TRAP-TYPE |
|
|
|
hpevtBootCpuFailed |
5034 |
SFW has detected that a CPU has failed. Data: The Physical Location of the CPU that failed |
TRAP-TYPE |
|
|
|
hpevtBootCpuLateTestFail |
5036 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootEfiNvmFail |
5045 |
EFI NVM has failed testing. The cell or system will now halt. |
TRAP-TYPE |
|
|
|
hpevtBootExtIntNestLimitedExceeded |
5050 |
The IVT interrupting nesting depth has been exceeded. This processor will be halted. Data: Number of the offending vector. |
TRAP-TYPE |
|
|
|
hpevtBootExtIntNotServiced |
5051 |
An external interrupt has been requested and not serviced. Data: Number of the vector |
TRAP-TYPE |
|
|
|
hpevtBootExtIntTaken |
5052 |
An external interrupt has been taken. Data: Number of the vector taken. |
TRAP-TYPE |
|
|
|
hpevtBootIncompatibleSlave |
5057 |
SFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor. |
TRAP-TYPE |
|
|
|
hpevtBootLostContextInt |
5064 |
Interrupt context was lost. Data: interrupt number. |
TRAP-TYPE |
|
|
|
hpevtBootMonarchTimeout |
5067 |
SFW has determined the monarch has timed out. SFW is deconfiguring the CPU. Data: Physical Location of CPU |
TRAP-TYPE |
|
|
|
hpevtBootOutOfRangeVector |
5076 |
A interrupt vector has been requested out of the acceptable range. Data: Vector Number. |
TRAP-TYPE |
|
|
|
hpevtBootPalProcFailure |
5079 |
A PAL Proc has failed. This will halt the processor. Data: Physical Location of CPU |
TRAP-TYPE |
|
|
|
hpevtBootTrapTaken |
5102 |
A trap has been taken. Data: Number of the vector taken. |
TRAP-TYPE |
|
|
|
hpevtBootUnclearedInt |
5103 |
At least one interrupt was not cleared. Data: The highest pending interrupt number |
TRAP-TYPE |
|
|
|
hpevtBootUnexpectedExtIntPostRedirTable |
5104 |
An unexpected external interrupt has occurred. Data: External Interrupt Number |
TRAP-TYPE |
|
|
|
hpevtBootUnexpectedMca |
5106 |
An unexpected MCA has occurred before MCAs are unmasked. Data: Local CPU Number. |
TRAP-TYPE |
|
|
|
hpevtBootUnexpectedTrapPostRedirTable |
5107 |
An unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number |
TRAP-TYPE |
|
|
|
hpevtInitInitiated |
5121 |
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 |
TRAP-TYPE |
|
|
|
hpevtIoCheckLbaMissingErr |
5123 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoCheckNumSlotsErr |
5124 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoCheckRopeWidthErr |
5125 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoCheckXtraLbaFoundErr |
5127 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoDllError |
5130 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoHotPlugCtrlFailed |
5131 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoInvalidRopeBundle |
5132 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoLbaClearErrFailed |
5133 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoLbaResetError |
5136 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoNotEnoughPowerError |
5137 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoPciMappingFailed |
5138 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoPciMappingTooBig |
5139 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoPciUnmappingFailed |
5140 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoPcixcapSampleError |
5141 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoPmNotRespondingError |
5142 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoRopeResetError |
5143 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoSbaClearErrFailed |
5144 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoSlotPowerDefaultError |
5145 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoSlotPowerOnError |
5146 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoSlotStandbyPowerError |
5147 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoUnknownPcixcapVal |
5148 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoUnsupRopeFreq |
5149 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoUnsupportedLba |
5150 |
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. |
TRAP-TYPE |
|
|
|
hpevtMdtLmmioEntryNotFound |
5156 |
There has been a problem building the Memory Data Table (MDT). |
TRAP-TYPE |
|
|
|
hpevtMdtPageZeroBad |
5157 |
Memory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt. |
TRAP-TYPE |
|
|
|
hpevtMemBibRegFailure |
5160 |
Indicates that the chipset register test has failed. The data field contains the physical address of the failing register. |
TRAP-TYPE |
|
|
|
hpevtMemCacheLine0WrRdFailed |
5161 |
After FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written. |
TRAP-TYPE |
|
|
|
hpevtMemDimmLoadOrderErr |
5171 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemDimmSpdChecksum |
5172 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemDimmTypeIncompatible |
5174 |
A DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform. |
TRAP-TYPE |
|
|
|
hpevtMemDimmTypeMismatch |
5175 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemDmtEntryNotFound |
5179 |
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.) |
TRAP-TYPE |
|
|
|
hpevtMemEccMbeDataTstFailed |
5180 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemEccMbeSignalTstFailed |
5181 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemEccSbeDataTstFailed |
5182 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemEccSbeEccTstFailed |
5183 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemEnoughMemFailed |
5185 |
Memory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest. |
TRAP-TYPE |
|
|
|
hpevtMemErrAddrNotInMbat |
5186 |
Memory FW could not figure out which rank maps to the physical address specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtMemErrClearFail |
5187 |
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC. |
TRAP-TYPE |
|
|
|
hpevtMemErrLogFailedToClear |
5189 |
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC. |
TRAP-TYPE |
|
|
|
hpevtMemErrorRegClearFailure |
5190 |
The Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear. |
TRAP-TYPE |
|
|
|
hpevtMemExtFatalLoadOrdErr |
5191 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemMainMemFailed |
5202 |
FW was unable to create a memory configuration with no errors in low memory to hand off to EFI. |
TRAP-TYPE |
|
|
|
hpevtMemMbeInRank |
5204 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemMcRegFailure |
5205 |
The chipset's memory controller failed the register test. The data field contains the address of the register that failed selftest. |
TRAP-TYPE |
|
|
|
hpevtMemNoMemFound |
5209 |
FW could not continue because there are no valid memory ranks loaded. |
TRAP-TYPE |
|
|
|
hpevtMemPdtDisabledHalt |
5211 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemPdtDisabledWarning |
5212 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemPdtTableFull |
5216 |
An attempt was made to add an entry to a full PDT. The entry is not added, and this event is sent. |
TRAP-TYPE |
|
|
|
hpevtMemRankEntryNotFound |
5219 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemTestFwdProgBitsInvalid |
5238 |
The forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field. |
TRAP-TYPE |
|
|
|
hpevtMemTestStatusBitsInvalid |
5244 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemUnexpectedMca |
5248 |
Memory rank shadowing has been selected but is not supported by the revision of the memory controller. |
TRAP-TYPE |
|
|
|
hpevtMemWarnDistributionCheckBypass |
5250 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemWarnLoadingOrderBypass |
5252 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemWarnLoopOnDestTest |
5253 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemWarnSetCheckBypass |
5255 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemWarnSpdBypass |
5256 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemWarnUsingAltConfig |
5257 |
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. |
TRAP-TYPE |
|
|
|
hpevtUndefinedSmcInterleaveErr |
5278 |
Indicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call. |
TRAP-TYPE |
|
|
|
hpevtFwInstalledCpuDegraded |
5335 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdRendezTreeError |
5354 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdCellConfigError |
5359 |
The currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with. |
TRAP-TYPE |
|
|
|
hpevtPdRemoteCsrReadError |
5360 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdCellLateForRendez |
5361 |
The currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with. |
TRAP-TYPE |
|
|
|
hpevtPdIncompatibleCpuTypes |
5365 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdCellLateLocalRendezSet |
5366 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellNotInGlobalSet |
5376 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricReadError |
5405 |
An error occurred reading a CSR. The CSR address is displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtXbcSlicesHwVersionDiffer |
5407 |
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 |
TRAP-TYPE |
|
|
|
hpevtXbcSlicesInDiffLocation |
5408 |
Crossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data. |
TRAP-TYPE |
|
|
|
hpevtDeadSram |
5416 |
SRAM cannot be accessed on the cell board. Execution cannot continue. |
TRAP-TYPE |
|
|
|
hpevtDeadDillon |
5417 |
The PDH Arbiter component/chip cannot be located or used. |
TRAP-TYPE |
|
|
|
hpevtDeadPdhHw |
5418 |
A required piece of PDH bus hardware cannot be contacted. |
TRAP-TYPE |
|
|
|
hpevtIoPciBusMixedSpeeds |
5419 |
The physical location of the PCI controller with mixed speeds is displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtIoPciBusDepthExceeded |
5420 |
During walking of the IO busses, the maximum depth was exceeded. This is a hardware configuration problem. The data field contains the physical location. |
TRAP-TYPE |
|
|
|
hpevtlotimeout |
5432 |
A Timeout occurred during RI initialization. The CSR is in the data field. The alert level will vary. |
TRAP-TYPE |
|
|
|
hpevtIoBuswalkSuperio |
5438 |
SuperIO has been detected in the PCI slot displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtIoLbaInitErr |
5448 |
An error was encountered when initing the rope number specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtOptsHdrCksumError |
5467 |
The Options component encountered a header checksum error. The actual data is in the data field of the chassis code. |
TRAP-TYPE |
|
|
|
hpevtOptsDataCksumError |
5468 |
The Options service data had a bad checksum. Actual data is in the data field. |
TRAP-TYPE |
|
|
|
hpevtPdMemUnintlvdMemory |
5474 |
The CellInfoList is not null and was expected to be. There has been an error in interleaving. |
TRAP-TYPE |
|
|
|
hpevtUnusableResource |
5490 |
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 |
TRAP-TYPE |
|
|
|
hpevtFwError |
5491 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramDataCmpError |
5492 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramCrcError |
5493 |
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. |
TRAP-TYPE |
|
|
|
hpevtErm |
5494 |
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. |
TRAP-TYPE |
|
|
|
hpevtErrorObtainingSemaphore |
5496 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramBlockRevMismatch |
5498 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramBlockNotFound |
5499 |
The requested NVRAM block was not found. The ID that was not found is displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtNvramBlockUnlocked |
5501 |
Firmware tried to unlock a NVRAM block that was already unlocked. Data field contains the block ID. |
TRAP-TYPE |
|
|
|
hpevtResetForReconfig |
5505 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdRendezUtilityError |
5507 |
During PD rendezvous, system firmware encountered a problem sending commands to the utilities system. This will prevent a fully functional PD from being created. |
TRAP-TYPE |
|
|
|
hpevtHalt |
5509 |
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. |
TRAP-TYPE |
|
|
|
hpevtDuiNoConsole |
5510 |
The DUI (Developers User Interface) was entered, but there is no console available for the interface. |
TRAP-TYPE |
|
|
|
hpevtErrorProcFailed |
5511 |
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. |
TRAP-TYPE |
|
|
|
hpevtReconfigResetFail |
5514 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdErrorReachableSet |
5515 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoBridgeDepthExceeded |
5518 |
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) |
TRAP-TYPE |
|
|
|
hpevtEfiConsoleDriverError |
5521 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemTestCodeInPage0Corrupt |
5525 |
This event is unused |
TRAP-TYPE |
|
|
|
hpevtRemoteCellStateUnknown |
5527 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdMltplCoreCells |
5528 |
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. |
TRAP-TYPE |
|
|
|
hpevtUtilSendCommandError |
5529 |
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. |
TRAP-TYPE |
|
|
|
hpevtUtilCellSlotError |
5530 |
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. |
TRAP-TYPE |
|
|
|
hpevtMcNoAccessToPd |
5547 |
This chassis code indicates that the cell does not have any access to a PD. |
TRAP-TYPE |
|
|
|
hpevtMcLossOfLockstep |
5548 |
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. |
TRAP-TYPE |
|
|
|
hpevtMcPdCellRendezFailed |
5550 |
This indicates that some of the cells did not show up during the PD level rendezvous. |
TRAP-TYPE |
|
|
|
hpevtMcProcErrHalt |
5556 |
This indicates that catastrophic errors have been found in the PIN block of the cell controller. The cell needs to be reset/ halt. |
TRAP-TYPE |
|
|
|
hpevtMcCellMonarchTimeout |
5557 |
This means that the cell monach cpu has not completed the assigned task within the timeout and hence it will be deconfigured. |
TRAP-TYPE |
|
|
|
hpevtMcPdCellMissedRendez |
5558 |
This indicates that the cell is too late for the PD level rendezvous. And hence it will not join the other PD cells. |
TRAP-TYPE |
|
|
|
hpevtMcPdMonarchTimeout |
5559 |
This indicates the state where the PD monarch was not able to complete the task within a certain time. It failed. |
TRAP-TYPE |
|
|
|
hpevtRemoteSetViewRootError |
5560 |
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. |
TRAP-TYPE |
|
|
|
hpevtCsrTestFailure |
5566 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdMemGetIcmInfoFailed |
5567 |
This chassis code reports the failure in collecting the ICM parameters needed for the cell interleaving. |
TRAP-TYPE |
|
|
|
hpevtPdMemGetCellInfoFailed |
5568 |
This chassis code indicates that the cell interleaving routine could not get the information on the cell memory. |
TRAP-TYPE |
|
|
|
hpevtPdMemUpdateCellGniFailed |
5569 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdMemAdjustMinZiFailed |
5570 |
This represents the failure in adjusting the memory information with the minimum ZI requirements. |
TRAP-TYPE |
|
|
|
hpevtStableProfileXsumError |
5572 |
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. |
TRAP-TYPE |
|
|
|
hpevtDynamicProfileXsumError |
5573 |
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. |
TRAP-TYPE |
|
|
|
hpevtPartitionProfileXsumError |
5574 |
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. |
TRAP-TYPE |
|
|
|
hpevtStableProfileSeqidInvalid |
5575 |
The Complex Profile Group A sequence ID is invalid. Booting cannot continue. The actual data is in the chassis code data field. |
TRAP-TYPE |
|
|
|
hpevtDynamicProfileSeqidInvalid |
5577 |
The Dynamic Complex Profile (Group B) sequence ID is invalid. The invalid Sequence ID is displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtEfiFwError |
5579 |
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. |
TRAP-TYPE |
|
|
|
hpevtCmplxProfilePdNumMismatch |
5580 |
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. |
TRAP-TYPE |
|
|
|
hpevtCmplxProfilePdNumInvalid |
5581 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortSm4Error |
5583 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortSm4NotReleased |
5584 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootBmcTokenUploadFailure |
5594 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootNvmTokenAccessFailure |
5595 |
The read from SAL NVM has failed. This is a stop boot condition. Data: The token number on which the read failed |
TRAP-TYPE |
|
|
|
hpevtBootBmcTokenDownloadError |
5596 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootFruReadError |
5598 |
The read of a FRU has failed. Data: Device ID of device that failed the FRU read. |
TRAP-TYPE |
|
|
|
hpevtBootFruXsumError |
5599 |
The read of a FRU has failed the checksum test. Data: Device ID of device that failed the FRU read. |
TRAP-TYPE |
|
|
|
hpevtBootFruVersionError |
5600 |
The read of a FRU has failed due to a version problem. Data: Device ID of device that failed the FRU read. |
TRAP-TYPE |
|
|
|
hpevtBootRomRevToFitRevWarning |
5601 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootRomRevToRevBlockWarning |
5602 |
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 |
TRAP-TYPE |
|
|
|
hpevtIoPciPerr |
5617 |
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). |
TRAP-TYPE |
|
|
|
hpevtIoPciSerr |
5618 |
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). |
TRAP-TYPE |
|
|
|
hpevtIoCheckLbaDeconfigErr |
5619 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellNotInAPd |
5622 |
The Reporting Cell is not configured to be in a PD, according to Complex Profile Group A. |
TRAP-TYPE |
|
|
|
hpevtMemDimmThermalLoadOrderWarn |
5623 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellMajorityNotPresent |
5626 |
Not enough cells made the Rendezvous for boot to continue. The rules are listed in the cause action section. |
TRAP-TYPE |
|
|
|
hpevtMcIoClearFail |
5646 |
SFW's Machine Check Handler was unable to log or clear I/O error registers. |
TRAP-TYPE |
|
|
|
hpevtMcRendezvousSlavesFail |
5677 |
SFW's MCA Handler has failed to rendezvous all the slaves Data: Return from the rendezvous call. |
TRAP-TYPE |
|
|
|
hpevtSalAbiFwError |
5692 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiEsiTableLengthErr |
5698 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiEsiTableChecksumErr |
5700 |
The computed checksum for the ESI (Extensible SAL Interface) table is not zero as expected. EFI is halting. Data Field: the computed checksum. |
TRAP-TYPE |
|
|
|
hpevtEfiEsiTableUnsupportedEntryType |
5701 |
EFI found an unsupported entry type within the ESI (Extensible SAL Interface) Table. Data Field: unknown type. |
TRAP-TYPE |
|
|
|
hpevtEfiHalt |
5708 |
EFI is halting. Look for the cause of the halt in preceding events. Data Field: the 'halt' (0x0F) major change in system state code. |
TRAP-TYPE |
|
|
|
hpevtMemChipspareNotSupported |
5711 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiAssertError |
5712 |
EFI has detected an internal error. The actual error is unspecified by this event. Examine previous events and console output for possible explanations. |
TRAP-TYPE |
|
|
|
hpevtEfiEfiBreakpoint |
5713 |
EFI has executed the 'break' shell command. EFI is halting. The 'break' command is currently implemented as an infinite loop to halt EFI. |
TRAP-TYPE |
|
|
|
hpevtEfiHcdHostHung |
5714 |
The EFI USB interrupt service has detected the host controller is hung. EFI is halting. |
TRAP-TYPE |
|
|
|
hpevtEfiSalHandoffVerMismatch |
5715 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSalRtcServiceNotInit |
5717 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSalTimerServiceNotInit |
5718 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSalStarttimerServiceNotInit |
5719 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiBreakpoint |
5721 |
EFI reached an unimplemented section of code. EFI is halting. Data Field: Unique identifier indicating the location reached within the code. |
TRAP-TYPE |
|
|
|
hpevtEfiSpeedyBootTokenNotRead |
5722 |
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.. |
TRAP-TYPE |
|
|
|
hpevtEfiSalCallbackAttempted |
5723 |
A SAL Callback was attempted. This is not permitted. EFI is halting. Data Field: index of the function that was being called. |
TRAP-TYPE |
|
|
|
hpevtEfiSalFreqBaseUnknown |
5724 |
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). |
TRAP-TYPE |
|
|
|
hpevtEfiSysEventAlreadyInit |
5725 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSysEventCreateEventFail |
5726 |
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. |
TRAP-TYPE |
|
|
|
hpevtFpgaNodeInitError |
5728 |
An error was detected while initializing the FPGA node and services associated with the PDH. |
TRAP-TYPE |
|
|
|
hpevtIoconfigNodeInitError |
5729 |
Firmware encountered an error when creating the ioconfig node as a child of the pdh node. |
TRAP-TYPE |
|
|
|
hpevtDillonPdhNodeInitError |
5730 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhPropertyError |
5731 |
The PDH service was unable to either get or set the property specified in the data field as an ASCII message. |
TRAP-TYPE |
|
|
|
hpevtPdhAcpihwNodeError |
5732 |
PDH encountered an error creating the ACPI Hardware Node in the device tree or installing its properties. |
TRAP-TYPE |
|
|
|
hpevtPdhIpmiNodeError |
5733 |
The PDH service encountered an error while creating the ipmi node or adding properties to it. The status is in the data field. |
TRAP-TYPE |
|
|
|
hpevtCpuSupplementalTestFailed |
5746 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricReadMbeError |
5747 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricUnexpectedStatus |
5749 |
The return value from a function was an unknown value. Data field is the unknown status that was returned. |
TRAP-TYPE |
|
|
|
hpevtEfiSysidBmcWarning |
5750 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSysidBmcReadError |
5751 |
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) |
TRAP-TYPE |
|
|
|
hpevtEfiSysidBmcWriteError |
5752 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSysidInvalid |
5753 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiRtIvtEsiTableErr |
5755 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiRtIvtEsiQueryErr |
5756 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiBootIvtEsiTableErr |
5757 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiBootIvtEsiQueryErr |
5758 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortPresenceError |
5762 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortHwLinkError |
5763 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortFeError |
5764 |
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. |
TRAP-TYPE |
|
|
|
hpevtXinLinkInitError |
5766 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiGetMfgModeNotInit |
5768 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiBmcMfgModeInvalid |
5769 |
The BMC has returned an invalid system mode. Data Field: the invalid mode. Expected values are 0 or 1. |
TRAP-TYPE |
|
|
|
hpevtEfiEnterMfgModeNotInit |
5770 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiExitMfgModeNotInit |
5771 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiTaccessServiceNotInit |
5772 |
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. |
TRAP-TYPE |
|
|
|
hpevtTreeNodeNotFound |
5774 |
A needed tree node was not found. The data field contains the ASCII name of the tree node that was not found. |
TRAP-TYPE |
|
|
|
hpevtEfiSystemStateRunningErr |
5776 |
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 |
TRAP-TYPE |
|
|
|
hpevtPalBusConfigIncompatible |
5777 |
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. |
TRAP-TYPE |
|
|
|
hpevtPalGetBusFeaturesFailed |
5778 |
Firmware was unable to correctly issue the Get Processor Bus Dependent Configuration Features command. |
TRAP-TYPE |
|
|
|
hpevtMemDimmPairMismatch |
5779 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiPosseLibNotInit |
5784 |
EFI is unable to initialize internal library. This collection of internal services is required for much of EFI's functionality. EFI is halting. |
TRAP-TYPE |
|
|
|
hpevtEfiSecurityNotInit |
5785 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInvalidSysmode |
5786 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecSetPassLevelErr |
5787 |
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. |
TRAP-TYPE |
|
|
|
hpevtMdtBad |
5788 |
SFW has determined that the Memory Data Table (MDT) table is invalid. |
TRAP-TYPE |
|
|
|
hpevtXbcReadRemoteRouteError |
5793 |
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). |
TRAP-TYPE |
|
|
|
hpevtXbcReadNeighborInfoError |
5794 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemDimmQuadMismatch |
5795 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemDimmFailed |
5796 |
The DIMM at the physical location given by the data field had excessive errors and has been marked as 'FAILED' by firmware. |
TRAP-TYPE |
|
|
|
hpevtXbcPortOeError |
5797 |
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). |
TRAP-TYPE |
|
|
|
hpevtXbcPortStatusError |
5798 |
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). |
TRAP-TYPE |
|
|
|
hpevtXbcPortLandmined |
5799 |
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). |
TRAP-TYPE |
|
|
|
hpevtPdIncompatibleCpuSpeeds |
5800 |
Reporting cell tried to rendezvous with a cell with processors that are running at a different speed. The data field lists the offending cell |
TRAP-TYPE |
|
|
|
hpevtFabricCellLinkNotInit |
5802 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricInvalidXbcNum |
5803 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricInvalidXbcPortNum |
5804 |
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). |
TRAP-TYPE |
|
|
|
hpevtUtilitiesLedParamError |
5805 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricUnexpectedNtype |
5806 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricPortNotCc |
5807 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricPortNotXbc |
5808 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricUnexpectedNChip |
5809 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricUnexpectedNPort |
5810 |
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). |
TRAP-TYPE |
|
|
|
hpevtBootNvmWriteToBmcTokenFailure |
5811 |
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. |
TRAP-TYPE |
|
|
|
hpevtUtilitiesLedError |
5812 |
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. |
TRAP-TYPE |
|
|
|
hpevtDuplicateCpuIds |
5813 |
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. |
TRAP-TYPE |
|
|
|
hpevtHp-uxDumpStatus |
5825 |
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. |
TRAP-TYPE |
|
|
|
hpevtSettingProcTimeoutFail |
5827 |
SFW has failed to set the processor timeout value via a PAL call. Data: PAL call return value. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInitVerifyErr |
5832 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInitCloseErr |
5833 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInitOpenErr |
5834 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInitWriteErr |
5836 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiSecInitWriteDenied |
5837 |
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. |
TRAP-TYPE |
|
|
|
hpevtErrDeadlockResetDetected |
5896 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemParityErr |
6002 |
SFW detected a memory address parity error. The data field contains the physical location of DIMM that saw the parity error. |
TRAP-TYPE |
|
|
|
hpevtMemRefreshStartError |
6146 |
Timeout Waiting for SDRAM parts to become ready - mem_status[0] Refresh Control Register |
TRAP-TYPE |
|
|
|
hpevtMemExtBaseboardIncompatible |
6180 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricDifferentTopologies |
6730 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricInvalidXbc2XbcPort |
6795 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricGetNeighborInfoError |
7652 |
The XBC could not get neighbor information. Data Field: XBC # << 32 | internal port attempting to access neighbor |
TRAP-TYPE |
|
|
|
hpevtXbcRoutingErrorState |
7653 |
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) |
TRAP-TYPE |
|
|
|
hpevtNoNvmErrLogSpace |
7655 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortError |
7657 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcPortRouteAround |
7658 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcUnexpectedState |
7660 |
Data field: the unexpected forward progress state (0:31) XBC number (32:44) Cell number (56:63) |
TRAP-TYPE |
|
|
|
hpevtXbcRoutingStateTimeout |
7661 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcNeighborPortNotRoutable |
7663 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricRouteXbcError |
7666 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricMaxBrokenLinks |
7667 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcForceUnlockSm4Timeout |
7671 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcGetGlobalSm4Timeout |
7673 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcReleaseSm4Timeout |
7674 |
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) |
TRAP-TYPE |
|
|
|
hpevtMpBatteryFailure |
7684 |
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. |
TRAP-TYPE |
|
|
|
hpevtMpSoftwareError |
7685 |
Management Processor Firmware detected a software error and is logging an event. The data represents data associated with the error seen. |
TRAP-TYPE |
|
|
|
hpevtMpI2cCommError |
7686 |
An I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset. |
TRAP-TYPE |
|
|
|
hpevtRomCrcError |
7690 |
A stored CRC value did not match the calculated CRC value for the specified address. |
TRAP-TYPE |
|
|
|
hpevtCpuRevisionMismatch |
7732 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuFreqMismatch |
7733 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuOverclocked |
7734 |
The rating for the cpu and the actual speed will be emitted in 2 sequential event data fields. |
TRAP-TYPE |
|
|
|
hpevtCmplxProfilIncoherent |
7758 |
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. |
TRAP-TYPE |
|
|
|
hpevtIdCommandRequired |
7767 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramBatteryFail |
7771 |
The battery on the SBCH is below the safe threshold. The battery can be replaced online. |
TRAP-TYPE |
|
|
|
hpevtPartitionTimeoutReset |
7773 |
The partition is being reset because its watchdog timer expired and automatic restart is enabled. |
TRAP-TYPE |
|
|
|
hpevtPdhcWatchdogTimedOut |
7774 |
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. |
TRAP-TYPE |
|
|
|
hpevtAbortPowerupOth |
7781 |
The Cabinet Power Up request was aborted due to ambient air over temperature. |
TRAP-TYPE |
|
|
|
hpevtAbortPwrupBps |
7782 |
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. |
TRAP-TYPE |
|
|
|
hpevtAbortStartBlowr |
7783 |
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. |
TRAP-TYPE |
|
|
|
hpevtAbortStartIofan |
7784 |
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. |
TRAP-TYPE |
|
|
|
hpevtAcDeleted |
7786 |
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. |
TRAP-TYPE |
|
|
|
hpevtBlowrFail |
7791 |
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. |
TRAP-TYPE |
|
|
|
hpevtBpsFail48flt |
7793 |
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. |
TRAP-TYPE |
|
|
|
hpevtBpsFailFanflt |
7795 |
The designated Bulk Power Supply is reporting its fan has failed. |
TRAP-TYPE |
|
|
|
hpevtBpsFailOt |
7796 |
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 |
TRAP-TYPE |
|
|
|
hpevtBpsNotRedundant |
7798 |
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. |
TRAP-TYPE |
|
|
|
hpevtBpsOvervoltage |
7799 |
The PM has detected the value of +48V power, as measured on the UGUY board, has exceeded an upper threshold. |
TRAP-TYPE |
|
|
|
hpevtBpsUndervoltage |
7803 |
The PM has detected the value of +48V power, as measured on the UGUY board, has fallen below a lower threshold. |
TRAP-TYPE |
|
|
|
hpevtCabFanFail |
7806 |
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. |
TRAP-TYPE |
|
|
|
hpevtIllegalBpsCfgOrPhaseFlt |
7824 |
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: |
TRAP-TYPE |
|
|
|
hpevtIllegalBpsid |
7825 |
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. |
TRAP-TYPE |
|
|
|
hpevtInletOvertempHi |
7827 |
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. |
TRAP-TYPE |
|
|
|
hpevtInletOvertempLo |
7828 |
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. |
TRAP-TYPE |
|
|
|
hpevtInletOvertempMid |
7829 |
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.. |
TRAP-TYPE |
|
|
|
hpevtIofanFail |
7836 |
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. |
TRAP-TYPE |
|
|
|
hpevtPowerOverload |
7842 |
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. |
TRAP-TYPE |
|
|
|
hpevtShutdownBlowr |
7845 |
After a BLOWR_FAIL, there were N-1 blowers functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage. |
TRAP-TYPE |
|
|
|
hpevtShutdownIofan |
7846 |
After a IOFAN_FAIL, there were N-1 fans functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage. |
TRAP-TYPE |
|
|
|
hpevtXucFanFail |
7849 |
One of two fans in the Utility chassis of the IO Expansion Cabinet has failed. |
TRAP-TYPE |
|
|
|
hpevtCluWatchdogReset |
7855 |
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. |
TRAP-TYPE |
|
|
|
hpevtEepromInvalidCksm |
7856 |
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. |
TRAP-TYPE |
|
|
|
hpevtHbpbBoardPowerFault |
7858 |
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. |
TRAP-TYPE |
|
|
|
hpevtHiobEepromRdFail |
7863 |
An attempt to read the EEPROM (FRUID) on the IO Backplane Board failed. |
TRAP-TYPE |
|
|
|
hpevtHiopbEepromRdFail |
7864 |
An attempt to read the EEPROM (FRUID) on the IO Backplane Power Board failed. |
TRAP-TYPE |
|
|
|
hpevtHiopbLpmFltRdFail |
7865 |
An attempt to read the Local Power Monitor Fault register on the IO Backplane Power Board failed. |
TRAP-TYPE |
|
|
|
hpevtHiopbOvertemp |
7866 |
The Local Power Monitor of the named IO Chassis is reporting a Power Brick over temperature condition. |
TRAP-TYPE |
|
|
|
hpevtHiopbPowerFault |
7867 |
The Local Power Monitor on the named IO Chassis has reported a power fault condition. |
TRAP-TYPE |
|
|
|
hpevtHiopbVoltMrgnFail |
7871 |
The Local Power Monitor on the named IO Power Board failed to properly margin the power as commanded. |
TRAP-TYPE |
|
|
|
hpevtSbchEepromRdFail |
7873 |
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. |
TRAP-TYPE |
|
|
|
hpevtUguyEepromRdFail |
7874 |
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. |
TRAP-TYPE |
|
|
|
hpevtSysBkpI2cWrFail |
7878 |
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 |
TRAP-TYPE |
|
|
|
hpevtSysBkpPowerFault |
7879 |
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). |
TRAP-TYPE |
|
|
|
hpevtWriteFruDataFail |
7891 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuFanFail |
7892 |
The fan on a CPU is not operating in a manner that provides enough air flow to cool the processor |
TRAP-TYPE |
|
|
|
hpevtCpuFanSlow |
7893 |
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 |
TRAP-TYPE |
|
|
|
hpevtDnaFanFail |
7894 |
The fan on a CC chip is not operating in a manner that provides enough air flow to cool the processor |
TRAP-TYPE |
|
|
|
hpevtDnaFanSlow |
7895 |
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 |
TRAP-TYPE |
|
|
|
hpevtPdhcToSysfwRevMismtch |
7896 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhCtrlrFwMismatch |
7902 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellPowerFault |
7903 |
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 |
TRAP-TYPE |
|
|
|
hpevtCpuInitNodeError |
7938 |
The CPU node retuned an error when calling its initialize node function. The specific status is displayed in the data field. |
TRAP-TYPE |
|
|
|
hpevtCpuExecuteCmdError |
7939 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuCmdStateInvalid |
7940 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuPalProcError |
7948 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPersistantError |
7963 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcLinkTestError |
7964 |
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) |
TRAP-TYPE |
|
|
|
hpevtPltfrmStorageReadErr |
7965 |
System firmware was unable to complete a platform storage read command from the utilities system. The exact status printed in the data field. |
TRAP-TYPE |
|
|
|
hpevtPltfrmStorageWriteErr |
7966 |
System firmware was unable to complete a platform storage write command. The actual status is returned in the data field. |
TRAP-TYPE |
|
|
|
hpevtTreeNodeErrorSequencer |
7973 |
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. |
TRAP-TYPE |
|
|
|
hpevtPartitionVariableError |
7974 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellRedundtPowerFault |
7975 |
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. |
TRAP-TYPE |
|
|
|
hpevtPalProcConfigIncompatible |
8009 |
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. |
TRAP-TYPE |
|
|
|
hpevtPalGetProcFeaturesFailed |
8010 |
System firmware was unable to successfully issue the PAL_GET_PROC_FEATURES PAL proc. The data field is unused |
TRAP-TYPE |
|
|
|
hpevtPdhcAssertionFailed |
8131 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhcFirmwareUnknownErr |
8132 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhcI2cWriteFailed |
8133 |
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). |
TRAP-TYPE |
|
|
|
hpevtPdhcI2cReadFailed |
8134 |
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). |
TRAP-TYPE |
|
|
|
hpevtPdhcSmbusWriteFailed |
8135 |
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). |
TRAP-TYPE |
|
|
|
hpevtPdhcSmbusReadFailed |
8136 |
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). |
TRAP-TYPE |
|
|
|
hpevtFrequencyProgramFailed |
8137 |
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. |
TRAP-TYPE |
|
|
|
hpevtSysFwFlashUpdateError |
8138 |
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). |
TRAP-TYPE |
|
|
|
hpevtCpuTmpSensorSetupFail |
8140 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuModuleThermalert |
8141 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhcFlashUpdateError |
8143 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellTypMismatchWSysfw |
8147 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhcPdhArbiterTimeout |
8149 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhcGetSm4Timeout |
8151 |
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. |
TRAP-TYPE |
|
|
|
hpevtIpmiBmc2hostMsgFailure |
8153 |
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. |
TRAP-TYPE |
|
|
|
hpevtEfiDebugLevelTokenErr |
8154 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcPortNotLandmined |
8156 |
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). |
TRAP-TYPE |
|
|
|
hpevtFabricValidateError |
8159 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricISRInvalidBkp |
8184 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricXinWrZeroErrMaskError |
8186 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricCcPriModeRegRdStatus |
8187 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricCcPriModeRegRdData |
8188 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricCcErrMaskRegRdStatus |
8189 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricCcErrMaskRegRdData |
8190 |
The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Error Mask CSR. |
TRAP-TYPE |
|
|
|
hpevtFabricXingNeighborPortBad |
8194 |
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) |
TRAP-TYPE |
|
|
|
hpevtPmAssertionFailed |
8199 |
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. |
TRAP-TYPE |
|
|
|
hpevtPmFirmwareUnknownErr |
8200 |
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. |
TRAP-TYPE |
|
|
|
hpevtPmCriticalDebug |
8202 |
This event is a tool to aid in the debugging and testing of firmware. |
TRAP-TYPE |
|
|
|
hpevtFabricLinkCorErrTestFailure |
8205 |
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) |
TRAP-TYPE |
|
|
|
hpevtPdIncompatibleFwRevs |
8207 |
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. |
TRAP-TYPE |
|
|
|
hpevtPmI2cWriteFailed |
8212 |
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). |
TRAP-TYPE |
|
|
|
hpevtPmI2cReadFailed |
8214 |
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). |
TRAP-TYPE |
|
|
|
hpevtCellInfoError |
8216 |
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. |
TRAP-TYPE |
|
|
|
hpevtRegistryMoveToCoreCellError |
8219 |
An error was encountered trying to relocate the registry on a slave cell to point to the core cells main memory structures. |
TRAP-TYPE |
|
|
|
hpevtProfileGroupCCrcError |
8220 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricAssertFabricUtils |
8239 |
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. |
TRAP-TYPE |
|
|
|
hpevtSalPmiFwError |
8240 |
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. |
TRAP-TYPE |
|
|
|
hpevtOlaWrongNumberCells |
8243 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricXbcRouteSourceCellPortErr |
8257 |
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) |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellIncompatible |
8261 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellDidNotReachRendezvous |
8263 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellStillAtBib |
8264 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellUnexpectedCellState |
8265 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellCantReachAliveCells |
8267 |
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. |
TRAP-TYPE |
|
|
|
hpevtXinInitIntermittentFailure |
8271 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhErrClearOlaSteeringBit |
8643 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricCc2XbcLinkInitFailed |
8648 |
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 |
TRAP-TYPE |
|
|
|
hpevtFwVirtualMappingError |
8652 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricLinkInitIntermittentFailure |
8679 |
Fabric Discovery's attempt to initialize the local cell's CC to XBC link has failed. The link initialization sequence has an intermittent problem. |
TRAP-TYPE |
|
|
|
hpevtIodiscIolinkError |
8712 |
An error was detected in the link between the CC and the I/O controller. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellErrAccessCmplxProfile |
8745 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootFwRelocMemErr |
8747 |
A Firmware tries to find a main memory block large enough meeting alignment requirements. |
TRAP-TYPE |
|
|
|
hpevtBootOlaCellNotConfigInCmplxProfile |
8752 |
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. |
TRAP-TYPE |
|
|
|
hpevtOptsNvmAllocError |
8756 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaUpdateRtcFailedOlaCell |
8757 |
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. |
TRAP-TYPE |
|
|
|
hpevtSalInfoTimeout |
8758 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhIprNotClearedOnCell |
8761 |
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 |
TRAP-TYPE |
|
|
|
hpevtPdhIprClearAttempts |
8762 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootOlaUpdateRtcFailedExistingCell |
8763 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemIncompleteEchelon |
8768 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricRdPortStatePortInvalid |
8771 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricWrPortStatePortInvalid |
8772 |
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) |
TRAP-TYPE |
|
|
|
hpevtMainBpLpmFlt |
8784 |
The main backplane is reporting the LPM status as fault. |
TRAP-TYPE |
|
|
|
hpevtIoBpLpmFlt |
8787 |
The IO backplane has reported a local power monitor fault. |
TRAP-TYPE |
|
|
|
hpevtActiveLogNotFound |
8806 |
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 |
TRAP-TYPE |
|
|
|
hpevtReachedMaxErrorLogs |
8807 |
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. |
TRAP-TYPE |
|
|
|
hpevtOldNoCellToDelete |
8814 |
System firmware has been invoked to perform a cell delete operation but no cell in the system appears to be ready for deletion. |
TRAP-TYPE |
|
|
|
hpevtErmOutOfHeap |
8819 |
Error Response Mode code attempted a malloc of heap space that failed. |
TRAP-TYPE |
|
|
|
hpevtMemDimmUnsupported |
8821 |
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. |
TRAP-TYPE |
|
|
|
hpevtOptsMallocError |
8828 |
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. |
TRAP-TYPE |
|
|
|
hpevtCellHwDegraded |
8837 |
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. |
TRAP-TYPE |
|
|
|
hpevtNotIntegratingCell |
8839 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoContextCorruptErr |
8842 |
The IO error context is corrupt. This will impair IO error reporting. |
TRAP-TYPE |
|
|
|
hpevtIoRopeFatal |
8843 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoBusFatal |
8844 |
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. |
TRAP-TYPE |
|
|
|
hpevtIoRopeUnitFatal |
8845 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhFlashWriteEnableBitSetNowCleared |
8851 |
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. |
TRAP-TYPE |
|
|
|
hpevtFirmwareInitError |
8855 |
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. |
TRAP-TYPE |
|
|
|
hpevtMcIncompleteCellSet |
8858 |
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. |
TRAP-TYPE |
|
|
|
hpevtMcDuringOsMca |
8861 |
This means that MCA occurred while OS_MCA was performing error recovery. |
TRAP-TYPE |
|
|
|
hpevtMcMemDumpAbandon |
8864 |
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. |
TRAP-TYPE |
|
|
|
hpevtAcpiConfigMismatch |
8872 |
The firmware parameter that defines the ACPI configuration is inconsistent in at least one of the cells in the partition. |
TRAP-TYPE |
|
|
|
hpevtFabricAssertFabricInit |
8876 |
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. |
TRAP-TYPE |
|
|
|
hpevtInvalidPiromData |
8877 |
A value read by the PDHC from a CPU module's Processor Information ROM was not within acceptable limits. |
TRAP-TYPE |
|
|
|
hpevtSettingFreqRatiosError |
8882 |
An invalid parameter was specified when trying to set the cpu bus config register, cpu frequencies ratio field. Valid range is 0xe - 0x17 |
TRAP-TYPE |
|
|
|
hpevtFabricXinInitDisableWrError |
8895 |
An attempt to disable the fabric link failed because writing the CC CSR failed. Data Field: (cell << 56) | return status |
TRAP-TYPE |
|
|
|
hpevtFabricXinErrMaskUnknownBkp |
8896 |
Could not determine the system type in order to write the appropriate error mask for the fabric link. Data Field: system type |
TRAP-TYPE |
|
|
|
hpevtFabricXinWrErrMaskError |
8897 |
Failed writing the XIN error mask for CC's fabric link. Data Field: (cell << 56) | return status |
TRAP-TYPE |
|
|
|
hpevtResetCommandError |
8906 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricInitCcLinkDisableErr |
8926 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricSetPortStateGetSm4Err |
8930 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricSetPortStateRlsSm4Err |
8931 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricAssertFabricErr |
8936 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricXinLinkAlreadyInit |
8939 |
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. |
TRAP-TYPE |
|
|
|
hpevtNoCpuModulesFoundByPdhc |
8940 |
The PDHC FW could not detect any CPU modules on its Cell board, so it is holding the Cell in reset. |
TRAP-TYPE |
|
|
|
hpevtCpuModCompatMismatch |
8941 |
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. |
TRAP-TYPE |
|
|
|
hpevtBadCpuModScratchCksum |
8942 |
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. |
TRAP-TYPE |
|
|
|
hpevtPdhBatteryLowWarning |
8954 |
The battery voltage level is low for the cell. This indicates that the NVRAM will not be saved if the power is removed. |
TRAP-TYPE |
|
|
|
hpevtFabricRouteXbcCopyRoutingErr |
8959 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricCopyRdBackFailed |
8960 |
The read immediately after a write while copying routing registers failed. Data: whether or not the XBC Key was enabled |
TRAP-TYPE |
|
|
|
hpevtFabricRtgCompleteSm4RlsErr |
8962 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricRtgCompleteSm4AccessErr |
8965 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricRouteTraversableCc2CcErr |
8968 |
Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE) |
TRAP-TYPE |
|
|
|
hpevtFabricDataRouteTraversableCc2CcErr |
8969 |
Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE) |
TRAP-TYPE |
|
|
|
hpevtFabricCc2ccTraverseLclXinRdErr |
8970 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricCc2ccTraverseRmtXinRdErr |
8971 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricCc2ccTraverseLclNotInit |
8972 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricCc2ccTraverseRmtNotInit |
8973 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricDisableXinLinkReadErr |
8974 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricXinInitRetryReadErr |
8975 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricAssertFabricCc |
8976 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuRestricted |
8979 |
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 |
TRAP-TYPE |
|
|
|
hpevtLstNotRun |
8982 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootSetCellStateFabricFailure |
8983 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootResetCellStateFailure |
8984 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemChipspareDeallocRank |
9000 |
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. |
TRAP-TYPE |
|
|
|
hpevtClockFreqError |
9019 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricColaInitTraversableErr |
9020 |
Could not traverse the fabric to the cell being added. Data field: (chosen cell << 56) | return status, where -1 = failure |
TRAP-TYPE |
|
|
|
hpevtFabricAttemptFocusedReroute |
9021 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricCellRerouteNinfoErr |
9022 |
Error getting the XBC port's expected neighbor from a firmware table. Data field: 0 (SUCCESS) or -1 (FAILURE) |
TRAP-TYPE |
|
|
|
hpevtBootWakeCpuIsCpuDeconfigErr |
9038 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootWakeCpuGetCountersErr |
9039 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootWakeCpuGetStructAddrErr |
9040 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootCheckCpu4CompletionErr |
9041 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootCheckCpuGetStructAddrErr |
9042 |
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(). |
TRAP-TYPE |
|
|
|
hpevtReconfigResetScheduled |
9043 |
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. |
TRAP-TYPE |
|
|
|
hpevtProfileWrongArchType |
9045 |
When processing the complex profile, the an unexpected 'Architecture Type' was specified in the PA/IA Arch field. The actual data found is displayed. |
TRAP-TYPE |
|
|
|
hpevtBootCheckCpuIsDeconfigErr |
9046 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootCheckCpuGetCountersErr |
9047 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootPdMonarchRtnFromSwSetFpErr |
9049 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootSlaveRtnFromFwSetFpErr |
9051 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootProblemBranchingToPgzLocation |
9052 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootBadCpuOrder |
9084 |
The Data Field contains the value used to determine a valid order. |
TRAP-TYPE |
|
|
|
hpevtBootGetSleepTimeoutStructAddrErr |
9365 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootMoveSlavesDispatcherAddrErr |
9367 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootMoveSlavesCheckSlaveErr |
9368 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootMoveSlavesFpSetAddrErr |
9370 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootMoveSlavesFpSetErr |
9371 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootMoveCellMonarchsStructAddrErr |
9372 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootMoveCellMonarchsCheckSlaveErr |
9373 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootMoveCellMonarchsFpSetAddrErr |
9375 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootMoveCellMonarchsFpSetErr |
9376 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricLogRoutingRdErr |
9403 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricLinkRendezDisableErr |
9412 |
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 |
TRAP-TYPE |
|
|
|
hpevtAcDeletedA0 |
9417 |
Power is no longer being supplied to input A0 on the cabinet specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtAcDeletedA1 |
9418 |
Power is no longer being supplied to input A1 on the cabinet specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtAcDeletedB0 |
9419 |
Power is no longer being supplied to input B0 on the cabinet specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtAcDeletedB1 |
9420 |
Power is no longer being supplied to input B1 on the cabinet specified in the data field. |
TRAP-TYPE |
|
|
|
hpevtFabricCc2CcLinkDisableErr |
9428 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricISREarlyCopyRoutingErr |
9430 |
Error writing the XBC port's routing registers. The cell will reboot. Data Field: XBC port << 44 | XBC num << 32 | return status |
TRAP-TYPE |
|
|
|
hpevtFabricPortPairRdPstatusErr |
9433 |
While testing link traversability, a XBC CSR could not be read. Data Field: Port Number << 44 | XBC Number << 32 | return value |
TRAP-TYPE |
|
|
|
hpevtPdhBatteryPowerLow |
9438 |
The Battery-Low interrupt was signaled in the Interrupt Pending Register in Dillon (PDH) by the hardware. PDHC is merely reporting the problem. |
TRAP-TYPE |
|
|
|
hpevtNoHandoffToOsMca |
9440 |
This means that the system FW MCA handler is not going to handoff to the OS_MCA handler. |
TRAP-TYPE |
|
|
|
hpevtBootRtnFromSwCantGetCounters |
9441 |
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(). |
TRAP-TYPE |
|
|
|
hpevtBootRtnFromSwCpuNotAsleep |
9442 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootDeconfigAbsentCantSetCpuState |
9445 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootMoveSlavesSetTimeoutErr |
9450 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootReconfigAllCpus |
9460 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootGetNumcoresFailure |
9461 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricRmtRoutePortTopoErr |
9465 |
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) |
TRAP-TYPE |
|
|
|
hpevtFabricRdFailedLinksError |
9468 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricWrFailedLinksRdError |
9469 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricWrFailedLinksWrError |
9470 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricIncFailedLinksRdError |
9471 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricIncFailedLinksWrError |
9472 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricIncFailedLinksHitLimit |
9473 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricRtgCompleteRdFldLinksErr |
9474 |
Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: PDC return status |
TRAP-TYPE |
|
|
|
hpevtFabricRtgCompleteWrFldLinksErr |
9475 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricCellRerouteRdXbcErr |
9476 |
Could not read the XBC register that marks the ports that have been routed around. Data Field: (XBC Num << 32) | PDC return status |
TRAP-TYPE |
|
|
|
hpevtFabricCellRerouteSm4RlsErr |
9479 |
Could not release the remote XBC's semaphore. Cell will halt. Data Field: (XBC Num << 32) | PDC return status |
TRAP-TYPE |
|
|
|
hpevtFabricRmtRoutePortRdErr |
9481 |
Failed to complete a read to the built-in port of a XBC. Data Field: (XBC Num << 32) | PDC return status |
TRAP-TYPE |
|
|
|
hpevtFabricRmtRoutePortWrErr |
9482 |
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 |
TRAP-TYPE |
|
|
|
hpevtIoLinkSubsystemFailed |
9484 |
The link between the CC and SBA failed meaning that I/O is not available to the reporting cell. |
TRAP-TYPE |
|
|
|
hpevtIoErrengineError |
9486 |
The structured exception handling within the system firmware failed during I/O initialization. |
TRAP-TYPE |
|
|
|
hpevtIoDiscEeMallocErr |
9487 |
There is not enough malloc resources for the I/O structure exception handling. I/O on the reported cell is not available. |
TRAP-TYPE |
|
|
|
hpevtIoDiscEeCreatetreeErr |
9488 |
Error creating the structure for housing the I/O structured exception handling services and data. I/O is lost on the reporting cell. |
TRAP-TYPE |
|
|
|
hpevtIoDiscEeInitErr |
9490 |
Error detected while initializing the I/O structure exception handling services. |
TRAP-TYPE |
|
|
|
hpevtIoDiscEeContextErr |
9492 |
The structured I/O exception handling data structures have an error. All I/O on the reporting cell is not available. |
TRAP-TYPE |
|
|
|
hpevtIoDiscCreateSbaNodeErr |
9493 |
While setting up the internal SBA data and service an error was detected. All I/O for the reporting cell is not available. |
TRAP-TYPE |
|
|
|
hpevtIoDiscSbaAttachserviceErr |
9494 |
An error attaching firmware services to the internal structures was detected. All I/O on the reporting cell is not available. |
TRAP-TYPE |
|
|
|
hpevtIoDiscSbaInitnodeErr |
9495 |
System firmware detected an error initializing internal SBA data structures and services. This is usually an error with unavailable resources. |
TRAP-TYPE |
|
|
|
hpevtIoDiscSbaUnknownErr |
9496 |
The SBA type is unknown to the system firmware. The I/O on the reporting cell is not available. |
TRAP-TYPE |
|
|
|
hpevtIoDeviceMissing |
9497 |
An expected I/O device cannot be detected by the system firmware. |
TRAP-TYPE |
|
|
|
hpevtFabricRmtRoutePortBadReroute |
9498 |
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 |
TRAP-TYPE |
|
|
|
hpevtAgtPredictMemFail |
9652 |
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. |
TRAP-TYPE |
|
|
|
hpevtWinAgtLockedProperty |
9653 |
Server Agents SNMP branch is not responding due to a portion of the IPMI Management Subsystem being locked by another entity. |
TRAP-TYPE |
|
|
|
hpevtIoPciPowerOverloadErr |
9658 |
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. |
TRAP-TYPE |
|
|
|
hpevtMemSbeSeedingEnabled |
9659 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricWrFailedLinksTopoErr |
9661 |
Read failure while writing the number of failed links to the XBC. Data Field: Return Status (SUCCESS = 0, FAILURE = -1) |
TRAP-TYPE |
|
|
|
hpevtBootErrInitGroupCPaFields |
9663 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricAssertFabricHop |
9666 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootFailedReadingProfileCInIcm |
9668 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricHaltLinkDisableErr |
9670 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootGetSpiromGetSiblingErr |
9674 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuClockRatioMismatch |
9678 |
The clock ratio that the processor is running at does not match the clock ratio that manageability is reporting. |
TRAP-TYPE |
|
|
|
hpevtBootStopBootOverride |
9681 |
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. |
TRAP-TYPE |
|
|
|
hpevtVgaBiosRelocFail |
9682 |
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. |
TRAP-TYPE |
|
|
|
hpevtCompMatrixXsumError |
9685 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootGetDefaultRdrsFailed |
9695 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootGetCurrentRdrsFailed |
9696 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootReadPrefetchFailed |
9697 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootReadZlcoFailed |
9698 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootUpdateZlcoAndPrefetchFailed |
9700 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootErrorReadingZlcoFlagInPdProfile |
9701 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootFindCoreCellCmplxProfileAcErr |
9706 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootFindCoreCellConfigSelectErr |
9707 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootCellLclCantFindViable |
9708 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootCellRmtCantFindViable |
9709 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootFindCoreCellNotInRendez |
9710 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootFindCoreCellLclNotViable |
9711 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootFindCoreCellFabriclessPdErr |
9712 |
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 |
TRAP-TYPE |
|
|
|
hpevtRtcAccessError |
9719 |
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. |
TRAP-TYPE |
|
|
|
hpevtBootAccessCellArchErr |
9727 |
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. |
TRAP-TYPE |
|
|
|
hpevtXbcLogSizeErr |
9740 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcLogClearErr |
9741 |
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) |
TRAP-TYPE |
|
|
|
hpevtIodiscPciLogError |
9744 |
Error encountered while collecting PCI error logs. The result is some or all PCI error logs will be unavailable. |
TRAP-TYPE |
|
|
|
hpevtIodiscSbaLogError |
9745 |
Error encountered while collecting SBA error logs. The result is some or all SBA error logs will be unavailable. |
TRAP-TYPE |
|
|
|
hpevtXbcInitMaxRetries |
9746 |
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) |
TRAP-TYPE |
|
|
|
hpevtWinAgtPredictMemFailWarning |
9750 |
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. |
TRAP-TYPE |
|
|
|
hpevtWinAgtPredictMemFailCritical |
9751 |
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. |
TRAP-TYPE |
|
|
|
hpevtPciFatalBusError |
9754 |
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. |
TRAP-TYPE |
|
|
|
hpevtPciFatalDeviceError |
9755 |
A PCI card has been marked as 'fatal' by the operating system due to a device error. |
TRAP-TYPE |
|
|
|
hpevtBootErrorReadingFirstBootToken |
9768 |
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 |
TRAP-TYPE |
|
|
|
hpevtBootNonPaCellDetected |
9769 |
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. |
TRAP-TYPE |
|
|
|
hpevtFabricErrorsXbcClearWrErr |
9774 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricErrorsXbcClearRdGlblErr |
9775 |
Failed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status |
TRAP-TYPE |
|
|
|
hpevtFabricErrorsXbcClrLoSevErr |
9776 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricErrorsXbcClrHiSevErr |
9777 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricErrsCsrLogClrCopyBlk0Err |
9781 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricErrsCsrLogClrCopyBlk2Err |
9782 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricXbcLoStateResetErr |
9783 |
Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status |
TRAP-TYPE |
|
|
|
hpevtFabricClrXbcSym01Failure |
9784 |
The XBC Low Severity error logs were not cleared. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | number of failed clear attempts |
TRAP-TYPE |
|
|
|
hpevtFabricClrXbcIsLoCsrErrErr |
9785 |
Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status |
TRAP-TYPE |
|
|
|
hpevtFabricClrXbcRdLoLogStateErr |
9786 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricXbcHiStateResetErr |
9787 |
Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status |
TRAP-TYPE |
|
|
|
hpevtFabricClrXbcIsHiCsrErrErr |
9788 |
Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status |
TRAP-TYPE |
|
|
|
hpevtFabricClrXbcRdHiLogStateErr |
9789 |
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 |
TRAP-TYPE |
|
|
|
hpevtFabricXbcWriteableInvalidCsr |
9827 |
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 |
TRAP-TYPE |
|
|
|
hpevtDcnfgFsbInit |
9867 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuParams |
9868 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuIcache |
9869 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuDcache |
9870 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuCacheState |
9871 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuCacheMonitor |
9872 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuMca |
9873 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuDisableMca |
9874 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuSelfTest |
9875 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuL2Cache |
9876 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuDefValue |
9877 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuInReg |
9878 |
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. |
TRAP-TYPE |
|
|
|
hpevtDcnfgCpuProgReg |
9879 |
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. |
TRAP-TYPE |
|
|
|
hpevtNoMemSelfTest |
9896 |
There was not enough error free memory in the system to run the late selftests. |
TRAP-TYPE |
|
|
|
hpevtVrmFlt |
10065 |
The specified rail is reporting a fault. |
TRAP-TYPE |
|
|
|
hpevtVrmIoVltFlt |
10068 |
The specified pci vrm is reporting a voltage fault. |
TRAP-TYPE |
|
|
|
hpevtPwrBrickVltFlt |
10069 |
The specified pci power brick is reporting a voltage fault. |
TRAP-TYPE |
|
|
|
hpevtBkPlaneVrmVltFlt |
10103 |
The specified system backplane vrm is reporting a module voltage fault. |
TRAP-TYPE |
|
|
|
hpevtBkPlaneFlt |
10105 |
The specified system backplane rail is reporting a fault |
TRAP-TYPE |
|
|
|
hpevtMstrMpFailed |
10115 |
The master mp has failed. The slave has taken over management of the cabinet. |
TRAP-TYPE |
|
|
|
hpevtNvramAlloc |
10116 |
The NVRAM service was unable to satisfy an NVRAM allocation request. |
TRAP-TYPE |
|
|
|
hpevtRtcTimeReg |
10132 |
The RTC seems to not be updating its internal time registers. The cell cannot boot without the RTC. |
TRAP-TYPE |
|
|
|
hpevtPAAFltMx2 |
10159 |
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. |
TRAP-TYPE |
|
|
|
hpevtDataErrEncount |
10343 |
The event data details the error return status from Phase3BackToBackPrep. Internal debug only, this refers to an unexpected firmware error or data corruption. |
TRAP-TYPE |
|
|
|
hpevtConfigMaxMemory |
10351 |
The maximum memory supported by this system has been exceeded. The data field contains the amount of memory supported by the system. |
TRAP-TYPE |
|
|
|
hpevtFailDelBadPort |
10357 |
Failed to delete a bad port while routing the fabric. Data field indicates return status |
TRAP-TYPE |
|
|
|
hpevtFailDelBadEdge |
10358 |
failed to delete an edge that was found to be bad during routing |
TRAP-TYPE |
|
|
|
hpevtCommandMemBuf |
10361 |
A command to the memory buffer chip failed to complete. |
TRAP-TYPE |
|
|
|
hpevtUnsupprtArflsCsrRouteTravsble |
10375 |
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. |
TRAP-TYPE |
|
|
|
hpevtInvalidPortToTravsble |
10376 |
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) |
TRAP-TYPE |
|
|
|
hpevtUnbleRdXBCPortNghbr |
10377 |
Unable to read XBC port neighbor information. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBCPortUnexpctNghbrChip |
10378 |
XBC port with an unexpected neighbor chip type. Data field: (expected chip type) | (actual chip type << 16) | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBCPortHaveUnxpctNghbrID |
10379 |
An XBC port was found to have an unexpected neighbor ID. Data field: (expected NID) | (actual NID << 16) | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBCHaveUnexpctNghbrPrtConn |
10380 |
An XBC was found to have an unexpected neighbor port connection. Data field: (expected port) | (actual port << 16) | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtDataNotFndEdgLst |
10381 |
The expected data was not found in the Arches Fabric expected edge list. Data field is unused |
TRAP-TYPE |
|
|
|
hpevtXBCPrtUnxpctNgbrChip |
10382 |
An XBC port has an unexpected neighbor chip type. Data field: neighbor type found, bits [7:0], other bits unused |
TRAP-TYPE |
|
|
|
hpevtXBCtoXBCLnkDwn |
10384 |
A previously good XBC-XBC link was found to be down. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBCprtFndErrTravsbl |
10385 |
An XBC port was found to have a Fatal Error during traversability test. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtUblRdXBCrouteTbl |
10387 |
Unable to read the XBC route table. Data field: (route index) | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBCLnkNotConnCSRTravsbl |
10388 |
An XBC link was found to be not connected while testing CSR traffic traversability. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtErrRdAlrecAlbIdCsr |
10389 |
Error reading Skyline ALREC_ALB_ID CSR Data field: (Skyline port) | (Cell number << 56) |
TRAP-TYPE |
|
|
|
hpevtCirRoutFndTstXbcCsr |
10390 |
A circular route was found while testing XBC CSR traffic traversability. Data field: (target XBC << 32) | (cellNum << 56) |
TRAP-TYPE |
|
|
|
hpevtXBCRdErrAlrecAlbIdCsr |
10391 |
Error reading ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXBC-XBCPrtHavInvldChipCnn |
10392 |
An XBC-XBC port had an invalid chip type connection. Data field: (expected chip type) | (actual chip type << 32) |
TRAP-TYPE |
|
|
|
hpevtXBCToXBClnkFndFatErr |
10394 |
In ArfIsXbcRouteTraversable, an XBC-XBC link was found to have fatal errors. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtErrRdXbcRotTablCsr |
10396 |
Error reading an XBC ROUTE_TABLE CSR. Data field: route index | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXbcPrtFndUnxpctNgbrChip |
10398 |
An XBC port was found with an unexpected neighbor chip. Data field: expected chip type | (actual chip type << 32) |
TRAP-TYPE |
|
|
|
hpevtCelPrtPairNotFndGrphDat |
10401 |
A cell/port pair was not found in the expected graph data. Data field: (cellNum << 32) | CC portNum |
TRAP-TYPE |
|
|
|
hpevtArchFabFndLocCelLnkNotConn |
10402 |
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) |
TRAP-TYPE |
|
|
|
hpevtXbcErrRdRoutCsr |
10403 |
Error reading the ROUTEx CSR on the XBC. Data field: route index | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXbcUnablRdAlrecAlbIdCsr |
10404 |
Unable to read the ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtXbcPrtHasUnxpctNgbrChptype |
10405 |
An XBC port has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32) |
TRAP-TYPE |
|
|
|
hpevtCelToCelLnkHasUnxpctNgbrChpType |
10406 |
A Cell-Cell link has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32) |
TRAP-TYPE |
|
|
|
hpevtCelPrtPairNotExstGrphDat |
10407 |
The cell/port pair does not exist in the Arches Fabric expected graph data. Data field: CC port | (cellNum << 32) |
TRAP-TYPE |
|
|
|
hpevtCelToCelLnkConnUnxpctNgbrPrt |
10408 |
A Cell-Cell link is connected to an unexpected neighbor port. Data field: expected neighbor port | (actual neighbor port << 32) |
TRAP-TYPE |
|
|
|
hpevtCelToCelLnkConnUnxpctCel |
10409 |
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) |
TRAP-TYPE |
|
|
|
hpevtVmRetErrNonCohTbl |
10413 |
VM_FindAllRoutes returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (source cell << 32) | (target cell << 48) |
TRAP-TYPE |
|
|
|
hpevtNctTblWrtGlobLnkSelNonCohFail |
10414 |
In SetupNCTable, a write to the GLOBAL_LINK_SEL_NONCOH CSR failed. Data field: (data written to CSR) | (actual CSR data read << 32) |
TRAP-TYPE |
|
|
|
hpevtNctTblFailArfPhs3 |
10415 |
SetupNCTable failed in ArfPhase3. Data field: cell set passed in to SetupNCTable |
TRAP-TYPE |
|
|
|
hpevtPostRndevzFailPrepBckToBckSys |
10427 |
A failure occurred while prepping a back-to-back system for post-rendezvous Arches Fabric setup. Data field: return value from Phase4BackToBackPrep |
TRAP-TYPE |
|
|
|
hpevtArfPhs4UnablSetNonCohLnk |
10429 |
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 |
TRAP-TYPE |
|
|
|
hpevtUnablSetNonCohRout |
10431 |
Unable to set the Non-Coherent route. Data field: (sourceCell << 32) | (cell set passed in to SetupNCTable) |
TRAP-TYPE |
|
|
|
hpevtUnableSetCohRoutCel |
10432 |
Unable to setup the Coherent route table for a cell in our partition. Data field: (sourceCell << 32) | (cell set passed in to SetupCohTable) |
TRAP-TYPE |
|
|
|
hpevtErrWrtXbcRoutTblEnblMskCsr |
10435 |
Error writing the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (route set to disable) | (xbcNum << 32) | (xbc port << 48) |
TRAP-TYPE |
|
|
|
hpevtVertxRetUnxpctErrNonCohTbl |
10436 |
The Arches Fabric vertex module returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (sourceCell << 32) | (dest cell << 48) |
TRAP-TYPE |
|
|
|
hpevtWrtSkyGlobLnkSelCohFail |
10439 |
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 |
TRAP-TYPE |
|
|
|
hpevtUnablWrtXbcPrtCsr |
10475 |
Unable to write the XBC port scratch CSR with the routing state. Data field: (routing state) | (xbcNum << 32) | (portNum << 48) |
TRAP-TYPE |
|
|
|
hpevtUpsRestored |
10490 |
Input power to the specified UPS has been restored. |
TRAP-TYPE |
|
|
|
hpevtUpsExhausted |
10495 |
The system is being powered down as UPS power is exhausted. |
TRAP-TYPE |
|
|
|
hpevtSALFailRedzvsProcs |
10509 |
During SAL Machine Check handling, SAL fail to round up all the processor entering SAL Machine check handler. |
TRAP-TYPE |
|
|
|
hpevtSALFailClrCECLog |
10510 |
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. |
TRAP-TYPE |
|
|
|
hpevtErrRdXbcGlobSemphr |
10521 |
Error reading the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32) |
TRAP-TYPE |
|
|
|
hpevtFailWrtXbcGlobSemphr |
10524 |
Failed to write the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32) |
TRAP-TYPE |
|
|
|
hpevtFailRdXbcGlobSemphr |
10528 |
Failed to read the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32) |
TRAP-TYPE |
|
|
|
hpevtFailRelXbcGlobSemphr |
10532 |
Failed to release the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32) |
TRAP-TYPE |
|
|
|
hpevtFailGetAddrXbcToXbcLnk |
10558 |
Failed to get an address when opening XBC to XBC links. Data field is return value from GetAlbAddrBlk function. Internal debug only. |
TRAP-TYPE |
|
|
|
hpevtFailOpnFabLnk |
10559 |
Failed to open a fabric link. Data field: [31:0] - error status from OpenFabricLink [39:32] - XBC ID [51:44] - XBC port number |
TRAP-TYPE |
|
|
|
hpevtErrWrtXbcRetRout |
10560 |
Error when writing the XBC return route. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number |
TRAP-TYPE |
|
|
|
hpevtErrEnblXbcRetRout |
10561 |
Error enabling the XBC return route. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number |
TRAP-TYPE |
|
|
|
hpevtErrSetXbcToXbcLnkRoutX |
10565 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrRoutRemtside |
10566 |
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: |
TRAP-TYPE |
|
|
|
hpevtErrGetAddrRoutRemtXbc |
10567 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrGetNgbrInfo |
10568 |
Error getting the neighbor info. Data field: [31:0] - error status from AlbGetNeighborInfo [39:32] - XBC ID [51:44] - XBC port number |
TRAP-TYPE |
|
|
|
hpevtErrFindShrtRout |
10569 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrWrtRemtXbcRoutReg |
10570 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrEnblRoutRemtXbc |
10571 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrWrtRoutRegLocXbc |
10572 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrWrtLocXbcRoutRegRchRemtCel |
10573 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrEnblLocXbcRout |
10574 |
Error enabling the local XBC routes. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number |
TRAP-TYPE |
|
|
|
hpevtSynGrphFailPhs4 |
10617 |
SynchGraphs() failed during Arches Fabric Phase 4. Data field: return value from SynchGraphs() |
TRAP-TYPE |
|
|
|
hpevtVmVertxFailSyncGrph |
10619 |
VM_DeleteVertex() failed in SynchGraphs(). Data field: (vertex id << 32) | (vertex type << 56) | (return value from VM_DeleteVertex()) |
TRAP-TYPE |
|
|
|
hpevtVmEdgFailFncSyncGrph |
10620 |
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) |
TRAP-TYPE |
|
|
|
hpevtUnexpctErrCalVertxMod |
10621 |
Unexpected error when calling an Arches Fabric vertex module function. Data field: return value from vertex module function |
TRAP-TYPE |
|
|
|
hpevtUnexpctRetVertxModCopCelGrph |
10622 |
Unexpected return from an Arches Fabric vertex module function while copying a cell's graph. Data field: return value from vertex module function |
TRAP-TYPE |
|
|
|
hpevtChecksumNvmBad |
10625 |
The checksum in the memory area of NVM is bad. Memory NVM will be cleared. |
TRAP-TYPE |
|
|
|
hpevtSalandBmcTokenBad |
10628 |
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. |
TRAP-TYPE |
|
|
|
hpevtBkPlaneCable |
10629 |
Detected incompatibility between the cell board and the I/O backplane and/or I/O backplane cables. |
TRAP-TYPE |
|
|
|
hpevtFparUnusable |
10698 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWoutOfNvram |
10702 |
Firmware is out of NVRAM and cannot built the ILM memory slice device map |
TRAP-TYPE |
|
|
|
hpevtNvramCPUCorrupt |
10703 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramIOCorrupt |
10704 |
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. |
TRAP-TYPE |
|
|
|
hpevtNvramLocMemCorrupt |
10705 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWInconsistExist |
10706 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWUnableCreatefParsIO |
10707 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWUnableCreatefParsCLM |
10708 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWOutOfNvram |
10771 |
Firmware has run out of NVRAM and cannot create the needed variable(s) |
TRAP-TYPE |
|
|
|
hpevtFWLbaReconfigFail |
10772 |
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. |
TRAP-TYPE |
|
|
|
hpevtCpuModuleBadConfig |
10779 |
The CPU modules have been installed in an illegal configuration on the cell board. |
TRAP-TYPE |
|
|
|
hpevtCpuInvalidTerminator |
10780 |
An invalid CPU terminator card is installed on the cell board. The data field indicates the physical location of the offending socket. |
TRAP-TYPE |
|
|
|
hpevtInvocationSoftResetCode |
10793 |
Invocation of the soft reset code from an interrupt or similar vector, or improper locking/releasing of semaphores. |
TRAP-TYPE |
|
|
|
hpevtDataSm4SelfReset |
10794 |
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. |
TRAP-TYPE |
|
|
|
hpevtfParsfailRelseResrce |
10795 |
A reset of an fPar discovered that an fPar failed to release critical resources within a reasonable time. |
TRAP-TYPE |
|
|
|
hpevtPFMManyErrors |
10814 |
Significant numbers of corrected memory errors have been detected on the memory subsystem |
TRAP-TYPE |
|
|
|
hpevtPFMCorrecErrorCache |
10824 |
Corrected errors detected in the cache portion of the memory for a processor module |
TRAP-TYPE |
|
|
|
hpevtPFMErrTagMemProc |
10827 |
Corrected errors detected in the tag portion of the memory for a processor module |
TRAP-TYPE |
|
|
|
hpevtfParsNotEnableBoot |
10830 |
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. |
TRAP-TYPE |
|
|
|
hpevtfParsNotRecveOwnShip |
10832 |
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. |
TRAP-TYPE |
|
|
|
hpevtFWErrSetNvramVal |
10833 |
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. |
TRAP-TYPE |
|
|
|
hpevtUnablWrtXbcPrtRoutTblEnblMsk |
10842 |
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) |
TRAP-TYPE |
|
|
|
hpevtProcessIntrptUnRecoverble |
10853 |
An unrecoverable processor interrupt occurred. IPF firmware owned the processor interrupt vector table (IVT) at the time of the interrupt. |
TRAP-TYPE |
|
|
|
hpevtInadequateMemTofPar |
10936 |
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. |
TRAP-TYPE |
|
|
|
hpevtFailCollVertxInfo |
10937 |
Couldn't collect vertex information during Fabric Info call. Data Field: return status |
TRAP-TYPE |
|
|
|
hpevtFailFndEdgProcCall |
10940 |
Couldn't find an appropriate number of edges during a procedure call. Data Field: the number of edges found |
TRAP-TYPE |
|
|
|
hpevtUnablGetLnkHlthStatProcCall |
10945 |
Unable to get the link health state during a procedure call. Data Field: (cell num << 56) | (port << 44) | (xbc << 32) |
TRAP-TYPE |
|
|
|
hpevtFabDatFailCrcChk |
10946 |
The fabric data failed a CRC check. Data Field: (xbc port << 44 ) | (xbc << 32) | return status) |
TRAP-TYPE |
|
|
|
hpevtVmCollVertcFailUnexpct |
11032 |
VM_CollectVertices failed unexpectedly. Could possibly be a data corruption problem. Data field: (cell number << 56) | (return value from VM_CollectVertices) |
TRAP-TYPE |
|
|
|
hpevtUnablGenAlbArfSetCsr |
11033 |
Unable to generate an ALB address in Arches Fabric ArfSetDefaultCSRs() function. Data field:(cell number << 56) | (port number << 48) | (xbc ID < 32) | (return value) |
TRAP-TYPE |
|
|
|
hpevtSetDefCsrFailUnexpct |
11034 |
SetDefaultCSRs function failed unexpectedly. Arches Fabric was unable to set XBC CSRs to default values. Data field: return value from SetDefaultCSRs |
TRAP-TYPE |
|
|
|
hpevtEncntErrRout |
11038 |
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 |
TRAP-TYPE |
|
|
|
hpevtEncntErrRoutFab |
11039 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrEncntRoutFabPrvntRoutSel |
11040 |
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 |
TRAP-TYPE |
|
|
|
hpevtInvlPrtRetRoutXbcCcLnk |
11041 |
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 |
TRAP-TYPE |
|
|
|
hpevtErrEncntRoutFabPrvntRoutSelSw |
11042 |
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 |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr1p2LDOFault |
11452 |
System backplane power has reported a 1.2v LDO fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr2p5LDOFault |
11454 |
System backplane power has reported a 2.5v LDO fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr3p3HseFault |
11456 |
System backplane power has reported a 3.3v house keeping power fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr12Fault |
11459 |
System backplane power has reported a 12v power fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr3p3Fault |
11461 |
System backplane power has reported a 3.3v power fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr1p5Fault |
11463 |
System backplane power has reported a 1.5v power fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtSysBckPlnPwr2p5Fault |
11465 |
System backplane power has reported a 2.5v power fault. The data field contains the physical location of the fault. |
TRAP-TYPE |
|
|
|
hpevtRcsNoProvClkBckPln |
11468 |
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. |
TRAP-TYPE |
|
|
|
hpevtHsoFaultOrRemv |
11471 |
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. |
TRAP-TYPE |
|
|
|
hpevtOpClkNoMtchRcsHso |
11478 |
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. |
TRAP-TYPE |
|
|
|
hpevtHsoNoRedund |
11481 |
System backplane Hot Swap Oscillator (HSO) boards are NOT redundant. |
TRAP-TYPE |
|
|
|
hpevtHsoInsuff |
11482 |
System backplane Hot Swap Oscillator (HSO) boards are insufficient. |
TRAP-TYPE |
|
|
|
hpevtFailRdRcsHso |
11483 |
Failure reading Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device. |
TRAP-TYPE |
|
|
|
hpevtFailWrtRcsHso |
11484 |
Failure writing Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device |
TRAP-TYPE |
|
|
|
hpevtFailRdRpm |
11485 |
Failure reading the Reset and Power Monitors (RPM) EEPROM. Data field contains the physical location of the device. |
TRAP-TYPE |
|
|
|
hpevtFailWrtRpm |
11486 |
Failure writing the Reset and Power Monitors (RPM) EEPROM. Datafield contains the physical location of the device |
TRAP-TYPE |
|
|
|
hpevtFailRdOsp |
11487 |
Failure reading the Onboard System Programmers (OSP) EEPROM. Datafield contains the physical location of the device |
TRAP-TYPE |
|
|
|
hpevtFailWrtOsp |
11488 |
Failure writing the Onboard System Programmers (OSP) EEPROM. Datafield contains physical location of the device |
TRAP-TYPE |
|
|
|
hpevtSbsFaultStrt |
11489 |
Serial Bit Stream (SBS) fault on startup. An SBS fault results in the MOAB's not being configured correctly. |
TRAP-TYPE |
|
|
|
hpevtFailRdIObckPlnLpm |
11495 |
Failure reading IO backplane LPM. Datafield contains the physical location of the device. |
TRAP-TYPE |
|
|
|
hpevtFailWrtIOBckPlnLpm |
11496 |
Failure writing IO backplane LPM. Datafield contains physical location of device. |
TRAP-TYPE |
|
|
|
hpevtSysSoftViolateWellBhaveRule |
11515 |
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 |
TRAP-TYPE |
|
|
|
hpevtfParIsDisbleFrmBoot |
11529 |
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) |
TRAP-TYPE |
|
|
|
hpevtfParNotInstantiateFW |
11530 |
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. |
TRAP-TYPE |
|
|
|
hpevtfParNotHaveIOResrc |
11531 |
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. |
TRAP-TYPE |
|
|
|
hpevtLocCelUnablClrLnkOffBit |
11580 |
The local cell was unable to clear the link_off bit on at least one CC-CC link. Data field: return value of Phase3BackToBackPrep() |
TRAP-TYPE |
|
|
|
hpevtUnexpctErrSetNctTbl |
11582 |
An unexpected error occurred in SetupNCTable(). Data field: return value from SetupNCTable() |
TRAP-TYPE |
|
|
|
hpevtPhs4UnexpctFail |
11583 |
Phase4BackToBackPrep() unexpectedly failed. Data field: return value of Phase4BackToBackPrep() |
TRAP-TYPE |
|
|
|
hpevtRetValNctCohTbl |
11586 |
Data field: return value from SetupNCTable() or SetupCohTable() |
TRAP-TYPE |
|
|
|
hpevtMemAlloctFail |
11603 |
Memory allocation failed. The data is the size of the memory block which could not be allocated. |
TRAP-TYPE |
|
|
|
hpevtMemLockFail |
11604 |
Memory locking failed. The data is the size of the memory block which could not be locked. |
TRAP-TYPE |
|
|
|
hpevtMinProcReqMoreThanAvail |
11605 |
The minimum number of processors required is more than the number available. The data is the number of available processors. |
TRAP-TYPE |
|
|
|
hpevtVMNotHandlGuestOSPerf |
11607 |
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. |
TRAP-TYPE |
|
|
|
hpevtMMIOmapFndInfoInTble |
11700 |
The code which initializes the MMIO/IOP map found that the table already contained information. |
TRAP-TYPE |
|
|
|
hpevtTCGETorIOCTLFail |
11706 |
A TCGETS or TCSETS IOCTL failed. The errno status will be in a subsequent event. |
TRAP-TYPE |
|
|
|
hpevtStatCallPMANFail |
11707 |
A stat call on the PMAN failed. The next event contains the failure errno. |
TRAP-TYPE |
|
|
|
hpevtNotAbleCreatNodeForComm |
11710 |
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. |
TRAP-TYPE |
|
|
|
hpevtVMNotOpen |
11711 |
The vm device was created but cannot be opened |
TRAP-TYPE |
|
|
|
hpevtCreatThreadPMANFail |
11718 |
An attempt to create a thread on the PMAN has failed. The next event contains the Unix error number. |
TRAP-TYPE |
|
|
|
hpevtMemAllocFWTblFail |
11721 |
Memory allocation for a firmware table has failed. The data contains the name of the firmware table. |
TRAP-TYPE |
|
|
|
hpevtSFWFailAllotNVM |
11788 |
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. |
TRAP-TYPE |
|
|
|
hpevtFwUnexpctIntrnlErrVertx |
11840 |
Data field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0] |
TRAP-TYPE |
|
|
|
hpOsUnsupportedWmixedCpuRevs |
11850 |
The OS being booted is not supported in a partition containing a mix of processor stepping revisions. |
TRAP-TYPE |
|
|
|
hpevtFwUnexpctErrSetLnk |
11851 |
Data field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0] |
TRAP-TYPE |
|
|
|
hpOsBootDisabledWmixedCpuKeys |
11870 |
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. |
TRAP-TYPE |
|
|
|
hpevtSysFwErrUpdtLnk |
11885 |
System firmware experienced an error while updating the link sel value. Data field indicates return status |
TRAP-TYPE |
|
|
|
hpevtFabUnablGenSkyCsrAddr |
11904 |
Fabric was unable to generate a Skyline CSR address Data field: cell number [63:56] and return value from address function [31:0] |
TRAP-TYPE |
|
|
|
hpevtFwUnablGenSkyCsrAdrr |
11905 |
Firmware was unable to generate a Skyline CSR address. Data field: cell number [63:56] | return value [31:0] |
TRAP-TYPE |
|
|
|
hpevtNoOSBootRendez |
11932 |
Target CPU receives wakeup interrupt to join the OS but the OS_BOOT_RENDEZ entry point is invalid or none-existent |
TRAP-TYPE |
|
|
|
hpevtChksmFailOSBootRendez |
11933 |
The entry point for OS_BOOT_RENDEZ exists, but fails the checksum test performed by firmware |
TRAP-TYPE |
|
|
|
hpevtCellNotInit |
11964 |
Cell on line add/delete is not initialized and cannot be used. |
TRAP-TYPE |
|
|
|
hpevtFPARsCompBroke |
11966 |
In FPARs mode, cell on line add/delete depends on functionality in the FPARs component. This is either broken or missing. |
TRAP-TYPE |
|
|
|
hpevtEncntUnexptErrOLA |
11970 |
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] |
TRAP-TYPE |
|
|
|
hpevtMCAOccPriorPreMCA |
11971 |
This indicates an MCA happening before a previous MCA was not completely handled. |
TRAP-TYPE |
|
|
|
hpevtMCAInitEvtProc |
11972 |
This indicates an MCA event happening before a previous INIT event was not completely processed. |
TRAP-TYPE |
|
|
|
hpevtUnablFndBadEdg |
11974 |
Firmware was unable to find a bad edge in an untraversable route. Data Field: (destCell << 56 | port num < 44 | xbc num << 32 | return status) |
TRAP-TYPE |
|
|
|
hpevtUnknEntityDrwPwrBus |
11989 |
Some entity that is not known to the firmware, is drawing power from the bus bars. |
TRAP-TYPE |
|
|
|
hpevtSoftPartNotBoot |
12001 |
Rebooting the partition to nPars because a soft partition could not be booted. |
TRAP-TYPE |
|
|
|
hpevtUnablRotArndBrkLnk |
12008 |
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 |
TRAP-TYPE |
|
|
|
hpevtUncorrtMemEccErrOccr |
12017 |
Indicates that an uncorrectable ECC error has been encountered, and gives the physical location of the DIMM that had the error. |
TRAP-TYPE |
|
|
|
hpevtInvalidTPM |
12048 |
Invalid or unsupported TPM detected in the system. TPM is disabled. Data filed unused |
TRAP-TYPE |
|
|
|
hpevtTPMFailInit |
12049 |
Firmware cannot initialize the TPM. TPM related security feature are disabled Data field unused |
TRAP-TYPE |
|
|
|
hpevtCpuTempExceedHiThres |
12050 |
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. |
TRAP-TYPE |
|
|
|
hpevtInlckOpenPCIPwr |
12091 |
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 |
TRAP-TYPE |
|
|
|
hpevtFaltDetDropRegIO |
12101 |
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 |
TRAP-TYPE |
|
|
|
hpevtFaltDetDropRegManBckPlne |
12102 |
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 |
TRAP-TYPE |
|
|
|
hpevtCellNotCfgCLMMode |
12119 |
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. |
TRAP-TYPE |
|
|
|
hpevttDoblDramInvoke |
12120 |
Corrected memory errors have been detected. Double DRAM chip sparing events have been invoked. |
TRAP-TYPE |
|
|
|
hpevtErrCeLLIO |
12128 |
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. |
TRAP-TYPE |
|
|
|
hpevtMltPltFrmErrCellBckPln |
12129 |
Multiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the backplane. |
TRAP-TYPE |
|
|
|
hpevtMultPltFrmErrCeLLIO |
12131 |
Multiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the IO controller. |
TRAP-TYPE |
|
|
|
hpevtServIDNotMatchCab |
12132 |
The server identification information does not match the cabinet type. The server will not power on until this condition is resolved. |
TRAP-TYPE |
|
|
|
hpevtDupDimNumDetect |
12135 |
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. |
TRAP-TYPE |
|
|
|
hpevtMPLostUPS |
12143 |
The MP has lost communications with the UPS via SNMP over the LAN |
TRAP-TYPE |
|
|
|
hpevtUnrecovProcIFAinterptInFW |
12149 |
An unrecoverable processor interrupt occurred while in IPF firmware. The data value is the processor IFA. |
TRAP-TYPE |
|
|
|
hpevtUnrecovProcISRinterptInFW |
12150 |
An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor ISR. |
TRAP-TYPE |
|
|
|
hpevtDblChipSpareInvoked |
12153 |
System firmware has detected and corrected memory errors. Double chip sparing has been invoked to help mitigate this condition. |
TRAP-TYPE |
|
|
|
hpevtExtClkCablRemvFrmCPUCab |
12155 |
External clock cable has been removed from the CPU cabinet. The data field contains the physical location of the cabinet. |
TRAP-TYPE |
|
|
|
hpevtSysFabEncntLnkErr |
12156 |
System Fabric encountered a link error after opening up the fabric link |
TRAP-TYPE |
|
|
|
hpevtFatErrOnCelToFabPrt44I32I1 |
12157 |
Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32) | 1 |
TRAP-TYPE |
|
|
|
hpevtSysFWgetFabProblm |
12159 |
System firmware encountered fabric problems. Data Field: (crossbar port << 44) | (crossbar << 32) |
TRAP-TYPE |
|
|
|
hpevtFatErrCelLnkToFabPrt44I32 |
12160 |
Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32) |
TRAP-TYPE |
|
|
|
hpevtReqPwrOnDenied |
12164 |
The request to power on, either via MP user interface, power button, or other, was denied by the Onboard Administrator. |
TRAP-TYPE |
|
|
|
hpevtBladeFrcPWon |
12165 |
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. |
TRAP-TYPE |
|
|
|
hpevtMPNotRecvRespEnclMangr |
12168 |
The MP has repeatedly tried to communicate with the Onboard Administrator and has not received any response |
TRAP-TYPE |
|
|
|
hpevtComplxProfNoMtch |
12199 |
There are miscompares in the complex profiles between cells in a partition. Data field is unused, earlier events will give more detail. |
TRAP-TYPE |
|
|
|
hpevtIODevMissCore |
12204 |
An I/O device is missing from the Core I/O. Internal peripherals may be not accessible. |
TRAP-TYPE |
|
|
|
hpevtFparUnablNotiCPU |
12207 |
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 |
TRAP-TYPE |
|
|
|
hpevtFparUnablNotiCpuIOSAPICredir |
12208 |
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 |
TRAP-TYPE |
|
|
|
hpevtOSSetWtchDogTimerToTimeOut |
12210 |
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. |
TRAP-TYPE |
|
|
|
hpevtOSShtDwnDueMCA |
12217 |
An OS is shutting down due to an MCA (Machine Check Abort) or INIT. |
TRAP-TYPE |
|
|
|
hpevtCLUFWIncomptblSysType |
12222 |
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. |
TRAP-TYPE |
|
|
|
hpevtOnlnIdentHWProb |
12227 |
Diagnostics running under the OS have detected a problem with the identified hardware. |
TRAP-TYPE |
|
|
|
hpevtProcOvTemp |
12228 |
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. |
TRAP-TYPE |
|
|
|
hpevtWindWtchDogXpired |
12244 |
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 |
TRAP-TYPE |
|
|
|
hpevtMPCtrlReprtMPBusCommFail |
12251 |
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. |
TRAP-TYPE |
|
|
|
hpevtSFWDetFailOptmzFab |
12289 |
A failure was encountered while running the Fabric API to optimize the fabric. |
TRAP-TYPE |
|
|
|
hpevtROMFailAuthentc |
12352 |
The alternate ROM failed to authenticate. The current (primary) ROM will continue to be used |
TRAP-TYPE |
|
|
|
hpevtAltrntROMUnblSwap |
12354 |
The alternate ROM was successfully authenticated but the primary and alternate ROM could not be swapped. The current primary will still be used |
TRAP-TYPE |
|
|
|
hpevtCCLinkDown |
12394 |
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] |
TRAP-TYPE |
|
|
|
hpevtUnrecovProcIntOccr |
12395 |
An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor status register. |
TRAP-TYPE |
|
|
|
hpevtElectrncKeyProblm |
12399 |
The 'e-keying error' only occurs during the power-up if the SVB must be left off due to an electronic keying problem. |
TRAP-TYPE |
|
|
|
hpevtBldeInstImproperLoc |
12400 |
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. |
TRAP-TYPE |
|
|
|
hpevtbldeInstViolateEnclre |
12401 |
The 'ccoling error' occurs during the power-up if the SVB must be left off due to insufficient cooling; more fans may be needed. |
TRAP-TYPE |
|
|
|
hpevtUSBStorAttch |
12503 |
This trap is sent when a USB storage device has been attached. |
TRAP-TYPE |
|
|
|
hpevtUSBStorRemoved |
12504 |
This trap is sent when a attached USB storage device is removed. |
TRAP-TYPE |
|
|
|
hpevtMigratNotSuccess |
12550 |
A migration was not successful. This contains the migration phase when it was terminated. |
TRAP-TYPE |
|
|
|
hpevtPwrExptGreatrPwrBulk |
12586 |
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. |
TRAP-TYPE |
|
|
|
hpevtBulkPwrReduncLost |
12589 |
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. |
TRAP-TYPE |
|
|
|
hpevtACReduncLost |
12591 |
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. |
TRAP-TYPE |
|
|
|
hpevtFanCoolNotRedunc |
12593 |
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. |
TRAP-TYPE |
|
|
|
hpevtFanInsufficientInCoolDomain |
12595 |
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). |
TRAP-TYPE |
|
|
|
hpevtOSNotUseAllProcs |
12627 |
Operating system is not using all available processors for the current system. |
TRAP-TYPE |
|
|
|
hpevtFMPUnexpctRstHasRcv |
12863 |
A Fabric Message Processor (FMP) has unexpectedly reset. The system has recovered from the problem. |
TRAP-TYPE |
|
|
|