FPL_IndicationProvider

• WBEM Severity: Information
  
• Event Summary: Test event
  
• Event Description: This is a test message from the monitor to test the communication path from the monitor to the notification mechanism.
  
• Probable Cause: Other
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: No action required.
  
• Recommended Action 1: Null.
  
  
  

• WBEM Severity: Minor
  
• Event Summary: Bad OS MCA checksum
  
• Event Description: The OS has registered an OS_MCA vector, but it has not passed the checksum
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: OS has registered a bad OS_MCA vector or the data has been lost.
  
• Recommended Action 1: Reboot system to allow vector to be re-registered.
  
  
  

• WBEM Severity: Major
  
• Event Summary: BMC interface to IPMI failed
  
• Event Description: The BMC has failed testing and has been disabled.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: BMC firmware has locked up or the BMC is disabled.
  
• Recommended Action 1: Cycle system power and attempt boot again. If error re-occurs contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Boot cell launch EFI failure
  
• Event Description: SFW failed to launch EFI
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The system has failed to launch EFI because of an internal error.
  
• Recommended Action 1: Reboot or update System FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Monarch selection failure
  
• Event Description: Monarch selection has failed. Data: 0x11 = Calibration Failure 0x22 = Select Code Failure
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An internal error has caused monarch selection to fail.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU monarch collision
  
• Event Description: Monarch Collision has occurred
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unexpected error has occurred during monarch selection.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Boot cell virtualize EFI failure
  
• Event Description: SFW attempted to virtualize EFI and failed
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An internal error has occurred that prevented EFI from virtualizing.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Boot cell virtualize PAL failure
  
• Event Description: SFW was unable to virtualize PAL
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW was unable to virtualize PAL.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Boot cell virtualize SAL failure
  
• Event Description: SFW was unable to virtualize SAL
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW was unable to virtualize SAL.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Boot cell virtualize SALPROC failure
  
• Event Description: SFW was unable to virtualize SALPROC
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW was unable to virtualize SALPROC.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU structure initialization failed
  
• Event Description: SFW has failed initializing the CPU Struct. Data: Physical location of CPU that produced failure
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A CPU has failed the configuration process.
  
• Recommended Action 1: Replace CPU. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU failed early config
  
• Event Description: A CPU has failed early config.
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Other
  
• Cause 1: A CPU has failed the early configuration process.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU failed early self test
  
• Event Description: A CPU has failed early self test. Data: PAL Test State.
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A CPU has failed early self test.
  
• Recommended Action 1: Replace CPU. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU failed
  
• Event Description: SFW has detected that a CPU has failed. Data: The Physical Location of the CPU that failed
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A CPU has failed.
  
• Recommended Action 1: Replace CPU. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU failed late self test
  
• Event Description: 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. See Cause/Action.
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: For ZX1 systems, a Correctable Single Bit Memory error has caused CPU late self test to fail. It is possible the CPU is not faulty in this case. For zx2 systems, the CPU has failed self test.
  
• Recommended Action 1: Look for the event "MEM_CORR_ERR" from the last time the system was running. If you find these events, replace that DIMM(s) before replacing the CPU's. Replace DIMMs with excessive "MEM_CORR_ERR" first. If after replacing all suspect DIMMs this event is still seen, replace the CPU. Cause2: A CPU has failed. Action2: Replace CPU. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: The CPU late test has failed because of insufficient memory
  
• Event Description: The CPU late test has failed because of insufficient memory
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Insufficient memory
  
• Recommended Action 1: Increase memory and reboot.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Could not allocate memory for EFI image
  
• Event Description: Could not allocate memory for EFI image
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW could not allocate enough memory for EFI image.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI image corrupted
  
• Event Description: EFI image is corrupted
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI image is corrupted.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI not in fit table
  
• Event Description: EFI fit error
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI image is not in FIT.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: NVRAM test fail
  
• Event Description: EFI NVM has failed testing. The cell or system will now halt.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: NVM is corrupted or bad.
  
• Recommended Action 1: Clear NVM, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI Rom size bad
  
• Event Description: EFI Image Error
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI image is corrupt.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI Rom checksum error
  
• Event Description: EFI Image Error.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI image is corrupt.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: External interruption nest limit exceeded
  
• Event Description: The IVT interrupting nesting depth has been exceeded. This processor will be halted. Data: Number of the offending vector.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal FW error.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: External interrupt not serviced
  
• Event Description: An external interrupt has been requested and not serviced. Data: Number of the vector
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal FW error.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: External interrupt taken
  
• Event Description: An external interrupt has been taken. Data: Number of the vector taken.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An external interrupt has been taken
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Forward Progress Log (FPL) access failed
  
• Event Description: Access to the FPL has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: FPL access has failed, possibly due to BMC communication interruption. SFW will not send any events to the FPL until the system is rebooted.
  
• Recommended Action 1: Reboot or update System and BMC FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: PSR fetch failure
  
• Event Description: SFW was unable to read the CPU PSR. Data: Physical location of CPU
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW tried to read the Processor Status Register before the CPU data structure has been setup.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Cell or system halt
  
• Event Description: SFW has halted the cell or system
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal Error
  
• Recommended Action 1: contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU PAL incompatible with cpu
  
• Event Description: SFW has determined that PAL is not compatible with the current processors.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Incompatible PAL.
  
• Recommended Action 1: Update SFW or change processors
  
  
  

• WBEM Severity: Major
  
• Event Summary: Slave is incompatible with monarch
  
• Event Description: SFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor.
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: Incompatible processors.
  
• Recommended Action 1: Replace processors.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Interrupt clear failure
  
• Event Description: Interrupt clear failed during cell config
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Interrupt clear failed.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: System Event Log (SEL) access failed
  
• Event Description: SFW has determined that an IPMI event failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An IPMI event has failed.
  
• Recommended Action 1: Reset the BMC and reboot. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Trap taken
  
• Event Description: Data: interrupt vector table (IVT) Offset
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: This will follow other events indicating some type of IVT error.
  
• Recommended Action 1: This event is for debugging the address, other events will determine the user action.
  
  
  

• WBEM Severity: Major
  
• Event Summary: LDB State bad on entry
  
• Event Description: LDB state bad
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: No action is required
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Interrupt with interrupt collection (ic) bit clear
  
• Event Description: Interrupt context was lost. Data: interrupt number.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Interrupt context was lost because the ic bit was cleared.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Min-state registration failure
  
• Event Description: Registering of the processor min state save area with PAL has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Registering of the processor min state save area with PAL has failed.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Boot monarch timed out
  
• Event Description: SFW has determined the monarch has timed out. SFW is deconfiguring the CPU. Data: Physical Location of CPU
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The monarch has timed out.
  
• Recommended Action 1: No action is required. Replace CPU if problem persists, system will reboot after this event.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: PAL_B not in firmware interface table (FIT)
  
• Event Description: A PAL_B FIT error has occurred
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal Error or ROM is corrupted.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: SAL_B not in firmware interface table (FIT)
  
• Event Description: A SAL_B FIT error has occurred
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal Error or ROM is corrupted.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: NVRAM test fail
  
• Event Description: NVM has failed test. The system will halt
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: NVM is corrupt or bad.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Interrupt vector out of range
  
• Event Description: A interrupt vector has been requested out of the acceptable range. Data: Vector Number.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An internal error has occurred.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Pal proc error getting pal copy info
  
• Event Description: The PAL Copy Info call has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL_COPY_PAL_INFO call returned a failure.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Pal proc error copying pal to memory
  
• Event Description: Error copying PAL to memory
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: There has been an error copying PAL to memory.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Boot pal procedure (proc) failure
  
• Event Description: A PAL Proc has failed. This will halt the processor. Data: Physical Location of CPU
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal PAL Error.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Console device failure
  
• Event Description: A console device has failed. Data: Physical Addr of device that failed.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A console device has failed.
  
• Recommended Action 1: Reset console device/system.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Platform interface device failure
  
• Event Description: A console device has failed. Data: Physical Addr of device that failed.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A console device has failed.
  
• Recommended Action 1: Reset console device/system. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: platform scratch RAM test failed
  
• Event Description: Platform Scratch RAM has failed the test.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad or corrupt Scratch RAM.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU rendezvous failure
  
• Event Description: A CPU has failed to enter rendezvous. Data: Local CPU Number
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad or slow CPU.
  
• Recommended Action 1: Replace CPU.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Error extracting sal_b from rom
  
• Event Description: SFW could not extract SAL_B from the ROM
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: ROM Corrupt or unreadable.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Scratch RAM bad
  
• Event Description: Platform Scratch RAM has failed test.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad or corrupt Scratch RAM.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: IPMI System Event Log (SEL) is full
  
• Event Description: IPMI SEL full
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: IPMI SEL full.
  
• Recommended Action 1: Clear SEL through BMC or MP.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Slave wakeup before vector registered
  
• Event Description: No wakeup vector registered for processor Data: Physical location of CPU
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: No wakeup vector registered for processor.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: CPU failed rendezvous handler
  
• Event Description: Slave Rendezvous handler has failed. Data: Physical Location of CPU
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW is unable to determine the FSB speed.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Error building SMBIOS Tables
  
• Event Description: SFW failed to build the SMBIOS tables. This is a stop boot condition.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW failed to build the SMBIOS tables.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Trap nest limit exceeded
  
• Event Description: The trap nesting limit has been exceeded. Data: Vector Number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The trap nesting limit has been exceeded.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Trap not serviced
  
• Event Description: A trap has been requested and not serviced. Data: Vector Number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: A invalid trap has been requested or a trap has not been installed.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Trap taken
  
• Event Description: A trap has been taken. Data: Number of the vector taken.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: A trap has been taken
  
• Recommended Action 1: Reboot or update System FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Uncleared interrupt
  
• Event Description: At least one interrupt was not cleared. Data: The highest pending interrupt number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: At least one interrupt was not cleared.
  
• Recommended Action 1: No action is required.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unexpected external interrupt
  
• Event Description: An unexpected external interrupt has occurred. Data: External Interrupt Number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An unexpected external interrupt has occurred.
  
• Recommended Action 1: Reboot or update System FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Interrupt before redirection table set up
  
• Event Description: An interrupt has occurred before setting up the Interrupt Vector Table. Data: Interrupt Number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An interrupt has occurred before setting up the Interrupt Vector Table.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: CPU unexpected MCA
  
• Event Description: An unexpected MCA has occurred before MCAs are unmasked. Data: Local CPU Number.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unexpected MCA
  
• Recommended Action 1: Reboot or update System FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unexpected trap
  
• Event Description: An unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An unexpected trap has occurred. During System Firmware boot time this indicates the system has requested a trap that firmware has not registered. During OS run time it indicates the system has requested a trap that is not recognized in the OS's trap table.
  
• Recommended Action 1: If at FW boot time, reboot or upgrade System FW. If problem persists contact your HP representative for support. If at OS run time, verify that the OS has properly installed its trap handler, and that only valid traps are caused. Investigate what could cause the trap that is signaled by the event or why the OS has not properly installed the trap handler. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: CPU unknown boot error
  
• Event Description: SFW has detected an unknown error.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unknown error.
  
• Recommended Action 1: Reboot or update System FW. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: System Firmware failed to retrieve the PAL entry address.
  
• Event Description: SFW has detected a PAL Failure
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW has detected a PAL Failure.
  
• Recommended Action 1: Reboot, update SFW if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Expected MC vector unregistered
  
• Event Description: Expected Machine Check occurred, but the operating system has not registered an Expected Machine Check Handler.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Expected Machine Check Vector not registered at the time of an Expected Machine Check
  
• Recommended Action 1: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Information
  
• Event Summary: INIT initiated
  
• Event Description: 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
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Software has requested an INIT or the INIT button has been pressed.
  
• Recommended Action 1: No action is required.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Expected I/O host bridge is missing
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O slot failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O slot.
  
  
  

• WBEM Severity: Major
  
• Event Summary: LBA has unexpected number of I/O slots
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The firmware needs to be updated. An incorrect I/O backplane is installed.
  
• Recommended Action 1: Contact your HP representative to check the firmware and the I/O backplane.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O rope width does not match expected value
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The firmware needs to be updated. An incorrect I/O backplane is installed.
  
• Recommended Action 1: Contact your HP representative to check the firmware and the I/O backplane.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Found unexpected I/O host bridge
  
• Event Description: Firmware found an unexpected I/O host bridge. Firmware will configure the I/O host bridge. Data Field: Physical location of the unexpected I/O host bridge.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The firmware needs to be updated. An incorrect I/O backplane is installed.
  
• Recommended Action 1: Contact your HP representative to check the firmware and the I/O backplane.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI clock DLL error
  
• Event Description: 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.
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Failed or improperly inserted I/O card.
  
• Recommended Action 1: Remove or reseat the I/O card.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI hot plug controller failed
  
• Event Description: An I/O host bridge's hot-plug controller has failed. Firmware will de-configure the I/O host bridge. Data Field: Physical location of the I/O host bridge.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Hot-plug controller failure. I/O host bridge failure.
  
• Recommended Action 1: Contact your HP representative to check the hot-plug controller and the I/O host bridge.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Found unknown I/O rope width
  
• Event Description: Firmware attempts to configure an I/O controller rope to an unsupported width. Firmware will de-configure any I/O host bridge connected to the rope. Data Field: Physical location of the failed rope.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal firmware error.
  
• Recommended Action 1: Contact your HP representative to check the firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O LBA clear error failed
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O host bridge failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O host bridge.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O host bridge inaccessible because rope reset failed to complete
  
• Event Description: An I/O host bridge is inaccessible because an I/O controller rope reset failed to complete. Firmware will de-configure the I/O host bridge. Data Field: Physical location of the I/O host bridge.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O CEC failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O CEC.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Insufficient power to turn on PCI slot
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The power budget for the IO subsystem has been exceeded.
  
• Recommended Action 1: The IO config in the system is unsupported. Verify that the IO config installed in the system is one that is supported. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI bus walk unknown error
  
• Event Description: Firmware encountered an unexpected error while attempting to configure an I/O root port's PCIe 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 root port.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal firmware error.
  
• Recommended Action 1: Contact your HP representative to check the firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI bus walk resources exceeded
  
• Event Description: 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 which were unable to get their resources. 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 device.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unsupported I/O configuration.
  
• Recommended Action 1: Remove any unsupported I/O cards. Move the I/O card to another slot.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI bus unmap unknown error
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal firmware error.
  
• Recommended Action 1: Contact your HP representative to check the firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCIXCAP sampling error
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O host bridge failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O host bridge.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Power monitor failed to respond
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: BMC failure.
  
• Recommended Action 1: Contact your HP representative to check the BMC.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O rope reset failed to complete
  
• Event Description: An I/O controller rope reset did not complete within the expected time limit. Firmware will de-configure the I/O host bridge attached to the rope. Data Field: Physical location of the de-configured I/O host bridge.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O chipset failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O controller.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O SBA clear error failed
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O chipset failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O chipset.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI slot has incorrect default power state
  
• Event Description: 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.
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A non-compliant PCI[X] card is inserted in the slot. Such cards leaks power to the PCI[X] bus, which violates the PCI Bus Specification.
  
• Recommended Action 1: Replace the card with a compliant card.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI slot power on error
  
• Event Description: 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.
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The hot-plug controller has failed.
  
• Recommended Action 1: Contact your HP representative to check the hot-plug slot.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI slot's standby power failed
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O slot failure.
  
• Recommended Action 1: Reseat IO card. Replace IO card. If problem persists, contact your HP representative to check the I/O slot.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Found invalid PCIXCAP value
  
• Event Description: An I/O host bridge or hot-plug controller reported an illegal PCI[X] bus mode for its bus or slot, respectively. Data Field: Physical location of the failed I/O host bridge or the failed I/O slot.
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The I/O card is damaged or improperly inserted.
  
• Recommended Action 1: Replace or reseat the I/O card.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Unsupported rope frequency
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal firmware error.
  
• Recommended Action 1: Contact your HP representative to check the firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Unsupported host bridge type
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Firmware needs to be updated. An incorrect I/O backplane is installed.
  
• Recommended Action 1: Contact your HP representative to check the firmware and the I/O backplane.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Machine Check initiated
  
• Event Description: A Machine Check has been initiated
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A Machine Check has occurred.
  
• Recommended Action 1: Analyze cause of Machine Check using diag's and EFI tools.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Error in temporary mdt area
  
• Event Description: There has been a problem building the Memory Data Table (MDT).
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The memory area where the MDT is supposed to be built has an error in it, so the MDT cannot be built there.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Failed to find lmmio entry in mdt
  
• Event Description: There has been a problem building the Memory Data Table (MDT).
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The MDT table is bad because it did not have an LMMIO entry in it.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Memory page zero bad
  
• Event Description: Memory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Memory page 0 was slated for deallocation in the PDT.
  
• Recommended Action 1: FW is written such that this event should never be generated. If the user sees this event, please contact HP support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Failed to find space in mdt
  
• Event Description: There has been a problem building the Memory Data Table (MDT).
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: FW requested an entry in the MDT, and there wasn't a large enough chunk of contiguous memory for the requested size.
  
• Recommended Action 1: Reboot, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: NVM Media failure: info was not retrieved/logged
  
• Event Description: There has been a media failure.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The Error handler has failed to retrieve or log data due to a media failure.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Bus interface register test failed
  
• Event Description: Indicates that the chipset register test has failed. The data field contains the physical address of the failing register.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The chipset failed the register test.
  
• Recommended Action 1: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory ECC normal write/read test failed
  
• Event Description: After FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The DIMM that maps to address 0 is not seated properly
  
• Recommended Action 1: Check all of the DIMMs in the system and make sure that they are inserted fully into the slot with the retention mechanism in place
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM loading order error: DIMM deallocated
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location.
  
• Recommended Action 1: Refer to the user's manual for Memory loading instructions.
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM SPD checksum failed
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The DIMMs SPD EEPROM got corrupted.
  
• Recommended Action 1: Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM SPD error
  
• Event Description: Detected a error in DIMM SPD
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Detection of SPD fatal error type - various types
  
• Recommended Action 1: Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Unsupported memory DIMM type
  
• Event Description: A DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: A DIMM with an invalid DIMM type was found
  
• Recommended Action 1: Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: The DIMM type of this DIMM doesn't match with others in the DIMM group
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The DIMMs in the rank do not have the same DIMM type
  
• Recommended Action 1: Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: The DIMM type table is full. New DIMM type cannot be added.
  
• Event Description: The DIMM type table is full
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Too many different types of DIMMs in system
  
• Recommended Action 1: Reduce the number of different types of DIMMs in the system.
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM number not found in DMT Table
  
• Event Description: 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 chipselect of the rank/echelon caller is looking for.)
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Probable internal FW error
  
• Recommended Action 1: Reload System Firmware A: Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory ECC multiple-bit data error detection failed
  
• Event Description: The FW self test 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The CEC failed MBE detection.
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory ECC multiple-bit ECC error signaling failed
  
• Event Description: The FW self test 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The CEC failed MBE detection.
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory ECC single-bit data error detection failed
  
• Event Description: The FW self test 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The CEC failed SBE detection.
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory single-bit ECC error detection failed
  
• Event Description: The FW self test 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The CEC failed SBE detection.
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Insufficient memory for operation
  
• Event Description: Memory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest.
  
• Probable Cause: Output Device Error
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: FW detected an uncorrectable error below 192MB
  
• Recommended Action 1: No action is needed if the system boots. Replace the offending DIMM(s) if the system does not boot
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory address not found in memory address routing registers
  
• Event Description: Memory FW could not figure out which rank maps to the physical address specified in the data field maps to.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The address logged in the CEC doesn't map to a memory rank, possibly due to a SFW error or NVM corruption
  
• Recommended Action 1: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory Error Information not cleared
  
• Event Description: Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Software Error or CEC error
  
• Recommended Action 1: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Couldn't clear memory error logs
  
• Event Description: Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Software Error or CEC error
  
• Recommended Action 1: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory error clear failed
  
• Event Description: The Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Software error or CEC error
  
• Recommended Action 1: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM loading order error: DIMM deallocated
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location.
  
• Recommended Action 1: Refer to the user's manual for Memory loading instructions.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Generic memory firmware error
  
• Event Description: An error occurred that memory FW does not know how to handle.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Corrupt NVM or System firmware failure.
  
• Recommended Action 1: Reload SFW-System from the current package. If assistance required, contact support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Memory interleave generation failed
  
• Event Description: FW was unable to create a memory configuration with no errors in low memory to hand off to EFI.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW is outdated.
  
• Recommended Action 1: Update SFW.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory register test failed
  
• Event Description: The chipset's memory controller failed the register test. The data field contains the address of the register that failed self test.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal SFW error.
  
• Recommended Action 1: Update to most recent SFW.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: No memory DIMMs detected
  
• Event Description: Memory Discovery could not detect any DIMMs installed.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: No DIMMs were detected
  
• Recommended Action 1: Install DIMMs or Contact HP Support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: No memory found
  
• Event Description: FW could not continue because there are no valid memory ranks/echelons loaded.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: FW found memory, but it could not find a correctly loaded rank.
  
• Recommended Action 1: Before this event is sent, FW will output which ranks it is deallocating and why. Review the preceding events and refer to the users manual to correct the memory loading.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Cannot log memory error because PDT is disabled
  
• Event Description: The PDT has been disabled, and FW found memory errors during self test. 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: FW found memory errors during self test, but could not deallocate the page because the PDT is disabled.
  
• Recommended Action 1: Reenable the PDT by clearing NVM
  
  
  

• WBEM Severity: Major
  
• Event Summary: PDT is disabled
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Informational event indicating that FW will not use the PDT this boot.
  
• Recommended Action 1: No action is needed if user does not want to use the PDT, otherwise, clear NVM
  
  
  

• WBEM Severity: Major
  
• Event Summary: Error adding entry to PDT
  
• Event Description: Error writing entry into the PDT.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: NVM write error.
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Cannot add PDT entry-PDT full
  
• Event Description: The memory page deallocation table (PDT) is full.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: An attempt was made to add an entry to a full PDT.
  
• Recommended Action 1: Run the 'pdt' command from the EFI shell and remove/replace the DIMM that has the most PDT entries. If that doesn't work, contact HP support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory platform data update failure
  
• Event Description: Memory FW was unable to save or restore the original error configuration (including CEC error log and signal enable and CPU ECC detection). This event should never be seen in the field unless there is a FW problem
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Memory FW was unable to save or restore the original error configuration.
  
• Recommended Action 1: If this is seen, update SFW.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Can't find memory rank entry
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The rank structure that corresponds to the rankID in the data field could not be found in the Rank table, possibly due to NVM corruption.
  
• Recommended Action 1: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory error overflow:
  
• Event Description: More than one error type was detected when only one error type was expected.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: An error other than a memory error occurred during the memory test
  
• Recommended Action 1: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory forward progress code invalid
  
• Event Description: The forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The forward progress bits are invalid.
  
• Recommended Action 1: Upgrade to latest system firmware, or contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory error status invalid
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Non-memory errors were detected during the memory test that FW doesn't know how to handle.
  
• Recommended Action 1: Update to the latest SFW A: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Memory error summary bits invalid
  
• Event Description: The memory test summary bits are invalid. The data field is the test summary bits.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The memory test summary word is invalid
  
• Recommended Action 1: Update to the latest SFW. A: Contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: The DIMM distribution check was bypassed
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Control bit to skip DIMM distribution check is set.
  
• Recommended Action 1: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: The DIMM Loading Order check was bypassed
  
• Event Description: Indicates the memory control bit was set to skip the memory DIMM loading order check. The memory DIMMs may or may not be installed in a supported order or configuration. There is no user interface to this memory control bit. It is intended for internal testing use only and should never be seen in a customer system.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Control bit to skip DIMM loading order check is set.
  
• Recommended Action 1: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Looping on destructive memory tests
  
• Event Description: Indicates the memory control bit is set to enable continuous memory test. The system boot process will never proceed past the destructive memory test. There is no user interface to this control bit. It is intended for internal test use only and should never be seen in a customer system.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Should never be seen in a customer system. If seen would indicate potential NVM corruption.
  
• Recommended Action 1: Clear NVM by removing PDH data backup battery.
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM Set Check has been skipped
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Control bit to skip DIMM set check is set.
  
• Recommended Action 1: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: Serial Presence Detect (SPD) has been skipped
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: BYPASS_SPD_BIT is set
  
• Recommended Action 1: Report event to the Response Center Update PDC
  
  
  

• WBEM Severity: Major
  
• Event Summary: An Alternate Memory Config has been loaded into the system
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Control bit to use an alternate memory config are set.
  
• Recommended Action 1: Clear NVM Update SFW Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Major
  
• Event Summary: OS INIT address not registered
  
• Event Description: The OS_INIT vector has not been registered
  
• Probable Cause: Unknown
  
• Event Category: OS
  
• Event Sub-Category: Unknown
  
• Cause 1: The OS has not registered an OS_INIT vector.
  
• Recommended Action 1: No action is required. The OS has failed to register the vector or has chosen not to.
  
  
  

• WBEM Severity: Major
  
• Event Summary: OS MCA address not registered
  
• Event Description: The OS_MCA vector has not been registered
  
• Probable Cause: Unknown
  
• Event Category: OS
  
• Event Sub-Category: Unknown
  
• Cause 1: The OS has not registered an OS_MCA vector.
  
• Recommended Action 1: No action is required. The OS has failed to register the vector or has chosen not to.
  
  
  

• WBEM Severity: Major
  
• Event Summary: OS MCA did not correct the Machine Check
  
• Event Description: An Uncorrected Machine Check has occurred
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Uncorrected Machine Check.
  
• Recommended Action 1: If automated analysis has not occurred, use diagnostics or the MCA analyzer to examine MCA logs.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Found bad miscellaneous register
  
• Event Description: A PDH register has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A PDH register has failed.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: SAL_CHECK failed for an unknown reason
  
• Event Description: The handler for SAL_CHECK has failed for an unknown reason.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The handler for SAL_CHECK has failed for an unknown reason.
  
• Recommended Action 1: Contact support
  
  
  

• WBEM Severity: Major
  
• Event Summary: SAL_INIT failed for an unknown reason
  
• Event Description: The handler for SAL_INIT has failed for an unknown reason.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The handler for SAL_INIT has failed for an unknown reason.
  
• Recommended Action 1: Call support
  
  
  

• WBEM Severity: Major
  
• Event Summary: Unspecified memory interleave error
  
• Event Description: Indicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: FW encountered a fatal interleaving error.
  
• Recommended Action 1: Update SFW A: Contact HP support to troubleshoot the problem
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unexpected return to SAL_CHECK
  
• Event Description: Unexpected return to SAL_CHECK.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unexpected return to SAL_CHECK.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unexpected return to SAL_INIT
  
• Event Description: The SFW TOC vector (SAL_INIT) has been unexpectedly returned to.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SAL_INIT has been unexpectedly returned to.
  
• Recommended Action 1: 1. Attempt a reset 2. Cycle power 3. Contact support
  
  
  

• WBEM Severity: Degraded/Warning
  
• Event Summary: Firmware is adding a DEGRADED cpu node to the device tree.
  
• Event Description: 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.
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A CPU that is not fully functional is installed in the cell board.
  
• Recommended Action 1: Replace cpu indicated in data field of event.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: PD rendezvous will fail do to a Firmware Tree error
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Decode the ASCII string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resource is unavailable.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The current cell is not configured as part of the expected set
  
• Event Description: The currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: A bad complex profile exists. Correct and redistribute.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A remote CSR could not be read
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The current cell is too late to rendezvous with other cells
  
• Event Description: The currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: The current cell detected incompatible CPUs on another cell
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: Mixed CPU types are installed in the same partition. Remove them.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Current cell was too slow creating the local rendezvous set
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Cell too slow. Could be bad hardware. Check for other errors and reset.
  
• Recommended Action 1: If assistance is required, contact the HP Support Center.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Reporting cell was not included in the global cell set
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Fabric problem, Connection problem or timing problem. Reset the PD.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: No Core Cell can be selected in the PD.
  
• Event Description: No cells in the PD can be a core cell. This is fatal.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Firmware was unable to notify utilities of the core cell number
  
• Event Description: System Firmware was unable to notify utilities of the selected core cell number.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Communication with utilities is broken. Check for earlier errors or NVRAM problems.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Fabric code unable to find a needed service provider.
  
• Event Description: The fabric code is unable to find a service provider for a required banyan service.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The registry is corrupt or the ROM is incomplete.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error in a fabric Port
  
• Event Description: The fabric port specified in the data field had an error.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Parity error detected on read from fabric
  
• Event Description: An error occurred reading a CSR. The CSR address is displayed in the data field.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Hardware problem. Check connections and reset.
  
• Recommended Action 1: Contact HP Support personnel to analyze the crossbar chip.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error writing to Fabric
  
• Event Description: Error writing to Fabric. CSR data in data field.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: write to XBC failed
  
• Recommended Action 1: Contact HP Support personnel to check the XBC
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Crossbar slices are out of rev with each other.
  
• Event Description: 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
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad hardware configuration, different revisions of crossbars are installed.
  
• Recommended Action 1: Check crossbar revisions and ensure all installed crossbar revisions are the same. Replace the crossbar that is not in rev with the others.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Crossbar slices are configured poorly
  
• Event Description: Crossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Fatal configuration. Reconfigure the hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A CPU has taken over for the monarch CPU
  
• Event Description: A CPU has taken over as the monarch CPU.
  
• Probable Cause: Processor Problem (Internal Machine Error)
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: The previous monarch may be suspect.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Sram cannot be used on the cell
  
• Event Description: SRAM cannot be accessed on the cell board. Execution cannot continue.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: SRAM cannot be located or used on the cell board. Replace the cell board.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: The PDH arbiter hardware cannot be located.
  
• Event Description: The PDH Arbiter component/chip cannot be located or used.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: ROM is corrupt. Replace the rom or reprogram flash.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A required piece of PDH bus hardware cannot be contacted.
  
• Event Description: A required piece of PDH bus hardware cannot be contacted.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Verify all connections of PDH bus components or replace the cell board.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: IO Link software error was corrected.
  
• Event Description: IO Link Software error was corrected.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: IO link error was detected and corrected.
  
• Recommended Action 1: No action required, information only.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Bad parity data from RD Rtn FIFO on PIO Read (UNC)
  
• Event Description: Bad parity data from RD Rtn FIFO on PIO Read (UNC).
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad parity data from RD Rin FIFO on PIO Read.
  
• Recommended Action 1: Replace hardware.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Parity error in Reg FIFO Internal parity error.
  
• Event Description: Parity error in Reg FIFO Internal parity error.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace bad hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: TLB Fetch timeout
  
• Event Description: TLB Fetch timeout.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace bad hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Link presence goes away, FE
  
• Event Description: Link presence goes away, FE.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Link presence lost on SBA interface.
  
• Recommended Action 1: Replace faulty hardware.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA to SBA parity error on command, rope will go fatal
  
• Event Description: LBA to SBA parity error on command, rope will go fatal.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Bad hardware.
  
• Recommended Action 1: Replace I/O chassis.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Access to invalid TLB entry Requesting rope fatal
  
• Event Description: Access to invalid TLB entry Requesting rope fatal.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: An IO device is requesting access to an invalid TLB entry.
  
• Recommended Action 1: Driver problem -- debug driver.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Memory fetch timeout
  
• Event Description: Memory Fetch Timeout.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace bad hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error was encountered when Initializing the LBA.
  
• Event Description: An error was encountered when initing the rope number specified in the data field.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace the bad hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: LBA correctable Timeout Error was encountered.
  
• Event Description: LBA correctable timeout error was encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: An LBA correctable timeout error occurred.
  
• Recommended Action 1: No action necessary, the error was corrected. Information only.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: LBA uncorrectable Function Error was encountered.
  
• Event Description: LBA uncorrectable Function Error was encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace the damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: LBA uncorrectable Timeout Error was encountered.
  
• Event Description: LBA uncorrectable Timeout Error was encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: LBA uncorrectable timeout error encountered
  
• Recommended Action 1: Repair/replace faulty hardware.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Misc. uncorrectable error discovered on LBA.
  
• Event Description: Misc uncorrectable error discovered on LBA.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA encountered an uncorrectable parity error.
  
• Event Description: LBA encountered an uncorrectable parity error.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace the damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA Misc. Fatal Error encountered.
  
• Event Description: LBA misc. Fatal Error encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA Fatal function error encountered.
  
• Event Description: LBA Fatal function error encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA Fatal Parity error encountered.
  
• Event Description: LBA Fatal Parity error encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: An LBA fatal parity error encountered.
  
• Recommended Action 1: Repair/replace the faulty hardware.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: LBA Fatal Timeout Error Encountered.
  
• Event Description: LBA Fatal timeout error encountered.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace damaged hardware.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: DIMM SPD Extended Checksum Failure
  
• Event Description: The calculated and compared Checksums of the SPD EEPROM don't match.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Replace any bad dimms.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: Options header checksum error encountered.
  
• Event Description: The Options component encountered a header checksum error. The actual data is in the data field of the chassis code.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reinitialize the options data.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: Options data checksum error was encountered.
  
• Event Description: The Options service data had a bad checksum. Actual data is in the data field.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Verify options data and reinitialize if necessary.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Internal inconsistency in the interleave tables.
  
• Event Description: Internal inconsistency in the interleave tables.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reconfigure and Reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: CellInfoList is not NULL.
  
• Event Description: The CellInfoList is not null and was expected to be. There has been an error in interleaving.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error in constructing the Memory Descriptor.
  
• Event Description: Error in constructing the Memory Descriptor.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Unable to update the local memory layout
  
• Event Description: Unable to update the local memory layout.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A required address was not found within a mapped address.
  
• Event Description: A required address was not found within a mapped address in the PDT.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Failure to install a Partition level PDT.
  
• Event Description: Failure to install a partition level PDT. Errors prevented it.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reset
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A critical resource could not be found or is unusable
  
• Event Description: 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
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Determine the failing component or hardware from the data field as described and replace.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Internal firmware programming error.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: A semaphore could not be obtained
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1:
  
• Recommended Action 1: Reset system to clear the semaphore Try reinitializing NVRAM. If problem persists, contact engineering.
  
  
  

• WBEM Severity: Major
  
• Event Summary: The requested NVRAM block was not found.
  
• Event Description: The requested NVRAM block was not found. The ID that was not found is displayed in the data field.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: No Action Required. Firmware can allocated space for the block.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: The requested NVRAM block is locked.
  
• Event Description: The block id specified in the data field is locked.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Retry the operation.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: Firmware tried to unlock a NVRAM block that was already unlocked.
  
• Event Description: Firmware tried to unlock a NVRAM block that was already unlocked. Data field contains the block ID.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: No action required.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The Header in NVRAM was not found
  
• Event Description: The header in the NVRAM space was not found.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: NVRAM cannot be used. It must be initialized first. Firmware will attempt the initialization.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The Freelist used for NVM block allocation is corrupt.
  
• Event Description: The Freelist used vor Non-Volatile Memory allocation is corrupt.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Band NVRAM/ reinitialize.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Firmware is preparing to reset for reconfiguration.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: This can be caused by many conditions including a bad complex profile, a bad hardware configuration, a cell arriving late to the rendezvous point. A cell not being able to rendezvous. Reconfiguration from partition manager is recommended.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: An error was encountered communicating with utilities during PD rendez.
  
• Event Description: During PD rendezvous, system firmware encountered a problem sending commands to the utilities system. This will prevent a fully functional PD from being created.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Verify communications with the utilities system.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Forward Progress is stopping. The Cell or System will not boot further.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: An error occurred which triggered system firmware to cease making forward progress. The CPU is put into a spin loop so that external debugging can take place. See earlier event ids to help determine the cause of the error. Also note that the Error Response Mode is likely to have directed firmware to HALT.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: No console is available for the DUI to use.
  
• Event Description: The DUI (Developers User Interface) was entered, but there is no console available for the interface.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: DUI was entered before the console is available. DUI will exit and processing will continue.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error Processing encountered an unrecoverable error
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Decode the ASCII message and correct the problem.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: System is unable to complete the Reset For Reconfiguration request.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Delay the request for reconfiguration until after the PD has been released from Sinc BIB.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The cell is not able to reach all requested cells through the fabric.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Fabric wasn't able to route to all cells described in the complex profile correctly due to a hardware problem. Some of the cells are unreachable. Update the complex profile or correct the hardware problem.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: LBA has unexpected number of I/O Slots.
  
• Event Description: 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)
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unsupported I/O configuration.
  
• Recommended Action 1: Remove the I/O cards below the specified PCI-to-PCI bridge.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Console device failed to connect.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Debugging event, not for release.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: Copying memory test code failed.
  
• Event Description: This event is unused
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: Memory test code located in main memory has been corrupted
  
• Recommended Action 1: Contact HP support personnel to troubleshoot the problem
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Multiple Core Cells have been discovered in the same PD
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Verify that the complex profile is correct and reset the partition.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The utilities component encountered an error when sending a command to the MP
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Verify the utilities system is connected correctly and reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: Error received after issuing the Retrieve Cell Slot State command
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Make sure the MP is connected and reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: This indicates that all the cpus in the cell did not rendezvous during the MCA.
  
• Event Description: This denotes the fact that all the cpus in the cell did not rendezvous.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: When this happens the cell will step through some of the error logging code on its own and then reset itself.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: This indicates that it does not have any access to the PD.
  
• Event Description: This chassis code indicates that the cell does not have any access to a PD.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Forward Progress indicator; the cell will independently step through the error logging steps before it resets itself.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: This indicates the loss of lockstep during the MCA path.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: The cell will take up a few more error logging steps independently before resetting itself.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The PD level cell rendezvous failed.
  
• Event Description: This indicates that some of the cells did not show up during the PD level rendezvous.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: This means that the cells will independently step through some of the error logging code and then reset themselves.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI parity error detected.
  
• Event Description: 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).
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O bus parity error.
  
• Recommended Action 1: Consult the error logs for additional information. Determine and replace the failed I/O device.
  
  
  

• WBEM Severity: Major
  
• Event Summary: PCI system error detected
  
• Event Description: 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).
  
• Probable Cause: I/O Device Error
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: I/O host bridge failure.
  
• Recommended Action 1: Contact your HP representative to check the I/O host bridge.
  
  
  

• WBEM Severity: Major
  
• Event Summary: I/O host bridge is deconfigured
  
• Event Description: Firmware has deconfigured an I/O host bridge due to an error (see earlier error event). Data Field: Physical location of the deconfigured I/O host bridge.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: See earlier error event.
  
• Recommended Action 1: See earlier error event.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Firmware was unable to publish the Partition Profile
  
• Event Description: Firmware tried to default the Partition (Group C) complex profile and encountered an error.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Manageability may be unavailable to update the profiles. Check the connections are reset.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The reporting cell is not configured to be in a PD.
  
• Event Description: The Reporting Cell is not configured to be in a PD, according to Complex Profile Group A.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Run parmgr to configure the cell into a PD and reset the PD or add the cell.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: DIMM thermal loading order warning
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The current DIMM loading order does not follow the guidelines in the user manual
  
• Recommended Action 1: Rearrange the DIMMs to follow the loading order specified in the Maintenance and Operation Manual
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: The PD cannot boot, a majority of cells did not arrive at Rendezvous
  
• Event Description: Not enough cells made the Rendezvous for boot to continue. The rules are listed in the cause action section.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PD Rendezvous Boot Rules: If greater than 50% of the assigned cells are rendezvoused, we will boot. If less than 50% of the assigned cells are rendezvoused, don't boot. If exactly 50% of the assigned cells are rendezvoused, including all of the preferred core cells, we will boot. If exactly 50% have rendezvoused, and there is a specified preferred core cell not rendezvoused, don't boot. If exactly 50% have rendezvoused, and there are no preferred core cells, don't boot. If any of the above apply in preventing the boot. Reconfigure the PD and reboot.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: INIT: Monarch failed in slave rendezvous
  
• Event Description: SFW's INIT handler failed to rendezvous the processors. Data field contains function return value.
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A processor has failed rendezvous.
  
• Recommended Action 1: Attempt a reboot. If the problem persists, examine the system event log for processor-related events.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: I/O error log/clear error
  
• Event Description: SFW's Machine Check Handler was unable to log or clear I/O error registers.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW's Machine Check Handler was unable to log or clear I/O error registers.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: MCA to BERR escalation not supported by PAL
  
• Event Description: Cannot escalate an MCA to BERR
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Cannot escalate an MCA to BERR.
  
• Recommended Action 1: Analyze Machine Check Logs using diagnostic tools and EFI tools.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: MCA to BINIT escalation not supported by PAL
  
• Event Description: Cannot escalate an MCA to BINIT.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL has indicated that it cannot escalate an MCA to BINIT.
  
• Recommended Action 1: If automated analysis has not occurred, use diagnostic tools or the MCA analyzer to examine the MCA log.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Machine Check (MC): failed to get the feature set from PAL.
  
• Event Description: SFW failed to get the feature set from PAL.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW failed to get the feature set from PAL
  
• Recommended Action 1: Update firmware to get newer PAL that support the PAL_GET_FEATUREs call.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: Previous PAL rendezvous failed; rebooting
  
• Event Description: PAL Failed to rendezvous the processors during a MCA.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL Failed to rendezvous the processors during a MCA.
  
• Recommended Action 1: Review error logs to determine cause of MCA. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: Set PAL features failed
  
• Event Description: SFW failed to set the feature set in PAL.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: SFW failed to set the feature set from PAL.
  
• Recommended Action 1: Update SFW. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC: Monarch failed in slave rendezvous
  
• Event Description: SFW's MCA Handler has failed to rendezvous all the slaves Data field contains the return value from the rendezvous call.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: A slave failed to rendezvous.
  
• Recommended Action 1: Reboot if necessary, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: Rendezvous vector out of range
  
• Event Description: A bad rendezvous vector has been registered.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: A bad rendezvous vector has been registered.
  
• Recommended Action 1: Reboot if necessary to re-register vector, if problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: No MC monarch
  
• Event Description: No Machine Check Monarch exists, exiting MC Rendezvous.
  
• Probable Cause: Unknown
  
• Event Category: OS
  
• Event Sub-Category: Unknown
  
• Cause 1: Software is making a SAL_MC_RENDEZVOUS call when it shouldn't.
  
• Recommended Action 1: Just a warning that software or OS is making a call when it shouldn't. SFW will ignore the call when this happen. Need to fix OS or software to not make the SAL_MC_RENDEZVOUS when there is no monarch processor chosen.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: No wakeup registered
  
• Event Description: The OS has not registered a wake-up mechanism for rendezvous.
  
• Probable Cause: Unknown
  
• Event Category: OS
  
• Event Sub-Category: Unknown
  
• Cause 1: OS or Software is calling SAL_MC_RENDEZ without registering a method to wake-up the processor.
  
• Recommended Action 1: OS or Software needs to be fixed to register a wake-up mechanism before calling SAL_MC_RENDEZ.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: MCA escalation not supported by PAL
  
• Event Description: PAL call failed to set the BINIT escalation bit
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL does not support the call to escalate further local MCA to global MCA.
  
• Recommended Action 1: Update SFW with contain a new PAL that support this feature. If no new PAL that support this feature, no action should be taken further.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: Get PAL features failed
  
• Event Description: The PAL call PAL_GET_FEATURES has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL does not support call to get the processor feature set during processor rendezvous.
  
• Recommended Action 1: Update system firmware with a new PAL that support the PAL_GET_FEATURES call.
  
  
  

• WBEM Severity: Major
  
• Event Summary: MC_RENDEZVOUS: Set PAL features failed
  
• Event Description: The PAL call PAL_SET_FEATURES has failed.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL does not support call to set the processor feature set during processor rendezvous
  
• Recommended Action 1: update system firmware with new PAL that support the PAL_SET_FEATURE call.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Internal Firmware Programming Error from the EFI portion of the firmware
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: memory extender loading order error
  
• Event Description: The Memory extenders have not been loaded in the correct order.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: The memory extenders have not been loaded in the correct order.
  
• Recommended Action 1: Load the Memory extenders according to the users manual.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Inconsistency in the length of the extensible SAL interface (ESI) table
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Table entries corrupted.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: The computed checksum for extensible SAL interface ESI Table incorrect.
  
• Event Description: The computed checksum for the ESI (Extensible SAL Interface) table is not zero as expected. EFI is halting. Data Field: the computed checksum.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Table's checksum miscomputed.
  
• Recommended Action 1: Upgrade system firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: ESI Table contains an unsupported entry type.
  
• Event Description: EFI found an unsupported entry type within the ESI (Extensible SAL Interface) Table. Data Field: unknown type.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Corrupted table.
  
• Recommended Action 1: Reboot system. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: A GUID was larger than the expected 128 bits.
  
• Event Description: EFI was attempting to output a GUID in the EFI_GUID_HALF1 and EFI_GUID_HALF2 events which was larger than 128 bits. The data field contains the actual length of the GUID in bytes.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Inconsistency in EFI firmware.
  
• Recommended Action 1: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI is halting
  
• Event Description: EFI is halting. Look for the cause of the halt in preceding events. Data Field: the "halt" (0x0F) major change in system state code.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unknown.
  
• Recommended Action 1: examine preceding events for problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: chipspare not supported on quad
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: Memory
  
• Event Sub-Category: Unknown
  
• Cause 1: User installed a x8 DIMM in a system configured for chipspare.
  
• Recommended Action 1: If user requires Chipspare, replace the DIMM with a x4 DIMM. If Chipspare is not required, then no action is required.
  
  
  

• WBEM Severity: Major
  
• Event Summary: EFI internal error detected resulting in execution of ASSERT macro
  
• Event Description: EFI has detected an internal error. The actual error is unspecified by this event. Examine previous events and console output for possible explanations.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The cause is unknown.
  
• Recommended Action 1: Look at previous events and ASCII information in this event for more information. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI has executed the 'break' shell command.
  
• Event Description: EFI has executed the "break" shell command. EFI is halting. The "break" command is currently implemented as an infinite loop to halt EFI.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Executing the "break" command.
  
• Recommended Action 1: Check for user entering "break" command. Check for shell scripts using the 'break' command.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI USB interrupt service has detected the host controller is hung
  
• Event Description: The EFI USB interrupt service has detected the host controller is hung. EFI is halting.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Problem with USB controller.
  
• Recommended Action 1: Reset the card containing the USB interface to restart the controller. Contact your HP representative to check the USB interface.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: The EFI/SAL handoff structure's version does not match EFI expectations
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI/SAL firmware mismatch.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unable to obtain access to all RTC SAL services
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI unable to create internal event. EFI out of resources.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Unable to obtain access to all SAL timer services
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Not all expected services are available. Mismatch between EFI and SAL versions. Internal EFI error.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI unable to start the periodic timer
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal system firmware error.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: No I/O port space region found in the memory data table (MDT)
  
• Event Description: EFI did not find an I/O port space region in the MDT. EFI is halting.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: EFI/SAL handoff structure corrupted.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: EFI reached an unimplemented section of code
  
• Event Description: EFI reached an unimplemented section of code. EFI is halting. Data Field: Unique identifier indicating the location reached within the code.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Reached unimplemented firmware.
  
• Recommended Action 1: Upgrade system firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: EFI unable to read current speedy boot settings
  
• Event Description: 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..
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: BMC not functioning properly.
  
• Recommended Action 1: Reset the BMC. Contact your HP representative to check the BMC.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Prohibited SAL callback attempted
  
• Event Description: A SAL Callback was attempted. This is not permitted. EFI is halting. Data Field: index of the function that was being called.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal EFI error.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: EFI unable to determine frequency base of the CPU interval timer
  
• Event Description: 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).
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Internal system firmware error.
  
• Recommended Action 1: Upgrade system firmware.
  
  
  

• WBEM Severity: Major
  
• Event Summary: EFI system events already initialized
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Multiple attempts to initialize system events, EFI internal error.
  
• Recommended Action 1: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Unable to create internal virtualization event while initializing IPMI events
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Out of resources. Internal EFI error.
  
• Recommended Action 1: Reboot system. Upgrade system firmware.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: There was an error creating or initializing the FPGA node in firmware
  
• Event Description: An error was detected while initializing the FPGA node and services associated with the PDH.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Unable to properly initialize a system firmware node
  
• Recommended Action 1: Check for other errors in the system first. Invalidate NVM and retry to boot. Get the latest firmware release.
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error encountered setting up the pdh arbiter node or service.
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: This is usually a symptom of an earlier problem. Check to be sure the pdh node was initialized into the tree correctly.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: The PDH component encountered an error dealing with a property on a node.
  
• Event Description: The PDH service was unable to either get or set the property specified in the data field as an ASCII message.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: This is usually due to a memory allocation problem. Verify that sram is usable and there is memory available.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error creating the acpi_hw node.
  
• Event Description: PDH encountered an error creating the ACPI Hardware Node in the device tree or installing its properties.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: May be out of malloc space or a previous tree error prevented this from being successful. Check for earlier errors.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Critical
  
• Event Summary: Error encountered creating or initializing the ipmi node
  
• Event Description: The PDH service encountered an error while creating the ipmi node or adding properties to it. The status is in the data field.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: Possibly out of memory or an earlier error left the tree in an unusable state.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: Installed processors are not of compatible models or families
  
• Event Description: Installed processors are not of compatible models or families
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: Installed processors are not of compatible models or families
  
• Recommended Action 1: Replace processors with compatible ones if all processors are to be used.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: caches sizes are inconsistent
  
• Event Description: Processors with different cache sizes are installed
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: Processors with different cache sizes are installed in the system.
  
• Recommended Action 1: Replace processors with compatible ones if all processors are to be used.
  
  
  

• WBEM Severity: Major
  
• Event Summary: processor steppings are not equal
  
• Event Description: Processors with different steppings are installed. Steppings are reported in the BOOT_CPU_CONFIG event.
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: If desired, replace processors with equal stepping ones, this is a warning only.
  
• Recommended Action 1: -
  
  
  

• WBEM Severity: Major
  
• Event Summary: selecting new monarch
  
• Event Description: SFW is selecting a new monarch processor due to compatibility problems.
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: The monarch processor was not the lowest stepping processor installed within the cell.
  
• Recommended Action 1: No action is required. FW takes action automatically. To avoid this event, be sure that the monarch processor is the lowest stepping of processor in the system.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: monarch not lowest stepping
  
• Event Description: The monarch stepping is not equal to the lowest installed CPU stepping.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: The monarch processor has a stepping that is greater than a slave processor installed in the system.
  
• Recommended Action 1: No action is needed. If problem persists, update System FW or contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: processors are over clocked
  
• Event Description: A CPU's FSB frequency is overclocked. Data: Local CPU Number.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: FSB speed faster than the capabilities of the processors
  
• Recommended Action 1: If multiple CPU's report this issue, check the BMC. If only one reports this issue, replace the CPU. If problem persists, contact HP support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: cpu access error on processor info area
  
• Event Description: There was an error reading the info ROM area of the CPU. Data: CPU Physical location
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: An early version of CPU or a bad info ROM.
  
• Recommended Action 1: Reboot. If problem persists contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: PAL A was not executed - HALT
  
• Event Description: PAL_A has not been executed and control has been transferred back to SAL_B.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL_A has not been executed.
  
• Recommended Action 1: Contact your HP representative for support.
  
  
  

• WBEM Severity: Fatal/Nonrecoverable
  
• Event Summary: PAL B was not executed - HALT
  
• Event Description: PAL_B has not been executed and control has been transferred back to SAL_B.
  
• Probable Cause: Unknown
  
• Event Category: System Firmware
  
• Event Sub-Category: Unknown
  
• Cause 1: PAL_B has not been executed.
  
• Recommended Action 1: Contact your HP representative for support.
  
  
  

• WBEM Severity: Major
  
• Event Summary: Prototype CPU installed
  
• Event Description: Data: Lower 32 bits have Local CPU Number
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A Prototype CPU is installed.
  
• Recommended Action 1: Replace CPU with a production CPU.
  
  
  

• WBEM Severity: Major
  
• Event Summary: final boot rendezvous monarch watchdog timeout
  
• Event Description: Data: Monarch's Local CPU Number
  
• Probable Cause: Unknown
  
• Event Category: Processor
  
• Event Sub-Category: Unknown
  
• Cause 1: A watchdog timer has expired and determined that a monarch is dead.
  
• Recommended Action 1: Reboot, if problem persists, replace CPU.
  
  
  

• WBEM Severity: Major
  
• Event Summary: A multi-bit error was found while reading a XBC CSR
  
• Event Description: 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.
  
• Probable Cause: Unknown
  
• Event Category: System Hardware
  
• Event Sub-Category: Unknown
  
• Cause 1: Possibly bad link or cell connection.
  
• Recommended Action 1: Reset partition, and check hardware associated with event data.