Hewlett-Packard
IPMI Forward Progress Log Monitor (Events)
Event 200
- Severity: MAJOR
- Event Summary: Bad OS MCA checksum
- Event Class: System
- Problem Description:
The OS has registered an OS_MCA vector,
but it has not passed the checksum
- Cause / Action:
Cause: OS has registered a bad OS_MCA vector
or the data has been lost. Action: Reboot system to allow vector to be
re-registered.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 201
- Severity: MAJOR
- Event Summary: BMC interface to IPMI failed
- Event Class: System
- Problem Description:
The BMC has failed testing and has been
disabled.
- Cause / Action:
Cause: BMC firmware has locked up or the BMC
is disabled. Action: Cycle system power and attempt boot again. If error
re-occurs contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 203
- Severity: FATAL
- Event Summary: Boot cell launch EFI failure
- Event Class: System
- Problem Description:
SFW failed to launch EFI
- Cause / Action:
Cause: The system has failed to launch EFI
because of an internal error.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 204
- Severity: MAJOR
- Event Summary: Monarch selection failure
- Event Class: System
- Problem Description:
0x11 = Calibration Failure 0x22 = Select
Code Failure
- Cause / Action:
Cause: An internal error has caused monarch
selection to fail. Action: Reboot system, swap processors if failure
persists.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 205
- Severity: MAJOR
- Event Summary: CPU monarch collision
- Event Class: System
- Problem Description:
Monarch Collision has occurred
- Cause / Action:
Cause: Unexpected error has occurred during
monarch selection. Action: Reboot, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 207
- Severity: FATAL
- Event Summary: Boot cell virtualize EFI failure
- Event Class: System
- Problem Description:
SFW attempted to virtualize EFI and
failed
- Cause / Action:
Cause: An internal error has occurred that
prevented EFI from virtualizing. Action: Reboot, if problem persists contact
your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 208
- Severity: FATAL
- Event Summary: Boot cell virtualize PAL failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize PAL
- Cause / Action:
Cause: SFW was unable to virtualize PAL.
Action: Reboot, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 209
- Severity: FATAL
- Event Summary: Boot cell virtualize SAL failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize SAL
- Cause / Action:
Cause: SFW was unable to virtualize SAL.
Action: Reboot, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 210
- Severity: FATAL
- Event Summary: Boot cell virtualize SALPROC failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize SALPROC
- Cause / Action:
Cause: SFW was unable to virtualize SALPROC.
Action: Reboot, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 211
- Severity: MAJOR
- Event Summary: CPU struct init failed
- Event Class: System
- Problem Description:
SFW has failed initializing the CPU
Struct.
- Cause / Action:
Cause: A CPU has failed the configuration
process. Action: Replace CPU. If problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 212
- Severity: MAJOR
- Event Summary: CPU failed early config
- Event Class: System
- Problem Description:
A CPU has failed early config.
- Cause / Action:
Cause: A CPU has failed the early
configuration process. Action: Replace CPU. If problem persists contact your
HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 213
- Severity: MAJOR
- Event Summary: CPU failed early selftest
- Event Class: System
- Problem Description:
A CPU has failed early self test. Data:
PAL Test State.
- Cause / Action:
Cause: A CPU has failed early self test.
Action: Replace CPU. If problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 214
- Severity: MAJOR
- Event Summary: CPU failed
- Event Class: System
- Problem Description:
SFW has detected that a CPU has failed.
Data: the local cpu number that failed.
- Cause / Action:
Cause: A CPU has failed. Action: Replace CPU.
If problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 215
- Severity: MAJOR
- Event Summary: CPU failed late selftest
- Event Class: System
- Problem 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.
- Cause / Action:
Cause 1: 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. 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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 216
- Severity: MAJOR
- Event Summary: CPU not enough late test memory
- Event Class: System
- Problem Description:
The CPU late test has failed because of
insufficient memory
- Cause / Action:
Cause: Insufficient memory Action: Increase
memory and reboot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 217
- Severity: FATAL
- Event Summary: Could not allocate memory for EFI image
- Event Class: System
- Problem Description:
Could not allocate memory for EFI image
- Cause / Action:
Cause: SFW could not allocate enough memory
for EFI image. Action: Replace/Add memory.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 218
- Severity: FATAL
- Event Summary: EFI image corrupted
- Event Class: System
- Problem Description:
EFI image is corrupted
- Cause / Action:
Cause: EFI image is corrupted. Action:
Reflash ROM if applicable, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 219
- Severity: FATAL
- Event Summary: EFI not in fit table
- Event Class: System
- Problem Description:
EFI fit error
- Cause / Action:
Cause: EFI image is not in FIT. Action:
Reflash ROM if applicable, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 220
- Severity: FATAL
- Event Summary: NVRAM test fail
- Event Class: System
- Problem Description:
EFI NVM has failed testing. The cell
will now halt.
- Cause / Action:
Cause: NVM is corrupted or bad. Action: Clear
NVM, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 221
- Severity: FATAL
- Event Summary: EFI Rom size bad
- Event Class: System
- Problem Description:
EFI Image Error
- Cause / Action:
Cause: EFI image is corrupt. Action: Reflash
ROM if applicable, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 222
- Severity: FATAL
- Event Summary: EFI Rom checksum error
- Event Class: System
- Problem Description:
EFI Image Error.
- Cause / Action:
Cause: EFI image is corrupt. Action: Reflash
ROM if applicable, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 223
- Severity: FATAL
- Event Summary: External interruption nest limit exceeded
- Event Class: System
- Problem Description:
The IVT interrupting nesting depth has
been exceeded. This processor will be halted Data: Number of the offending
vector
- Cause / Action:
Cause: Internal FW error.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 224
- Severity: FATAL
- Event Summary: External interrupt not serviced
- Event Class: System
- Problem Description:
An external interrupt has been requested
and not serviced. Data: Number of the vector
- Cause / Action:
Cause: Internal FW error.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 225
- Severity: FATAL
- Event Summary: Ext int taken
- Event Class: System
- Problem Description:
An external interrupt has been taken.
Data: Number of the vector taken.
- Cause / Action:
Cause: An external interrupt has been taken
Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 226
- Severity: MAJOR
- Event Summary: Forward Progress Log (FPL) access failed
- Event Class: System
- Problem Description:
Access to the FPL has failed.
- Cause / Action:
Cause: FPL access has failed.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 227
- Severity: FATAL
- Event Summary: PSR fetch failure
- Event Class: System
- Problem Description:
SFW was unable to read the CPU PSR.
Data: Local CPU number
- Cause / Action:
Cause: SFW was unable to read the CPU PSR.
Action: Replace CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 228
- Severity: FATAL
- Event Summary: Cell halt
- Event Class: System
- Problem Description:
SFW has halted the cell
- Cause / Action:
Cause: Internal Error Action: contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 229
- Severity: MAJOR
- Event Summary: CPU PAL incompatible with cpu
- Event Class: System
- Problem Description:
SFW has determined that PAL is not
compatible with the current processors.
- Cause / Action:
Cause: Incompatible PAL. Action: Update PAL
or change processors
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 230
- Severity: MAJOR
- Event Summary: Slave is incompatible with monarch
- Event Class: System
- Problem Description:
SFW has determined that a slave
processor is incompatible with the monarch. Data: Physical location of the
incompatible processor.
- Cause / Action:
Cause: Incompatible processors. Action:
Replace processors.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 231
- Severity: MAJOR
- Event Summary: Interrupt clear failure
- Event Class: System
- Problem Description:
Interrupt clear failed during cell
config
- Cause / Action:
Cause: Interrupt clear failed. Action:
Reboot, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 232
- Severity: MAJOR
- Event Summary: System Event Log (SEL) access failed
- Event Class: System
- Problem Description:
SFW has determined that an IPMI event
failed.
- Cause / Action:
Cause: An IPMI event has failed. Action:
None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 233
- Severity: FATAL
- Event Summary: Trap taken
- Event Class: System
- Problem Description:
Data: IVT Offset
- Cause / Action:
Cause: This will follow other events
indicating some type of IVT error. Action: This event is for debugging the
address, other events will determine the user action.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 234
- Severity: MAJOR
- Event Summary: LDB State bad on entry
- Event Class: System
- Problem Description:
LDB state bad
- Cause / Action:
Action: None required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 235
- Severity: FATAL
- Event Summary: Interrupt with ic bit clear
- Event Class: System
- Problem Description:
Interrupt context was lost Data:
interrupt number.
- Cause / Action:
Cause: Interrupt context was lost. Action:
none
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 236
- Severity: FATAL
- Event Summary: Min-state registration failure
- Event Class: System
- Problem Description:
Registering of the processor min state
save area with PAL has failed.
- Cause / Action:
Cause: Registering of the processor min state
save area with PAL has failed. Action: Replace processor, if problem
persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 238
- Severity: MAJOR
- Event Summary: Boot monarch timed out
- Event Class: System
- Problem Description:
SFW has determined the monarch has timed
out Data: Local CPU Number
- Cause / Action:
Cause: The monarch has timed out. Action:
None, Replace CPU if problem persists, system will reboot after this
event.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 239
- Severity: FATAL
- Event Summary: PAL_B not in FIT table
- Event Class: System
- Problem Description:
A PAL_B FIT error has occurred
- Cause / Action:
Cause: Internal Error or ROM is corrupted.
Action: Reflash ROM if applicable, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 240
- Severity: FATAL
- Event Summary: SAL_B not in FIT table
- Event Class: System
- Problem Description:
A SAL_B FIT error has occurred
- Cause / Action:
Cause: Internal Error or ROM is corrupted.
Action: Reflash ROM if applicable, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 241
- Severity: FATAL
- Event Summary: NVRAM test fail
- Event Class: System
- Problem Description:
NVM has failed test. The system will
halt
- Cause / Action:
Cause: NVM is corrupt or bad. Action: Reboot,
if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 242
- Severity: FATAL
- Event Summary: Interrupt vector out of range
- Event Class: System
- Problem Description:
A interrupt vector has been requested
out of the acceptable range. Data: Vector Number.
- Cause / Action:
Cause: An internal error has occurred
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 243
- Severity: FATAL
- Event Summary: Pal proc error getting pal copy info
- Event Class: System
- Problem Description:
The PAL Copy Info call has failed
- Cause / Action:
Cause: An internal error has occurred.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 244
- Severity: FATAL
- Event Summary: Pal proc error copying pal to memory
- Event Class: System
- Problem Description:
Error coping PAL to memory
- Cause / Action:
Cause: There has been an error copying PAL to
memory. Action: Reboot, if problem persists contact your HP representative
for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 245
- Severity: MAJOR
- Event Summary: Boot pal proc failure
- Event Class: System
- Problem Description:
A PAL Proc has failed. This will halt
the processor. Data: Local CPU Number
- Cause / Action:
Cause: Internal PAL Error. Action: Reboot, if
problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 246
- Severity: MAJOR
- Event Summary: Console device failure
- Event Class: System
- Problem Description:
A console device has failed. Data:
Physical Addr of device that failed.
- Cause / Action:
Cause: A console device has failed. Action:
Reset console device/system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 247
- Severity: MAJOR
- Event Summary: Platform interface device failure
- Event Class: System
- Problem Description:
A console device has failed. Data:
Physical Addr of device that failed.
- Cause / Action:
Cause: A console device has failed. Action:
Reset console device/system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 248
- Severity: MAJOR
- Event Summary: platform scratch RAM test failed
- Event Class: System
- Problem Description:
Platform Scratch RAM has failed the
test.
- Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action:
Reboot, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 249
- Severity: MAJOR
- Event Summary: CPU rendezvous failure
- Event Class: System
- Problem Description:
A CPU has failed to meet rendezvous.
Data: Local CPU Number
- Cause / Action:
Cause: Bad or slow CPU. Action: Replace
CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 250
- Severity: FATAL
- Event Summary: Error extracting sal_b from rom
- Event Class: System
- Problem Description:
SFW could not extract SAL_B from the ROM
- Cause / Action:
Cause: ROM Corrupt or unreadable. Action:
Reflash ROM if applicable, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 251
- Severity: FATAL
- Event Summary: Scratch RAM bad
- Event Class: System
- Problem Description:
Platform Scratch RAM has failed test.
- Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action:
Reboot, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 252
- Severity: MAJOR
- Event Summary: IPMI System Event Log (SEL) is full
- Event Class: System
- Problem Description:
IPMI SEL full
- Cause / Action:
Cause: IPMI SEL full. Action: Clear SEL
through BMC or MP.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 253
- Severity: MAJOR
- Event Summary: Slave wakeup before vector registered
- Event Class: System
- Problem Description:
No wakeup vector registered for
processor Data: Local CPU Number
- Cause / Action:
Cause: No wakeup vector registered for
processor. Action: Reboot, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 254
- Severity: MAJOR
- Event Summary: CPU failed rendezvous handler
- Event Class: System
- Problem Description:
Slave Rendezvous handler has failed.
Data: Local CPU Number.
- Cause / Action:
Cause: Internal Error. Action: Reboot, if
problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 255
- Severity: FATAL
- Event Summary: Error building SMBIOS Tables
- Event Class: System
- Problem Description:
SFW failed to build the SMBIOS tables
- Cause / Action:
Cause: SFW failed to build the SMBIOS tables.
Action: None, if SMBIOS is preventing functionality, reboot. If problem
persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 256
- Severity: FATAL
- Event Summary: Trap nest limit exceeded
- Event Class: System
- Problem Description:
The trap nesting limit has been
exceeded. Data: Vector Number
- Cause / Action:
Cause: The trap nesting limit has been
exceeded. Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 257
- Severity: FATAL
- Event Summary: Trap not serviced
- Event Class: System
- Problem Description:
A trap has been requested and not
serviced. Data: Vector Number
- Cause / Action:
Cause: A invalid trap has been requested or a
trap has not been installed. Action: Reboot if necessary, if problem
persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 258
- Severity: FATAL
- Event Summary: Trap taken
- Event Class: System
- Problem Description:
A trap has been taken. Data: Number of
the vector taken.
- Cause / Action:
Cause: A trap has been taken Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 259
- Severity: MAJOR
- Event Summary: Uncleared interrupt
- Event Class: System
- Problem Description:
At least one interrupt was not cleared.
Data: The highest pending interrupt number
- Cause / Action:
Cause: At least one interrupt was not
cleared. Action: None.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 260
- Severity: FATAL
- Event Summary: Unexpected external interrupt
- Event Class: System
- Problem Description:
An unexpected external interrupt has
occurred. Data: External Interrupt Number
- Cause / Action:
Cause: An unexpected external interrupt has
occurred. Action: None.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 261
- Severity: FATAL
- Event Summary: Interrupt before redirection table set up
- Event Class: System
- Problem Description:
An interrupt has occurred before setting
up the IVT. Data: Interrupt Number
- Cause / Action:
Cause: An interrupt has occurred before
setting up the IVT. Action: None.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 262
- Severity: FATAL
- Event Summary: CPU unexpected MCA
- Event Class: System
- Problem Description:
An unexpected MCA has occurred before
MCA's are unmasked. Data: Local CPU Number.
- Cause / Action:
Cause: Unexpected MCA Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 263
- Severity: FATAL
- Event Summary: Unexpected trap
- Event Class: System
- Problem Description:
An unexpected trap has occurred. The
trap number is either invalid or the requested trap has not been registered.
Data: Trap Number
- Cause / Action:
Cause: 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 trap table.
Action: 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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 264
- Severity: FATAL
- Event Summary: CPU unknown boot error
- Event Class: System
- Problem Description:
SFW has detected an unknown error.
- Cause / Action:
Cause: unknown error. Action: None, if
problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 265
- Severity: MAJOR
- Event Summary: CC errors PAL failure
- Event Class: System
- Problem Description:
SFW has detected a PAL Failure
- Cause / Action:
Cause: SFW has detected a PAL Failure.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 266
- Severity: MAJOR
- Event Summary: Expected MC vector unregistered
- Event Class: System
- Problem Description:
Expected Machine Check Vector not
registered
- Cause / Action:
Cause: Expected Machine Check Vector not
registered at the time of an Expected Machine Check
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 267
- Severity: FATAL
- Event Summary: INIT initiated
- Event Class: System
- Problem 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
- Cause / Action:
Cause: Software has requested an INIT or the
INIT button has been pressed. Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 268
- Severity: MAJOR
- Event Summary: Expected I/O host bridge is missing
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: I/O host bridge failure. An incorrect
I/O backplane is installed. Action: Contact your HP representative to check
the I/O host bridge and the I/O backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 269
- Severity: MAJOR
- Event Summary: LBA has unexpected number of I/O slots
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The firmware needs to be updated. An
incorrect I/O backplane is installed. Action: Contact your HP representative
to check the firmware and the I/O backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 270
- Severity: MAJOR
- Event Summary: I/O rope width does not match expected value
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The firmware needs to be updated. An
incorrect I/O backplane is installed. Action: Contact your HP representative
to check the firmware and the I/O backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 271
- Severity: MAJOR
- Event Summary: Found unexpected I/O host bridge
- Event Class: System
- Problem Description:
Firmware found an unexpected I/O host
bridge. Firmware will configure the I/O host bridge and display the
following EFI warning message, "Unexpected hardware I/O configuration." Data
Field: Physical location of the unexpected I/O host bridge.
- Cause / Action:
Cause: The firmware needs to be updated. An
incorrect I/O backplane is installed. Action: Contact your HP representative
to check the firmware and the I/O backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 272
- Severity: MAJOR
- Event Summary: PCI clock DLL error
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Failed or improperly inserted I/O
card. Action: Remove or reseat the I/O card. Cause: Failed I/O chipset.
Failed I/O backplane. Action: Contact your HP representative to check the
I/O chipset and backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 273
- Severity: MAJOR
- Event Summary: PCI hot plug controller failed
- Event Class: System
- Problem Description:
An I/O host bridge's hot-plug controller
has failed. Firmware will deconfigure the I/O host bridge and display the
following EFI warning message, "Failed I/O slot(s) deconfigured." Data
Field: Physical location of the I/O hostbridge.
- Cause / Action:
Cause: Hot-plug controller failure. I/O host
bridge failure. Action: Contact your HP representative to check the hot-plug
controller and the I/O host bridge.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 274
- Severity: MAJOR
- Event Summary: Found unknown I/O rope width
- Event Class: System
- Problem Description:
Firmware attempts to configure an I/O
controller rope to an unsupported width. Firmware will deconfigure any I/O
host bridge connected to the rope. Data Field: Physical location of the
failed rope.
- Cause / Action:
Cause: Internal firmware error. Action:
Contact your HP representative to check the firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 275
- Severity: MAJOR
- Event Summary: I/O LBA clear error failed
- Event Class: System
- Problem 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 hostbridge.
- Cause / Action:
Cause: A failed or improperly seated I/O card
is present. Action: Replace or reseat the I/O card(s). Cause: I/O host
bridge failure. Action: Contact your HP representative to check the I/O host
bridge.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 276
- Severity: MAJOR
- Event Summary: I/O host bridge inaccessible because rope reset
failed to complete
- Event Class: System
- Problem Description:
An I/O host bridge is inaccessible
because an I/O controller rope reset failed to complete. Firmware will
deconfigure the I/O host bridge and display the following EFI warning
message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of
the I/O host bridge.
- Cause / Action:
Cause: I/O chipset failure. Action: Contact
your HP representative to check the I/O chipset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 277
- Severity: MAJOR
- Event Summary: Insufficient power to turn on PCI slot
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The power budget is exceeded. Action:
Install an additional power supply on the system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 278
- Severity: MAJOR
- Event Summary: PCI bus walk unknown error
- Event Class: System
- Problem Description:
Firmware encountered an unexpected error
while attempting to configure an I/O host bridge's I/O devices. Firmware
will continue boot but will not configure the I/O devices connected to the
specified I/O host bridge. Such I/O devices will not be usable as console
nor boot devices but might be usable by the O/S. Data Field: Physical
location of the I/O host bridge.
- Cause / Action:
Cause: Internal firmware error. Action:
Contact your HP representative to check the firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 279
- Severity: MAJOR
- Event Summary: PCI bus walk resources exceeded
- Event Class: System
- Problem 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 connected to the specified I/O host bridge. In addition,
firmware will display the following EFI warning message, "Insufficient
resources to assign to one or more I/O devices." Such I/O devices will not
be usable as console nor boot devices but might be usable by the O/S. Data
Field: Physical location of the I/O host bridge.
- Cause / Action:
Cause: Unsupported I/O configuration. Action:
Remove any unsupported I/O cards. Move the I/O card to another slot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 280
- Severity: MAJOR
- Event Summary: PCI bus unmap unknown error
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Internal firmware error. Action:
Contact your HP representative to check the firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 281
- Severity: MAJOR
- Event Summary: PCIXCAP sampling error
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: I/O host bridge failure. Action:
Contact your HP representative to check the I/O host bridge.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 282
- Severity: MAJOR
- Event Summary: Power monitor failed to respond
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: BMC failure. Action: Contact your HP
representative to check the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 283
- Severity: MAJOR
- Event Summary: I/O rope reset failed to complete
- Event Class: System
- Problem Description:
An I/O controller rope reset did not
complete within the expected time limit. Firmware will deconfigure the I/O
host bridge attached to the rope. Data Field: Physical location of the
deconfigured I/O host bridge.
- Cause / Action:
Cause: I/O chipset failure. Action: Contact
your HP representative to check the I/O controller.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 284
- Severity: MAJOR
- Event Summary: I/O SBA clear error failed
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: I/O chipset failure. Action: Contact
your HP representative to check the I/O chipset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 285
- Severity: MAJOR
- Event Summary: PCI slot has incorrect default power state
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: 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. Action: Replace the card with a
compliant card. Cause: The hot-plug controller has failed. Action: Contact
your HP representative to check the hot-plug slot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 286
- Severity: MAJOR
- Event Summary: PCI slot power on error
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The I/O card is damaged or improperly
inserted. Action: Replace or reseat the I/O card. Cause: The hot-plug
controller has failed. Action: Contact your HP representative to check the
hot-plug slot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 287
- Severity: MAJOR
- Event Summary: PCI slot's standby power failed
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: I/O slot failure. Action: Contact your
HP representative to check the I/O slot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 288
- Severity: MAJOR
- Event Summary: Found invalid PCIXCAP value
- Event Class: System
- Problem Description:
An I/O host bridge or hot-plug
controller reported an illegal PCI[X] bus mode for its bus or slot,
respectively. Firmware will deconfigure the I/O host bridge or I/O slot and
display the following EFI warning, "Failed I/O slot(s) deconfigured." Data
Field: Physical location of the failed I/O host bridge or the failed I/O
slot.
- Cause / Action:
Cause: The I/O card is damaged or improperly
inserted. Action: Replace or reseat the I/O card. Cause: I/O host bridge
failure. Hot-plug controller failure. Action: Contact your HP representative
to check the I/O host bridge or the hot-plug controller.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 289
- Severity: MAJOR
- Event Summary: Unsupported rope frequency
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Internal firmware error. Action:
Contact your HP representative to check the firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 290
- Severity: MAJOR
- Event Summary: Unsupported host bridge type
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Firmware needs to be updated. An
incorrect I/O backplane is installed. Action: Contact your HP representative
to check the firmware and the I/O backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 292
- Severity: FATAL
- Event Summary: Machine Check initiated
- Event Class: System
- Problem Description:
A Machine Check has been initiated
- Cause / Action:
Cause: A Machine Check has occurred. Action:
Analyze cause of Machine Check using diag's and EFI tools.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 293
- Severity: FATAL
- Event Summary: Error in temporary mdt area
- Event Class: System
- Problem Description:
There has been a problem building the
MDT table.
- Cause / Action:
Cause: MDT table bad. Action: Reboot if
necessary, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 294
- Severity: FATAL
- Event Summary: Failed to find lmmio entry in mdt
- Event Class: System
- Problem Description:
There has been a problem building the
MDT.
- Cause / Action:
Cause: MDT table bad. Action: Reboot if
necessary, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 295
- Severity: FATAL
- Event Summary: Memory page zero bad
- Event Class: System
- Problem Description:
Memory page 0 was slated for
deallocation in the PDT. EFI cannot launch with page 0 bad, so the system
will halt.
- Cause / Action:
Cause: Memory page 0 was slated for deallocation
in the PDT. Action: FW is written such that this event should never be generated.
If the user sees this event, please contact HP support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 296
- Severity: FATAL
- Event Summary: Failed to find space in mdt
- Event Class: System
- Problem Description:
There has been a problem building the
MDT.
- Cause / Action:
Cause: MDT table bad. Action: Reboot if
necessary, if problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 297
- Severity: MAJOR
- Event Summary: Media failure: info was not retrieved/logged
- Event Class: System
- Problem Description:
There has been a media failure.
- Cause / Action:
Cause: The Error handler has failed to
retrieve or log data due to a media failure. Action: Reboot if necessary, if
problem persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 298
- Severity: MAJOR
- Event Summary: Bus interface register test failed
- Event Class: System
- Problem Description:
Indicates that the chipset register test
has failed. The data field contains the physical address of the failing
register.
- Cause / Action:
Cause: The chipset failed the register test.
Action:
Contact HP support to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 299
- Severity: MAJOR
- Event Summary: Memory ECC normal write/read test failed
- Event Class: System
- Problem Description:
After FW's first access to main memory,
FW detected that the CEC logged an error after reading back what was just
written.
- Cause / Action:
Cause: The DIMM that maps to cache line 0 is in a
chipspare condition Action: Contact HP support Cause: The DIMM that maps to address 0
is not seated properly Action: 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 Cause: System may be running at the wrong frequency. Action: Verify the system
bus frequency and the memory bus frequency.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 300
- Severity: MAJOR
- Event Summary: DIMM loading order error: DIMM deallocated
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: A required DIMM is not loaded in order to
allow for proper operation of the DIMM specified in the physical location.
Action: Refer to the user's manual for Memory loading instructions.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 301
- Severity: MAJOR
- Event Summary: DIMM SPD checksum failed
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The DIMMs SPD EEPROM got corrupted. Action:
Contact HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 302
- Severity: MAJOR
- Event Summary: DIMM SPD fatal error
- Event Class: System
- Problem Description:
Detected a fatal error in DIMM SPD
- Cause / Action:
Cause: Detection of SPD fatal error type -
various types Action: Contact HP Support personnel to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 303
- Severity: MAJOR
- Event Summary: Unsupported memory DIMM type
- Event Class: System
- Problem Description:
A DIMM was installed whose DIMM type is
not compatible with the current set of supported DIMMs for this platform.
- Cause / Action:
Cause: A DIMM with an invalid DIMM type was
found Action: Contact HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 304
- Severity: MAJOR
- Event Summary: The DIMM type of this DIMM doesn't match with
others in the DIMM group
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: The DIMMs in the rank do not have the
same DIMM type Action: Contact HP Support personnel to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 305
- Severity: MAJOR
- Event Summary: The DIMM type table is full. New DIMM type cannot
be added.
- Event Class: System
- Problem Description:
The DIMM type table is full
- Cause / Action:
Cause: Too many different types of DIMMs in
system Action: Reduce the number of different types of DIMMs in the system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 306
- Severity: MAJOR
- Event Summary: DIMM number not found in DMT Table
- Event Class: System
- Problem 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 caller is looking for.)
- Cause / Action:
Cause: Probable internal FW error Action: Reload
System Firmware Action: Contact HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 307
- Severity: MAJOR
- Event Summary: Memory ECC multiple-bit data error detection
failed
- Event Class: System
- Problem Description:
The FW selftest of CEC multi-bit error
(MBE) detection has failed. The upper 32 bits of the data field contain the
Dword offset within the cacheline of the failed MBE detection. The lower 32
bits are split in two, and they contain the bit numbers within the Dword
that were flipped in order to casue an MBE.
- Cause / Action:
Cause: The CEC failed MBE detection. Action: Contact
HP support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 308
- Severity: MAJOR
- Event Summary: Memory ECC multiple-bit ECC error signalling
failed
- Event Class: System
- Problem Description:
The FW selftest of CEC multi-bit error
(MBE) signalling 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 casue an MBE.
- Cause / Action:
Cause: The CEC failed MBE detection. Action: Contact
HP support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 309
- Severity: MAJOR
- Event Summary: Memory ECC single-bit data error detection failed
- Event Class: System
- Problem Description:
The FW selftest of CEC single-bit error
(SBE) detection has failed. The data field contains the bit within the Dword
that was flipped that caused the CEC to not see an SBE.
- Cause / Action:
Cause: The CEC failed SBE detection. Action: Contact
HP support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 310
- Severity: MAJOR
- Event Summary: Memory ECC single-bit ECC error detection failed
- Event Class: System
- Problem Description:
The FW selftest of CEC single-bit error
(SBE) detection has failed. The data field contains the bit within the Dword
that was flipped that caused the CEC to not see an SBE.
- Cause / Action:
Cause: The CEC failed SBE detection. Action: Contact
HP support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 311
- Severity: MAJOR
- Event Summary: Insufficient memory for operation
- Event Class: System
- Problem Description:
Memory FW detected errors below 1MB. FW
will not allow boot in this case, so memory FW will reinterleave and retest.
- Cause / Action:
Cause: FW detected memory errors below 1MB. Action:
None needed if FW recovers. If system will not boot, contact HP support to
troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 312
- Severity: MAJOR
- Event Summary: Memory address not found in MBAT
- Event Class: System
- Problem Description:
Memory FW could not figure out which
rank maps to the physical address specified in the data field maps to.
- Cause / Action:
Cause: The address logged in the CEC doesn't map
to a memory rank, possibly due to a software error or NVM corruption Action:
Contact HP support to trouble shoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 313
- Severity: MAJOR
- Event Summary: Memory Error Information not cleared
- Event Class: System
- Problem Description:
Memory FW was unable to clear the
platform error logs on the CEC. The data field contains the error status of
the CEC.
- Cause / Action:
Cause: Software Error or CEC error Action: Contact HP
support to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 314
- Severity: MAJOR
- Event Summary: Couldn't clear memory error logs
- Event Class: System
- Problem Description:
Memory FW was unable to clear the
platform error logs on the CEC. The data field contains the error status of
the CEC.
- Cause / Action:
Cause Software Error or CEC error Action: Contact HP
support to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 315
- Severity: MAJOR
- Event Summary: Memory error clear failed
- Event Class: System
- Problem 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.
- Cause / Action:
Cause Software error or CEC error Action: Contact HP
support to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 316
- Severity: MAJOR
- Event Summary: DIMM loading order error: DIMM deallocated
- Event Class: System
- Problem 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.
- Cause / Action:
Cause A required DIMM is not loaded in order to
allow for proper operation of the DIMM specified in the physical location.
Action: Refer to the user's manual for Memory loading instructions.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 317
- Severity: MAJOR
- Event Summary: Generic memory firmware error
- Event Class: System
- Problem Description:
An error occurred that memory FW does
not know how to handle.
- Cause / Action:
Cause Corrupt NVM or System firmware failure
Action:
Contact HP support to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 318
- Severity: FATAL
- Event Summary: Memory interleave generation failed
- Event Class: System
- Problem Description:
FW was unable to create a memory
configuration with no errors in low memory to hand off to EFI.
- Cause / Action:
Cause1: DIMM(s) that map into low memory have
errors on them. Action1: Contact HP support to troubleshoot the problem. Cause2: SFW
is outdated. Action2: Update SFW.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 319
- Severity: MAJOR
- Event Summary: Memory register test failed
- Event Class: System
- Problem Description:
The chipset's memory controller failed
the register test. The data field contains the address of the register that
failed selftest.
- Cause / Action:
Cause1: The register within the chipset went bad.
Action1: Contact HP support to troubleshoot the problem Cause2: Internal SFW error.
Action2: Update to most recent SFW.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 320
- Severity: FATAL
- Event Summary: SPD found no memory DIMMs
- Event Class: System
- Problem Description:
Memory Discovery could not detect any
DIMMs installed.
- Cause / Action:
Cause: No DIMMs were detected Action: Install
DIMMs or Contact HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 321
- Severity: FATAL
- Event Summary: No memory found
- Event Class: System
- Problem Description:
FW could not continue because there are
no valid memory ranks loaded.
- Cause / Action:
Cause FW found memory, but it could not find a
correctly loaded rank. Action: Before this event is sent, FW will output which
ranks it is deallocating and why. Review the preceeding events and refer to
the users manual to correct the memory loading.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 322
- Severity: FATAL
- Event Summary: Cannot log memory error because PDT is disabled
- Event Class: System
- Problem Description:
The PDT has been disabled, and FW found
memory errors during selftest. This is a stopboot condition. Also, the PDT
will never be disabled in customer systems, so this event should never be
seen in the field.
- Cause / Action:
Cause FW found memory errors during selftest,
but could not deallocate the page because the PDT is disabled. Action: Reenable
the PDT by clearing NVM
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 323
- Severity: MAJOR
- Event Summary: PDT is disabled
- Event Class: System
- Problem 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.
- Cause / Action:
Cause Informational event indicating that FW
will not use the PDT this boot. Action: None if user does not want to use the
PDT, otherwise, clear NVM
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 324
- Severity: MAJOR
- Event Summary: Error adding entry to PDT
- Event Class: System
- Problem Description:
Error writing entry into the PDT.
- Cause / Action:
Cause NVM write error. Action: Contact HP support
personnel to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 325
- Severity: CRITICAL
- Event Summary: Cannot add PDT entry--PDT full
- Event Class: System
- Problem Description:
The memory page deallocation table (PDT)
is full.
- Cause / Action:
Cause Excessive memory errors Action: Contact HP
Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 326
- Severity: MAJOR
- Event Summary: Memory platform data update failure
- Event Class: System
- Problem 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
- Cause / Action:
Cause Memory FW was unable to save or restore
the original error configuration. Action: If this is seen, update SFW.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 327
- Severity: MAJOR
- Event Summary: Can't find memory rank entry
- Event Class: System
- Problem 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.
- Cause / Action:
Cause 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. Action: Contact HP support to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 329
- Severity: MAJOR
- Event Summary: Memory error overflow:
- Event Class: System
- Problem Description:
More than one error type was detected
when only one error type was expected.
- Cause / Action:
Cause: An error other than a memory error
occurred during the memory test Action: Contact HP support to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 330
- Severity: MAJOR
- Event Summary: Memory forward progress code invalid
- Event Class: System
- Problem Description:
The forward progress bits that memory FW
uses to track state are invalid. The data field is the fwd progress field.
- Cause / Action:
Cause: The forward progress bits are invalid.
Action:
Upgrade to latest system firmware, or contact HP support to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 331
- Severity: MAJOR
- Event Summary: Memory error status invalid
- Event Class: System
- Problem Description:
The memory error status has bits set in
it that indicate another non-memory error occurred. The data field contains
the chipset's error status.
- Cause / Action:
Cause: Non-memory errors were detected during the
memory test that FW doesn't know how to handle. Action: Update to the latest SFW
Action: Contact HP support to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 332
- Severity: MAJOR
- Event Summary: Memory error summary bits invalid
- Event Class: System
- Problem Description:
The memory test summary bits are
invalid. The data field is the test summary bits.
- Cause / Action:
Cause: The memory test summary word is invalid
Action:
Update to the latest SFW. Action: Contact HP support to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 333
- Severity: MAJOR
- Event Summary: The DIMM distribution check was bypassed
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Control bit to skip DIMM distribution
check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 334
- Severity: MAJOR
- Event Summary: The DIMM Loading Order check was bypassed
- Event Class: System
- Problem Description:
The control bit to skip the DIMM loading
order check is set and the DIMM loading order check was skipped. This bit
should only be done in the factory and not in the field.
- Cause / Action:
Cause: Control bit to skip DIMM loading order
check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 335
- Severity: MAJOR
- Event Summary: Looping on destructive memory tests
- Event Class: System
- Problem Description:
The control bit to loop on destructive
memory test is set and the destructive memory tests are run continously.
This bit should only be done in the factory and not in the field.
- Cause / Action:
Cause: Control bit to loop on destructive memory
test is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 336
- Severity: MAJOR
- Event Summary: DIMM Set Check has been skipped
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Control bit to skip DIMM set check is set.
Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 337
- Severity: MAJOR
- Event Summary: Serial Presence Detect (SPD) has been skipped
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Control bit to skip DIMM SPD check is set.
Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 340
- Severity: MAJOR
- Event Summary: OS INIT address not registered
- Event Class: System
- Problem Description:
The OS_INIT vector has not been
registered
- Cause / Action:
Cause: The OS has not registered an OS_INIT
vector. Action: None, the OS has failed to register the vector or has chosen
not to.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 341
- Severity: MAJOR
- Event Summary: OS MCA address not registered
- Event Class: System
- Problem Description:
The OS_MCA vector has not been
registered
- Cause / Action:
Cause: The OS has not registered an OS_MCA
vector. Action: None, the OS has failed to register the vector or has chosen
not to.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 342
- Severity: MAJOR
- Event Summary: OS MCA did not correct the Machine Check
- Event Class: System
- Problem Description:
An Uncorrected Machine Check has
occurred
- Cause / Action:
Cause: Uncorrected Machine Check. Action:
Analyze cause of Machine Check using diagnostic and EFI tools.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 343
- Severity: FATAL
- Event Summary: Found bad miscellaneous register
- Event Class: System
- Problem Description:
A PDH register has failed.
- Cause / Action:
Cause: A PDH register has failed. Action:
Reboot if necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 344
- Severity: MAJOR
- Event Summary: SAL_CHECK failed for an unknown reason
- Event Class: System
- Problem Description:
The handler for SAL_CHECK has failed for
an unknow reason.
- Cause / Action:
Cause: The handler for SAL_CHECK has failed
for an unknown reason. Action: Reboot if necessary, if problem persists
contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 345
- Severity: MAJOR
- Event Summary: SAL_INIT failed for an unknown reason
- Event Class: System
- Problem Description:
The handler for SAL_INIT has failed for
an unknow reason.
- Cause / Action:
Cause: The handler for SAL_INIT has failed
for an unknown reason. Action: Reboot if necessary, if problem persists
contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 347
- Severity: MAJOR
- Event Summary: Unexpected return to SAL_CHECK
- Event Class: System
- Problem Description:
SAL_CHECK has been unexpectedly returned
to.
- Cause / Action:
Cause: SAL_CHECK has been unexpectedly
returned to. Action: Reboot if necessary, if problem persists contact your
HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 348
- Severity: MAJOR
- Event Summary: Unexpected return to SAL_INIT
- Event Class: System
- Problem Description:
SAL_CHECK has been unexpectedly returned
to.
- Cause / Action:
Cause: SAL_CHECK has been unexpectedly
returned to. Action: Reboot if necessary, if problem persists contact your
HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 349
- Severity: CRITICAL
- Event Summary: Firmware is adding a DEGRADED cpu node to the
device tree.
- Event Class: System
- Problem Description:
Firmware is adding a device tree node
for a CPU that is degraded in functionality. The cpu should not be trused.
- Cause / Action:
A CPU that is not fully functional is
installed in the cell board. Replace.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 350
- Severity: CRITICAL
- Event Summary: PD rendez will fail do to a Firmware Tree error
- Event Class: System
- Problem 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 ansii string in the data field.
- Cause / Action:
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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 351
- Severity: CRITICAL
- Event Summary: The current cell is not configured as part of the
expected set
- Event Class: System
- Problem Description:
The currently executing cell is not
configured to be part of the cell set it is attempting to rendezvous with.
- Cause / Action:
A bad complex profile exists. Correct and
redistribute.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 352
- Severity: CRITICAL
- Event Summary: A remote CSR could not be read
- Event Class: System
- Problem 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.
- Cause / Action:
Either a hardware connection problem exists,
or fabric was unable to be routed. Verify hardware and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 353
- Severity: CRITICAL
- Event Summary: The current cell is too late to rendezvous with
other cells
- Event Class: System
- Problem 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.
- Cause / Action:
This cell took to long completing previous
steps to rendezvous. A bad complex profile could also cause this problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 354
- Severity: FATAL
- Event Summary: The current cell detected incompatible CPUs on
another cell
- Event Class: System
- Problem 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.
- Cause / Action:
Mixed CPU types are installed in the same
partition. Remove them.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 355
- Severity: CRITICAL
- Event Summary: Current cell was too slow creating the local
rendezvous set
- Event Class: System
- Problem 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.
- Cause / Action:
Cell too slow. Could be bad hardware. Check
for other errors and reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 356
- Severity: CRITICAL
- Event Summary: Reporting cell was not included in the global cell
set
- Event Class: System
- Problem 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.
- Cause / Action:
Fabric problem, Connection problem or timing
problem. Reset the PD.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 357
- Severity: FATAL
- Event Summary: No Core Cell can be selected in the PD.
- Event Class: System
- Problem Description:
No cells in the PD can be a core cell.
This is fatal.
- Cause / Action:
No cells have a functioning core IO card. Add
a core IO card to a cell in the PD and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 358
- Severity: CRITICAL
- Event Summary: Firmware was unable to notify utilities of the
core cell number
- Event Class: System
- Problem Description:
System Firmware was unable to notify
utilities of the selected core cell number.
- Cause / Action:
Communication with utilities is broken. Check
for earlier errors or NVRAM problems.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 359
- Severity: CRITICAL
- Event Summary: Fabric code unable to find a needed service
provider.
- Event Class: System
- Problem Description:
The fabric code is unable to find a
service provider for a required banyan service.
- Cause / Action:
The registry is corrupt or the ROM is
incomplete.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 360
- Severity: CRITICAL
- Event Summary: Error in a fabric Port
- Event Class: System
- Problem Description:
The fabric port specified in the data
field had an error.
- Cause / Action:
Reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 361
- Severity: CRITICAL
- Event Summary: Parity error detected on read from fabric
- Event Class: System
- Problem Description:
An error occurred reading a CSR. The CSR
address is displayed in the data field.
- Cause / Action:
Hardware problem. Check connections and
reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 362
- Severity: CRITICAL
- Event Summary: Error writing to Fabric
- Event Class: System
- Problem Description:
Error writing to Fabric. CSR data in
data field.
- Cause / Action:
Bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 363
- Severity: FATAL
- Event Summary: Crossbar slices are out of rev with each other.
- Event Class: System
- Problem Description:
Incompatible crossbar slices are
installed The data field is the two revisions reported by slice1 and slice0
of the CSR data.
- Cause / Action:
Bad hardware configuration. Replace the
crossbar.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 364
- Severity: FATAL
- Event Summary: Crossbar slices are configured poorly
- Event Class: System
- Problem Description:
Crossbar slices are in different
locations. The data field is the two locations reported by slice1 and slice0
of the CSR data.
- Cause / Action:
Fatal configuration. Reconfigure the
hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 365
- Severity: CRITICAL
- Event Summary: A CPU has taken over for the monarch CPU
- Event Class: System
- Problem Description:
A CPU has taken over as the monarch CPU.
- Cause / Action:
The previous monarch may be suspect.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 366
- Severity: FATAL
- Event Summary: Sram cannot be used on the cell
- Event Class: System
- Problem Description:
SRAM cannot be accessed on the cell
board. Execution cannot continue.
- Cause / Action:
SRAM cannot be located or used on the cell
board. Replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 367
- Severity: FATAL
- Event Summary: The dillon hardware cannot be located.
- Event Class: System
- Problem Description:
The dillon component/chip cannot be
located or used.
- Cause / Action:
ROM is corrupt. Replace the rom or reprogram
flash.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 368
- Severity: CRITICAL
- Event Summary: A required piece of PDH bus hardware cannot be
contacted.
- Event Class: System
- Problem Description:
A required piece of PDH bus hardware
cannot be contacted.
- Cause / Action:
Verify all connections of PDH bus components
or replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 372
- Severity: MAJOR
- Event Summary: IO Link software error was corrected.
- Event Class: System
- Problem Description:
IO Link Software error was corrected.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 373
- Severity: CRITICAL
- Event Summary: Bad parity data from RD Rtn FIFO on PIO Read (UNC)
- Event Class: System
- Problem Description:
Bad parity data from RD Rtn FIFO on PIO
Read (UNC).
- Cause / Action:
Replace bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 374
- Severity: CRITICAL
- Event Summary: Parity error in Reg FIFO Internal parity error.
- Event Class: System
- Problem Description:
Parity error in Reg FIFO Internal parity
error.
- Cause / Action:
Replace bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 375
- Severity: CRITICAL
- Event Summary: TLB Fetch timeout
- Event Class: System
- Problem Description:
TLB Fetch timeout.
- Cause / Action:
Replace bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 376
- Severity: FATAL
- Event Summary: Link presence goes away, FE
- Event Class: System
- Problem Description:
Link presence goes away, FE.
- Cause / Action:
Replace the link.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 377
- Severity: FATAL
- Event Summary: LBA to SBA parity error on command, rope will go
fatal
- Event Class: System
- Problem Description:
LBA to SBA parity error on command, rope
will go fatal.
- Cause / Action:
Bad hardware.
Replace I/O chassis.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 378
- Severity: FATAL
- Event Summary: Access to invalid TLB entry Requesting rope fatal
- Event Class: System
- Problem Description:
Access to invalid TLB entry Requesting
rope fatal.
- Cause / Action:
Replace bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 379
- Severity: FATAL
- Event Summary: Memory fetch timeout
- Event Class: System
- Problem Description:
Memory Fetch Timeout.
- Cause / Action:
Replace bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 380
- Severity: CRITICAL
- Event Summary: Error was encountered when initializing the LBA.
- Event Class: System
- Problem Description:
An error was encountered when initiating
the rope number specified in the data field.
- Cause / Action:
Replace the bad hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 381
- Severity: MAJOR
- Event Summary: LBA correctable Timeout Error was encountered.
- Event Class: System
- Problem Description:
LBA correctable timeout error was
encountered.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 382
- Severity: CRITICAL
- Event Summary: LBA uncorrectable Function Error was encountered.
- Event Class: System
- Problem Description:
LBA uncorrectable Function Error was
encountered.
- Cause / Action:
Replace the damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 383
- Severity: CRITICAL
- Event Summary: LBA uncorrectable Timeout Error was encountered.
- Event Class: System
- Problem Description:
LBA uncorrectable Timeout Error was
encountered.
- Cause / Action:
Replace the damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 384
- Severity: CRITICAL
- Event Summary: Misc. uncorrectable error discovered on LBA.
- Event Class: System
- Problem Description:
Misc uncorrectable error discovered on
LBA.
- Cause / Action:
Replace damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 385
- Severity: FATAL
- Event Summary: LBA encountered an uncorrectable parity error.
- Event Class: System
- Problem Description:
LBA encountered an uncorrectable parity
error.
- Cause / Action:
Replace the damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 386
- Severity: FATAL
- Event Summary: LBA Misc. Fatal Error encountered.
- Event Class: System
- Problem Description:
LBA misc. Fatal Error encountered.
- Cause / Action:
Replace damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 387
- Severity: FATAL
- Event Summary: LBA Fatal function error encountered.
- Event Class: System
- Problem Description:
LBA Fatal function error encountered.
- Cause / Action:
Replace damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 388
- Severity: FATAL
- Event Summary: LBA Fatal Parity error encountered.
- Event Class: System
- Problem Description:
LBA Fatal Parity error encountered.
- Cause / Action:
Replace hardware, either PCI card or IO
backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 389
- Severity: FATAL
- Event Summary: LBA Fatal Timeout Error Encountered.
- Event Class: System
- Problem Description:
LBA Fatal timeout error encountered.
- Cause / Action:
Replace damaged hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 392
- Severity: CRITICAL
- Event Summary: DIMM SPD Extended Checksum Failure
- Event Class: System
- Problem Description:
The calculated and compared Checksums of
the SPD EEPROM don't match.
- Cause / Action:
Replace any bad dimms.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 393
- Severity: MAJOR
- Event Summary: Options header checksum error encountered.
- Event Class: System
- Problem Description:
The Options component encountered a
header checksum error. The actual data is in the data field of the chassis
code.
- Cause / Action:
Reinitialize the options data.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 394
- Severity: MAJOR
- Event Summary: Options data checksum error was encountered.
- Event Class: System
- Problem Description:
The Options service data had a bad
checksum. Actual data is in the data field.
- Cause / Action:
Verify options data and reinitialize if
necessary.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 395
- Severity: CRITICAL
- Event Summary: Internal inconsistency in the interleave tables.
- Event Class: System
- Problem Description:
Internal inconsistency in the interleave
tables.
- Cause / Action:
Reconfigure and Reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 396
- Severity: MAJOR
- Event Summary: CellInfoList is not NULL.
- Event Class: System
- Problem Description:
The CellInfoList is not null and was
expected to be. There has been an error in interleaving.
- Cause / Action:
Reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 397
- Severity: CRITICAL
- Event Summary: Error in constructing the Memory Descriptor.
- Event Class: System
- Problem Description:
Error in constructing the Memory
Descriptor.
- Cause / Action:
Reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 398
- Severity: CRITICAL
- Event Summary: Unable to update the local memory layout
- Event Class: System
- Problem Description:
Unable to update the local memory
layout.
- Cause / Action:
Reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 399
- Severity: CRITICAL
- Event Summary: A required address was not found within a mapped
address.
- Event Class: System
- Problem Description:
A required address was not found within
a mapped address in the PDT.
- Cause / Action:
Reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 400
- Severity: CRITICAL
- Event Summary: Failure to install a Partition level PDT.
- Event Class: System
- Problem Description:
Failure to install a partition level
PDT. Errors prevented it.
- Cause / Action:
Reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 401
- Severity: CRITICAL
- Event Summary: A FATAL resource could not be found or is
unusable
- Event Class: System
- Problem Description:
A FATAL 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
Segmant not usable: 0xdead0005; bad NVRAM: 0xdead0006; Dillon unusable:
0xdead0007; SRAM unusable: 0xdead0008; CPU unusable: 0xdead0009; Options
Component Unusable: 0xdead000a; Real Time Clock unusable: DEAD_RTC; Unknown:
0xdead0086
- Cause / Action:
Determine the failing component or hardware
from the data field as described and replace.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 402
- Severity: FATAL
- Event Summary: Internal firmware programming error.
- Event Class: System
- Problem 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.
- Cause / Action:
Report the IP to the firmware team. Reset the
system. This cannot be worked around in the field.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 405
- Severity: CRITICAL
- Event Summary: A semaphore could not be obtained
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Action: Reset system to clear the
semaphore Try reinitializing NVRAM. If problem persists, contact
engineering.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 407
- Severity: MAJOR
- Event Summary: The requested NVRAM block was not found.
- Event Class: System
- Problem Description:
The requested NVRAM block was not found.
The ID that was not found is displayed in the data field.
- Cause / Action:
No Action Required. Firmware can allocated
space for the block.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 408
- Severity: MAJOR
- Event Summary: The requested NVRAM block is locked.
- Event Class: System
- Problem Description:
The block id specified in the data field
is locked.
- Cause / Action:
Retry the operation.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 409
- Severity: MAJOR
- Event Summary: Firmware tried to unlock a NVRAM block that was
already unlocked.
- Event Class: System
- Problem Description:
Firmware tried to unlock a NVRAM block
that was already unlocked. Data field contains the block ID.v
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 410
- Severity: CRITICAL
- Event Summary: The Header in NVRAM was not found
- Event Class: System
- Problem Description:
The header in the NVRAM space was not
found.
- Cause / Action:
NVRAM cannot be used. It must be initialized
first. Firmware will attempt the initialization.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 411
- Severity: CRITICAL
- Event Summary: The Freelist used for NVM block allocation is
corrupt.
- Event Class: System
- Problem Description:
The Freelist used vor Non-Volatile
Memory allocation is corrpt.
- Cause / Action:
Band NVRAM/ reinitialize.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 412
- Severity: CRITICAL
- Event Summary: Firmware is preparing to reset for
reconfiguration.
- Event Class: System
- Problem 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.
- Cause / Action:
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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 413
- Severity: CRITICAL
- Event Summary: An error was encountered communicating with
utilities during PD render.
- Event Class: System
- Problem 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.
- Cause / Action:
Verify communications with the utilities
system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 414
- Severity: FATAL
- Event Summary: Forward Progress is stopping. The Cell or System
will not boot further.
- Event Class: System
- Problem 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.
- Cause / Action:
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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 415
- Severity: MAJOR
- Event Summary: No console is available for the DUI to use.
- Event Class: System
- Problem Description:
The DUI (Developers User Interface) was
entered, but there is no console available for the interface.
- Cause / Action:
DUI was entered before the console is
available. DUI will exit and processing will continue.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 416
- Severity: CRITICAL
- Event Summary: Error Processing encountered an unrecoverable
error
- Event Class: System
- Problem 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.
- Cause / Action:
Decode the ASCII message and correct the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 417
- Severity: CRITICAL
- Event Summary: System is unable to complete the Reset For
Reconfiguration request.
- Event Class: System
- Problem 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.
- Cause / Action:
Delay the request for reconfiguration until
after the PD has been released from SINC BIB.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 418
- Severity: CRITICAL
- Event Summary: The cell is not able to reach all requested cells
through the fabric.
- Event Class: System
- Problem 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.
- Cause / Action:
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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 419
- Severity: MAJOR
- Event Summary: LBA has unexpected number of I/O Slots.
- Event Class: System
- Problem 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)
- Cause / Action:
Cause: Unsupported I/O configuration. Action:
Remove the I/O cards below the specified PCI-to-PCI bridge.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 420
- Severity: CRITICAL
- Event Summary: Console device failed to connect.
- Event Class: System
- Problem 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.
- Cause / Action:
Debugging event, not for release.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 421
- Severity: MAJOR
- Event Summary: Copying memory test code failed.
- Event Class: System
- Problem Description:
This event is unused
- Cause / Action:
Cause: Memory test code located in main memory
has been corrupted Action: Contact HP support personnel to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 423
- Severity: CRITICAL
- Event Summary: Multiple Core Cells have been discovered in the
same PD
- Event Class: System
- Problem 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 CRITICAL problem.
- Cause / Action:
Verify that the complex profile is correct
and reset the partition.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 424
- Severity: CRITICAL
- Event Summary: The utilities component encountered an error when
sending a command to the MP
- Event Class: System
- Problem 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
occure when the SINC cannot talk to the MP.
- Cause / Action:
Verify the utilities system is connected
correctly and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 426
- Severity: CRITICAL
- Event Summary: This indicates that all the cpus in the cell did
not rendezvous during the MCA.
- Event Class: System
- Problem Description:
This denotes the fact that all the cpus
in the cell did not rendezvous.
- Cause / Action:
When this happens the cell will step through
some of the error logging code on its own and then reset itself.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 427
- Severity: CRITICAL
- Event Summary: This indicates that it does not have any access to
the PD.
- Event Class: System
- Problem Description:
This chassis code indicates that thecell
does not have any access to a PD.
- Cause / Action:
Forward Progress indicator; the cell will
independently step through the error logging steps before it resets
itself.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 428
- Severity: CRITICAL
- Event Summary: This indicates the loss of lockstep during the MCA
path.
- Event Class: System
- Problem 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.
- Cause / Action:
The cell will take up a few more error
logging steps independently before resetting itself.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 429
- Severity: CRITICAL
- Event Summary: The PD level cell rendezvous failed.
- Event Class: System
- Problem Description:
This indicates that some of the cells did
not show up during the PD level rendezvous.
- Cause / Action:
This means that the cells will independently
step through some of the error logging code and then reset themselves.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 434
- Severity: CRITICAL
- Event Summary: The reporting cell is not configured to be in a
PD.
- Event Class: System
- Problem Description:
The Reporting Cell is not configured to
be in a PD, according to Complex Profile Group A.
- Cause / Action:
Run parmgr to configure the cell into a PD
and reset the PD or add the cell.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 437
- Severity: FATAL
- Event Summary: The PD cannot boot, a majority of cells did not
arrive at Rendezvous
- Event Class: System
- Problem Description:
Not enough cells made the Rendezvous for
boot to continue. The rules are listed in the cause action section.
- Cause / Action:
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.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 439
- Severity: MAJOR
- Event Summary: INIT: Monarch failed in slave rendezvous
- Event Class: System
- Problem Description:
SFW's INIT handler has failed to
rendezvoused the processors.
- Cause / Action:
Cause: A processor has failed rendezvous.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 440
- Severity: MAJOR
- Event Summary: MC: I/O error log/clear error
- Event Class: System
- Problem Description:
SFW's Machine Check Handler was unable
to log or clear I/O error records.
- Cause / Action:
Cause: SFW's Machine Check Handler was unable
to log or clear I/O error records. Action: Reboot if necessary, if problem
persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 441
- Severity: MAJOR
- Event Summary: MC: MCA to BERR escalation not supported by PAL
- Event Class: System
- Problem Description:
Cannot escalate an MCA to BERR
- Cause / Action:
Cause: Cannot escalate an MCA to BERR.
Action: Analyze Machine Check Logs using diagnostic tools and EFI tools.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 442
- Severity: MAJOR
- Event Summary: MC: MCA to BINIT escalation not supported by PAL
- Event Class: System
- Problem Description:
Cannot escalate an MCA to BINIT.
- Cause / Action:
Cause: Cannot escalate an MCA to BINIT.
Action: Analyze Machine Check Logs using diagnostic tools and EFI tools.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 443
- Severity: MAJOR
- Event Summary: MC: Get PAL features failed
- Event Class: System
- Problem Description:
SFW failed to get the feature set from
PAL.
- Cause / Action:
Cause: SFW failed to get the feature set from
PAL. Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 444
- Severity: MAJOR
- Event Summary: MC: Previous PAL rendezvous failed; rebooting
- Event Class: System
- Problem Description:
PAL Failed to rendezvous the processors
during a MCA.
- Cause / Action:
Cause: PAL Failed to rendezvous the
processors during a MCA.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 445
- Severity: MAJOR
- Event Summary: MC: Set PAL features failed
- Event Class: System
- Problem Description:
SFW failed to get the feature set from
PAL.
- Cause / Action:
Cause: SFW failed to get the feature set from
PAL. Action: None
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 446
- Severity: MAJOR
- Event Summary: MC: Monarch failed in slave rendezvous
- Event Class: System
- Problem Description:
SFW's MCA Handler has failed to
rendezvous all the slaves Data: Return from the rendezvous call.
- Cause / Action:
Cause: A slave failed to rendezvous. Action:
Reboot if necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 447
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: Rendezvous vector out of range
- Event Class: System
- Problem Description:
A bad rendezvous vector has been
registered.
- Cause / Action:
Cause: A bad rendezvous vector has been
registered. Action: Reboot if necessary to re-register vector, if problem
persists contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 448
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: No MC monarch
- Event Class: System
- Problem Description:
No Machine Check Monarch exists, exiting
MC Rendezvous.
- Cause / Action:
Forward progress, no action required
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 449
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: No wakeup registered
- Event Class: System
- Problem Description:
The OS has not registered a wake-up
mechanism for rendezvous.
- Cause / Action:
Forward progress, no action required
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 450
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: MCA escalation not supported by PAL
- Event Class: System
- Problem Description:
PAL call failed to set the BINIT
escalation bit
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 451
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: Get PAL features failed
- Event Class: System
- Problem Description:
The PAL call PAL_GET_FEATURES has
failed.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 452
- Severity: MAJOR
- Event Summary: MC_RENDEZVOUS: Set PAL features failed
- Event Class: System
- Problem Description:
The PAL call PAL_SET_FEATURES has
failed.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 453
- Severity: FATAL
- Event Summary: Internal Firmware Programming Error from the EFI
portion of the firmware
- Event Class: System
- Problem 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.
- Cause / Action:
Report the IP to the firmware team. Reset the
system. This cannot be worked around in the field.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 455
- Severity: FATAL
- Event Summary: Inconsistency in the length of the ESI table
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Table entries corrupted. Action:
Reboot system. Cause: New table entry types added by SAL not understood by
EFI. Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 456
- Severity: FATAL
- Event Summary: The computed checksum for ESI Table incorrect.
- Event Class: System
- Problem Description:
The computed checksum for the ESI
(Extensible SAL Interface) table is not zero as expected. EFI is halting.
Data Field: the computed checksum.
- Cause / Action:
Cause: Table corrupted. Action: Reboot the
system. Cause: Table's checksum miscomputed. Action: Upgrade system
firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 457
- Severity: MAJOR
- Event Summary: ESI Table contains an unsupported entry type.
- Event Class: System
- Problem Description:
EFI found an unsupported entry type
within the ESI (Extensible SAL Interface) Table. Data Field: unknown type.
- Cause / Action:
Cause: Corrupted table. Action: Reboot
system. Cause: Mismatch between SAL and EFI. Action: Upgrade system
firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 458
- Severity: MAJOR
- Event Summary: A GUID was larger than the expected 128 bits.
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Inconsistency in EFI firmware. Action:
Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 459
- Severity: FATAL
- Event Summary: EFI is halting
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Unknown. Action: examine preceding
events for problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 461
- Severity: MAJOR
- Event Summary: EFI internal error detected resulting in execution
of ASSERT macro
- Event Class: System
- Problem Description:
EFI has detected an internal error. The
actual error is unspecified by this event. Examine previous events and
console output for possible explanations.
- Cause / Action:
The cause is unknown. See previous events and
console output for causes.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 462
- Severity: FATAL
- Event Summary: EFI has executed the "break" shell command.
- Event Class: System
- Problem Description:
- Cause / Action:
Cause: Executing the "break command. Action:
Check for user entering "break" command. Check for shell scripts using the
"break" command.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 463
- Severity: FATAL
- Event Summary: EFI USB HCD interrupt service has detected the
host controller is hung
- Event Class: System
- Problem Description:
The EFI USB HCD interrupt service has
detected the host controller is hung. EFI is halting.
- Cause / Action:
Cause: Problem with USB controller. Action:
Reset the card containing the USB interface to restart the controller.
Contact your HP representative to check the USB interface.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 464
- Severity: FATAL
- Event Summary: The EFI/SAL handoff structure's version does not
match EFI expectations
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: EFI/SAL firmware mismatch. Action:
Upgrade System Firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 465
- Severity: FATAL
- Event Summary: Unable to obtain access to all RTC SAL services
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Not all expected services are
available. Mismatch between EFI and SAL versions. Internal EFI error.
Action: Upgrade system firmware. Cause: EFI unable to create internal
event. EFI out of resources. Action: Reset system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 466
- Severity: FATAL
- Event Summary: Unable to obtain access to all SAL timer services
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Not all expected services are
available. Mismatch between EFI and SAL versions. Internal EFI error.
Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 467
- Severity: FATAL
- Event Summary: EFI unable to start the periodic timer
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Internal system firmware error.
Action: Reset the system. Cause: Mismatch between EFI and SAL versions
Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 468
- Severity: FATAL
- Event Summary: No I/O port space region found in the MDT
- Event Class: System
- Problem Description:
EFI did not find an I/O port space
region in the MDT. EFI is halting.
- Cause / Action:
Cause: EFI/SAL handoff structure corrupted.
Action: Determine source of corruption and reboot. Cause: EFI/SAL mismatch.
Action: Check system firmware versions and upgrade if necessary.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 469
- Severity: FATAL
- Event Summary: EFI reached an unimplemented section of code
- Event Class: System
- Problem Description:
EFI reached an unimplemented section of
code. EFI is halting. Data Field: Unique identifier indicating the location
reached within the code.
- Cause / Action:
Cause: Reached unimplemented firmware.
Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 470
- Severity: MAJOR
- Event Summary: EFI unable to read current speedy boot settings
- Event Class: System
- Problem 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 boottest EFI shell command and via
the OS. These other accesses will likely fail. Data Field: Return status
from internal EFI function.
- Cause / Action:
Cause: BMC not functioning. Action: Reset the
BMC. Contact your HP representative to check the BMC. Cause: BMC/SAL
firmware mismatch. Action: Upgrade system firmware and/or BMC firmware.
Cause: EFI/SAL version mismatch. Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 471
- Severity: FATAL
- Event Summary: Unpermitted SAL callback attempted
- Event Class: System
- Problem Description:
A SAL Callback was attempted. This is
not permitted. EFI is halting. Data Field: index of the function that was
being called.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 472
- Severity: MAJOR
- Event Summary: EFI unable to determine frequency base of the CPU
interval timer
- Event Class: System
- Problem Description:
EFI is unable to determine the frequency
base for the Interval Timer within the CPU. The SAL procedure EFI uses to
get this information returned an error. EFI uses this information to create
delays within EFI based on the interval timer. EFI will assume 800 MIPS.
Data Field: return status from the SAL procedure.
- Cause / Action:
Cause: Invalid timer ratio. Action: Reset
system. Cause: Internal system firmware error. Action: Upgrade system
firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 473
- Severity: MAJOR
- Event Summary: EFI system events already initialized
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Multiple attempts to initialize system
events, EFI internal error. Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 474
- Severity: MAJOR
- Event Summary: Unable to create internal virtualization event
while initializing IPMI events
- Event Class: System
- Problem 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.
- Cause / Action:
Cause: Out of resources. Internal EFI error.
Action: Reboot system. Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 476
- Severity: CRITICAL
- Event Summary: There was an error creating or initializing the
FPGA node in firmware
- Event Class: System
- Problem Description:
An error was detected while initializing
the FPGA node and services associated with the PDH.
- Cause / Action:
Cause: Unable to properly initialize a system
firmware node Action: Check for other errors in the system first. Invalidate
NVM and retry to boot. Get the latest firmware release.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 481
- Severity: FATAL
- Event Summary: some processors not compatible
- Event Class: System
- Problem Description:
Installed processors are not of
compatible models or families
- Cause / Action:
Replace processors with compatible ones if
all processors are to be used.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 482
- Severity: FATAL
- Event Summary: caches sizes are inconsistent
- Event Class: System
- Problem Description:
Processors with different cache sizes
are installed
- Cause / Action:
Replace processors with compatible ones if
all processors are to be used.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 483
- Severity: MAJOR
- Event Summary: processor steppings are not equal
- Event Class: System
- Problem Description:
Processors with different steppings are
installed
- Cause / Action:
If desired, replace processors with equal
stepping ones, this is a warning only.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 484
- Severity: MAJOR
- Event Summary: selecting new monarch
- Event Class: System
- Problem Description:
SFW is selecting a new processor due to
compatibility problems.
- Cause / Action:
Replace incompatible processor if
desired.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 485
- Severity: FATAL
- Event Summary: monarch not lowest stepping
- Event Class: System
- Problem Description:
The monarch stepping is not equal to the
lowest installed CPU stepping.
- Cause / Action:
Replace the processor with one that has an
equal stepping to the others.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 487
- Severity: MAJOR
- Event Summary: processors are over clocked
- Event Class: System
- Problem Description:
A CPU's FSB frequency is overclocked.
Data: Local CPU Number.
- Cause / Action:
Change FSB frequency.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 488
- Severity: MAJOR
- Event Summary: cpu access error on processor info area
- Event Class: System
- Problem Description:
There was an error reading the info ROM
area of the CPU. Data: Local CPU Number
- Cause / Action:
Cause: An early version of CPU or a bad info
ROM. Action: Replace CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 489
- Severity: MAJOR
- Event Summary: PAL A was not executed - HALT
- Event Class: System
- Problem Description:
PAL_A has not been executed and control
is being trasnferred back to SAL_B.
- Cause / Action:
No Action.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 490
- Severity: FATAL
- Event Summary: PAL B was not executed - HALT
- Event Class: System
- Problem Description:
PAL_B has not been executed and control
is being transferred back to SAL_B.
- Cause / Action:
No Action.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 491
- Severity: MAJOR
- Event Summary: Prototype CPU installed
- Event Class: System
- Problem Description:
Data: Lower 32 bits have Local CPU
Number
- Cause / Action:
Cause: A Prototype CPU is installed. Action:
Replace CPU with a production CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 492
- Severity: MAJOR
- Event Summary: final boot rendezvous monarch watchdog timeout
- Event Class: System
- Problem Description:
Data: Monarch's Local CPU Number
- Cause / Action:
Cause: A watchdog timer has expired and
determined that a monarch is dead. Action: Reboot, if problem persists,
replace CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 493
- Severity: MAJOR
- Event Summary: A multi-bit error was found while reading a XBC
CSR
- Event Class: System
- Problem Description:
While reading a XBC CSR, a multi-bit
error was found.
- Cause / Action:
None.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 494
- Severity: MAJOR
- Event Summary: The return value from a function was an unknown
value.
- Event Class: System
- Problem Description:
The return value from a function was an
unknown value. Data field is the unknown status that was returned.
- Cause / Action:
None.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 495
- Severity: MAJOR
- Event Summary: Cannot get system ID status from BMC
- Event Class: System
- Problem Description:
EFI queries the BMC on the system board
for the status of a system ID. The BMC could not complete the request
successfully or on time. Data Field: Internal EFI function status.
- Cause / Action:
Cause: The communication with the system ID
is lost Action: Unplug power from the system for 10 seconds and try
rebooting the system. Cause: Inaccessible FRU EPROM on system board and/or
I/O backplane. Failure in IPMI messaging path on system board and/or I/O
backplane Action: Check FRU EPROM content and accessibility on system and
I/O backplane using ifru. If BMC communication is not working (no answer
from BMC), flash BMC firmware. If it cannot be done or doesn't solve the
problem, replace system board. If system board FRU EPROM cannot be accessed,
replace system board If I/O backplane FRU EPROM cannot be accessed, replace
I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 496
- Severity: MAJOR
- Event Summary: Cannot read a system ID
- Event Class: System
- Problem Description:
BMC reported a system ID status as
inaccessible, reported invalid status or cannot return the current value of
a system ID. Data Field: uuid status or internal EFI function status. System
ID status: a 1 byte value 0 extended to 64bits: 0x00 -> primary and
secondary values are valid 0x01 -> primary and secondary values are magic
0x02 -> primary and secondary values are inaccessible 0x04 -> primary
and secondary values are invalid 0x08 -> primary and secondary values are
null (UUID only) 0x10 -> primary and secondary values are different,
value (primary or secondary) is valid 0x11 -> primary and secondary
values are different, value (primary or secondary) is magic 0x12 ->
primary and secondary values are different, value (primary or secondary) is
inaccessible 0x14 -> primary and secondary values are different, value
(primary or secondary) is invalid 0x18 -> primary and secondary values
are different, value (primary or secondary) is null (UUID only)
- Cause / Action:
Cause: BMC failure Action: Unplug power from
the system for 10 seconds and try rebooting the system. Cause:
Inaccessible/corrupted FRU EPROM on system board and/or I/O backplane.
Action: Check content of FRU EPROM of the system board and I/O backplane
using ifru. If FRU EPROM content can be accessed on both board flash BMC
firmware. If content cannot be accessed on system board replace system
board. If content cannot be accessed on I/O backplane, replace I/O backplane
If this cannot be done or doesn't solve the issue replace system board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 497
- Severity: MAJOR
- Event Summary: Failed to write new system ID. BMC reported an
error
- Event Class: System
- Problem Description:
Firmware tried to write a primary or
secondary system ID as requested by the user during the boot sequence. The
write failed. Data Field: Internal EFI function status.
- Cause / Action:
Cause: Communication failure with the BMC.
Action: Unplug power from the system for 10 seconds and try rebooting the
system. Cause: Inaccessible/corrupted FRU EPROM on system board and/or I/O
backplane. Inaccessible/corrupted FRU EPROM on system board and/or I/O
backplane. Action: Check content of FRU EPROM of the system board and I/O
backplane using ifru. If FRU EPROM content can be accessed on both board
flash BMC firmware. If content cannot be accessed on system board replace
system board. If content cannot be accessed on I/O backplane, replace I/O
backplane If it cannot be done or doesn't solve the issue replace system
board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 498
- Severity: MAJOR
- Event Summary: The system ID(s) currently in the system is
invalid
- Event Class: System
- Problem Description:
The system ID(s) currently in the system
is either invalid or, if the EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR
or EFI_SYSID_BMC_WRITE_ERROR events are also present, inaccessible to the
system firmware. A stop boot condition will be generated and software
license will probably be invalid. Data Field: uuid: 2 byte value. If
preceded by 0xbad00000000000 the following valid values are possible: 0000
-> valid (should never see his one) 0001 -> magic 0002 ->
inaccessible If zero extended: 1st byte refers to primary UUID, 2nd byte to
secondary 00 -> valid 10 / 01 -> magic 11 / 02 -> inaccessible 12 /
- Cause / Action:
Cause: The system ID(s) is invalid and the
user did not elect to fix the problem. Action: Reboot the system and follow
the prompts to fix the issue. Cause: The system ID(s) cannot be accessed or
the BMC is not providing the requested information. One of the following
events will also be present: EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR
or EFI_SYSID_BMC_WRITE_ERROR Action: Fix the error indicated by the other
system ID event.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 499
- Severity: FATAL
- Event Summary: EFI unable to find the SAL services for installing
interrupt handlers
- Event Class: System
- Problem Description:
EFI is unable to find the SAL services
for installing interrupt handlers. EFI was trying to install the run-time
handlers that are required for normal EFI booting. EFI will be halting. Data
Field: internal EFI function status.
- Cause / Action:
Cause: Mismatch between EFI and SAL. Action:
Upgrade system firmware. Cause: Corrupted ESI table. Action: Reboot
system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 500
- Severity: FATAL
- Event Summary: EFI unable to find the SAL service to install
run-time interrupt handlers
- Event Class: System
- Problem Description:
EFI is unable to find the SAL service to
install run-time interrupt handlers. These handlers are required for normal
EFI booting. EFI will be halting. Data Field: internal EFI function status.
- Cause / Action:
Cause: Mismatch between EFI and SAL. Action:
Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 501
- Severity: FATAL
- Event Summary: EFI unable to find the SAL services for installing
interrupt handlers
- Event Class: System
- Problem Description:
EFI is unable to find the SAL services
for installing interrupt handlers. EFI was trying to install the boot-time
handlers that are required for normal EFI booting. EFI will be halting. Data
Field: internal EFI function status.
- Cause / Action:
Cause: Mismatch between EFI and SAL. Action:
Upgrade system firmware. Cause: Corrupted firmware table. Action: Find
source of corruption and reboot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 502
- Severity: FATAL
- Event Summary: EFI unable to find the SAL service to install
boot-time interrupt handlers
- Event Class: System
- Problem Description:
EFI is unable to find the SAL service to
install boot-time interrupt handlers. These handlers are required for normal
EFI booting. EFI will be halting. Data Field: internal EFI function status.
- Cause / Action:
Cause: Mismatch between EFI and SAL. Action:
Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 503
- Severity: MAJOR
- Event Summary: Too many parameters were passed to the utilities
system
- Event Class: System
- Problem Description:
Too many parameters were passed in a
request for the utilities system to perform an operation. No more data is
provided.
- Cause / Action:
This is a firmware error. Contact FW
engineering.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 504
- Severity: CRITICAL
- Event Summary: A crossbar port is unexpectedly not present.
- Event Class: System
- Problem Description:
A crossbar port is expected to be
present, but its presence detect bit is not set. Data field bits 32:43
contain the crossbar ID, bits 44:55 contain the port number for which the
error occurred, and bits 0:31 contain the port status information.
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 505
- Severity: CRITICAL
- Event Summary: A crossbar port unexpectedly has its HW_LINK_OK
bit not set.
- Event Class: System
- Problem Description:
A crossbar port is expected to have its
HW_LINK_OK bit set, but it is not. Data field bits 32:43 contain the
crossbar ID, bits 44:55 contain the port number for which the error
occurred, and bits 0:31 contain the port status information.
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 506
- Severity: CRITICAL
- Event Summary: A connected port was found to be in FE
- Event Class: System
- Problem Description:
A connected crossbar port was found to
have its FE bit set. Data field bits 32:43 contain the crossbar ID, bits
44:55 contain the port number for which the error occurred, and bits 0:31
contain the port status information.
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 507
- Severity: CRITICAL
- Event Summary: There was an error while initializing the
Concorde-Xbc interface.
- Event Class: System
- Problem Description:
There was an error while initializing
the Concorde-Xbc interface. The data field contains the address of the
Concorde CSR for which the error occurred.
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 508
- Severity: FATAL
- Event Summary: The CC - XBC link failed to initialize.
- Event Class: System
- Problem Description:
The CC - XBC link failed to initialize.
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 509
- Severity: MAJOR
- Event Summary: Unable to determine system mode because EFI/SAL
interface not initialized
- Event Class: System
- Problem Description:
EFI is unable to determine current
system mode. The EFI/SAL interface is not initialized. This interface should
have been initialized before now. This event indicates an internal EFI
error. EFI will continue executing.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 510
- Severity: MAJOR
- Event Summary: BMC returned an invalid system mode
- Event Class: System
- Problem Description:
The BMC has returned an invalid system
mode. Data Field: the invalid mode. Expected values are 0 or 1.
- Cause / Action:
Cause: Mismatch between BMC and EFI firmware.
Action: Upgrade system firmware or BMC firmware as necessary.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 511
- Severity: MAJOR
- Event Summary: EFI unable to specify system mode because EFI/SAL
interface not initialized
- Event Class: System
- Problem Description:
EFI is unable to specify a new system
mode. The EFI/SAL interface point is not initialized. This interface should
have been initialized before now. This event indicates an internal EFI
error. EFI will continue executing in the current mode.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 512
- Severity: MAJOR
- Event Summary: Unable to enter normal system mode because EFI/SAL
interface not initialized
- Event Class: System
- Problem Description:
EFI is unable to enter normal system
mode. The EFI/SAL interface is not initialized. This interface should have
been initialized before now. This event indicates an internal EFI error. EFI
will continue executing in the current mode.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 513
- Severity: FATAL
- Event Summary: Unable to initialize part of the SAL/EFI interface
- Event Class: System
- Problem Description:
EFI is unable to initialize part of the
SAL/EFI interface. This crucial service provides access to certain BMC
functionality such as the security system. EFI will halt. Data Field: Return
status from internal EFI function.
- Cause / Action:
Cause: Incompatible versions of EFI and SAL
Internal EFI error. Action: Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 515
- Severity: CRITICAL
- Event Summary: An expected tree node was not found
- Event Class: System
- Problem Description:
A needed tree node was not found. The
data field contains the ascii name of the tree node that was not found.
- Cause / Action:
This is a bug. Contact engineering.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 516
- Severity: MAJOR
- Event Summary: EFI unable to modify system state to "running"
- Event Class: System
- Problem Description:
- Cause / Action:
Cause: BMC malfunctioning. Action: Reset BMC.
Cause: BMC non functional. Action: Contact your HP representative to check
the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 518
- Severity: MAJOR
- Event Summary: The Get Processor Bus Dependent Configuration
Features PAL call failed.
- Event Class: System
- Problem Description:
Firmware was unable to correctly issue
the Get Processor Bus Dependent Configuration Features command.
- Cause / Action:
Contact engineering. There is a PAL
compatibility problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 520
- Severity: FATAL
- Event Summary: EFI unable to initialize internal library
- Event Class: System
- Problem Description:
EFI is unable to initialize internal
library. This collection of internal services is required for much of EFI's
functionality. EFI is halting.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 521
- Severity: CRITICAL
- Event Summary: EFI unable to initialize security system
- Event Class: System
- Problem Description:
EFI is unable to initialize the security
system. The privilege level of the system may or may not be Admin. It is
likely certain EFI facilities will be unavailable. EFI will continue booting
but security may be compromised. Data Field: Return status from internal EFI
function.
- Cause / Action:
Cause: EFI out of resources. Action: Reboot
system. Cause: SAL or EFI mismatch/failure. Action: Upgrade system firmware.
Cause: BMC not responding properly. Action: Reset BMC. Contact your HP
representative to check the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 522
- Severity: MAJOR
- Event Summary: EFI detected invalid internal privilege level
- Event Class: System
- Problem Description:
EFI detected an invalid value for its
internal privilege level. This value is stored within SAL. EFI will continue
but system security may be compromised. Data Field: The invalid privilege
level.
- Cause / Action:
Cause: SAL storage corrupted. Action: Reboot
system. Cause: Invalid argument with EFI. Action: Upgrade system
firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 523
- Severity: MAJOR
- Event Summary: EFI detected invalid privilege level when setting
password
- Event Class: System
- Problem Description:
EFI detected an invalid privilege level
when setting a BMC password. Only the levels of Admin (0x30) and User (0x20)
are permitted. Data Field: the invalid privilege level.
- Cause / Action:
Cause: Internal EFI error. Action: Upgrade
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 524
- Severity: FATAL
- Event Summary: EFI MDT table is bad
- Event Class: System
- Problem Description:
SFW has determined that the MDT table is
invalid.
- Cause / Action:
Cause: SFW has determined that the MDT table
is invalid. Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 525
- Severity: MAJOR
- Event Summary: Processor has incompatible fixed core ratio
- Event Class: System
- Problem Description:
Data: Local CPU Number.
- Cause / Action:
Cause: A CPU has a different fixed ration
than the FSB frequency set in the chipset. Action: Replace CPU
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 526
- Severity: FATAL
- Event Summary: All processors slated for compatibility
deconfiguration
- Event Class: System
- Problem Description:
Data: A bitmask for which CPUs are
slated to be deconfigured
- Cause / Action:
Cause: The user or SFW has set all CPUs to be
deconfigured. Action: Replace bad processors, if problem persists contact
your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 527
- Severity: CRITICAL
- Event Summary: An unexpected or invalid value was read from a
crossbar remote route table.
- Event Class: System
- Problem Description:
An error occurred while reading a
crossbar remote route table, or an unexpected/invalid value was read from the
table. The data field consists of the crossbar ID (32:43), the port number
of which the table was read (44:55), and the return status of the read call
(0:32).
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 528
- Severity: CRITICAL
- Event Summary: Error reading the PORT[n]_NEIGHBOR_INFO XBC CSR.
- Event Class: System
- Problem Description:
An error occurred while trying to read
the PORT[n]_NEIGHBOR_INFO crossbar CSR. The data field consists of the
crossbar ID (32:43) and port number (44:55) for which the CSR was read.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 530
- Severity: MAJOR
- Event Summary: Firmware detected excessive errors on the DIMM.
- Event Class: System
- Problem Description:
The DIMM at the physical location given
by the data field had excessive errors and has been marked as "FAILED" by
firmware.
- Cause / Action:
Firmware detected excessive errors on the
DIMM / Replace the specified DIMM
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 531
- Severity: CRITICAL
- Event Summary: The OE (output enable) bit was not set for a XBC
port.
- Event Class: System
- Problem Description:
A XBC port was expected to be
functional, but its OE bit was not set. The data field consists of the
contents of the port_status CSR (0:31), the XBC number (32:43), and the port
number (44:55).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 532
- Severity: CRITICAL
- Event Summary: An error occurred while trying to read the
PORT_STATUS CSR for a XBC port.
- Event Class: System
- Problem Description:
Unable to read the PORT_STATUS CSR for a
XBC port. The data field consists of the contents of the PORT_STATUS CSR
(0:31), the XBC number (32:43), and the port number (44:55).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 533
- Severity: CRITICAL
- Event Summary: A XBC port was unexpectedly found to be landmined.
- Event Class: System
- Problem Description:
A XBC port was unexpectedly found to be
landmined. The data field consists of the XBC number (32:43) and the port
number (44:55).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 535
- Severity: CRITICAL
- Event Summary: The link between the local CC and the local XBC is
unexpectedly not initialized.
- Event Class: System
- Problem Description:
The link between the local CC and the
local XBC is unexpectedly not initialized. The data field is the
XIN_LINK_STATE CC CSR value.
- Cause / Action:
Cause: An error initializing fabric Action: A
previously reported event may provide exact details Reboot, if failure
persists, then either replace the CC chip or the system backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 536
- Severity: CRITICAL
- Event Summary: An invalid XBC number was given.
- Event Class: System
- Problem Description:
A value that was expected to be a XBC
number was found to be an invalid XBC number. The data field is the invalid
XBC number.
- Cause / Action:
A bad value was passed in as a parameter to
fabric traversability functions. No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 537
- Severity: CRITICAL
- Event Summary: An invalid XBC port number was given.
- Event Class: System
- Problem Description:
A value that was expected to be a valid
XBC port number was found to be invalid. The data field is the XBC number
(33:44) and the invalid XBC port number (44:55).
- Cause / Action:
A bad value was passed in as a parameter to
fabric traversability functions. No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 539
- Severity: CRITICAL
- Event Summary: An unexpected neighbor type was read from a XBC
PORT_NEIGHBOR_INFO CSR.
- Event Class: System
- Problem Description:
A neighbor type read from a XBC
PORT_NEIGHBOR_INFO CSR was different than the expected neighbor type. The
data field contains the expected type (32:63) and the actual neighbor type
(0:31).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 540
- Severity: CRITICAL
- Event Summary: A given XBC port is not a valid XBC-CC port.
- Event Class: System
- Problem Description:
A XBC port number was unexpectedly found
to not be a valid XBC-CC port. The data field consists of the XBC number
(32:43) and the port number (44:55).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 541
- Severity: CRITICAL
- Event Summary: A XBC port was unexpectedly found to be an invalid
XBC-XBC port.
- Event Class: System
- Problem Description:
A XBC port was unexpectedly found to be
an invalid XBC-XBC port. The data field consists of the XBC number (32:43)
and the port number (44:55).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 542
- Severity: CRITICAL
- Event Summary: The XBC neighbor chip number does not match the
expected value for this topology
- Event Class: System
- Problem Description:
The XBC neighbor chip number does not
match the expected value for this topology. The data field contains the
expected neighbor chip number (32:63) and the actual neighbor chip number
(0:31).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 543
- Severity: CRITICAL
- Event Summary: The XBC neighbor port number does not match the
expected value for this topology
- Event Class: System
- Problem Description:
The XBC neighbor port number does not
match the expected value for this topology. The data field contains the
expected neighbor port number (32:63) and the actual neighbor port number
(0:31).
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 544
- Severity: FATAL
- Event Summary: Write through to BMC token failed
- Event Class: System
- Problem Description:
Data: Upper 32 bits, BMC failure return
value. This is a stop boot condition. Lower 32 bits, BMC token number that
failed.
- Cause / Action:
Cause: Problem accessing the BMC. Action:
Reset BMC or reboot, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 546
- Severity: CRITICAL
- Event Summary: Duplicate CPU Ids were detected within a cell.
- Event Class: System
- Problem Description:
2 CPUs think that they have the same ID
within the cell. Typically this would mean that PAL reported the same cpu id
for more than 1 cpu on a bus. The cpuid is in the data field.
- Cause / Action:
Most likely cause is a bad cpu module
connection on the cell board. Replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 547
- Severity: MAJOR
- Event Summary: OS crashdump started (D700)
- Event Class: System
- Problem Description:
OS crashdump started (D700)
- Cause / Action:
panic occurred
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 548
- Severity: CRITICAL
- Event Summary: OS legacy PA hex fault code (Bxxx)
- Event Class: System
- Problem Description:
OS legacy PA hex fault code (Bxxx).
Possible I/O error or system panic
- Cause / Action:
fault/panic
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 549
- Severity: MAJOR
- Event Summary: OS dump status (EFxx)
- Event Class: System
- Problem Description:
OS dump status (EFxx). Report on the
success/failure of the writing of the dump. EF00 = success (followed by
either EF0A = successful dump with sync, or EF09 = successful dump without
sync), EFFF = a general error, EFFE = dump path assertion failure, EFFD = no
dump was taken by default, choice or failure, EFFC = dump was aborted by
user.
- Cause / Action:
panic path: attempt to write out the dump is
complete
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 550
- Severity: MAJOR
- Event Summary: Setting processor response timeout failed
- Event Class: System
- Problem Description:
SFW has failed to set the processor
timeout value via a PAL call. Data: PAL call return value.
- Cause / Action:
Cause: A PAL call made by SFW has failed.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 551
- Severity: MAJOR
- Event Summary: Unable to validate blank password during EFI
security initialization
- Event Class: System
- Problem Description:
During EFI security initialization, the
attempt to determine what privilege level a blank password provides, failed.
Most likely this indicates the BMC has failed. EFI assumes that the BMC has
failed and will attempt to continue booting. Some EFI functionality may be
unavailable. Data Field: Return status from internal EFI function.
- Cause / Action:
Cause: SAL failed. Action: Reset the system.
Upgrade system firmware. Cause: BMC failed. Action: Reset the BMC. Contact
your HP representative to check the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 552
- Severity: MAJOR
- Event Summary: Unable to enter Guest mode during EFI security
initialization
- Event Class: System
- Problem Description:
As part of normal security
initialization, EFI attempted to issue a close session to the BMC (I.e.
force the BMC to GUEST mode). This attempt failed. EFI is unable to
initialize the security system. EFI will continue but security may be
compromised. Data Field: Return status from internal EFI function.
- Cause / Action:
Cause: SAL failure. Action: Reset the system.
Upgrade system firmware. Cause: BMC failure. Action: Reset the BMC. Contact
your HP representative to check the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 553
- Severity: MAJOR
- Event Summary: Unable to increase privilege during EFI security
initialization
- Event Class: System
- Problem Description:
As part of normal security
initialization, EFI attempted to issue an open session to the BMC in order
to raise the privilege level to the highest permitted by a blank password.
This attempt failed. EFI is unable to initialize the security system. Data
Field: Return status from internal EFI function.
- Cause / Action:
Cause: SAL failure. Action: Reset the system.
Upgrade system firmware. Cause: BMC failure. Action: Reset the BMC. Contact
your HP representative concerning the BMC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 554
- Severity: MAJOR
- Event Summary: EFI unable to write privilege level during
security initialization
- Event Class: System
- Problem Description:
As part of normal security
initialization, EFI attempted to record the current privilege level. This
attempt failed. EFI is unable to initialize the security system. Data Field:
Return status from internal EFI function.
- Cause / Action:
Cause: SAL failure. Action: Reboot the
system. Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 555
- Severity: MAJOR
- Event Summary: EFI was denied permission to write the privilege
level during security init
- Event Class: System
- Problem Description:
As part of normal security
initialization, EFI attempted to record the current privilege level. This
attempt failed with a privilege violation error. EFI is unable to initialize
the security system. Data Field: Return status from internal EFI function.
- Cause / Action:
Cause: SAL is not in ADMIN or USER mode.
Action: Reboot the system. Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 556
- Severity: MAJOR
- Event Summary: OS dump, error writing image area to disk (E055)
- Event Class: System
- Problem Description:
OS dump, error writing image area to
disk (E055)
- Cause / Action:
panic path forward progress
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 557
- Severity: CRITICAL
- Event Summary: It stands for diagnosis of catastrophic errors in
the PIN block of concorde.
- Event Class: System
- Problem Description:
This indicates that catastrophic errors
have been found in the PIN block of the concorde. The cell needs to be
reset/ halt.
- Cause / Action:
This means that the cell will be reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 559
- Severity: CRITICAL
- Event Summary: This indicates that the cell missed the rendezvous
at the partition level.
- Event Class: System
- Problem Description:
This indicates that the cell is too late
for the PD level rendezvous. And hence it will not join the other PD cells.
- Cause / Action:
The cell will independently step through some
of the error logging steps and then finally reset itself.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 560
- Severity: CRITICAL
- Event Summary: This means that the PD monarch timed out.
- Event Class: System
- Problem Description:
This indicates the state where the PD
monarch was not able to complete the task within a certain time. It failed.
- Cause / Action:
The cell will be reset ; also the partition
will be reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 563
- Severity: CRITICAL
- Event Summary: This indicates the failure in collecting the
Complex profile info.
- Event Class: System
- Problem Description:
This chassis code reports the failure in
collecting the ICM parameters needed for the cell interleaving.
- Cause / Action:
The partition level memory interleaving
cannot continue without the appropriate information.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 564
- Severity: CRITICAL
- Event Summary: This chassis code indicates the failure in
collecting the cell info.
- Event Class: System
- Problem Description:
This chassis code indicates that the
cell interleaving routine could not get the information on the cell memory.
- Cause / Action:
The partition level memory will fail.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 565
- Severity: CRITICAL
- Event Summary: This indicates the failure in updating the GNI
info of the cell with CLM.
- Event Class: System
- Problem Description:
This chassis code is used to represent
the failure in updating the GNI information of the cell with the CLM ( cell
local memory) information obtained from the Complex Profile.
- Cause / Action:
The partition level memory will fail at this
point.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 566
- Severity: CRITICAL
- Event Summary: This indicates the failure in adjusting the mem
info with Minimum ZI req.
- Event Class: System
- Problem Description:
This represents the failure in adjusting
the memory information with the minimum ZI requirements.
- Cause / Action:
This will cause the partition level memory to
exit cell interleaving.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 570
- Severity: FATAL
- Event Summary: Internal Firmware Programming Error from the EFI
portion of the firmware
- Event Class: System
- Problem Description:
An internal EFI firmware error was
encountered. This is usually caused by a bad parameter passed to a function,
corrupt memory, corrupt malloc, corrupt firmware tree or something similar.
The data field contains the IP address of the function that encountered the
error.
- Cause / Action:
Report the IPF to the firmware team. Reset
the system. This cannot be worked around in the field.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 573
- Severity: MAJOR
- Event Summary: Could not obtain the crossbar port semaphore
- Event Class: System
- Problem Description:
Tried to obtain the port semaphore but
GetPortSemaphore returned an ERROR. Could be a failed write to the port
semaphore crossbar CSR or another cell owned the semaphore. Data field bits
32:63 contain the crossbar ID and bits 0:31 contain the port number for
which the semaphore was being obtained.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 574
- Severity: MAJOR
- Event Summary: Could not release the crossbar port semaphore.
- Event Class: System
- Problem Description:
Currently owned the port semaphore but
could not release the semaphore. Data field bits 32:63 contain the crossbar
ID and bits 0:32 contain the port number.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 576
- Severity: FATAL
- Event Summary: BMC token upload failure
- Event Class: System
- Problem Description:
There was an error reading from the BMC
token when attempting to write to SAL NVM. This is a stop boot condition.
Data: BMC Token Number.
- Cause / Action:
Cause: A read from the BMC failed. Action: AC
power cycle if necessary, if problem persists contact your HP representative
for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 577
- Severity: MAJOR
- Event Summary: NVM token access failure
- Event Class: System
- Problem Description:
The read from SAL NVM has failed. This
is a stop boot condition. Data: The token number on which the write failed
- Cause / Action:
Cause: NVM Error, or incorrect permissions to
read token. Action: Retry, AC power cycle if necessary, if problem persists
contact your HP representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 578
- Severity: FATAL
- Event Summary: BMC token download failure
- Event Class: System
- Problem Description:
There was an error when trying to write
to the BMC Tokens. This is a stop boot condition Data: lower 32 bits are BMC
token number, upper 32 bits is the status return from the BMC.
- Cause / Action:
Cause: BMC Error. Action: AC power cycle if
necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 579
- Severity: FATAL
- Event Summary: Error Writing BMC first boot token
- Event Class: System
- Problem Description:
There has been an error writing the
BMC_FIRST_BOOT token. This is a stop boot condition.
- Cause / Action:
Cause: BMC Error. Action: AC power cycle if
necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 580
- Severity: MAJOR
- Event Summary: Fru Id read error
- Event Class: System
- Problem Description:
The read of the motherboard FRU has
failed. Data: Device ID of device that failed the FRU read.
- Cause / Action:
Cause: Error reading the motherboard FRU.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 581
- Severity: MAJOR
- Event Summary: Fru Id checksum error
- Event Class: System
- Problem Description:
The read of the motherboard FRU has
failed a checksum. Data: Device ID of device that failed the FRU read.
- Cause / Action:
Cause: Error reading the motherboard FRU.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 582
- Severity: MAJOR
- Event Summary: FRU Id version error
- Event Class: System
- Problem Description:
The read of the motherboard FRU has
failed due to a version problem. Data: Device ID of device that failed the
FRU read.
- Cause / Action:
Cause: Error reading the motherboard FRU.
Action: Reboot if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 583
- Severity: MAJOR
- Event Summary: Rom revision not equal to FIT revision
- Event Class: System
- Problem Description:
A ROM Rev and FIT Rev do not match.
Data: Code for what didn't match: 0x1 = PAL_A, 0x2 = PAL_B, 0x4 = SAL_A, 0x8
= ACPI, 0xA = EFI
- Cause / Action:
Cause: A ROM Rev and FIT Rev do not match.
Action: Update ROM, , if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 584
- Severity: MAJOR
- Event Summary: ROM revision not equal to Rev block
- Event Class: System
- Problem Description:
A ROM Rev and Rev Block do not match.
Data: Code for what didn't match: 0x3 = PAL, 0x5 = SAL_A, 0x7 = SAL_B, 0x9 =
ACPI, 0xB = EFI, 0xC = BMC
- Cause / Action:
Cause: A ROM Rev and Rev Block do not match.
Action: Update ROM, , if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 585
- Severity: MAJOR
- Event Summary: Primary Fit bad
- Event Class: System
- Problem Description:
The FIT is bad.
- Cause / Action:
Cause: The FIT is bad. Action: Reboot, update
ROM if necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 586
- Severity: MAJOR
- Event Summary: Secondary Fit bad
- Event Class: System
- Problem Description:
The FIT is bad.
- Cause / Action:
Cause: The FIT is bad. Action: Reboot, update
ROM if necessary, if problem persists contact your HP representative for
support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 587
- Severity: MAJOR
- Event Summary: PAL A execution rom warning
- Event Class: System
- Problem Description:
PAL_A_ROM has generated a warning.
- Cause / Action:
Cause: PAL_A_ROM has generated a warning.
Action: Reboot, update ROM if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 588
- Severity: MAJOR
- Event Summary: PAL B execution ROM warning
- Event Class: System
- Problem Description:
PAL_B_ROM has generated a warning.
- Cause / Action:
Cause: PAL_B_ROM has generated a warning.
Action: Reboot, update ROM if necessary, if problem persists contact your HP
representative for support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 589
- Severity: CRITICAL
- Event Summary: An error was encountered when firmware tried to
update the Group B Profile
- Event Class: System
- Problem Description:
Firmware tried to default the Dynamic
(Group B) complex profile and encountered an error.
- Cause / Action:
Manageability may be unavailable to update
the profiles. Check the connections are reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 590
- Severity: CRITICAL
- Event Summary: A DIMM loading order error has occurred
- Event Class: System
- Problem Description:
The loading order of the DIMMs is
incorrect. The cell is halted.
- Cause / Action:
Cause: Incorrect loading of the DIMMs on the
cell Action: Install the DIMMs in the correct order. DIMMs are installed in
ranks of DIMMs , starting with DIMM 0A, 0B, etc. Subsequent ranks are loaded
in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 591
- Severity: MAJOR
- Event Summary: Refresh Control Error Timeout
- Event Class: System
- Problem Description:
Timeout Waiting for SDRAM parts to
become ready - mem_status[0] Refresh Control Register
- Cause / Action:
Cause: At start of memory refresh, timing out
waiting for ready bit to be set Action: Contact HP Support personnel to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 592
- Severity: MAJOR
- Event Summary: memory extender/baseboard FRU mismatch
- Event Class: System
- Problem Description:
The version of Memory extender installed
in the system has not been qualified to work with the version of the
baseboard installed in the system.
- Cause / Action:
Cause: Memory extender and baseboard are
incompatible Action: Contact HP support to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 593
- Severity: FATAL
- Event Summary: Fabric topology mismatch with XBCs in complex
- Event Class: System
- Problem Description:
There is a fabric topology mismatch with
the XBCs in the complex. Data Field: (Topology of XBC << 32) |
Topology of destination XBC 0x00 Topology not yet determined 0x30 Domelight
0x40 U-Turn (Left cabinet) 0x41 U-Turn (Right cabinet) 0x42 Cross-Flex 0x43
U-Turn
- Cause / Action:
There is a fabric topology mismatch with XBC
in complex.
Contact HP Support personnel to analyze the cell, XBC flex
cables, system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 594
- Severity: CRITICAL
- Event Summary: An invalid XBC to XBC port was found.
- Event Class: System
- Problem Description:
While routing the XBC to XBC ports, an
invalid port was encountered. The data field is the crossbar number (32:43)
and the port number (44:55).
- Cause / Action:
Cause: Loss of Lockstep Action: Reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 595
- Severity: MAJOR
- Event Summary: Could not get neighbor information.
- Event Class: System
- Problem Description:
The XBC could not get neighbor
information. Data Field: XBC # << 32 | internal port attempting to
access neighbor
- Cause / Action:
Cause: Defective XBC link Defective XBC
Action: Check XBC link connections Reset the system backplane Contact HP
Support personnel to troubleshoot problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 596
- Severity: CRITICAL
- Event Summary: The XBC's routing state was marked as in ERROR
- Event Class: System
- Problem Description:
For the XBC being routed, routing has
already been attempted, but an error occurred. Inspect chassis codes from
other cells for more details regarding the nature of the problem. The data
field consists of the XBC number (32:63)
- Cause / Action:
Another cell already attempted routing for
the XBC and found an error. Action: Check for hardware failure: flex cables,
crossbar chip, etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 597
- Severity: MAJOR
- Event Summary: It indicates that there is no NVM error space left
for logging an Error Event.
- Event Class: System
- Problem Description:
This means that the error event log
cannot be logged to the persistent storage. The data field gives the event
type that was supposed to be logged.
- Cause / Action:
The error event will not be logged.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 598
- Severity: CRITICAL
- Event Summary: An XBC port found to have an unexpected error.
- Event Class: System
- Problem Description:
An XBC port was found to have an
unexpected error. The data field consists of the crossbar number (32:63) and
the current port errors (0:31)
- Cause / Action:
Cause: A port was landmined so it had to be
routed around. Action: Check flex cables
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 599
- Severity: CRITICAL
- Event Summary: A XBC port route around has occurred
- Event Class: System
- Problem Description:
During fabric routing a port on a XBC
was found in error or had been previously marked as in error. PDC will route
around this XBC port. Data Field: XBC number (32:63) and external XBC port
number (0:31)
- Cause / Action:
Cause: During routing, when a XBC to XBC port
is found to be in error, or was previously marked in error, it is routed
around. This chassis code indicates that which XBC port was routed around.
Action: Reset the system backplane to clear the error If the suspect XBC
port uses a flex cable, check / replace the flex cable and then the system
backplane(s) involved. If the suspect XBC port uses the hardwire link built
into the system backplane, replace the system backplane involved.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 600
- Severity: MAJOR
- Event Summary: During routing a crossbar is found to be in an
uexpected routing state.
- Event Class: System
- Problem Description:
Data field: the unexpected forward
progress state (0:31) XBC number (32:44) Cell number (56:63)
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 601
- Severity: MAJOR
- Event Summary: An unexpected XBC forward progress state was
continually found until timing out.
- Event Class: System
- Problem Description:
A crossbar was found to be in an
unexpected forward progress state during fabric routing. This crossbar
stayed in the unexpected state until Fabric Discovery timed out. Data fied:
unexpected forward progress (0:31) XBC number (32:44) Cell number (56:63)
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 602
- Severity: FATAL
- Event Summary: During remote routing, the current port's neighbor
is not healthy.
- Event Class: System
- Problem Description:
An XBC port was found that is not
healthy. This indicates at least one of the following about the port: -
Hardware link is not okay - Presence detect is false - Fatal error detected
- SBE detected - LPE detected - Port landmined The data field of the chassis
code indicates which port is unhealthy, as well as the fabric routing state
before the problem was encountered.
- Cause / Action:
An XBC port is not healthy. Action: Check for
hardware failure: flex cables, crossbar chips, etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 603
- Severity: FATAL
- Event Summary: The CC to XBC link is not viable.
- Event Class: System
- Problem Description:
The CC to XBC link is not viable.
- Cause / Action:
Cause: The CC to XBC link is not operational.
Action: Reset the cell Reset the system backplane Contact HP Support
personnel to troubleshoot problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 604
- Severity: FATAL
- Event Summary: Remote routing a crossbar failed.
- Event Class: System
- Problem Description:
There was a problem performing remote
routing on the local XBC. Chassis codes sent before this one may provide
more details about the exact nature of the problem. The data field consists
of the XBC number that failed routing (32:63)
- Cause / Action:
A failure was encountered while performing
remote routing on an XBC, most likely due to a problem with the system
backplane or local cell. Action: Check for hardware failure: CC, XBC to CC
link, flex cables, crossbar chip, etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 605
- Severity: FATAL
- Event Summary: Too many XBC-to-XBC were broken in the complex.
- Event Class: System
- Problem Description:
Two or more XBC-XBC links were found to
be broken. The data field is the XBC number (32:63) and a bit map of the
ports broken (0:31)
- Cause / Action:
Port status indicated that two or more ports
on a XBC had errors. Action: Check for hardware failure: flex cables,
crossbar chip, etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 606
- Severity: CRITICAL
- Event Summary: This cell did not get the XBC Global Semaphore.
- Event Class: System
- Problem Description:
After unlocking the XBC Global Semaphore
for a takeover, this cell did not get the semaphore.
- Cause / Action:
C1: Another cell won the race and got the
semaphore before this cell. This would be apparent in chassis codes. A1:
None. C2: XBC write or read failure. A2: check XBC, check link, check CC
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 607
- Severity: FATAL
- Event Summary: Attempted an XBC SM4 takeover and timed out trying
to unlock the SM4.
- Event Class: System
- Problem Description:
When a cell holds an XBC semaphore for
an extended period of time, fabric will attempt to takeover the semaphore so
that the rest of the cells will have access to it. Fabric will attempt to
take the SM4 for a period of time. If it is unable to unlock the SM4 within
the timeout period, it will send this chassis code and halt the cell. Data
field: XBC number (32:63) and current owner (cell) of the semaphore (0:31)
- Cause / Action:
Cannot takeover an XBC semaphore that has
been held for a long time. Try forcing firmware to reroute the fabric by
cycling 48V power on the cabinets. Look for other fabric chassis codes that
explain why the current owner of the SM4 was unable to release it. Look for
fabric problems on the backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 608
- Severity: FATAL
- Event Summary: Waiting for the XBC Global Semaphore has timed
out.
- Event Class: System
- Problem Description:
During Fabric Discovery, the cell will
wait until it gets the XBC's Global Semaphore. It waits for a very long
time. This chassis code indicates that the wait has timed out.
- Cause / Action:
XBC Key Contention. Hardware Failure Action:
Look for other chassis codes that indicate XBC Key contention Check XBC
Check Links/Flex Cables
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 609
- Severity: FATAL
- Event Summary: A timeout occurred while attempting to release the
XBC semaphore.
- Event Class: System
- Problem Description:
The XBC Release Semaphore timeout is
designed to fail last. The semaphore could not be released. Any other cell
(even outside the PD) may be blocked because the XBC is a global resource.
Data field: current semaphore owner (0:31) XBC number (32:43) port number
(44:55) cell number (56:63)
- Cause / Action:
XBC Key Contention. Hardware Failure Action:
Look for additional chassis codes that would explain the failure Check XBC
Check Link/Flex Cables
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 610
- Severity: MAJOR
- Event Summary: Management Processor Firmware Battery Failure or
NVRAM change
- Event Class: System
- Problem Description:
Management Processor Firmware detected
improper data in NVRAM (bad checksums.) Either the NVRAM layout changed, or
the Management Processor Battery may not be maintaining the data through A/C
power cycles.
- Cause / Action:
Determine if the firmware was recently
upgraded. This is often the reason for the NVRAM to change. If not, and the
A/C power has been removed, than it's possible the battery is indeed going
bad and would need to be replaced.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 611
- Severity: MAJOR
- Event Summary: Management Processor Firmware Software Error
- Event Class: System
- Problem Description:
Management Processor Firmware detected a
software error and is logging an event. The data represents data associated
with the error seen.
- Cause / Action:
A software error was detected and is being
logged. The internal data is connected to the location and module where the
error occurred. The Forward Progress Log will receive additional (lower
alert level) event entries with more data associated with this event.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 612
- Severity: MAJOR
- Event Summary: Management Processor detected an I2C Communication
Error with BMC.
- Event Class: System
- Problem Description:
An I2C Communication failure with the
Baseboard Management Controller was detected. Without I2C communication, the
system cannot be powered on/off or reset.
- Cause / Action:
An I2C Communication failure with the
Baseboard Management Controller was detected. Without I2C communication, the
system cannot be powered on/off or reset. Check the I2C communication via
the 'SR' command or the 'PS' command. If it is indeed down, look for
hardware reasons. It's possible resetting the Management Processor firmware
("XD" command option 'r') or completely cycling AC power of the system will
restore the communication.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 613
- Severity: CRITICAL
- Event Summary: A CRC error was discovered when verifying the ROM
- Event Class: System
- Problem Description:
A stored CRC value did not match the
calculated CRC value for the specified address.
- Cause / Action:
Either the ROM was programmed incorrectly or
has gone bad. Reprogram the Flash on the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 614
- Severity: MAJOR
- Event Summary: An error was encountered when executing a PAL_PROC
- Event Class: System
- Problem Description:
An error was encountered when executing
a PAL_PROC. This code will be emitted in pairs. The Proc INDEX will be in
the data of the first chassis code. The status is in the second data field.
- Cause / Action:
PAL was unable to be successfully called. See
other event ids to determine if action needs to be taken.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 615
- Severity: FATAL
- Event Summary: CPUs (and or termination) loaded in wrong order
- Event Class: System
- Problem Description:
CPUs not loaded in correct order.
Correct loading order is CPU 0, 1, 2, 3.
- Cause / Action:
Cause: CPUs not loaded in correct order.
Action: Load CPUs in order 0, 1, 2, 3.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 616
- Severity: CRITICAL
- Event Summary: Error Reading a platform storage variable from the
PDHC/MP
- Event Class: System
- Problem Description:
System firmware was unable to complete a
platform storage read command from the utilities system. The exact status
printed in the data field.
- Cause / Action:
Either the MP is not present, or the
requested information does not exist. Ensure that the MP is functioning and
that the proper data is being requested.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 617
- Severity: CRITICAL
- Event Summary: An error was returned on a Platform Storage Write
Command to the PDHC/MP
- Event Class: System
- Problem Description:
System firmware was unable to complete a
platform storage write command. The actual status is returned in the data
field.
- Cause / Action:
The MP is not present, may be out of space,
or the command was badly formatted. Ensure that the MP has enough space and
try again. If the problem persists, contact engineering.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 618
- Severity: CRITICAL
- Event Summary: The Sequencer was unable to find/use a needed tree
node
- Event Class: System
- Problem Description:
The Sequencer was unable to find the
tree node it needed to complete an operation. The tree node is in the ascii
in the data field.
- Cause / Action:
This is a bug, contact engineering
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 619
- Severity: CRITICAL
- Event Summary: Firmware encountered an error in processing the
partition variables
- Event Class: System
- Problem Description:
System firmware attempted to read a
partition variable from the GSP and store it in options. An error was
encountered during this process. The data field contains the partition
variable element ID that was being processed.
- Cause / Action:
Either the GSP was not present or there was a
resource problem storing the variable. There should be other clues in the
event id log to indicate which is the case. Restore the GSP.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 620
- Severity: CRITICAL
- Event Summary: A non-FATAL cell power fault has occurred
- Event Class: System
- Problem Description:
One or more power converter on the Cell
or Cell Power Board has reported a fault. However, because of redundancy in
the power system, the power to the Cell is still good. The data field
contains detailed power fault location information (see Cell ERS for more
information). Data Byte[0]: bit0 - Power_Fault status, bit1 - Power_Good
status Data Byte[1]: Contents of Power Board Converter Status register. Data
Byte[2]: Contents of Cell Converter Status register. Data Byte[3]: Contents
of CPU Module Power Status register.
- Cause / Action:
Cause(1): A power converter has failed.
Cause(2): A CPU Power Module has been disabled following a thermal warning
reported by that CPU Module.
Action: Contact HP Support personnel to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 622
- Severity: MAJOR
- Event Summary: Firmware was unable to determine the Processor
Dependent Features
- Event Class: System
- Problem Description:
System firmware was unable to
successfully issue the PAL_GET_PROC_FEATURES PAL proc. The data field is
unused
- Cause / Action:
Contact Engineering, This is a bug.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 624
- Severity: CRITICAL
- Event Summary: The CLU has encountered an undefined case
- Event Class: System
- Problem Description:
The CLU has encountered an undefined
case in its control flow.
- Cause / Action:
Cause: CLU firmware on the UGUY has gotten
into an unexpected execution path, most likely due to a hardware issue on
the UGUY. Action: Check revision of CLU firmware. If out of date, or known
bad revision, use FWUU to update CLU firmware. Contact HP Support personnel
to troubleshoot problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 625
- Severity: MAJOR
- Event Summary: An unknown Cell voltage margin has been detected.
- Event Class: System
- Problem Description:
The Cell voltage margin settings do not
match the Normal, +5%, or -5% values.
- Cause / Action:
Cause: A user has manually, using back-door
debugging methods, altered the voltage margin setting of one or more Cell
Board or Cell Power Board converters.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 626
- Severity: MAJOR
- Event Summary: The run-time verification of a programming
assumption has failed.
- Event Class: System
- Problem Description:
For debug purposes, many assumptions
made by the PDHC developer(s) are checked at run-time. If this event log is
seen, it will either indicate that the hardware is in a unknown state that
is not handled by the PDHC, or that a programming bug has been found. For
developer debug purposes, the data field describes where in the code that
the error was detected. Data Bytes[0-1]: The line number within the source
code file where the error was detected. Data Bytes[2-7]: The first 6
characters of the source code file name.
- Cause / Action:
Cause: Hardware in unknown state, or
programming bug found.
Action: Upgrade PDHC firmware to latest revision.
If already at current revision, contact HP Support personnel to troubleshoot
the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 627
- Severity: MAJOR
- Event Summary: An unknown error has been detected by the PDHC
firmware.
- Event Class: System
- Problem Description:
An unknown error has been detected by
the PDHC firmware. For developer debug purposes, the data field describes
where in the code that the error was detected. Data Bytes[0-1]: The line
number within the source code file where the error was detected. Data
Bytes[2-7]: The first 6 characters of the source code file name.
- Cause / Action:
Cause: Hardware in unknown state, or
programming bug found.
Action: Upgrade PDHC firmware to latest revision.
If already at current revision, contact HP support personnel to troubleshoot
the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 628
- Severity: MAJOR
- Event Summary: An attempt to write to a device on the PDHCs I2C
bus has failed.
- Event Class: System
- Problem Description:
An attempt to write to a device on the
PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU
EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A
converters, and, if they are accessible, the CPU Module Power Pods' FRU
EEPROMs. The Data field information contains information that can identify
the exact device that has failed. Refer to the Cell ERS for a mapping of I2C
device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C
Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size
of attempted access (in bytes).
- Cause / Action:
Cause: A hardware fault has
occurred.
Action: Contact HP Support personnel to troubleshoot the Cell
Board, Cell Power Board, and/or PDH Daughtercard.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 629
- Severity: MAJOR
- Event Summary: An attempt to read from a device on the PDHC's I2C
bus has failed.
- Event Class: System
- Problem Description:
An attempt to read from a device on the
PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU
EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A
converters, and, if they are accessible, the CPU Module Power Pods' FRU
EEPROMs. The Data field information contains information that can identify
the exact device that has failed. Refer to the Cell ERS for a mapping of I2C
device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C
Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size
of attempted access (in bytes).
- Cause / Action:
Cause: A hardware fault has
occurred.
Action: Contact HP Support personnel to troubleshoot the Cell
Board, Cell Power Board, and/or PDH Daughtercard.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 630
- Severity: MAJOR
- Event Summary: An attempt to write to a device on the PDHC's SM
bus has failed.
- Event Class: System
- Problem Description:
An attempt to write to a device on the
PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU
EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules'
thermal sensors. The Data field information contains information that can
identify the exact device that has failed. Refer to the Cell ERS for a
mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved
Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word
Address Data Bytes[6-7]: Size of attempted access (in bytes).
- Cause / Action:
Cause: A hardware fault has
occurred.
Action: Contact HP Support personnel to troubleshoot the Cell
Board, Cell Power Board, and/or PDH Daughtercard.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 631
- Severity: MAJOR
- Event Summary: An attempt to read from a device on the PDHC's SM
bus has failed.
- Event Class: System
- Problem Description:
An attempt to read from a device on the
PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU
EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules'
thermal sensors. The Data field information contains information that can
identify the exact device that has failed. Refer to the Cell ERS for a
mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved
Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word
Address Data Bytes[6-7]: Size of attempted access (in bytes).
- Cause / Action:
Cause: A hardware fault has
occurred.
Action: Contact HP Support personnel to troubleshoot the Cell
Board, Cell Power Board, and PDH Daughtercard.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 632
- Severity: CRITICAL
- Event Summary: Cell boot has been disabled due to a failure
setting the frequency registers.
- Event Class: System
- Problem Description:
The PDHC did not read valid frequency
information from the CPU modules' or Cell's FRU EEPROMs, or the frequency
registers would not update properly. Following this event, the Cell will not
boot until the problem is corrected and Cell Power has been turned off, then
on again, using the PE command.
- Cause / Action:
Cause(1, probable): Invalid data programmed
in the Cell's FRU EEPROM or a CPU module's Scratch/FRU EEPROM. Action (1):
If in manufacturing, program correct data in partition specific field of the
Cell or CPU Module's FRU EEPROM. Otherwise, contact HP support personnel to
troubleshoot the problem. Cause(2): A hardware fault has occurred.
Action(2): Contact HP Support personnel to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 633
- Severity: MAJOR
- Event Summary: An error has occurred while updating System FW.
- Event Class: System
- Problem Description:
An error has occurred while updating
System FW. More details about the update failure may be available as
displayed by the Firmware Update Utility (FWUU).
- Cause / Action:
Cause(1): Obsolete version of FWUU.
Action(1): If you are not using the latest revision of FWUU, obtain and use
the latest version of FWUU to retry the update. Cause(2): MP firmware not at
a revision that supports the current version of PDHC FW or System FW.
Action(2): If MP is not at a compatible revision, update the MP firmware to
a compatible revision and repeat the firmware update. Cause(3): Other error
indicated by FWUU. Action(3): Exit from FWUU, reset the MP using the XD
command, then attempt to update Sytem FW. If repeated attempts to update the
System FW fail, contact HP support personnel to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 634
- Severity: MAJOR
- Event Summary: The PDHC firmware was reset for some unknown
reason.
- Event Class: System
- Problem Description:
The PDHC firmware was reset for some
unknown reason.
- Cause / Action:
Cause(1): System FW has reset the PDHC
because it suspects the PDHC of corrupting shared memory. Cause(2): A PDHC
watchdog timer timeout has occurred because the PDHC was stuck in some
unknown state. Cause(3): An unknown hardware fault has caused the PDHC to
reset.
Action: Upgrade PDHC firmware to the latest revision. If the error
continues, contact HP support personnel to troubleshoot the PDH Daughtercard
and/or Cell Board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 635
- Severity: CRITICAL
- Event Summary: Cell boot has been disabled because setup of a CPU
thermal sensor failed.
- Event Class: System
- Problem Description:
A hardware fault prevented the PDHC from
configuring the thermal sensor(s) on one or more of the CPU modules.
Following detection of this fault condition, the Cell will be prevented from
booting until the Cell is powered "off", then "on", using the PE command.
- Cause / Action:
Cause(1): A hardware fault exists in the
communication path to a CPU module's thermal sensor, or in the thermal
sensor itself. Cause(2): A hardware fault prevents access to a CPU module's
Processor Information ROM.
Action: Contact HP support personnel to
troubleshoot the Cell Board, the PDH Daughtercard, and/or the offending CPU
module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 636
- Severity: CRITICAL
- Event Summary: A CPU module has reported overtemp, so will be
powered off in 2 minutes.
- Event Class: System
- Problem Description:
A CPU module's temperature has exceed
the high temperature threshold. As a result of this event, an irrevocable 2
minute timer will begin. At the end of 2 minutes, the offending CPU module
will be powered off by the Cell hardware. The Cell must be powered off then
on using the MP's PE command before the CPU module will be powered again.
- Cause / Action:
Cause(1): Excessive heat in the data center
has caused the CPU module to heat up beyond the programmed temperature
threshold. Action(1): Resolve the environmental problem, shut down the
partition, then PE the Cell off, then on again. Cause(2): A hardware fault
has caused the CPU module to heat up beyond the programmed temperature
threshold. Cause(3): The Processor Information ROM on the processor module
is unprogrammed or programmed with invalid temperature thresholds.
Action(2,3): Contact HP support personnel to troubleshoot the
problem.
Cause(1): Excessive heat in the data center has caused the CPU
module to heat up beyond the programmed temperature threshold. Action(1):
Resolve the environmental problem, shut down the partition, then PE the Cell
off, then on again. Cause(2): A hardware fault has caused the CPU module to
heat up beyond the programmed temperature threshold. Cause(3): The Processor
Information ROM on the processor module is unprogrammed or programmed ! with
invalid temperature thresholds. Action(2,3): Contact HP support personnel to
troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 637
- Severity: MAJOR
- Event Summary: An error occurred while updating the PDHC
firmware.
- Event Class: System
- Problem Description:
An error occurred while updating the
PDHC firmware. More specific details of the update error may be displayed by
the Firmware Update utility running on the MP.
- Cause / Action:
Cause(1): MP firmware not at a revision that
supports that version of PDHC firmware. Action(1): If MP is not at a
compatible revision, update the MP firmware to a compatible revision and
repeat PDHC firmware update. Cause(2): Other error indicated by Firmware
Update. Action(2): Exit from Firmware Update, reset the MP using the XD
command, then attempt to update PDHC firmware again. If repeated attempts to
update the PDHC firmware fail, contact HP support personnel to troubleshoot
the problem
Cause(1): MP firmware not at a revision that supports that
version of PDHC firmware. Action(1): If MP is not at a compatible revision,
update the MP firmware to a compatible revision and repeat PDHC firmware
update. Cause(2): Other error indicated by Firmware Update. Action(2): Exit
from Firmware Update, reset the MP using the XD command, then attempt to
update PDHC firmware again. If repeated attempts to update the PDHC firmware
fail, contact HP support personnel to troubleshoot ! the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 638
- Severity: CRITICAL
- Event Summary: CPU Revisions did not match
- Event Class: System
- Problem Description:
2 CPUs in the system are reporting
different revisions. This event will be emitted in groups of 3 with the two
revisions reported in the first 2 data fields and the CPU number in the 3rd
data field.
- Cause / Action:
2 CPUs are at different revisions. Replace
incompatible CPU.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 639
- Severity: CRITICAL
- Event Summary: 2 cpus are running at mismatched frequencies.
- Event Class: System
- Problem Description:
This chassis code will be emitted in
pairs. 2 cpus are reporting that they are running at different frequencies.
The two frequencies are reported in the data fields.
- Cause / Action:
There is a CPU or Cell compatibility problem.
Verify that all cpus are clocked at the same frequency and have the same
ratios set.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 640
- Severity: CRITICAL
- Event Summary: A cpu is being over clocked
- Event Class: System
- Problem Description:
The rating for the cpu and the actual
speed will be emitted in 2 sequential event data fields.
- Cause / Action:
A cpu is being clocked at a rate higher than
it is rated for. Replace the cpu or cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 641
- Severity: FATAL
- Event Summary: Copy of complex profile on sub and cells don't
match
- Event Class: System
- Problem Description:
The complex profile is stored in NVRAM
on the MP and each cell. All copies must match. For this error to be
generated, not only is the MP's copy of the complex profile invalid, but not
all of the cell's copies match.
- Cause / Action:
Cause: MP NVRAM was erased by removing MP
from system without setting "NVRAM SAVE" switch to on. MP was replaced with
cabinet's AC Breakers "off". Either of first two causes and replacing or
installing a cell board with cabinet's AC Breakers "off". Action: Remove
cell board causing problem. Power complex on and allow cells to distribute
their copy of complex profile to MP, then add new cell following proper OLA
procedures. Remove improper cell board. Execute MP Handler "CC" command and
choose "Last Profile". This will load the sub with what should be the same
copy as the cells. Then add new cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 642
- Severity: FATAL
- Event Summary: Duplicate cabinet number detected
- Event Class: System
- Problem Description:
The MP detected 2 or more cabinets with
the same cabinet number.
- Cause / Action:
Cause: When adding a new cabinet to the
complex or replacing the UGUY, the cabinet number switch was set to a number
already in use. Action: Turn off AC breakers to cabinet with duplicate
number. Check all other cabinet numbers in the complex for validity. Set
cabinet number switch on UGUY-PCB in new cabinet (s) to proper cabinet
number. Turn on AC breakers for cabinet(s).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 643
- Severity: FATAL
- Event Summary: MP ID command must be run
- Event Class: System
- Problem Description:
The complex identification information
in group A of the complex profile is invalid. The MP (Managability
Processor) command "ID" must be run. The SSKEY hardware is required.
- Cause / Action:
Cause: This is the first time the machine has
been powered on and there is no valid complex profile anywhere. Action: Run
"CC" command and generate genesis profile. Cause: MP lost its profile by
being replaced with power off ,or, "NVRAM save" switch was not enabled and
MP was removed and replaced. Also, at the same time, a cell was replaced or
added while power was off. Both scenarios are violations of OL* Rules. A
complex_profile_incoherent code was issued. The "cc" command was run and
genesis profile was selected. Action: If "cc" command is selected, choose
"last good profile" instead of genesis profile, or remove illegal cell(s),
power up and follow OL* Rules.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 645
- Severity: MAJOR
- Event Summary: MP Battery is low
- Event Class: System
- Problem Description:
The battery on the SBCH is below the
safe threshold. The battery can be replaced online.
- Cause / Action:
Cause: MP was running on battery for too
long. Someone didn't set "NVRAM Save" switch to "off". Action: Replace
battery as per MP Battery Remove and Replace procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 646
- Severity: FATAL
- Event Summary: Partition being reset due to watchdog timeout
expiring
- Event Class: System
- Problem Description:
The partition is being reset because its
watchdog timer expired and automatic restart is enabled.
- Cause / Action:
Cause: There are 2 watchdog mechanisms, both
of which trigger the MP to reset a partition if its OS becomes unresponsive.
An unresponsive OS is detected when the OS fails to refresh the watchdog
timer before it expires. PA systems refresh the watchdog timer by emitting
an event with data field set to activity level/timeout, and the timeout
fields specifies the desired timeout. This timer can be disabled with the MP
AR command. IPF systems refresh the watchdog timer using the IPMI clear
watchdog command. The AR command does not affect the IPMI watchdog timer.
Regardless of which timer was in use, the MP emits this event when timer
expiration triggers resetting the partition. Action: Find out why the
partition's OS had hung. The cause could be bad HW that crashed the
partition, or in rare cases, a combination of events that caused the OS to
be unable to refresh the watchdog timer. Look for other events preceeding
the timeout for clues to the root cause of the partition bei! ng
unresponsive.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 647
- Severity: MAJOR
- Event Summary: PDHC FW was reset by hardware due to firmware
inactivity.
- Event Class: System
- Problem Description:
The processor dependent hardware
controller (PDHC) on the cell board had its watchdog timer expire. The PDHC
will reset the watchdog as the main program runs. If the watchdog does not
get reset within 7 seconds the timer will expire, resetting the PDHC.
- Cause / Action:
Cause: Processor dependent hardware
controller (PDHC) Hardware Failed; causing inactivity. PDHC Firmware hung;
causing inactivity.
Action: Even though the PDHC will reset itself
without interrupting the cell, HP Support personnel should be contacted to
troubleshoot the PDH daughtercard and/or cell board as soon as possible.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 649
- Severity: MAJOR
- Event Summary: Power Up Aborted, Over Temp
- Event Class: System
- Problem Description:
The Cabinet Power Up request was aborted
due to ambient air over temperature.
- Cause / Action:
Cause: Computer Room over temp Action: Cool
Computer Room Cause: Environment immediately surrounding cabinet. Action:
Correct local environmental problem Cause: Reporting Error Action:
Troubleshoot ambient air sensor/cable/PM3.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 651
- Severity: FATAL
- Event Summary: No Cabinet Start, Insufficient Blowers
- Event Class: System
- Problem Description:
When given a power up request, the
cabinet had to abort the start up due to less than the required number of
Cabinet Blowers installed.
- Cause / Action:
Cause: The number of blowers required is a
hard number. It is not dependent upon the number of entities installed in a
Cabinet. The Utilities Subsystem is not allowing the Cabinet to power up due
to an insufficient number of installed blowers. Action: Install missing
Cabinet Blowers. If proper number of blowers are installed, troubleshoot
blower presence detection.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 652
- Severity: FATAL
- Event Summary: No Cabinet Start, Insufficient IO Fans
- Event Class: System
- Problem Description:
When given a power up request, the
cabinet had to abort the start up due to less than the required number of IO
fans present.
- Cause / Action:
Cause: The number of IO fans required is a
hard number. It is not dependent upon the number of entities installed in a
Cabinet. The Utilities Subsystem is not allowing the cabinet to power up due
to an insufficient number of installed IO fans. Action: Install missing IO
fans, or if proper number installed, troubleshoot IO fan presence
detection.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 653
- Severity: MAJOR
- Event Summary: AC power to the PDCA was removed. Data Byte 3
specifies PDCA number.
- Event Class: System
- Problem Description:
The AC power connected to the PDCA
(Power Distribution Control Assembly) was removed. The data field contains
the physical location of the PDCA. The PDCA source that was deleted can be
identified by the implementation dependent field (data byte 3) of the
physical location: data byte[3]: 0 for PDCA 0, 1 for PDCA 1.
- Cause / Action:
Cause: Circuit breakers on the PDCA are open.
Action: Close the PDCA circuit breakers. Cause: Power source supplying AC to
the PDCA has failed. Action: Troubleshoot AC power problem. Cause: PDCA
(Power Distribution Control Assembly) has failed. Action: Replace the PDCA
with proper type (4-wire or 5-wire) PDCA following power distribution
control assembly Remove and Replace procedures. Cause: AC Detection and
monitoring circuitry failed. Action: Troubleshoot and replace failed Field
Replaceable Units.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 654
- Severity: MAJOR
- Event Summary: Cabinet Main Blower Failed
- Event Class: System
- Problem Description:
A cabinet main blower has failed.
Depending on the number of blowers still operating, the cabinet may or may
not shut down. View the Error Log entries to determine if the cabinet is
operating. If many log entries call out entities powering off during the
same time frame as this BLOWR_FAIL, the cabinet has probably shutdown.
Carefully review the log for the first few events within the same time frame
for the root cause of the problem. The GSP command, PS, will show a detailed
power status for a cabinet. If the +48V LED on the Front Panel Board is not
lit, power is not enabled to the cabinet. This is an indication the cabinet
blowers have probably gone from N to N - 1 status requiring an immediate
cabinet shutdown.
- Cause / Action:
Cause: Cabinet Blower Failed Action: Replace
failed blower module as soon as possible following the Blower Module Remove
and Replace Procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 655
- Severity: MAJOR
- Event Summary: 48 Volt Converter Failed. Data Byte 3 specifies
PDCA number.
- Event Class: System
- Problem Description:
A 48 Volt DC Converter powered by the
specified PDCA failed on the designated Bulk Power Supply. The PDCA powering
the converter on the BPS that failed can be identified by the implementation
dependent field (data byte 3) of the BPS' physical location: data byte[3]: 0
for PDCA 0, 1 for PDCA 1.
- Cause / Action:
Cause: The 48 Volt DC Converter powered by
the PDCA identified failed in the named Bulk Power Supply. Action: Contact
HP Support personnel to troubleshoot problem Cause: The PDCA identified has
failed. This will be evident by many BPS_FAIL codes and probably a
AC_DELETED code in the Event Log. Action: Contact HP Support personnel to
troubleshoot problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 657
- Severity: MAJOR
- Event Summary: Fan failed in designated Bulk Power Supply
- Event Class: System
- Problem Description:
The designated Bulk Power Supply is
reporting its fan has failed.
- Cause / Action:
Cause: Fan failure or fan obstructed Action:
If fan is obstructed, remove obstruction. If no obstruction, Contact HP
Support personnel to troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 659
- Severity: MAJOR
- Event Summary: Bulk Power Supplies are not Redundant.
- Event Class: System
- Problem Description:
The number of functioning Bulk Power
Supplies has decreased to where the Cabinet Power supplied (number of
available Bulk Power Supplies times power output per each) minus the
estimated Cabinet Power consumed is greater than 0, but less than the output
of one Bulk Power Supply.
- Cause / Action:
Cause: Entities were added to the cabinet,
increasing the estimated Power Consumption. Or, a non-functional GSP bus
entity has become functional, providing previously missing power consumption
information. Action: Purchase and install a Bulk Power Supply, if redundancy
is desired. Cause: Bulk Power Supply failed. Action: Contact HP Support
personnel to troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 660
- Severity: FATAL
- Event Summary: +48V DC has exceeded its upper limit
- Event Class: System
- Problem Description:
The PM has detected the value of +48V
power, as measured on the UGUY board, has exceeded an upper threshold.
- Cause / Action:
Cause: The cabinet's 48V power has exceeded
an acceptable upper threshold. Action: Contact HP Support personnel to
troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 661
- Severity: FATAL
- Event Summary: +48V DC has fallen below its lower limit
- Event Class: System
- Problem Description:
The PM has detected the value of +48V
power, as measured on the UGUY board, has fallen below a lower threshold.
- Cause / Action:
Cause: The cabinet's 48V power has fallen
below an acceptable lower threshold. Action: Contact HP Support personnel to
troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 662
- Severity: MAJOR
- Event Summary: Cabinet Fan Failed
- Event Class: System
- Problem Description:
A cabinet fan has failed. Depending on
the number of cabinet fans still operating, the cabinet may or may not shut
down. View the Error Log entries to determine if the cabinet is operating.
- Cause / Action:
Cause: Cabinet Fan Failed Action: Replace
failed cabinet fan module as soon as possible following the Cabinet Fan
Module Remove and Replace Procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 670
- Severity: FATAL
- Event Summary: Housekeeping power has exceeded expected levels.
- Event Class: System
- Problem Description:
Housekeeping power has exceeded expected
levels.
- Cause / Action:
Cause: The cabinet's housekeeping power has
risen above an acceptable upper threshold. Action: Contact HP Support
personnel to troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 671
- Severity: FATAL
- Event Summary: Housekeeping power has fallen below expected
levels.
- Event Class: System
- Problem Description:
Housekeeping power has fallen below
expected levels.
- Cause / Action:
Cause: The cabinet's housekeeping power has
fallen below an acceptable upper threshold. Action: Contact HP Support
personnel to troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 672
- Severity: MAJOR
- Event Summary: The BPSs for the cabinet are illegally configured.
Data Byte 3 = PDCA number.
- Event Class: System
- Problem Description:
Through failures or reconfiguration, the
BPS for the cabinet named are illegally configured. There must be a BPS
connected to each phase of the power. Phase 1 feeds BPS slots 0 & 1,
phase 2 feeds slots 2 & 3, and phase 3 feeds 4 & 5. There must be a
BPS connected to each phase. If 4 BPS are installed in a cabinet in slots 0
- 3 and 4 & 5 were empty, this would be an illegal configuration. They
should be installed in 0,1,2,and 4 or 0,1,3,and 5 or some combination
thereof. The PDCA physical location determines which phase is configured
incorrectly. Data Byte 3 (implementation dependent field) indicates the PDCA
number used when the configuration error occurred:
- Cause / Action:
Cause: The BPS are installed in an illegal
configuration. Action: Re-configure the BPS in a manner consistent with the
explanation in the Problem Description statement
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 673
- Severity: MAJOR
- Event Summary: BPS ID received from installed Bulk Power Supply
was unknown
- Event Class: System
- Problem Description:
A Bulk Power Supply is reporting an
unknown BPS ID. The Bulk Power Supply will not be powered up and added to
the Power Available tally. If cabinet is not powered up, it will refuse to
power up until this fault is corrected.
- Cause / Action:
Cause: The designated power supply is
responding with an illegal BPS ID. It could be a faulty supply, a different
revision, or a wrong supply in the wrong box. Action: Replace this Bulk
Power Supply with a proper one. Cause: A new revision of Power Supply that
requires a PM3 firmware upgrade was attempting install. Action: Check
service notes for firmware revisions and compatibility charts.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 675
- Severity: FATAL
- Event Summary: Ambient Air Sensor Overtemp Warning
- Event Class: System
- Problem Description:
The cabinet's Ambient Air Sensor
detected a change in air temperature entering the over-temp-high range. The
Cabinet will be shutting itself down to prevent component damage.
- Cause / Action:
Cause: Room Temperature has risen to a
FATAL level. Action: Shutdown and power off the system. Correct air
temperature problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 676
- Severity: MAJOR
- Event Summary: Ambient Air Sensor Overtemp Warning
- Event Class: System
- Problem Description:
The cabinet's Ambient Air Sensor
detected a change in air temperature crossing to the low range. The air
temperature may be rising or falling. This is just a reporting of entering
the over-temp-low range.
- Cause / Action:
Cause: Room Temperature is rising or falling.
Action: Check the error log's previous entries within a logical time frame.
If temperature is rising, prepare for system shutdown. If temperature is
dropping, then problem is probably resolved.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 677
- Severity: MAJOR
- Event Summary: Ambient Air Sensor Overtemp Warning
- Event Class: System
- Problem Description:
The cabinet's Ambient Air Sensor
detected a change in air temperature crossing to the mid range. The air
temperature may be rising or falling. This is just a reporting of entering
the over-temp-mid range.
- Cause / Action:
Cause: Room Temperature is rising or falling.
Action: Check the error log's previous entries within a logical time frame.
If temperature is rising, prepare for system shutdown. If temperature is
dropping, then problem is probably resolved.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 678
- Severity: MAJOR
- Event Summary: IO Fan Failed
- Event Class: System
- Problem Description:
An IO Chassis cooling fan has failed.
Depending on the number of fans still operating, the cabinet may or may not
shut down. View Error Log entries to determine if the cabinet is operating.
If many log entries call out entities powering off during the same time
frame as this IOFAN_FAIL, the cabinet has probably shutdown. Carefully
review the log for the first few events within the same time frame for the
root cause of the problem. The Guardian Service Processor command, PS, will
show a detailed power status for a cabinet. The +48V LED on the Front Panel
Board not lit, power is not enabled to the cabinet, indicating the cabinet
IO Chassis fans have probably gone from N to N - 1 status requiring an
immediate cabinet shutdown.
- Cause / Action:
Cause: IO Cooling Fan Failed Action: Replace
IO Fan Module as soon as possible following the IO Fan Module Remove and
Replace Procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 680
- Severity: MAJOR
- Event Summary: Cabinet Power System is in overload.
- Event Class: System
- Problem Description:
This code is issued when the Cabinet
Power supplied (number of Bulk Power Supplies times power output per each)
minus the estimated Cabinet Power consumed drops below 0. Utilities firmware
will not allow a cabinet in this state to power up (see ABORT_PWRUP_BPS).
Utilities firmware will not shut down a cabinet in this state. However,
there is a possibility of a cabinet brownout, making the cabinet unreliable.
- Cause / Action:
Cause: A Bulk Power Supply has failed, or,
entities were added. Look for one or more BPS_Fail Chassis Codes preceding
this one for the actual failures. This code is a warning of possible cabinet
unreliability. Action: Contact HP Support personnel to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 681
- Severity: FATAL
- Event Summary: Cabinet Shutdown - Insufficient Blowers
- Event Class: System
- Problem Description:
After a BLOWR_FAIL, there were N-1
blowers functioning. This is an illegal condition causing immediate cabinet
shutdown to prevent component damage.
- Cause / Action:
Cause: One blower has failed creating
condition N. Before condition N was corrected, another blower in the same
cabinet was declared failed. This created the illegal condition of N-1.
Action: Contact HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 682
- Severity: FATAL
- Event Summary: Cabinet Shutdown - Insufficient IO Fans
- Event Class: System
- Problem Description:
After a IOFAN_FAIL, there were N-1 fans
functioning. This is an illegal condition causing immediate cabinet shutdown
to prevent component damage.
- Cause / Action:
Cause: One IO fan has failed creating
condition N. Before condition N was corrected, another IO fan in the same
cabinet failed. This created the illegal condition of N-1. Action: Contact
HP Support personnel to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 683
- Severity: MAJOR
- Event Summary: IO Expansion Utility Cabinet Fan Failed
- Event Class: System
- Problem Description:
One of two fans in the Utility chassis
of the IO Expansion Cabinet has failed.
- Cause / Action:
Cause: IO Expansion Utility Fan or Fan sensor
failure PM failure Action: Contact HP Support personnel to troubleshoot the
problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 684
- Severity: FATAL
- Event Summary: Watchdog Timer Expired
- Event Class: System
- Problem Description:
The Watchdog Timer checks for
inactivity, or hung state, of the Cabinet Level Utilities (CLU) portion of
the UGUY. During activity, the timer is continually reset. If the timer
expires, it will automatically reset the CLU microprocessor. This will not
affect running partitions.
- Cause / Action:
Cause: CLU has been reset after a firmware
update. Action: None. Cause: The CLU firmware has been reset by the MFG MP
command RU. Action: None. Cause: Hardware or firmware failure on the UGUY.
Action: Check revision of CLU firmware. If out of date, or known bad
revision, use FWUU to update CLU firmware. Contact HP Support personnel to
troubleshoot problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 685
- Severity: FATAL
- Event Summary: Invalid checksum from EEPROM
- Event Class: System
- Problem Description:
An invalid checksum was received when
reading the FRUID EEPROM for the device named in the chassis code. If this
is a single error, the fault lies with the named FRU. If there are many
INVALID_CKSM entries in the Event Log, there is probably a problem with the
I2C bus.
- Cause / Action:
Cause: Data corrupted in the named EEPROM.
Action: If this is a single entry, replace the FRU. Cause: Problem with I2C
bus. Action: If every entity with a FRUID logs an error, the problem is
probably with the CLU portion of the Utilities Board. Replace the Utilities
Board following the Utilities Board Remove and Replace Procedures. If there
are a few entities reporting checksum errors, but several have reported in
properly, chances are one device is causing the problem with the I2C bus.
This will take a more concerted effort to find and correct that problem.
Probably wish to take the bus to a minimum configuration and test, add, test
until the failure is verified.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 686
- Severity: MAJOR
- Event Summary: System Backplane Power Board Fault
- Event Class: System
- Problem Description:
One or more of the System Backplane
Power Boards is reporting a DC Fault through the System Backplane Local
Power Monitor. The physical location of the failing power board is in the
Data Field of the event.
- Cause / Action:
Cause: A DC-DC converter on the named power
board failed. Action: Contact HP Support personnel to troubleshoot the
problem Caution: The 1.8 volt converters are N+1. The 3.3 volt converters
are N+2. If there is a situation where a 1.8 fails at the same time as a 3.3
on a different power board, replace the failed 1.8 board first.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 687
- Severity: MAJOR
- Event Summary: Read of EEPROM failed
- Event Class: System
- Problem Description:
An attempt to read the EEPROM (FRUID) on
the IO Backplane Board failed.
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should identify entities on both the System
Backplane and the Master IO Backplane. Action: Contact HP Support personnel
to troubleshoot the problem. Cause: The cable from the Utilities Backplane
to the Master IO Backplane is bad, or is not properly connected. Action:
Check and reseat the Master IO Backplane Utilities cable. If no help,
contact HP Support personnel to troubleshoot the problem. Cause: The I2C bus
into the IO Backplane EEPROM is bad. Action: Could possibly be a bent pin on
the Master IO Backplane Utilities cable connectors. Check the connectors at
each end of the cable for bent or broken pins. If the connectors and cable
are good, contact HP Support personnel to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 688
- Severity: MAJOR
- Event Summary: Read of EEPROM failed
- Event Class: System
- Problem Description:
An attempt to read the EEPROM (FRUID) on
the IO Backplane Power Board failed.
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should identify entities on both the System
Backplane and the Master IO Backplane. Action: Contact HP Support personnel
to troubleshoot the problem. Cause: The cable from the Utilities Backplane
to the Master IO Backplane is bad, or is not properly connected. Action:
Check and reseat the Master IO Backplane Utilities cable. If no help,
contact HP Support personnel to troubleshoot the problem. Cause: The I2C bus
into the IO Power Board EEPROM is bad. Action: Could possibly be a bent pin
on the Master IO Backplane Utilities cable connectors. Check the connectors
at each end of the cable for bent or broken pins. Or, it could be a bent pin
on the Master IO Backplane where the PCI Cardcage connects. If the MIOB,
connectors and cable are good, contact HP Support personnel to troubleshoot
the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 689
- Severity: MAJOR
- Event Summary: Read of LPM Fault failed
- Event Class: System
- Problem Description:
An attempt to read the Local Power
Monitor Fault register on the IO Backplane Power Board failed.
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should identify entities on both the System
Backplane and the Master IO Backplane. Action: Contact HP Support personnel
to troubleshoot the problem. Cause: The cable from the Utilities Backplane
to the Master IO Backplane is bad, or is not properly connected. Action:
Check and reseat the Master IO Backplane Utilities cable. If no help,
contact HP Support personnel to troubleshoot the problem. Cause: The IO
Backplane Power Board is bad. Action: Contact HP Support personnel to
troubleshoot the problem. Cause: The I2C bus into the IO Power Board EEPROM
is bad. Action: Could possibly be a bent pin on the Master IO Backplane
Utilities cable connectors. Check the connectors at each end of the cable
for bent or broken pins. Or, it could be a bent pin on the Master IO
Backplane where the PCI Cardcage connects. If the MIOB, connectors ! and
cable are good, contact HP Support personnel to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 690
- Severity: FATAL
- Event Summary: IO Power Board Over temperature
- Event Class: System
- Problem Description:
The Local Power Monitor of the named IO
Chassis is reporting a Power Brick over temperature condition.
- Cause / Action:
Cause: The ambient air is too warm. Action:
Check the Error Log for other Over tempature Warnings to confirm the environmental
problem. Cause: The specified Power Brick, or the Local Power Monitor, has
failed in such a manner as to report this error. Action: Contact HP Support
personnel to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 691
- Severity: FATAL
- Event Summary: IO Power Board Fault
- Event Class: System
- Problem Description:
The Local Power Monitor on the named IO
Chassis has reported a power fault condition.
- Cause / Action:
Cause: The named power brick on the named IO
Chassis has failed. Action: Contact HP Support personnel to troubleshoot the
problem. Cause: Input power has created some fault conditions. This will be
evident by the presence of several chassis codes in the Error Log within the
same time frame. Action: The Error Log must be reviewed carefully for the
root cause of the errors. There is almost always a single cause, even if
many events are reported.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 692
- Severity: MAJOR
- Event Summary: Voltage Margin on IO Power Board failed
- Event Class: System
- Problem Description:
The Local Power Monitor on the named IO
Power Board failed to properly margin the power as commanded.
- Cause / Action:
Cause: The IO Power Board LPM is not
communicating with the CLU. Action: Some troubleshooting will be involved
here. Is it the IO Power Board LPM, or the CLU. You'll have to check the
Error Log for other entries related to either CLU communications problems or
the IO Power Board LPM. If there are messages about other
HIOPB_VOLT_MRGN_FAIL entries as well as SYS_BKP_VOLT_MRGN_FAIL, it is
pointing to the CLU. Cause: The MP is not communicating with the CLU.
Action: The MP bus (USB) is not functioning. There should be many entries in
the Error Log with the same type of error message. They will point to MP bus
errors. Also, try the GSP "PS" command. This will display status of entities
within a cabinet.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 693
- Severity: MAJOR
- Event Summary: Failure to read data from a FRUID EEPROM
- Event Class: System
- Problem Description:
Either by command or as part of
initialization, the data from a FRUID EEPROM failed a read command. This
does not necessarily mean the FRU has failed, just that the FRUID can't be
read. The specific FRU Handle of the failing FRUID is embedded in the two
uppermost bytes of the data field.
- Cause / Action:
Cause: The CLU can't read the data from a
FRUID EEPROM. Action: Contact HP Support personnel to troubleshoot the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 694
- Severity: MAJOR
- Event Summary: Failure to read data from a SBCH FRUID EEPROM
- Event Class: System
- Problem Description:
Either by command or as part of
initialization, the data from a FRUID EEPROM failed a read command. This
does not necessarily mean the FRU has failed, just that the FRUID data
cannot be read.
- Cause / Action:
Cause: The CLU cannot read the data contained
in the EEPROM on the SBCH board in the same cabinet. Action: Contact HP
Support personnel to troubleshoot the problem. If this is the only READ
failure in this timeframe, replace the SBCH board following the SBCH Board
Remove and Replace Procedures as soon as possible. If there are other READ
failures in this same cabinet, replace the Utilities Board following the
Utilities Board Remove and Replace Procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 695
- Severity: MAJOR
- Event Summary: Failure to read data from a UGUY FRUID EEPROM
- Event Class: System
- Problem Description:
Either by command or as part of
initialization, the data from a FRUID EEPROM failed a read command. This
does not necessarily mean the FRU has failed, just that the FRUID can't be
read.
- Cause / Action:
Cause: Attempted access to read the UGUY
FRUID EEPROM failed. Action: If there is only one FRUID that can't be read,
replace that FRU as soon as possible. If there are a lot of log entries for
different FRUs, suspect the Utilities Board or the Utilities cable to those
FRUs. For example, if the failures are all associated with a Master IO
Backplane, the failing FRU is probably the Utilities cable to that
backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 696
- Severity: MAJOR
- Event Summary: Read EEPROM failed
- Event Class: System
- Problem Description:
An attempt to read the EEPROM (FRUID) on
the System Backplane failed
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should indentify entities on both the System
Backplane and the Master IO Backplane. Action: Replace the Utilities board
(UGUY) following the Utilities Board Remove and Replace procedures. Cause:
The 100 pin cable from the Utilities Backplane to the System Backplane is
bad, or is not properly connected. Action: Check and reseat the System
Backplane Utilities cable. If this does not resolve the issue, replace the
System Backplane utilities cable following the Backplane Utilities Cable
Remove and Replace procedures. Cause: The I2C bus into the System Backplane
EEPROM is bad. Action: Could possibly be a bent pin on the System Backplane
Utilities cable connectors. Check the connectors at each end of the cable
for bent or broken pins. If the connectors and cable are good, replace the
System Backplane following the System Backplane Re! move and Replace
procedures. NOTE: System Backplane replacement is a major undertaking.
Ensure all other possibilities have been explored before replacing the
backplane. You should have WTEC approval before replacing the backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 697
- Severity: MAJOR
- Event Summary: Read command on System Backplane I2C bus failed
- Event Class: System
- Problem Description:
A read command on the system backplane
I2C bus failed.
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should indentify entities on both the System
Backplane and the Master IO Backplane. Action: Replace the Utilities board
(UGUY) following the Utilities Board Remove and Replace procedures. Cause:
The 100 pin cable from the Utilities Backplane to the System Backplane is
bad, or is not properly connected. Action: Check and reseat the System
Backplane Utilities cable. If no help, replace the System Backplane
utilities cable following the Backplane Utilities Cable Remove and Replace
procedures. Cause: The I2C bus into the System Backplane EEPROM is bad.
Action: Could possibly be a bent pin on the System Backplane Utilities cable
connectors. Check the connectors at each end of the cable for bent or broken
pins. If the connectors and cable are good, replace the System Backplane
following the System Backplane Remove and Replace procedures. NOTE: System
Backplane replacement is a major undertaking. Ensure all other possibilities
have been explored before replacing the backplane. You should have WTEC
approval before replacing the backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 698
- Severity: MAJOR
- Event Summary: Write command on System Backplane I2C bus failed
- Event Class: System
- Problem Description:
A write command on the system backplane
I2C bus failed. The type of command that failed can be identified by the
activity status field (last byte) of the encoded field. B = RC Cable
Configuration Register write C = Backplane Voltage Margin Register write 9 =
Flex circuit configuration register write
- Cause / Action:
Cause: The I2C controller on the Utilities
Board (CLU section) is bad. This will be shown by many I2C failure codes in
the Error Log. These codes should identify entities on both the System
Backplane and the Master IO Backplane. Action: Replace the Utilities board
(UGUY) following the Utilities Board Remove and Replace procedures. Cause:
The 100 pin cable from the Utilities Backplane to the System Backplane is
bad, or is not properly connected. Action: Check and reseat the System
Backplane Utilities cable. If no help, replace the System Backplane
utilities cable following the Backplane Utilities Cable Remove and Replace
procedures. Cause: The I2C bus into the System Backplane EEPROM is bad.
Action: Could possibly be a bent pin on the System Backplane Utilities cable
connectors. Check the connectors at each end of the cable for bent or broken
pins. If the connectors and cable are good, replace the System Backplane
following the System Backplane Remove and Replace procedure. NOTE: System
Backplane replacement is a major undertaking. Ensure all other possibilities
have been explored before replacing the backplane. You should have WTEC
approval before replacing the backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 699
- Severity: FATAL
- Event Summary: System Backplane Power Fault
- Event Class: System
- Problem Description:
The Local Power Monitor on the named
System Backplane has detected a power fault. The failing Backplane Power
Board status is read from the Backplane LPM I2C interface register and the
value is placed in the data field of the event (bits 15-8).
- Cause / Action:
Cause: While running normally, the CLU
microcontroller detected a fault on the I2C Bus from the system Backplane
LPM. Action: Check other log entries around this time for other events. If
there are other events, analyze for best troubleshooting approach. Check the
log carefully as a shorted ASIC could cause many errors to occur. These
errors will not necessarily point to the ASIC. If none, replace failed
Backplane Power Board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 700
- Severity: CRITICAL
- Event Summary: System Backplane voltage margin failed
- Event Class: System
- Problem Description:
Margining voltage to the System
Backplane has failed.
- Cause / Action:
Cause: The CLU was unable to write to the
voltage margin register on the System backplane. Action: Try re-margining
the system backplane and check connections. If many I2C access events are
occurring inspect the UGUY utilities board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 701
- Severity: MAJOR
- Event Summary: Failure to write data to FRUID EEPROM
- Event Class: System
- Problem Description:
An attempt to write data to the FRUID
EEPROM by the MFG level MP command WF failed. The FRU handle of the failing
FRUID is embedded in the two uppermost bytes of the data field.
- Cause / Action:
Cause: The entity being written to is not
powered up. Action: Power the entity with the PE command. Cause: The entity
being written to has failed. Action: Replace the entity with the failed
FRUID. Cause: The I2C bus has failed. Look for other entries in the Error
Log to confirm this. If there are a lot of entries in this timeframe about
I2C failures, analyze errors the errors to see if they are all within a
cabinet, or the entire complex. Action: Each cabinet's Utilities Board (CLU
and PM) is responsible for the query over I2C for the FRUID, LPM status, and
other information. If there are other entries in the Error Log and they are
all within a cabinet, replace the Utilities Board following the Utilities
Board Remove and Replace Procedures.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 707
- Severity: FATAL
- Event Summary: PDH Controller firmware version is not supported
with this version of MP FW
- Event Class: System
- Problem Description:
The MP checked the FW revision of the
PDHC identified in the physical location data field and discovered that it
did not recognize the revision as one that it has been qualified with. This is
an unsupported configuration.
- Cause / Action:
Update PDHC or MP FW
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 708
- Severity: CRITICAL
- Event Summary: Power fault on cell board
- Event Class: System
- Problem Description:
The local Power Monitor is reporting a
fault with the named Cell Power Board.
- Cause / Action:
Cause: One or more of the DC to DC power
converters on the Cell Power Board is displaying a fault condition. Action:
Contact HP Support personnel to troubleshoot the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 710
- Severity: MAJOR
- Event Summary: The ExecuteCommand function failed on a CPU.
- Event Class: System
- Problem Description:
ExecuteCommand issues commands that
execute on remote CPUs via IPI interrupts. If the command failed to execute,
this event is printed and the data field contains the status.
- Cause / Action:
Inter-Processor-Interrupts may not be
working, or the command may have timed out. This could be a firmware bug or
hardware problem. Look for other clues in the event log.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 711
- Severity: MAJOR
- Event Summary: A remote CPU is not prepared to receive a command
- Event Class: System
- Problem Description:
A remote CPU is in a state where it
cannot receive and execute a new command. The current status of the CPU is
provided in the data field.
- Cause / Action:
The CPU may be stuck waiting for a previous
command or may not be healthy. This could also be caused by a system
resource contention problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 712
- Severity: CRITICAL
- Event Summary: Boot is disabled because the cell type does not
match the System FW ROM type.
- Event Class: System
- Problem Description:
The cell type (IPF or PA) does not match
System FW type. The cell type is detected based on information stored in CPU
modules' FRUID EEPROMs. The System FW type is determined based on data that
is embedded in the System FW ROM image. This is checked each time Cell power
transitions from off to on, and each time the System FW is updated.
Following the detection of this mismatch, the Cell will not be allowed to
boot until the problem has been resolved.
- Cause / Action:
Cause(1): The System FW ROM in unprogrammed,
or an invalid System FW ROM image is programmed in the System FW flash.
Action(1): Update the System FW using Firmware Update from the MP. Cause(2):
The Cell's installed CPU modules do not all have the same type, frequency
and partition compatibility, so the Cell type cannot be accurately
determined. In this case, a CPU_MOD_COMPAT_MISMATCH event should also be
emitted. Action(2): Contact HP support personnel to troubleshoot the
mismatched CPU module Cause(3): A CPU module's FRU data is programmed
incorrectly. Action(3): If this is in manufacturing, re-program the FRU
specific field of the FRU data for the CPU module. Otherwise, contact HP
support personnel to troubleshoot the mismatched CPU module..
Cause(1):
The System FW ROM in unprogrammed, or an invalid System FW ROM image is
programmed in the System FW flash. Action(1): Update the System FW using
Firmware Update from the MP. Cause(2): The Cell's installed CPU modules d! o
not all have the same type, frequency and partition compatibility, so the
Cell type cannot be accurately determined. In this case, a
CPU_MOD_COMPAT_MISMATCH event should also be emitted. Action(2): Contact HP
support personnel to troubleshoot the mismatched CPU module. Cause(3): A CPU
module's FRU data is programmed incorrectly. Action(3): If this is in
manufacturing, re-program the FRU specific field of the FRU data for the CPU
module. Otherwise, contact HP support personnel to troubleshoot the
mismatched CPU module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 713
- Severity: MAJOR
- Event Summary: The PDHC has waited an abnormally long time for
PDH bus access.
- Event Class: System
- Problem Description:
This event is emitted after the PDHC has
waited longer than a maximum expected time for the PDH arbiter to grant it
control of the PDH bus. The PDHC will continue waiting for contol of the PDH
bus until the arbiter grants it control, or the Cell is powered off using
the MP's PE command. While waiting for the PDH bus, the PDHC will NOT
perform its normal duties such as monitoring the Cell status, and passing
messages from the system to the MP, and the PDHC heartbeat will not blink.
- Cause / Action:
Cause (probable): A hardware fault is
preventing the PDH arbiter from granting the PDHC control of the bus.
Action: Contact HP support personnel to troubleshoot the cell board and/or
PDH daughtercard. Cause: Bad connection on UGUY clock cable. Action: Check
UGUY clock cable connection.
Cause (probable): A hardware fault is
preventing the PDH arbiter from granting the PDHC control of the bus.
Action: Contact HP support personnel to troubleshoot the Cell Board and/or
PDH Daughtercard. Cause: Bad connection on UGUY clock cable. Action: Check
UGUY clock cable connection.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 714
- Severity: MAJOR
- Event Summary: The PDHC has waited an abnormally long time to
obtain the PDH semaphore.
- Event Class: System
- Problem Description:
This event is emitted after the PDHC has
waited longer than a maximum expected time to obtain control of the PDH bus
semaphore. The PDHC will continue waiting for contol of the PDH bus
semaphore until System FW relinquishes control of the semaphore, or the Cell
is powered off using the MP's PE command. While waiting for the PDH bus
semaphore, the PDHC will NOT perform its normal duties such as monitoring
the Cell status, and passing messages from the system to the MP, and the
PDHC heartbeat will not blink. The data field contains debug data that may
be useful for developers. Data_byte[0] = last value read from PDHC's address
for the microSemaphore register. Data_byte[1] = boolean indicator
(1=set,0=not_set) of whether the PDHC's flag is set. Data_byte[2] = boolean
indicator (1=set,0=not_set) of whether the System FW's flag is set.
- Cause / Action:
Cause(1): System FW has control of the PDH
bus semaphore, and has failed to relinquish control of it. Action(1): Update
the System FW revision to the latest version of System FW using the Firmware
Update Utility. Cause(2): A hardware fault is preventing the PDH bus
semaphore from being taken/released as expected. Action(2): Contact HP
support personnel to troubleshoot the Cell Board and/or PDH Daughtercard
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 715
- Severity: MAJOR
- Event Summary: An error occurred while transmitting an IPMI
message in the BMC2HOST direction.
- Event Class: System
- Problem Description:
This event indicates that an error
occurred while transmitting an IPMI message in the BMC2HOST direction. The
data field contains more detailed information about the source of the error.
Data Bytes 0 & 1 form a 16-bit IPMI error indicator that has the
following values and meanings: 1 - IPMI_HOST_BUSY_TIMEOUT - The PDHC could
not put a message in the BMC2HOST hardware message queue for over 10
seconds, so the pending message(s) were dropped. 2 - IPMI_INVALID_MSG_SIZE -
The MP sent an IPMI message response that has an embedded size indicator
that is less than 4 bytes or greater than the size of the message data. The
poorly formed message response will be dropped. 3 - IPMI_BMC2HOST_Q_FULL -
The BMC2HOST message queue in the PDHC is full, so a message response from
the MP has been dropped.
- Cause / Action:
Cause(1): An unknown OS IPMI driver or
Utilities FW bug has occurred. Action(1): Update PDHC FW, MP FW, System FW
and the OS IPMI driver to the latest revisions. Cause(2): A hardware fault
is preventing the BMC2HOST queue from working. Action(2): Contact HP support
personnel to troubleshoot the PDH Daughtercard.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 716
- Severity: MAJOR
- Event Summary: EFI unable to read initial debug level from the
BMC
- Event Class: System
- Problem Description:
EFI was unable to read the initial debug
level from the BMC token. EFI will continue with an unknown value for the
debug level. Data Field: Return status from internal EFI function.
- Cause / Action:
Cause: BMC not functioning properly. Action:
Reset the BMC. Contact your HP representative to check the BMC. Cause: SAL
service to read tokens not functioning properly. Action: Reset the system.
Clear NVM. Upgrade system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 717
- Severity: CRITICAL
- Event Summary: A XBC port was unexpectedly found to not be
landmined.
- Event Class: System
- Problem Description:
A XBC port was unexpectedly found to not
be landmined. The data field consists of the XBC number (32:43) and the port
number (44:55).
- Cause / Action:
Cause: An XBC is indicating a port failure
Action: Validate all of the cells connectivity to the PD Check the TOGO
chips seating reset the system replace either cells/system backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 718
- Severity: FATAL
- Event Summary: An invalid number of XBC ports were landmined in
the system.
- Event Class: System
- Problem Description:
The number of landmined XBC ports was
not within the allowable range. There is a minimum number of landmined ports
because some ports are always unused. There is a maximum number of landmined
ports because there is a limit to the number of broken links allowed in a
system. The data field shows the number of landmined ports found
- Cause / Action:
Check for hardware failures: crossbar chips,
etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 719
- Severity: FATAL
- Event Summary: The backplane was not recognized as one that
contains fabric
- Event Class: System
- Problem Description:
Data field contains the backplane type
found. During Intra SKD Routing, the backplane type detected was either a
Medel backplane or was unrecognized. The backplane could therefore not be
routed. This is a firmware sanity check. Data Field: system type
- Cause / Action:
Cause: An unrecognized backplane is
installed. Action: Contact HP Support Personnel to determine why the
backplane was unrecognized.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 720
- Severity: MAJOR
- Event Summary: Writing the XIN Error Mask Register to zero failed
- Event Class: System
- Problem Description:
Prior to initializing the CC to XBC
link, the XIN error mask should be zeroed out to prevent spurious errors
from interfering with the link initialization. This write to zero out the
error mask failed. Data Field: (cell << 56) | return status
- Cause / Action:
CC Write Failure.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 722
- Severity: CRITICAL
- Event Summary: Data read from the CC Primary Mode CSR
- Event Class: System
- Problem Description:
The Coherency Controller's (CC) XIN link
did not initialize properly. The data field contains the data read from the
CC Primary Error Mode CSR.
- Cause / Action:
CC to XBC link init failure. Contact your HP
service representative to check the CC to XBC link
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 723
- Severity: CRITICAL
- Event Summary: Dumping error info. Read status of the CC Error
Mask Register
- Event Class: System
- Problem Description:
The Coherency Controller's (CC) XIN link
did not initialize properly. The data field contains the return status from
an attempted read of the CC Primary Error Mode CSR. (0 = SUCCESS)
- Cause / Action:
CC to XBC link init failure. Contact your HP
service representative to check the CC to XBC link
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 724
- Severity: CRITICAL
- Event Summary: Data read from the CC Error Mask CSR
- Event Class: System
- Problem Description:
The Coherency Controller's (CC) XIN link
did not initialize properly. The data field contains the data read from the
CC Error Mask CSR.
- Cause / Action:
CC to XBC link init failure. Contact your HP
service representative to check the CC to XBC link
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 725
- Severity: MAJOR
- Event Summary: The link could not be crossed upon first attempt
- Event Class: System
- Problem Description:
The neighbor's port connected to the
link being crossed is not routable. This was the first attempt to cross the
link, PDC will now look for another link it can cross. DATA: (xbcNum
<< 32 ) | (port << 44)
- Cause / Action:
The neighbor port is not routable. The port
is either: not connected, landmined, in FE, or contains an SBE or
LPE.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 726
- Severity: CRITICAL
- Event Summary: Failed reading an XBC forward progress register
- Event Class: System
- Problem Description:
Fabric read error. Data field: (XBC
number << 32 | return status)
- Cause / Action:
Fabric access error
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 727
- Severity: CRITICAL
- Event Summary: Could not find an adjacent XBC due to broken
fabric links
- Event Class: System
- Problem Description:
Too many crossbar links are broken. Cell
cannot boot, halting. Data field: XBC number << 32
- Cause / Action:
Possible crossbar failure
Contact HP
Support personnel to analyze the crossbar.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 728
- Severity: MAJOR
- Event Summary: The run-time verification of a programming
assumption has failed.
- Event Class: System
- Problem Description:
For debug purposes, many assumptions
made by the PM developer(s) are checked at run-time. If this event log is
seen, it will either indicate that the hardware is in a unknown state that
is not handled by the PM, or that a programming bug has been found. For
developer debug purposes, the data field describes where in the code that
the error was detected. Data Bytes[0-1]: The line number within the source
code file where the error was detected. Data Bytes[2-7]: The first 6
characters of the source code file name.
- Cause / Action:
Cause: Hardware in unknown state, or
programming bug found. Action: Upgrade PM firmware to latest revision. If
already at current revision, replace UGUY board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 729
- Severity: MAJOR
- Event Summary: An unknown error has been detected by the PDHC
firmware.
- Event Class: System
- Problem Description:
An unknown error has been detected by
the PM firmware. For developer debug purposes, the data field describes
where in the code that the error was detected. Data Bytes[0-1]: The line
number within the source code file where the error was detected. Data
Bytes[2-7]: The first 6 characters of the source code file name.
- Cause / Action:
Cause: Hardware in unknown state, or
programming bug found. Action: Upgrade PM firmware to latest revision. If
already at current revision, replace UGUY board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 731
- Severity: MAJOR
- Event Summary: Testing of correctable errors injected from the CC
has failed
- Event Class: System
- Problem Description:
Failed link testing to ensure that SBE
and LPE errors are detected properly by the XBC. The XBC did not detect any
errors. Data field indicates the return status: (1 = err detected, 0 = no
err detected, -1 = XBC accesses failed)
- Cause / Action:
Cause: Either the CC failed to inject the
errors, the XBC failed to detect them, or PDC could not access the XBC CSR.
Action: Check results from other cells connected to the same XBC. Check CC,
Check XBC, Contact HP Support Personnel.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 732
- Severity: FATAL
- Event Summary: A cabinet has been configured using an invalid
cabinet number
- Event Class: System
- Problem Description:
The data field contains the cabinet
number that is invalid
- Cause / Action:
Re-configure cabinet to use a valid cabinet
number
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 733
- Severity: CRITICAL
- Event Summary: Cells trying to join a PD are at incompatible
firmware revisions
- Event Class: System
- Problem Description:
The cell indicated in the data field is
at a different firmware revision than the reporting cell. This is determined
by evaluating the checksums of the 2 ROM images.
- Cause / Action:
The reporting cell is at a different firmware
revision than the cell reported in the data field. A PD cannot be
established. Please reprogram the 2 cells to the same firmware revision.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 734
- Severity: MAJOR
- Event Summary: An attempt to write to a device on the PM's I2C
bus has failed.
- Event Class: System
- Problem Description:
An attempt to write to a device on the
PM's I2C bus has failed. The Data field contains information that can
identify the exact device that has failed. Refer to the UGUY ERS for a
mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data
Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data
Bytes[6-7]: Size of attempted access (in bytes).
- Cause / Action:
Cause: A hardware error has occurred. Action:
Replace the UGUY board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 735
- Severity: MAJOR
- Event Summary: An attempt to read from a device on the PM's I2C
bus has failed.
- Event Class: System
- Problem Description:
An attempt to read from a device on the
PM's I2C bus has failed. The Data field contains information that can
identify the exact device that has failed. Refer to the UGUY ERS for a
mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data
Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data
Bytes[6-7]: Size of attempted access (in bytes).
- Cause / Action:
Cause: A hardware error has occurred. Action:
Replace the UGUY board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 736
- Severity: MAJOR
- Event Summary: An error was encountered updating the cell info
structure in ICM
- Event Class: System
- Problem Description:
An error was encountered trying to
obtain the data required for the cell information structure in ICM. The data
field is an ASCII message that indicates the information that was not found.
- Cause / Action:
This should not happen. Contact engineering
to diagnose the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 737
- Severity: MAJOR
- Event Summary: An error was encountered pointing the slave cell
consoles to the diva
- Event Class: System
- Problem Description:
An error was encountered establishing
the slave cells use of the diva console.
- Cause / Action:
A CPU on the slave cell could not process an
interrupt in time or establish the diva console.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 738
- Severity: CRITICAL
- Event Summary: An error was encountered trying to relocate a
slave cells registry
- Event Class: System
- Problem Description:
An error was encountered trying to
relocate the registry on a slave cell to point to the core cells main memory
strucutres.
- Cause / Action:
There could be a PD rendezvous error or a
processor on the slave cell failed to respond to an interrupt in time.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 742
- Severity: MAJOR
- Event Summary: Unexpected fabric firmware error
- Event Class: System
- Problem Description:
An unexpected error occurred while
initializing the fabric. The firmware is not able to analyze this error.
Clues to the cause of this error may be found in the IPMI forward progress
log (FPL) either shortly before or after this log entry occurred. The FPL is
available from the management processor using the "sl" command. - Cause / Action:
An unanticipated error occurred. Contact HP
Support personnel to analyze the IPMI FPL log.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 743
- Severity: FATAL
- Event Summary: Internal firmware programming error in the PMI
handler.
- Event Class: System
- Problem 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.
- Cause / Action:
Report the IP to the firmware team. Reset the
system. This cannot be worked around in the field.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 744
- Severity: CRITICAL
- Event Summary: During a Cell On Line Add inconsistent number of
cells discovered
- Event Class: System
- Problem Description:
During the on line addition of a cell
the partition adding the cell has determined inconsistent data as to which
cell is being added. The cell addition will be aborted and the partition
will resume execution without the new cell.
- Cause / Action:
This can be caused by inconsistent profile
information. This can also occur when an expected cell did not make the
original boot of the partition. Update the complex profile to all the cells
with a correct view of the system and try to add the cell again.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 745
- Severity: MAJOR
- Event Summary: Error reading source cell port on XBC during data
traversability test
- Event Class: System
- Problem Description:
An error occurred while reading the
routing from the source cell's port on the source XBC. Data Field: (source
cell << 56 | source XBC << 32)
- Cause / Action:
A read error most likely occurred. Look for
preceding chassis codes to determine exact cause.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 753
- Severity: MAJOR
- Event Summary: CPUs of different maximum core frequencies are
installed
- Event Class: System
- Problem Description:
CPU's of mixed maximum core frequencies
are installed
- Cause / Action:
Cause: CPU's of mixed maximum core
frequencies are installed. Action: If operating at the slowest of the
maximum core frequency of installed CPU's is acceptable, no action is
necessary. If not, replace the slower core frequency CPU's to match the
faster CPU's. This will enable all CPU's to work at their maximum
frequency.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 754
- Severity: FATAL
- Event Summary: The RVL CC-Togo link initialization workaround
(PS221) failed
- Event Class: System
- Problem Description:
The Concorde-Togo link initialization is
having an intermittent failure. The data field contains the number of
initialization sequences that failed before being successful.
- Cause / Action:
Cause: The link initialization failed at
least once and then subsequently was successful.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 756
- Severity: CRITICAL
- Event Summary: Fabric Discovery could not initialize the local
cell's XBC link
- Event Class: System
- Problem Description:
Fabric Discovery's final attempt to
initialize the local cell's CC to Crossbar Chip (XBC) link has failed. This
cell cannot talk to the fabric. Data: link init state bit read from the CC
Link State register
- Cause / Action:
Cause: CC to XBC link init failure. Action:
check CC, XBC, reset cell, reset backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 760
- Severity: FATAL
- Event Summary: Internal firmware programming error
- Event Class: System
- Problem 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 physical address that failed mapping to a virtual address
- Cause / Action:
Report the IP to the firmware team. Reset the
system. This cannot be worked around in the field.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 771
- Severity: CRITICAL
- Event Summary: Error writing the XIN init disable register.
- Event Class: System
- Problem Description:
Failure while writing the XBC CSR
containing the link status
- Cause / Action:
Check XBC, CC, backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 772
- Severity: CRITICAL
- Event Summary: Error reading the XIN init state register.
- Event Class: System
- Problem Description:
Failure while reading the XBC CSR
containing the link status
- Cause / Action:
Check XBC, CC, backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 773
- Severity: CRITICAL
- Event Summary: intermittent failure while retrying the CC to XBC
link init
- Event Class: System
- Problem Description:
Fabric Discovery's attempt to initialize
the local cell's CC to XBC link has failed. The link initialization sequence
has an intermittent problem.
- Cause / Action:
contact your HP service representative
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 774
- Severity: MAJOR
- Event Summary: Initialization of a PCI node in the firmware
device tree failed
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: A firmware error setting up data
storage to allow PCI bus bridge processing to occur. Action: Correct any
previous errors reset the system clear NVM and reset the system Update to
the latest recipe Replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 775
- Severity: CRITICAL
- Event Summary: An error was encountered while scanning the PCI
bus.
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: A firmware error setting up data
storage to allow PCI bus scanning to occur. Action: Correct any previous
errors reset the system clear NVM and reset the system Update to the latest
recipe Replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 776
- Severity: MAJOR
- Event Summary: An error was encountered initializing the PCI
bridge
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: A firmware error setting up data
storage to allow PCI bus bridge processing to occur. Action: Correct any
previous errors reset the system clear NVM and reset the system Update to
the latest recipe Replace the cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 777
- Severity: MAJOR
- Event Summary: An error was encountered initializing the PCI IO
map.
- Event Class: System
- Problem Description:
pfa
- Cause / Action:
Cause: PCI requested I/O port size larger
than system can handle Action: Correct any previous errors Remove cards that
are requesting too much memory space or move a card to a dual rope slot (PCI
slots 1-7).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 778
- Severity: MAJOR
- Event Summary: An error was encountered creating the PCI MMIO map
- Event Class: System
- Problem Description:
pfa
- Cause / Action:
Cause: PCI requested memory map size larger
than system can handle Action: Correct any previous errors Remove cards that
are requesting too much memory space or move a card to a dual rope slot (PCI
slots 1-7).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 779
- Severity: CRITICAL
- Event Summary: There was an error initializing the SBA node
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: An error was while initializing the
SBA firmware structures Action: Correct any previous errors Invalidate NVM
and reset replace the cell board
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 780
- Severity: CRITICAL
- Event Summary: There was an error discovering the SBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: An error was discovered with the SBA
during discovery Action: Correct any previous errors Replace the I/O
backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 781
- Severity: CRITICAL
- Event Summary: An error was encountered while resetting the SBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: An error was detected while resetting
the ropes Action: replace the I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 782
- Severity: MAJOR
- Event Summary: There was an error initializing the IO link
- Event Class: System
- Problem Description:
An error was detected in the link
between the CC and the I/O controller.
- Cause / Action:
Cause: Unable to establish the link between
the CC and IOC. Action: Validate power to the I/O chassis Reset th system
A/C power cycle Replace the I/O backplane, cell, and system backplane to
resolve the issue.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 783
- Severity: MAJOR
- Event Summary: There is a problem initializing the REO cable
- Event Class: System
- Problem Description:
cable status
- Cause / Action:
Check the REO cable connection
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 784
- Severity: CRITICAL
- Event Summary: The IO chassis discovered was powered off
- Event Class: System
- Problem Description:
Identified the cell number that is
connected to the chassis.
- Cause / Action:
No action required.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 785
- Severity: MAJOR
- Event Summary: There was an error initializing the LBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Error initializing the LBA node and
services Action: Validate that there is not another error causing this error
invalidate NVM and reset or replace the cell board
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 786
- Severity: CRITICAL
- Event Summary: There was an error querying the LBA width
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Error while writing the LBA phase data
Action: Replace the I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 787
- Severity: MAJOR
- Event Summary: There was an error with the LBA phase
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Error while writing the LBA phase data
Action: Replace the I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 788
- Severity: MAJOR
- Event Summary: There was an error clearing the LBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Unable to clear an error in the LBA
Action: Check other events for the error being generated replace either the
PCI card or the I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 789
- Severity: CRITICAL
- Event Summary: There was an error with the LBA log
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Error log is corrupt Action: Clear
errors and continue
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 790
- Severity: CRITICAL
- Event Summary: There was an error discovering the LBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: The wrong backplane type was detected
Action: replace I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 791
- Severity: MAJOR
- Event Summary: There was an error configuring the LBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Unable to configure the LBA Action:
replace I/O backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 792
- Severity: CRITICAL
- Event Summary: There was an error scanning the PCI bus
- Event Class: System
- Problem Description:
An error was encountered while
attempting to scan the PCI bus
- Cause / Action:
Cause: ld not scan the card in a populated
slot. Typically caused by an improperly installed or faulty PCI
card.
Action: Reseat or replace the faulty card.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 793
- Severity: CRITICAL
- Event Summary: There was an error configuring PCI space through
the LBA
- Event Class: System
- Problem Description:
error code
- Cause / Action:
Cause: Unable to obtain semaphore Action:
reset Update to latest recipe
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 808
- Severity: CRITICAL
- Event Summary: The Options service received an NVRAM allocation
error.
- Event Class: System
- Problem Description:
The Options service received an error
when attempting to allocate an NVRAM storage block. Either an error was
returned from the call, or the call returned successfully yet an invalid
address was returned.
- Cause / Action:
Invalidate NVRAM and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 810
- Severity: MAJOR
- Event Summary: SAL errlog access timeout
- Event Class: System
- Problem Description:
Access to SAL error log procedure timed
out because the log facility was busy processing a request from another CPU.
Data field indicates the SAL procedure ID.
- Cause / Action:
Firmware is taking too long to process
requests.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 816
- Severity: MAJOR
- Event Summary: The echelon given in the data field is not fully
populated.
- Event Class: System
- Problem Description:
One or more dimms are missing from the
echelon given in the data field. The dimms may not be installed or firmware
was not able to detect the dimms.
- Cause / Action:
cause - the specified echelon is not fully
populated and is not usable action - add or replace dimms in the specified
echelon
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 817
- Severity: MAJOR
- Event Summary: Attempted to read the port state from an illegal
port number
- Event Class: System
- Problem Description:
The code that reads the port state
(landmine vs. healthy) expects a XBC internal port number, it received bogus
data. The port state cannot be read. Data Field: (port << 44) | (xbc
num << 32)
- Cause / Action:
An invalid port number has been provided. The
port number will be converted to an internal port and processing should
continue.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 818
- Severity: MAJOR
- Event Summary: Attempted to write the port state for an illegal
port
- Event Class: System
- Problem Description:
The code that writes the port state
(landmine vs. healthy) expects a XBC internal port number, it received bogus
data. The port state cannot be read. Data Field: (port << 44) | (xbc
num << 32)
- Cause / Action:
An invalid port number has been provided. The
port number will be converted to an internal port and processing should
continue.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 822
- Severity: CRITICAL
- Event Summary: System firmware was unable to default the complex
profile
- Event Class: System
- Problem Description:
System firmware was unable to default
the complex profile
- Cause / Action:
Needed information could not be obtained.
Reset the MP.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 824
- Severity: MAJOR
- Event Summary: Means that the error log space in the NVRAM has
not been allocated.
- Event Class: System
- Problem Description:
This chassis code shows that the error
log space in the NVRAM has not been allocated for the current error event.
This will be emitted out whenever a error section is attempted to be logged
without allocation of log space in NVRAM
- Cause / Action:
This happens because of the NVRAM is full
with unconsumed error logs. Clear the error logs.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 825
- Severity: MAJOR
- Event Summary: This indicates the maximum number of logs for the
event.
- Event Class: System
- Problem Description:
This indicates that the error logs for a
particular event type have reached the maximum allowed to be stored in the
NVRAM. The event type is indicated in the data field.
- Cause / Action:
This shouldn't be occur. But in case it does
than clear the error logs of this event type from the nvram.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 826
- Severity: MAJOR
- Event Summary: On Line Delete operation was begun but firmware
could not find a cell that can be deleted.
- Event Class: System
- Problem Description:
System firmware has been invoked to
perform a cell delete operation but no cell in the system appears to be
ready for deletion.
- Cause / Action:
This can occur if the OS has not returned all
the CPUs to firmware or if a cell is not marked correctly in the complex
profile to allow its deletion.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 827
- Severity: FATAL
- Event Summary: The bulk power system is above its current
capacity.
- Event Class: System
- Problem Description:
The bulk power supply is over current
- Cause / Action:
N/A
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 828
- Severity: MAJOR
- Event Summary: The bulk specified is warning of a potential
thermal problem.
- Event Class: System
- Problem Description:
Data: Bulk location.
- Cause / Action:
The bulk power supply is warning of an
over temperature condition
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 829
- Severity: CRITICAL
- Event Summary: Malloc failed while trying to process and ERM
- Event Class: System
- Problem Description:
Error Response Mode code attempted a
malloc of heap space that failed.
- Cause / Action:
Heap space is completely used or corrupt.
Contact Product Engineering.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 830
- Severity: MAJOR
- Event Summary: Dimm at physical location in data field is not
supported on this platform.
- Event Class: System
- Problem Description:
The dimm in the physical location given
by the data field is not supported on this platform. The dimm may not be
supported by the hardware, or the dimm may not have been properly qualified
for this platform.
- Cause / Action:
Cause: Unsupported dimm in specified slot
Action: Replace dimm with supported dimm.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 831
- Severity: CRITICAL
- Event Summary: The OPTIONS component received a memory allocation
error.
- Event Class: System
- Problem Description:
The OPTIONS component was unable to
allocate NVRAM memory in order to store a non-volatile variable. The storage
area for NVRAM options may be full, or there may be undetected corruption.
- Cause / Action:
Invalidate NVRAM and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 832
- Severity: MAJOR
- Event Summary: A dimm or CPU has is deconfigured or failed
testing
- Event Class: System
- Problem Description:
A dimm or CPU has failed and is not
operational for the system. This event is emitted prior to determining if
the cell should be integrated into the Partition.
- Cause / Action:
A deconfigured dimm or cpu has been detected.
Examine earlier events to isolate the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 833
- Severity: CRITICAL
- Event Summary: The cell will not join the PD
- Event Class: System
- Problem Description:
A cpu or dimm error has been detected,
and the Complex Profile, Cell Integration Table, Cell integration policy
says to not integrate the cell into the PD.
- Cause / Action:
Broken hardware was detected and the cell
integration policy combined to cause the cell to not join the PD. Fix the
broken hardware or change the policy using parmgr.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 834
- Severity: MAJOR
- Event Summary: The error context in NVM was corrupt
- Event Class: System
- Problem Description:
The IO error context is corrupt. This
will impair IO error reporting.
- Cause / Action:
NVM is corrupted.
Check for other errors
in the system first. Invalidate NVM and retry boot. Get the latest firmware
release.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 837
- Severity: CRITICAL
- Event Summary: Firmware encountered a problem trying to
initialize
- Event Class: System
- Problem Description:
System firmware encountered an error
while trying to perform an operation during system initialization. This
event ID will always be emitted before an event ID that describes the
status of the operation that failed.
- Cause / Action:
Examine the related event that failed and
correct that problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 838
- Severity: MAJOR
- Event Summary: This means that all the cpus in the cell did not
show up.
- Event Class: System
- Problem Description:
This means that all the cpus in the cell
did not show up.
- Cause / Action:
This will result in the cell stepping
independently to collect its logs and resetting itself.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 839
- Severity: MAJOR
- Event Summary: This means that all the cells did not rendezvous
during the PD rendezvous.
- Event Class: System
- Problem Description:
This means that all the cells did not
rendezvous during the PD rendezvous. The data part will contain the Expected
data and the actual mask of the cells that rendezvoused.
- Cause / Action:
The cells will reset themselves.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 840
- Severity: MAJOR
- Event Summary: The FW tree sanity check failed during the MCA
error processing.
- Event Class: System
- Problem Description:
The FW tree sanity check failed during
the MCA error processing.
- Cause / Action:
The cells will independently log errors and
reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 841
- Severity: MAJOR
- Event Summary: This means that the registry sanity check failed
during MCA error handling.
- Event Class: System
- Problem Description:
This means that the registry sanity
check failed during MCA error handling.
- Cause / Action:
The cells will independently log errors and
reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 842
- Severity: MAJOR
- Event Summary: This means that MCA occurred while OS_MCA was
performing error recovery.
- Event Class: System
- Problem Description:
This means that MCA occurred while OS_MCA
was performing error recovery.
- Cause / Action:
The cells will log information and reset.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 843
- Severity: MAJOR
- Event Summary: One of the BT errors occurred that results in
abandoning memory dump.
- Event Class: System
- Problem Description:
This means that memory dump will be
abandoned due to work-around for CN2272. This happens when one of the
Blocking timeout in the Processor input block of the concorde occurs.
- Cause / Action:
Cause: A machine check has occurred and cells
have not rendezvoused. Action: Cells will reset themselves.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 844
- Severity: MAJOR
- Event Summary: The firmware tree is not complete and hence there
will be no PD rendezvous.
- Event Class: System
- Problem Description:
The firmware tree is not complete and
hence there will be no PD rendezvous.
- Cause / Action:
The cell will log errors and reset
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 845
- Severity: CRITICAL
- Event Summary: ACPI configuration mismatch across cells in the
partition
- Event Class: System
- Problem Description:
The firmware parameter that defines the
ACPI configuration is inconsistent in at least one of the cells in the
partition.
- Cause / Action:
Set the ACPI configuration parameter again to
ensure that all cells have a consistent value.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 846
- Severity: CRITICAL
- Event Summary: Failed clearing of the XIN_ERR_ORDER_STATUS CSR
- Event Class: System
- Problem Description:
Writing the XIN_ERR_ORDER_STATUS
register of the CC failed. This is some sort of a hardware failure. Data
Field: return status
- Cause / Action:
Failure to access the register or the write
did not work.
Contact HP Support personnel to check the CC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 848
- Severity: MAJOR
- Event Summary: Unexpected fabric firmware error
- Event Class: System
- Problem Description:
An unexpected error occurred while
initializing the fabric. The firmware is not able to analyze this error.
Clues to the cause of this error may be found in the IPMI forward progress
log (FPL) either shortly before or after this log entry occurred. The FPL is
available from the management processor using the "sl" command.
- Cause / Action:
An unanticipated error occurred. Contact HP
Support personnel to analyze the IPMI FPL log.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 849
- Severity: MAJOR
- Event Summary: Invalid data read from a CPU module's Processor
Information ROM.
- Event Class: System
- Problem Description:
A value read by the PDHC from a CPU
module's Processor Information ROM was not within acceptable limits.
- Cause / Action:
Cause (probable): The CPU module's Processor
Information ROM is unprogrammed. Action: Contact HP support personnel to
troubleshoot the CPU module pointed to by the physical location portion of
this event. Cause: The CPU module's Processor Information ROM contains
invalid data. Action: Contact HP support personnel to troubleshoot the CPU
module pointed to by the physical location portion of this event.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 851
- Severity: MAJOR
- Event Summary: Option block in nvram has a checksum error
- Event Class: System
- Problem Description:
The overhead structure of the OPTIONS
block in NVRAM has a checksum error.
- Cause / Action:
Clear NVRAM.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 852
- Severity: MAJOR
- Event Summary: CC to CC link did not initialize on the local cell
- Event Class: System
- Problem Description:
During a cell OLA, the link on the local
cell failed to initialize. Data Field: (my cell << 32) | XIN Link
State
- Cause / Action:
link failure between the XBC and the
CC
Check CC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 853
- Severity: MAJOR
- Event Summary: Failed to write the CC link disable register
- Event Class: System
- Problem Description:
An attempt to disable the fabric link
failed because writing the CC CSR failed. Data Field: (cell << 56) |
return status
- Cause / Action:
Fabric Access Failure.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 854
- Severity: MAJOR
- Event Summary: An unknown backplane type was found
- Event Class: System
- Problem Description:
Could not determine the system type in
order to write the appropriate error mask for the fabric link. Data Field:
system type
- Cause / Action:
CSR Read/Write error
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event Details:
Examples:
Event 855
- Severity: MAJOR
- Event Summary: Error writing the CC link error mask
- Event Class: System
- Problem Description:
Failed writing the XIN error mask for
CC's fabric link. Data Field: (cell << 56) | return status
- Cause / Action:
Fabric Access Error.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 856
- Severity: MAJOR
- Event Summary: Failed to read the CC's fabric link error mask
- Event Class: System
- Problem Description:
Could not read the XIN Link error mask
register. Data Field: (cell << 56) | return status
- Cause / Action:
CC CSR access failure.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 857
- Severity: CRITICAL
- Event Summary: Could not initialize the CC to CC link upon boot.
- Event Class: System
- Problem Description:
The CC to CC link initialization
sequence has failed. Data Field: link init status
- Cause / Action:
CC CSR Access Failure.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 858
- Severity: MAJOR
- Event Summary: An Error occurred trying to notify the MP of the
attempted reset.
- Event Class: System
- Problem Description:
An error occurred while trying to notify
the MP that a reset is about to occur (QPartitionReleaseBIB command). The
status is in the data field.
- Cause / Action:
The MP is not functioning or the PDHC cannot
communicate with it. Reset the MP.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 860
- Severity: MAJOR
- Event Summary: Failed disabling the XIN link for a single cell
medel
- Event Class: System
- Problem Description:
A fabric access error occurred while
trying to disable the CC to CC link on a single cell Medel system. This cell
will halt. Data field: error status
- Cause / Action:
Fabric Access Error.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 861
- Severity: CRITICAL
- Event Summary: Error while getting the XBC Semaphore
- Event Class: System
- Problem Description:
While updating the Port State register,
the cell could not get the XBC semaphore. Data field is: (Port Num <<
44 | XBC num << 32 | return status). Where return status is: (0
Success; -1 Access Failure; -2 Semaphore Owned By Another, -3 Semaphore
Already Owned; -4 XBC Key Contention)
- Cause / Action:
Most likely a hardware problem, but confirm
the cause by looking at the return status. Action: Check XBC, Backplane,
Flex Cables, Contact HP Support Personnel for further troubleshooting.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 862
- Severity: MAJOR
- Event Summary: Error releasing the XBC Semaphore
- Event Class: System
- Problem Description:
While updating the Port State register,
the cell could not get the XBC semaphore. Data field is: (Port Num <<
44 | XBC num << 32 | return status). Where return status is: (0
Success; -1 Generic Failure)
- Cause / Action:
Cause: Fabric Access problem. Either an error
reading the hardware or XBC Key contention. Action: Look for additional
chassis codes to provide detail. Check XBC, Backplane, Flex Cables, Contact
HP Support Personnel.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 864
- Severity: MAJOR
- Event Summary: Unexpected fabric firmware error
- Event Class: System
- Problem Description:
An unexpected error occurred while
initializing the fabric. The firmware is not able to analyze this error.
Clues to the cause of this error may be found in the IPMI forward progress
log (FPL) either shortly before or after this log entry occurred. The FPL is
available from the management processor using the "sl" command. -
Cause / Action:
An unanticipated error occurred. Contact HP
Support personnel to analyze the IPMI FPL log.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 865
- Severity: MAJOR
- Event Summary: The CC's XIN link was found to be already
initialized
- Event Class: System
- Problem Description:
While attempting to initialize the XIN
link, it was found to already be initialized. A firmware assertion has
failed. The link will not be re-initialized and processing should continue
as normal. However, the system could be confused at this point.
- Cause / Action:
Firmware problem. Contact HP Support
Personnel.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 866
- Severity: CRITICAL
- Event Summary: Cell has been disabled by the PDHC because no CPU
modules were found.
- Event Class: System
- Problem Description:
The PDHC FW could not detect any CPU
modules on its Cell board, so it is holding the Cell in reset.
- Cause / Action:
Cause(1, probable): No CPU modules are
installed. Action(1): Install CPU modules on the Cell. Cause(2): A Cell or
PDH Daughtercard error is causing the presence of CPU modules to be reported
incorrectly to the PDHC. Action(2): Contact HP support personnel to
troubleshoot the PDH Daughtercard and/or Cell board. Cause(3): The CPU
module(s) that are installed have invalid data stored in the partition
specific field of the FRU EEPROM. Action(3): If in manufacturing, reprogram
the partition specific field of the CPU module(s) FRU EEPROM. Otherwise,
contact HP support personnel to troubleshoot the unreported CPU module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 867
- Severity: CRITICAL
- Event Summary: Cell has been disabled by PDHC FW because the CPU
modules are not compatible.
- Event Class: System
- Problem Description:
The Cell has been disabled by PDHC FW
because the CPU modules are not compatible. Compatibility is determined
based on data stored in the Scratch/FRUID EEPROM on each CPU module. The CPU
module partition compatibility byte for each CPU module must be identical.
- Cause / Action:
Cause(1): At least one of the installed CPU
modules are incompatible with at least one other CPU module. Action(1):
Contact HP support personnel to troubleshoot the CPU modules on the Cell.
Cause(2): The FRUID data stored in a CPU Module's Scratch/FRUID EEPROM is
incorrectly programmed. Action(1): Reprogram the FRUID data (manufacturing
only) or contact HP support personnel to troubleshoot the CPU module on the
Cell.
Cause(1): At least one of the installed CPU modules are
incompatible with at least one other CPU module. Action(1): Contact HP
support personnel to troubleshoot one or more CPU modules on the Cell.
Cause(2): The FRUID data stored in a CPU Module's Scratch/FRUID EEPROM is
incorrectly programmed. Action(1): Reprogram the FRUID data (manufacturing
only) or contact HP support personnel to troubleshoot the CPU module on the
Cell.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 868
- Severity: CRITICAL
- Event Summary: Cell has been disabled because of invalid data in
a CPU module Scratch EEPROM.
- Event Class: System
- Problem Description:
The Cell has been disabled because of
invalid data in a CPU module Scratch EEPROM. PDHC FW checksums the FRUID
data stored in each CPU module's Scratch EEPROM. If a checksum fails, the
Cell is held in reset and will not boot. The data field identifies the CPU
module that failed.
- Cause / Action:
Cause: The CPU module is not an HP CPU
module, or the FRUID data for this CPU module has not been
programmed.
Action: Contact HP support personnel to troubleshoot the CPU
module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 869
- Severity: MAJOR
- Event Summary: The Cell Battery voltage level low warning
- Event Class: System
- Problem Description:
The battery voltage level is low for the
cell. This indicates that the NVRAM will not be saved if the power is
removed.
- Cause / Action:
Cause1: The Cell Battery is low. Action1: It
needed to be replaced.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 870
- Severity: CRITICAL
- Event Summary: Error while copying the XBC routing to the local
port
- Event Class: System
- Problem Description:
There was an error while copying the
routing for the XBC to the local XBC port. The cell will reset. Data: (XBC
port << 44) | (XBC num << 32) | return status
- Cause / Action:
Error accessing XBC CSRs.
Contact HP
Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 871
- Severity: CRITICAL
- Event Summary: A read after write of a XBC CSR failed
- Event Class: System
- Problem Description:
The read immediately after a write while
copying routing registers failed. Data: whether or not the XBC Key was
enabled
- Cause / Action:
Fabric Access Error, XBC Key Disabled. Check
XBC, links, backplane, Contact HP Support Personnel for
furthertroubleshooting.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 872
- Severity: MAJOR
- Event Summary: Couldn't release the Semaphore while writing
routing states.
- Event Class: System
- Problem Description:
Failed to release a XBC Semaphore while
marking each XBC in the complex to indicate that routing has completed.
Data: (XBC num << 32) | return value
- Cause / Action:
Fabric Access Error. Check XBC, Check
links.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 873
- Severity: CRITICAL
- Event Summary: Couldn't write the XBC's forward progress register
- Event Class: System
- Problem Description:
Writing this XBC's forward progress
register failed. Data: (XBC num << 32) | return value
- Cause / Action:
Fabric Access Error. Couldn't write this
XBC.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 874
- Severity: CRITICAL
- Event Summary: Couldn't access the XBC semaphore registers.
- Event Class: System
- Problem Description:
Failed to get a XBC Semaphore while
marking each XBC in the complex to indicate that routing has completed.
Skipping this XBC. Data: (XBC num << 32) | return value
- Cause / Action:
Fabric Access Error. Couldn't read or write
this XBC.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 875
- Severity: CRITICAL
- Event Summary: Couldn't determine the complex fabric topology
- Event Class: System
- Problem Description:
Reading this XBC's topology register
failed. Data Field: (xbc num << 32) | return status
- Cause / Action:
Fabric Access Error. Couldn't write this
XBC.
Contact HP Support personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 876
- Severity: MAJOR
- Event Summary: Error checking a cell to cell link during
traversability tests
- Event Class: System
- Problem Description:
Could not check the traversability
between two cells on an XBCless platform. Data field: return status (1 =
SUCCESS, 0 = FALSE, -1 = FAILURE)
- Cause / Action:
Probably an error reading the XIN. Look for
additional descriptive chassis codes.
Contact HP Support personnel to
check the CC
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 877
- Severity: MAJOR
- Event Summary: An error occurred while traversing the cell to
cell link.
- Event Class: System
- Problem Description:
Could not check the traversability
between two cells on an XBCless platform. Data field: return status (1 =
SUCCESS, 0 = FALSE, -1 = FAILURE)
- Cause / Action:
Probably an error reading the XIN. Look for
additional descriptive chassis codes.
Contact HP Support personnel to
check the CC
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 878
- Severity: MAJOR
- Event Summary: Error reading the local cell's XIN link state
- Event Class: System
- Problem Description:
While checking traversability of a 2
cell back to back system, there was an error reading the local cell's XIN
block. Data Field: return status (1 or -1)
- Cause / Action:
Hardware Access Error. Have your HP support
representative check the Coherency Controller (CC).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 879
- Severity: MAJOR
- Event Summary: Error reading the remote cell's XIN link state
register
- Event Class: System
- Problem Description:
While checking traversability of a 2
cell back to back system, there was an error reading the local cell's XIN
block. Data Field: return status (1 or -1)
- Cause / Action:
Hardware Access Error. Have your HP support
representative check the backplane and Coherency Controller (CC).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 880
- Severity: MAJOR
- Event Summary: The XIN link is not connected to the target cell.
- Event Class: System
- Problem Description:
Could not traverse to the target cell.
The XIN link is either not initialized, or is not connected to the target
cell. However, the target cell is designated to be within the partition.
Data Field: target cell << 56 | XIN link state register
- Cause / Action:
Ensure the cells are connected. Check
historical chassis codes from most recent boot to see if the link had ever
initialized. Have your HP support representative check the backplane and
Coherency Controller (CC).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 881
- Severity: MAJOR
- Event Summary: The XIN link is not connected to the target cell.
- Event Class: System
- Problem Description:
Could not traverse to the target cell.
The XIN link is either not initialized, or is not connected to the target
cell. However, the target cell is designated to be within the partition.
Data Field: target cell << 56 | XIN link state register
- Cause / Action:
Ensure the cells are connected. Check
historical chassis codes from most recent boot to see if the link had ever
initialized. Have your HP support representative check the backplane and
Coherency Controller (CC).
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 882
- Severity: MAJOR
- Event Summary: Error reading the XIN_LINK_STATE register while
disabling the link
- Event Class: System
- Problem Description:
Error reading the XIN_LINK_STATE
register of the CC. This occurred while verifying that the link had been
disabled. Data Field: cell being read << 56 | return status from the
CSR read.
- Cause / Action:
Hardware Access Error.
Contact HP Support
personnel to analyze the fabric, CC, Backplane.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 883
- Severity: CRITICAL
- Event Summary: Error reading the XIN_LINK_STATE register
- Event Class: System
- Problem Description:
Failure while reading the XBC CSR
containing the link status. This occurred while attempting the retry process
to get XBC to CC link initialized. Data Field: link init status
- Cause / Action:
link init problem
Contact HP Support
personnel to check the XBC, CC, backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 884
- Severity: MAJOR
- Event Summary: Unexpected fabric firmware error
- Event Class: System
- Problem Description:
An unexpected error occurred while
initializing the fabric. The firmware is not able to analyze this error.
Clues to the cause of this error may be found in the IPMI forward progress
log (FPL) either shortly before or after this log entry occurred. The FPL is
available from the management processor using the "sl" command.
- Cause / Action:
An unanticipated error occurred. Contact HP
Support personnel to analyze the IPMI FPL log.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 885
- Severity: MAJOR
- Event Summary: The CPU is performance or functionally restricted
- Event Class: System
- Problem Description:
The CPU that just completed self tests
is functionally or performance restricted. The data field contains the
self-test state word.
- Cause / Action:
A CPU is broken. Replace it.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 886
- Severity: MAJOR
- Event Summary: The RTC was found to be invalid and has been
cleared
- Event Class: System
- Problem Description:
The RTC was found to be invalid and has
been cleared
- Cause / Action:
Cause: The RTC was invalid Action: None, the
problem has been corrected by SFW.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 887
- Severity: MAJOR
- Event Summary: Status indicates that the Late Self Tests did not
actually run
- Event Class: System
- Problem Description:
System firmware requested that Late Self
Tests be run by PAL, but PAL returned that the tests did not actually run on
the processor. The data field indicates the status word returned by PAL.
- Cause / Action:
This could be caused by an incompatibility
problem between PAL and the CPUs. Check that PAL supports all the CPUs
installed on the system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 888
- Severity: CRITICAL
- Event Summary: A fabric walk failed while updating the cell state
- Event Class: System
- Problem Description:
An attempt to update the cell state has
failed due to a fabric crossbar failure. The cell number being updated in in
bits 63:56, while the traversable cell set (those cells connected to the
fabric) is returned in bits 31:0
- Cause / Action:
Look for adjacent chassis codes to determine
the cause of FabricWalk failure. Check the backplane and fabric
connectivity. Contact the HP Support Personnel for further
troubleshooting.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 889
- Severity: CRITICAL
- Event Summary: Could not reset the cell due to failure updating
cell state
- Event Class: System
- Problem Description:
Failed to reset a cell due to an error
setting the cell's state. The cell will not be reset with the other cells in
the PD. The cell number is reported in the data field.
- Cause / Action:
Most likely a failure on the fabric or on the
CC. Fabric failures should produce additional chassis codes. If no
additional chassis codes indicate the cause of the failure, then contact
the HP Support Personnel for further troubleshooting.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 890
- Severity: MAJOR
- Event Summary: DRAM failure on DIMM XX, deallocte rank
- Event Class: System
- Problem Description:
SFW has detected that a DRAM is failing
on the DIMM specified by the physical location. The rank the failing DIMM is
part of will be deallocated.
- Cause / Action:
Cause: SFW detected a failing DIMM Action: Replace the DIMM flagged by SFW
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 891
- Severity: CRITICAL
- Event Summary: System Clocks are not valid
- Event Class: System
- Problem Description:
Internal CPU clocks are not valid when
compared with the real time clock. The data field contains the hex value of
the elapsed time. If this value is off a small percentage from the expected
value (which is given in the next chassis code), the event is emitted.
- Cause / Action:
The Cell board has a problem. Either the Real
Time Clock is not working properly or the system is not being clocked at the
value it thinks it is.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 892
- Severity: CRITICAL
- Event Summary: Cell Online Addition failed due to fabric access
error
- Event Class: System
- Problem Description:
Could not traverse the fabric to the
cell being added. Data field: (chosen cell << 56) | return status,
where -1 = failure
- Cause / Action:
Cause: Fabric Access Failure, Action: Check
CC to CC link. Look for additional failure chassis codes to provide more
detail.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 893
- Severity: CRITICAL
- Event Summary: Fabric found a bad XBC port on a reboot.
Attempting to route around it.
- Event Class: System
- Problem Description:
A XBC port was found to be unhealthy on
this reboot. This cell will attempt to route around it. Data field: (local
Cell << 56) | (local internal Port << 44) | (local XBC <<
32) | XBC internal port number being routed around.
- Cause / Action:
Cause: link errors. Action: Run DC
Connectivity test. Check flex cables, XBCs, and CCs.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 894
- Severity: MAJOR
- Event Summary: Could not access an internal firmware table while
rerouting XBC port
- Event Class: System
- Problem Description:
Error getting the XBC port's expected
neighbor from a firmware table. Data field: 0 (SUCCESS) or -1 (FAILURE)
- Cause / Action:
Cause: Firmware Error. Action: Capture
chassis codes and contact HP Support.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 895
- Severity: MAJOR
- Event Summary: Cell/Partition to be reset because PDC couldn't
read PDH memory
- Event Class: System
- Problem Description:
Either PDC is going to halt the cell or
reset the partition because PDC was unable to access the PDH memory of
either its local cell or another cell in the partition. The data field
contains the error return value from PDC function IsHCellCpuDeconfig().
- Cause / Action:
Cause1: Cell hardware problem like PDH memory
itself, the coherency controller, the executing CPU or interaction between
any of these cell components. Action1: Contact HP Support to troubleshoot
the cell and either fix it or replace it. Cause2: PDC bug in which PDC
thinks it was unable to safely access PDH memory when maybe it really could
have. Action2: Contact HP Support to see if a new PDC image is
available.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 896
- Severity: MAJOR
- Event Summary: Cell/Partition to be reset because PDC couldn't
read PDH memory
- Event Class: System
- Problem Description:
Either PDC is going to halt the cell or
reset the partition because PDC was unable to access the PDH memory of
either its local cell or another cell in the partition. The data field
contains the error return value from PDC function
SleepAndWakeupCountersGet().
- Cause / Action:
Cause1: Cell hardware problem like PDH memory
itself, the Concorde chip, the executing Mako or interaction between any of
these cell components. Action1: Troubleshoot the cell and either fix it or
replace it. Cause2: PDC bug in which PDC has passed an invalid argument from
one PDC function to another. Action2: Upgrade PDC if this is found to be the
problem and a new PDC image is available.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 897
- Severity: MAJOR
- Event Summary: Cell/Partition to be reset because PDC couldn't
read PDH memory
- Event Class: System
- Problem Description:
Either PDC is going to halt the cell or
reset the partition because PDC was unable to access the PDH memory of
either its local cell or another cell in the partition. The data field
contains the error return value from PDC function PdhGetHCellStructAddr().
- Cause / Action:
Cause1: Cell hardware problem like PDH memory
itself, the Concorde chip, the executing Mako or interaction between any of
these cell components. Action1: Troubleshoot the cell and either fix it or
replace it. Cause2: PDC bug in which PDC thinks it was unable to safely
access PDH memory when maybe it really could have. Action2: Upgrade PDC if
this is found to be the problem and a new PDC image is available.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 898
- Severity: MAJOR
- Event Summary: Cell/Partition to be reset because PDC couldn't
read PDH memory
- Event Class: System
- Problem Description:
Either PDC is going to halt the cell or
reset the partition because PDC was unable to access the PDH memory of
either its local cell or another cell in the partition. The data field
contains the error return value from PDC function
HasCpuCompletedWakeupTask().
- Cause / Action:
Cause1: Cell hardware problem like PDH memory
itself, the Concorde chip, the executing Mako or interaction between any of
these cell components. Action1: Troubleshoot the cell and either fix it or
replace it. Cause2: PDC bug in which PDC thinks it was unable to safely
access PDH memory when maybe it really could have. Action2: Upgrade PDC if
this is found to be the problem and a new PDC image is available.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 899
- Severity: MAJOR
- Event Summary: Cell/Partition to be reset because PDC couldn't
read PDH memory
- Event Class: System
- Problem Description:
Either PDC is going to halt the cell or
reset the partition because PDC was unable to access the PDH memory of
either its local cell or another cell in the partition. The data field
contains the error return value from PDC function PdhGetHCellStructAddr().
- Cause / Action:
Cause1: Cell hardware problem like PDH memory
itself, the Concorde chip, the executing Mako or interaction between any of
these cell components. Action1: Troubleshoot the cell and either fix it or
replace it. Cause2: PDC bug in which PDC thinks it was unable to safely
access PDH memory when maybe it really could have. Action2: Upgrade PDC if
this is found to be the problem and a new PDC image is available.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 900
- Severity: MAJOR
- Event Summary: A reset for reconfiguration will be performed soon
on the cell.
- Event Class: System
- Problem Description:
There is a need to reset the cell for
reconfiguration, but it cannot be done yet because the cell has not reported
at BIB. The Reset is being scheduled to be performed later.
- Cause / Action:
An error during cell initialization occurred
and the cell will not be able to join the partition. Look for other errors
in the event log that articulate the exact problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 901
- Severity: MAJOR
- Event Summary: The Partition Profile specifies the wrong
architecture type
- Event Class: System
- Problem Description:
When processing the complex profile, the
an unexpected "Architecture Type" was specified in the PA/IA Arch field. The
actual data found is displayed.
- Cause / Action:
This is caused by the wrong type of complex
profile being loaded. System firmware will default a new partition profile
and continue on.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 902
- Severity: MAJOR
- Event Summary: Cell/Partition is about to be reset because PDC is
unable to access CPU data
- Event Class: System
- Problem Description:
While trying to determine whether or not
a particular processor has completed the task for which it was awakened, PDC
was unable to access the deconfig byte information about the target
processor. A processor should always be able to access this data in PDH
memory for any processor on its own cell and for any processor on a cell
that is alive in the partition. Therefore, PDC is either going to halt the
cell or reset the partition because of this problem. The data field contains
the PDC error return status from IsHCellCpuDeconfig().
- Cause / Action:
Cause1: Cell hardware problem, like a problem
with PDH registers or PDH memory, or a problem with the concorde or Mako
chips. Action1: Troubleshoot the cell and either fix cell or replace the
cell board. Cause2: PDC problem such that PDC is passing bad data from one
function to another. Action2: Upgrade PDC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 903
- Severity: MAJOR
- Event Summary: Cell/Partition is about to be reset because PDC is
unable to access CPU data
- Event Class: System
- Problem Description:
While trying to determine whether or not
a particular processor has completed the task for which it was awakened, PDC
was unable to access the CPU's sleep and wakeup counters for the target
processor. A processor should always be able to access this data in PDH
memory for any processor on its own cell and for any processor on a cell
that is alive in the partition. Therefore, PDC is either going to halt the
cell or reset the partition because of this problem. The data field contains
the PDC error return status from SleepAndWakeupCountersGet().
- Cause / Action:
Cause1: Cell hardware problem, like a problem
with PDH registers or PDH memory, or a problem with the concorde or Mako
chips. Action1: Troubleshoot the cell and either fix cell or replace the
cell board. Cause2: PDC problem such that PDC is passing bad data from one
function to another. Action2: Upgrade PDC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 904
- Severity: MAJOR
- Event Summary: Cell/Partition about to be reset because PDC is
unable to access CPU data
- Event Class: System
- Problem Description:
While trying to determine whether or not
a particular processor has completed the task for which it was awakened, PDC
was unable to access the CPU's forward progress state (ie PST state) for the
target processor. A processor should always be able to access this data in
PDH memory for any processor on its own cell and for any processor on a cell
that is alive in the partition. Therefore, PDC is either going to halt the
cell or reset the partition because of this problem. The data field contains
the PDC error return status from CpuFpSet().
- Cause / Action:
Cause1: Cell hardware problem, like a problem
with PDH registers or PDH memory, or a problem with the concorde or Mako
chips. Action1: Troubleshoot the cell and either fix cell or replace the
cell board. Cause2: PDC problem such that PDC is passing bad data from one
function to another. Action2: Upgrade PDC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 905
- Severity: MAJOR
- Event Summary: Cell/Partition is about to be reset because PDC is
unable to access CPU data
- Event Class: System
- Problem Description:
While trying to determine whether or not
a particular processor has completed the task for which it was awakened, PDC
was unable to access the CPU's Forward Progress State (ie PST state) for the
target processor. A processor should always be able to access this data in
PDH memory for any processor on its own cell and for any processor on a cell
that is alive in the partition. Therefore, PDC is either going to halt the
cell or reset the partition because of this problem. The data field contains
the PDC error return status from CpuFpSet().
- Cause / Action:
Cause1: Cell hardware problem, like a problem
with PDH registers or PDH memory, or a problem with the concorde or Mako
chips. Action1: Troubleshoot the cell and either fix cell or replace the
cell board. Cause2: PDC problem such that PDC is passing bad data from one
function to another. Action2: Upgrade PDC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 906
- Severity: MAJOR
- Event Summary: PDC is unable to branch to other software via the
Page Zero location
- Event Class: System
- Problem Description:
At a certain point in PDC boot, all of
the processors in the partition except the PD monarch are put into a sleep,
and they remain there until they are awakened by the PD monarch, at which
time they read an architected location in Page Zero to find out where to
branch to. This gives the OS a mechanism by which to bring processors under
its control and have it executing OS code. This chassis log is sent if and
when a problem is detected by PDC regarding the contents in the Page Zero
location. This means that PDC cannot branch to the location logged in the
Page Zero location. So, PDC sends this chassis log and then the processor
returns to sleep. The data field is unused.
- Cause / Action:
Cause1: The MEM_RENDEZ fields of Page Zero
were programmed incorrectly. Action1: Upgrade or patch the OS. Cause2: Cell
Hardware or memory problem that PDC didn't catch. Action2: Troubleshoot the
cell to find out if page zero contents are screwed up or if hardware is just
failed to do the OS write or failed to do the PDC read. Verify that memory
is properly written and holds contents at the page zero locations. Perhaps
replace the cell board or replace the memory. Cause3: PDC is not doing the
appropriate verification of the page zero contents and is treating it like
its invalid even though maybe its not. Action3: Upgrade PDC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 908
- Severity: MAJOR
- Event Summary: PDC couldn't access a data structure in PDH memory
- Event Class: System
- Problem Description:
While trying to get the sleep counter
and the wakeup counter for a particular processor, which is kept in a data
structure in PDH memory, PDC was unable to determine the address to the data
structure on the remote cell. PDC is supposed to be able to calculate
addresses to anything in PDH memory on other cells in the partition. The
data field contains the PDC error return status from a function called
PdhGetHCellStructAddr().
- Cause / Action:
Cause1: Cell hardware problem with the PDH
memory, the Concorde chip, or the Mako processor itself. Action1:
Troubleshoot/Replace the cell. Cause2: PDC bug in which PDC is trying to
access PDH memory of a cell not in its partition. Action2: Upgrade PDC if
there is a version of PDC that fixes such a problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 909
- Severity: MAJOR
- Event Summary: Error occurred accessing a PDC data structure
- Event Class: System
- Problem Description:
Error occurred accessing a PDC data
structure. Depending upon the situation the cell or entire partition will be
reset. The data field contains the return status for the function that
encountered the error.
- Cause / Action:
Cause1: Hardware problem with the PDH riser
card. Action1: Contact HP Support to confirm the PDH riser card is
functioning properly. Cause2: Hardware problem with the CPU or cell board.
Action2: Contact HP Support to confirm the CPUs and cell board are
functioning properly.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 910
- Severity: MAJOR
- Event Summary: Cell about to be halted because PDC couldn't
determine relocated address of code
- Event Class: System
- Problem Description:
PDC is about to halt the cell because
PDC was unable to determine the GNI address of the SlaveDispatcher function
of PDC relocated to memory by PDC. The data field contains the error return
value from the function GetGniCodeAddrFromRomCodeAddr().
- Cause / Action:
Cause1: Hardware connecting cells in the
partition experienced a problem such that cells in the partition together
can no longer communicate. Action1: Troubleshoot the fabric and
reseat/replace the cells or cables or backplane if necessary. Cause2: Cell
was unable to access its own PDH memory. Action2: Troubleshoot the cell
board and replace it if necessary. Cause3: PDC bug such that PDC didn't log
the relocation address. Action3: Check for PDC upgrade
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 911
- Severity: MAJOR
- Event Summary: Halting cell because a CPU didn't complete the
task for which it was awakened
- Event Class: System
- Problem Description:
PDC is about to halt the cell because at
least one of the processors didn't complete the task for which they were
awakened and then return to sleep. The data field contains an error return
status.
- Cause / Action:
Cause1: Hardware problem with the CPU, CC, or
PDH flash. Action1: Troubleshoot the cell and/or replace it.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 912
- Severity: MAJOR
- Event Summary: Cell about to be halted because PDC couldn't
determine relocated address of code
- Event Class: System
- Problem Description:
PDC is about to halt the cell because
PDC was unable to determine the GNI address of the CpuFpSet() function of
PDC relocated to memory by PDC. The data field contains the error return
value from the function GetGniCodeAddrFromRomCodeAddr().
- Cause / Action:
Cause1: Hardware connecting cells in the
partition experienced a problem such that cells in the partition together
can no longer communicate. Action1: Troubleshoot the fabric and
reseat/replace the cells or cables or backplane if necessary. Cause2: Cell
was unable to access its own PDH memory. Action2: Troubleshoot the cell
board and replace it if necessary. Cause3: PDC bug such that PDC didn't log
the relocation address. Action3: Check for PDC upgrade
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 913
- Severity: MAJOR
- Event Summary: Cell about to be halted because CPU couldn't
change its CPU FP (PST) state
- Event Class: System
- Problem Description:
PDC is about to halt the cell because
one or more of the slaves were unable to change their CPU FP state in PDH
memory on the local cell. The data field contains an error return status.
- Cause / Action:
Cause1: Hardware problem with the cell (like
PDH memory) or the CC or CPU. Action1: Contact HP support to troubleshoot or
replace the cell board. Cause2: PDC bug. Action2: Contact HP Support to
check for PDC upgrade.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 914
- Severity: CRITICAL
- Event Summary: Partition about to be reset because PDC couldn't
get address to a structure
- Event Class: System
- Problem Description:
PDC was trying to move the cell monarchs
on each of the non-core cells into the Dispatcher, but in order to do that,
the PD monarch needs to be able to read the CPU number of the cell monarch
on each of the non-core cells, which is kept in a data structure on each of
the cells. PDC was unable to get the address to the CELL_CPU_STATE structure
in PDH memory in a cell in the partition. The data field is the error return
status from the PDC function called PdhGetHCellStructAddr().
- Cause / Action:
Cause1: Hardware connecting cells in the
partition experienced a problem such that cells in the partition together
can no longer communicate. Action1: Troubleshoot the fabric and replace
backplane or cells. Cause2: Cell was unable to access its own PDH memory.
Action2: Troubleshoot the cell board and replace it if necessary. Cause3:
PDC bug such that PDC passed invalid arguments to try to get the address to
the data structure. Action3: Upgrade PDC if there is a fix for this
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 915
- Severity: CRITICAL
- Event Summary: Resetting a partition because a CPU didn't
complete the task it was awakened for
- Event Class: System
- Problem Description:
PDC is about to reset the partition
because at least one of the processors didn't complete the task for which
they were awakened and then return to sleep. The data field contains the
error return status from the PDC function CheckSingleSlave().
- Cause / Action:
Cause1: Hardware problem with the Mako chip,
Concorde chip, or PDH flash. Action1: Troubleshoot the cell and/or replace
it.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 916
- Severity: CRITICAL
- Event Summary: Resetting partition because PDC couldn't determine
relocated address of code
- Event Class: System
- Problem Description:
PDC is about to reset the partition
because it is unable to determine the GNI address for the CpuFpSet()
function for one or more of the cells in the partition. The data field
contains the error return status from GetGniCodeAddrFromRomCodeAddr().
- Cause / Action:
Cause1: Hardware connecting cells in the
partition experienced a problem such that cells in the partition together
can no longer communicate. Action1: Troubleshoot the fabric and replace
backplane or cells. Cause2: Cell was unable to access its own PDH memory.
Action2: Troubleshoot the cell board and replace it if necessary. Cause3:
PDC bug such that PDC didn't log the relocation address. Action3: Upgrade
PDC if there is a fix for this problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 917
- Severity: CRITICAL
- Event Summary: Resetting partition because a CPU was unable to
change its CPU FP state
- Event Class: System
- Problem Description:
PDC is about to reset the partition
because one or more of the processors were unable to successfully modify
their CPU FP State (aka their PST state). The data field contains the error
return status from the CpuFpSet() function.
- Cause / Action:
Cause1: Hardware problem with PDH memory,
Concorde chip, or the Mako chip. Action1: Troubleshoot the cell and/or
replace it. Cause2: PDC bug in which passed invalid arguments. Action2:
Upgrade PDC if there is a fix.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 918
- Severity: MAJOR
- Event Summary: CPU Dual Core Initialization Failed
- Event Class: System
- Problem Description:
CPU Dual Core Initialization Failed
- Cause / Action:
Attempt Reboot, Replace Processor
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 919
- Severity: MAJOR
- Event Summary: Second CPU in Pair has been disabled
- Event Class: System
- Problem Description:
None
- Cause / Action:
The second CPU in the Dual Core has been
deconfigured as a result of the first core being deconfigured. Investigate
the cause of the first core being deconfigured
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 920
- Severity: MAJOR
- Event Summary: Virtualzing Dual Core Registers Failed
- Event Class: System
- Problem Description:
None
- Cause / Action:
Reboot, if problem continues, replace CPU
Module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 921
- Severity: MAJOR
- Event Summary: Virtualizing Dual Core Interposer has failed
- Event Class: System
- Problem Description:
None
- Cause / Action:
Virtualizing the Dual Core Interposer has
failed. Reboot, if problem continues, Replace CPU module.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 922
- Severity: MAJOR
- Event Summary: Install PMI Handler Failed
- Event Class: System
- Problem Description:
None
- Cause / Action:
Reboot, if problem continues replace CPU
Module
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 923
- Severity: FATAL
- Event Summary: Cell failed compatibility checks.
- Event Class: System
- Problem Description:
Cell and or CPUs have failed
compatibility checks.
- Cause / Action:
Cause - CPUs are incompatible with each
other, or the cell front side bus frequency is incompatible with the CPUs.
Action - Correct the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 924
- Severity: FATAL
- Event Summary: PDH space not available after release from reset.
- Event Class: System
- Problem Description:
PDH space not available after release
from reset.
- Cause / Action:
Cause - Hardware failure. Action - Fix the
hardware, cell or PDH riser.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 925
- Severity: FATAL
- Event Summary: MPON failed to release.
- Event Class: System
- Problem Description:
MPON failed to release.
- Cause / Action:
Cause - Hardware failure. Action - Fix the
hardware, cell or pdh riser.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 926
- Severity: FATAL
- Event Summary: Dillon failed to reset.
- Event Class: System
- Problem Description:
Dillon failed to reset.
- Cause / Action:
Cause - Hardware failure. Action - Fix the
hardware, pdh riser or cell.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 927
- Severity: FATAL
- Event Summary: DMD clock is not running.
- Event Class: System
- Problem Description:
DMD clock is not running.
- Cause / Action:
Cause - Hardware problem Action - Fix the
hardware, pdh riser or cell board.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 928
- Severity: CRITICAL
- Event Summary: All cpus on the Cell are scheduled to be
deconfigured
- Event Class: System
- Problem Description:
All possible CPUs on a cell have been
scheduled for deconfiguration.
- Cause / Action:
All cpus on the cell have been scheduled for
deconfiguration. On the next reset, the cell will no longer be operational;
system firmware will deconfigure all the cpus and this cell will not be part
of a partition. This action is not recommended. To recover, the NVRAM on the
PDH card must be cleared, the cell power cycled, and defaults restored from
disk.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 929
- Severity: CRITICAL
- Event Summary: A read error occurred while dumping the routing
registers
- Event Class: System
- Problem Description:
A read error occurred while dumping the
XBC port routing registers during boot. This cell will attempt fabricless
boot. Data field: (XBC port << 48) | (XBC num << 32) | error
status reg
- Cause / Action:
Cause: Fabric Read Error. Action: Check XBC,
CC, links, etc.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 930
- Severity: FATAL
- Event Summary: Failed to disable the CC to CC link
- Event Class: System
- Problem Description:
After cell rendezvous for a 2 cell
Medel, only one cell made it into the partition. Disabling the link failed.
The cell will reset for reconfig. Data Field: return status
- Cause / Action:
Failure to read or write Concorde
CSRs.
Contact HP Support personnel to check the Check CC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 931
- Severity: MAJOR
- Event Summary: Power has been removed from AC input A0.
- Event Class: System
- Problem Description:
Power is no longer being supplied to
input A0 on the cabinet specified in the data field.
- Cause / Action:
A power source has been removed from the
chassis.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 932
- Severity: MAJOR
- Event Summary: Power has been removed from AC input A1.
- Event Class: System
- Problem Description:
Power is no longer being supplied to
input A1 on the cabinet specified in the data field.
- Cause / Action:
A power source has been removed from the
chassis.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 933
- Severity: MAJOR
- Event Summary: Power has been removed from AC input B0.
- Event Class: System
- Problem Description:
Power is no longer being supplied to
input B0 on the cabinet specified in the data field.
- Cause / Action:
A power source has been removed from the
chassis.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 934
- Severity: MAJOR
- Event Summary: Power has been removed from AC input B1.
- Event Class: System
- Problem Description:
Power is no longer being supplied to
input B1 on the cabinet specified in the data field.
- Cause / Action:
A power source has been removed from the
chassis.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 935
- Severity: MAJOR
- Event Summary: Failed to disable the XIN link during a failed
link init
- Event Class: System
- Problem Description:
Failed to disable the XIN link init CSR
on a XBCless system. Cell will halt. Data field: return status (0 = SUCCESS,
-1 = FAILURE), -1 is expected for this event.
- Cause / Action:
Have your HP Support Representative check the
Coherency Controller
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 937
- Severity: MAJOR
- Event Summary: Error while reading the remote CC's XIN Error Mask
register
- Event Class: System
- Problem Description:
Could not read the XIN error mask
regisiter on the CC. Data Field: cell number and return status
- Cause / Action:
CC access failure.
Contact HP Support
personnel to check the CC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 938
- Severity: MAJOR
- Event Summary: Error clearing the init packet received bit in the
XIN error mask
- Event Class: System
- Problem Description:
Could not write the XIN error mask
register on the CC. Data Field: cell number and return status
- Cause / Action:
Cause: CC access failure.
PDC Reviewed
alert level for SR - 9/6/03 CC.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 939
- Severity: MAJOR
- Event Summary: Failed to read the XBC's Port Status register
- Event Class: System
- Problem Description:
While testing link traveresability, a XBC
CSR could not be read. Data Field: Port Number << 44 | XBC Number
<< 32 | return value
- Cause / Action:
Cause: fabric access failure Action: Check
XBC, Check CC, Check backplane
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 941
- Severity: CRITICAL
- Event Summary: FW will not handoff to the OS_MCA handler for this
MCA event
- Event Class: System
- Problem Description:
This means that the system FW MCA
handler is not going to handoff to the OS_MCA handler.
- Cause / Action:
The error logs should be retrieved from the
EFI shell prompt.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 942
- Severity: CRITICAL
- Event Summary: The NVRAM block table maintained by System
Firmware is corrupt
- Event Class: System
- Problem Description:
Unused
- Cause / Action:
The NVRAM-based descriptor for System
Firmware NVRAM blocks is corrupt.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 943
- Severity: MAJOR
- Event Summary: All CPUs were deconfigured and have now been
reconfigured.
- Event Class: System
- Problem Description:
All CPUs have been determined to be
manually deconfigured in NVM during boot. This may only happen when
switching from single core CPU deconfiguration to multi-core CPU
deconfiguration in product qualification testing. As a recovery, NVM
settings have been changed to reconfigure all CPUs.
- Cause / Action:
Cause: User test operational error. Action:
Reboot system and update CPU configuration as desired.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 944
- Severity: MAJOR
- Event Summary: A failure has occurred trying to determine the
number of CPU cores per module.
- Event Class: System
- Problem Description:
A failure has occurred trying to
determine the number of CPU cores per module. Depending upon the situation,
either the cell will be halted or the entire partition will be reset.
- Cause / Action:
C1: Hardware failure with CPU, CC or cell
board. A1: Contact HP Support to confirm the CPUs, CC, and cell board are
functioning properly. Update PDC if a version is available to fix this
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 945
- Severity: MAJOR
- Event Summary: Couldn't read the topology from the XBC register
- Event Class: System
- Problem Description:
While writing the remote routing, the
local XBC could not be accessed to determine the topology. Look for
additional chassis codes to determine what will happen as a result of this
failure. Data field: return status, either SUCCESS (0) or (-1)
- Cause / Action:
Fabric Access Error
Contact HP Support
personnel to check the XBC, Backplane, CC
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 947
- Severity: MAJOR
- Event Summary: Failed to read the XBC CSR that contains the
number of failed links
- Event Class: System
- Problem Description:
Could not read the XBC register that
contains the number of links that are currently broken on the complex. Data
Field: (XBC Num << 32) | PDC return status
- Cause / Action:
Fabric Access Failure
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 948
- Severity: MAJOR
- Event Summary: Failed to read the XBC CSR that contains the
number of failed links
- Event Class: System
- Problem Description:
Could not read the XBC register that
contains the number of links that are currently broken on the complex. Data
Field: (XBC Num << 32) | PDC return status
- Cause / Action:
Fabric Access Failure
Contact HP Support
personnel to check XBC, Backplane, CC, look for additional chassis codes to
describe the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 949
- Severity: MAJOR
- Event Summary: Failed to write the XBC CSR that contains the
number of failed links
- Event Class: System
- Problem Description:
Could not write the XBC register that
contains the number of links that are currently broken on the complex. Data
Field: (XBC Num << 32) | PDC return status
- Cause / Action:
Fabric Access Failure
Contact HP Support
personnel to check XBC, Backplane, CC, look for additional chassis codes to
describe the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 952
- Severity: CRITICAL
- Event Summary: This cell encountered too many broken crossbar
links
- Event Class: System
- Problem Description:
Too many broken crossbar links were
found. This cell will have no connectivity to other cells in the complex. It
will attempt a fabricless boot, except in a few configurations. Data Field:
(XBC Num << 32) | number of broken links
- Cause / Action:
Cause: Broken fabric links, Action: Check
XBC, Backplane, Flex Cables, look for additional chassis codes to describe
the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 958
- Severity: MAJOR
- Event Summary: Failed to do a broadcast write to the XBC Remote
Routing registers
- Event Class: System
- Problem Description:
Failed to complete a broadcast write to
an XBC. Data Field: (XBC Num << 32) | PDC return status
- Cause / Action:
Fabric Access Failure
Contact HP Support
personnel to check the XBC, Backplane, CC. Look for additional chassis codes
to describe the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 959
- Severity: MAJOR
- Event Summary: Failed to read a XBC Remote Routing register
- Event Class: System
- Problem Description:
Failed to complete a read to the
built-in port of a XBC. Data Field: (XBC Num << 32) | PDC return
status
- Cause / Action:
Fabric Access Failure
Contact HP Support
personnel to check the XBC, Backplane, CC. Look for additional chassis codes
to describe the problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 960
- Severity: MAJOR
- Event Summary: Failed to write a XBC Remote Routing register
- Event Class: System
- Problem Description:
Failed to complete a write to the local
cell's port of the XBC. Data Field: (XBC Port << 44) | (XBC Num
<< 32) | PDC return status
- Cause / Action:
Cause: Fabric Access Failure, Action: Check
XBC, Backplane, CC. Look for additional chassis codes to describe the
problem.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 961
- Severity: CRITICAL
- Event Summary: The link between the CC and SBA failed
- Event Class: System
- Problem Description:
The link between the CC and SBA failed
meaning that I/O is not available to the reporting cell.
- Cause / Action:
See other associated events for the root
cause of the failure.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 962
- Severity: CRITICAL
- Event Summary: The SBA failed and the cell has no I/O
- Event Class: System
- Problem Description:
An error was detected in the SBA and the
reporting cell has no I/O.
- Cause / Action:
See other associated events that describe the
root cause.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 963
- Severity: CRITICAL
- Event Summary: The system firmware had an error with the
structured error handling mechanism.
- Event Class: System
- Problem Description:
The structured exception handling within
the system firmware failed during I/O initialization.
- Cause / Action:
Cause: Either there is an error in the system
firmware or the system firmware has exhausted all resources. Action:
Invalidate NVM or check for newer version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 964
- Severity: CRITICAL
- Event Summary: Not enough malloc resources for I/O structure
error handling.
- Event Class: System
- Problem Description:
There is not enough malloc resources for
the I/O structure exception handling. I/O on the reported cell is not
available.
- Cause / Action:
Either invalidate NVM or check for a new
version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 965
- Severity: CRITICAL
- Event Summary: Unable to create entry for I/O structure error
handling.
- Event Class: System
- Problem Description:
Error creating the structure for housing
the I/O structured exception handling services and data. I/O is lost on the
reporting cell.
- Cause / Action:
This is a system firmware error, either
invalidate NVM or check for a newer version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 966
- Severity: CRITICAL
- Event Summary: Unable to bind services for I/O structure
exception handling.
- Event Class: System
- Problem Description:
Unable to bind the I/O structure
exception handling to the internal data structures.
- Cause / Action:
This is a system firmware error. Either reset
NVM or check for a newer version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 967
- Severity: CRITICAL
- Event Summary: Error initializing the I/O structure exception
handling services.
- Event Class: System
- Problem Description:
Error detected while initializing the
I/O structure exception handling services.
- Cause / Action:
This is a system firmware error. Either reset
NVM or check for a newer version of system formware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 968
- Severity: CRITICAL
- Event Summary: Error initializing structured I/O exception data
structures.
- Event Class: System
- Problem Description:
Error initializing the I/O structure
exception handling data structures.
- Cause / Action:
This is a system formware error, there is a
conflict with system resources. Either reset NVM or check for a newer
version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 969
- Severity: CRITICAL
- Event Summary: The I/O exception context has an error.
- Event Class: System
- Problem Description:
The structured I/O exception handling
data structures have an error. All I/O on the reporting cell is not
available.
- Cause / Action:
This is a system firmware error. Reset the
system, invalidate NVM and reset the system, or check for a newer version of
the system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 970
- Severity: CRITICAL
- Event Summary: Error creating the internal data and services for
the SBA.
- Event Class: System
- Problem Description:
While setting up the internal SBA data
and service an error was detected. All I/O for the reporting cell is not
available.
- Cause / Action:
This is a system firmware error. Reset the
system; invalidate NVM and reset the system; or check for a newer version of
system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 971
- Severity: CRITICAL
- Event Summary: Error attaching the series to the SBA internal
data structures.
- Event Class: System
- Problem Description:
An error attaching firmware services to
the internal structures was detected. All I/O on the reporting cell is not
available.
- Cause / Action:
This is a system firmware error. Reset the
partition; invalidate NVM on the reporting cell and reset the system; or
check for a newer version of system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 972
- Severity: CRITICAL
- Event Summary: Error initializing the intrenal SBA data and
services.
- Event Class: System
- Problem Description:
System firmware detected an error
initializing internal SBA data structures and services. This is usually an
error with unavailable resources.
- Cause / Action:
This is a system formware error. Reset the
partition; invalidate NVM on the reporting cell and reset the partition; or
check for newer system firmware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 973
- Severity: CRITICAL
- Event Summary: The SBA type is unknown to the system firmware
- Event Class: System
- Problem Description:
The SBA type is unknown to the system
firmware. The I/O on the reporting cell is not available.
- Cause / Action:
This is either a system firmware error, or
the wrong I/O is connected to the system. Validate the system recipe both
firmware and hardware.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 974
- Severity: MAJOR
- Event Summary: An embedded I/O device is missing.
- Event Class: System
- Problem Description:
An expected I/O device cannot be
detected by the system firmware.
- Cause / Action:
Replaces the I/O card specified by the
physical location.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 975
- Severity: MAJOR
- Event Summary: Fabric link route around failed because the route
around port was bad
- Event Class: System
- Problem Description:
Too many broken links! The XBC port
route around failed because the route-around port was bad too. Data field:
(XBC port << 44) | (XBC num << 32) | port state
- Cause / Action:
Cause: 2 or more XBC links are not
routable.
Contact HP Support personnel to check the XBC, Flex Cables,
Backplane, CCs, etc
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 977
- Severity: MAJOR
- Event Summary: (warning) Outputted in MFG, when Memory SBE
Seeding is enabled
- Event Class: System
- Problem Description:
This is a warning that the system is
running in a degregated mode. It will only be emitted in MFG mode when
Memory SBE Seeding is enabled. This is only for testing of SBE seeding for
LAB and possibly MFG use ONLY. It should NEVER be seen in the field.
- Cause / Action:
Cause: In MFG with Memory SBE Seeding control
Flag (26) Enabled. Should never be seen at a customer's machine.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 978
- Severity: CRITICAL
- Event Summary: Failed to read the fabric topology information
from the XBC
- Event Class: System
- Problem Description:
Read failure while writing the number of
failed links to the XBC. Data Field: Return Status (SUCCESS = 0, FAILURE =
-1)
- Cause / Action:
Fabric Access Failure.
Contact HP Support
personnel to analyze the fabric.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 981
- Severity: CRITICAL
- Event Summary: Could not disable the XIN link before a fabricless
boot
- Event Class: System
- Problem Description:
Before attempting a fabricless boot, the
cell's link to the fabric should be disabled to provide isolation and
stability. The link could not be disabled, so the cell will halt.
- Cause / Action:
Fabric Access Error.
Contact HP Support
personnel to check the CC, Check XBC
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 985
- Severity: CRITICAL
- Event Summary: Manual override of fatal stop boot condition
- Event Class: System
- Problem Description:
The user has manually bypassed a stop
boot condition (caused by a fatal error during boot) and continued to boot
an O/S. The system might experience unpredictable failures.
- Cause / Action:
Cause: The user has initiated manual O/S boot
despite the existence of a fatal error. Action: Correct the fatal error
condition (see output of "INFO WARNING" EFI shell command), reboot the
system, and then initiate O/S boot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 986
- Severity: MAJOR
- Event Summary: Firmware unable to relocate VGA BIOS
- Event Class: System
- Problem Description:
Firmware was unable to relocate the VGA
BIOS to the hardcoded VGA BIOS region in main memory (physical address range
0xc0000 - 0xdffff). VGA routing has been disabled by firmware. No VGA device
will be accessible on this boot.
- Cause / Action:
Cause: Most likely there is a permanent
memory error in the VGA BIOS region (physical address 0xc0000 - 0xdffff).
Action: Replace the DIMM causing the permanent memory error in the VGA BIOS
region. The PDT reports which DIMM is causing errors in the physical address
range 0xc0000 - 0xdffff.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 993
- Severity: MAJOR
- Event Summary: PDC could not access a complex profile
- Event Class: System
- Problem Description:
PDC could not access a complex profile.
The cell will be reset. Data field contains the return status from the
function that encountered the error.
- Cause / Action:
Cause1: An error occurred which prevented the
complex profiles from being distributed properly. Action1: Create and
distribute a new complex profile using ParMgr on a functional partition in
the complex. Restore the last complex profile using the "CC" command from
the MP, then use ParMgr to create a new complex profile. Generate a genesis
complex profile using the "CC" command from the MP, then use ParMgr to
create a new complex profile. Cause2: A hardware problem exists with MP or
PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are
functioning properly.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 994
- Severity: MAJOR
- Event Summary: No possible core cells were found in the
configured set
- Event Class: System
- Problem Description:
Could not find a potential core cell for
the partition in the configured set. This cell will reset for
reconfiguration. Data Field: return status from failing function
- Cause / Action:
Cause: most likely a configuration problem,
Action: check to ensure a valid core cell is configured to be in the
partition.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 995
- Severity: MAJOR
- Event Summary: Could not find a viable core cell in the partition
- Event Class: System
- Problem Description:
The potential core cell was not viable
(ie. no core I/O, etc). This cell will reset for reconfiguration. Data
Field: bit mask of cells that made the rendezvous set
- Cause / Action:
Cause: Configuration error, fabric failure;
the intended core cell failed during boot. Action: check partition
configuration, check for failed cells.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 996
- Severity: MAJOR
- Event Summary: Could not find a viable core cell in the partition
- Event Class: System
- Problem Description:
The potential core cell was not viable
(ie. no core I/O, etc). This cell will reset for reconfiguration. Data
Field: bit mask of cells that made the rendezvous set
- Cause / Action:
Cause: Configuration error, Mainbackplane
failure, The intended core cell failed during boot. Action: Check partition
configuration, Check for failed cells, as indicated by high-alert level IPMI
events earlier in the boot.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Event 997
- Severity: MAJOR
- Event Summary: The core cell selected is not in the rendezvoused
partition
- Event Class: