HP Insight Management WBEM Provider Events Reference Guide

Malloc failed while trying to process and ERM. Probable Cause: Heap space is
completely used or corrupt. Contact Product Engineering. WBEM EventID: 829.
WBEM ProviderName: FPL_IndicationProvider.Error8819
Dimm at physical location in data field is not supported on this platform. Probable
Cause: Unsupported dimm in specified slot. Recommended Action: Replace dimm
with supported dimm. WBEM EventID: 830. WBEM ProviderName:
FPL_IndicationProvider.Warning8821
The OPTIONS component received a memory allocation error. Probable Cause:
Invalidate NVRAM and reset. WBEM EventID: 831. WBEM ProviderName:
FPL_IndicationProvider.Error8828
A dimm or CPU has been deconfigured or failed testing. Probable Cause: A
deconfigured dimm or cpu has been detected. Examine earlier events to isolate the
problem. WBEM EventID: 832. WBEM ProviderName: FPL_IndicationProvider.Warning8837
The cell will not join the PD. Probable Cause: Broken hardware was detected and
the cell integration policy combined to cause the cell to not join the PD. Recommended
Action: Fix the broken hardware or change the policy using parmgr. If assistance is
required, contact the HP Support Center. WBEM EventID: 833. WBEM ProviderName:
FPL_IndicationProvider.Error8839
The error context in NVM was corrupt. Probable Cause: NVM is corrupted.
Recommended Action: Check for other errors in the system first. Invalidate NVM
and retry boot. Get the latest firmware release. WBEM EventID: 834. WBEM
ProviderName: FPL_IndicationProvider.Warning8842
Firmware encountered a problem trying to initialize. Probable Cause: System firmware
encountered an initialization error. Recommended Action: Examine detailed event
logs to determine the cause. WBEM EventID: 837. WBEM ProviderName:
FPL_IndicationProvider.Error8855
This means that all the cpus in the cell did not show up. Probable Cause: This will
result in the cell stepping independently to collect its logs and resting itself. WBEM
EventID: 838. WBEM ProviderName: FPL_IndicationProvider.Warning8857
This means that all the cells did not rendezvous during the PD rendezvous. Probable
Cause: The cells will reset themselves. WBEM EventID: 839. WBEM ProviderName:
FPL_IndicationProvider.Warning8858
The FW tree sanity check failed during the MCA error processing. Probable Cause:
The cells will independently log errors and reset. WBEM EventID: 840. WBEM
ProviderName: FPL_IndicationProvider.Warning8859
This means that the registry sanity check failed during MCA error handling. Probable
Cause: The cells will independently log errors and reset. WBEM EventID: 841. WBEM
ProviderName: FPL_IndicationProvider.Warning8860
This means that MCA occurred while OS_MCA was performing error recovery.
Probable Cause: The cells will log information and reset. WBEM EventID: 842. WBEM
ProviderName: FPL_IndicationProvider.Warning8861
One of the BT errors occurred that results in abandoning memory dump. Probable
Cause: A machine check has occurred and cells have not rendezvoused. Recommended
Action: Cells will reset themselves. WBEM EventID: 843. WBEM ProviderName:
FPL_IndicationProvider.Warning8864
The firmware tree is not complete and hence there will be no PD rendezvous. Probable
Cause: The cell will log errors and reset. WBEM EventID: 844. WBEM ProviderName:
FPL_IndicationProvider.Warning8865
ACPI configuration mismatch across cells in the partition. Probable Cause: Set the
ACPI configuration parameter again to ensure that all cells have a consistent value.
WBEM EventID: 845. WBEM ProviderName: FPL_IndicationProvider.Error8872
Platform Events 53