HP Integrity rx4640 Windows Integrity Management Agents Reference - Page 113

Probable bug in System Firmware, EFI driver, Instruction or Data Cache Memory I-Cache or

Get HP Integrity rx4640 PDF manuals and user guides View all HP Integrity rx4640 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

10823 10824 10825 10826 10827 10830 10832 10833 10842 10853 10871 10927 Threshold parity errors have been detected in the Instruction or Data Cache Memory (I-Cache or D-Cache). The operating system has recovered from the errors, but this is an abnormally high Contact your HP support representative to check failure rate the processor Threshold corrected platform errors have been detected in the cache portion of the memory for the processor module. The operating system has recovered from the errors, but this is an Contact your HP support representative to check abnormally high failure rate the processor Threshold corrected platform errors have been detected on the system bus for the processor Contact your HP support representative to check module. The operating system has recovered from the processor module or the system bus for the the errors, but this is an abnormally high failure processor if an excessive number of these errors rate are generated Threshold corrected platform errors have been detected on the processor bus for the processor Contact your HP support representative to check module. The operating system has recovered from the processor module or the system bus for the the errors, but this is an abnormally high failure processor if an excessive number of these errors rate are generated Threshold corrected platform errors have been detected in the tag portion of the memory for the processor module. The operating system has Contact your HP support representative to check recovered from the errors, but this is an the processor module if an excessive number of abnormally high failure rate. these errors are generated fPars-mode EFI variable is set to enable fPars operation but no fPars are actually enabled to boot. So the server boots in hard partition mode. This is a configuration usage problem, possibly a user error such as might occur if a previously bootable config was made unbootable by setting the enabled fPar existence variables, e.g., 'fPar0', Use the configuration tool released with the OS 'fPar1', ... 'fParN' to 0x00 (disabled) and then to disable fPars mode or to configure and enable rebooting bootable fPars. An fPar was directed to reset using the ESIT DirectedfParResetAndMigrate() service but the Use the configuration tool released with the OS target (recipient) fPar of the resources is in a state to correctly assign these resources to an fPar and that cannot receive ownership of these resources. reset that fPar so they will be claimed. Firmware could not store to the NVRAM holding Reset the server, restore factory default NVRAM the EFI preferred-bsp variable and reconfigure soft partitions. System firmware was unable to write a fabric hardware register. Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric Probable bug in System Firmware, EFI driver, EFI app or OS loader (prior to OS launch). The event data field contains the IVT offset applicable to the interrupt. See table 5-7 (Interruption Vector Provide console log containing register dump to Table) in the Intel ASDM Volume 2. HP Customer Engineer. Disable rope in non-mca path, error exit in MCA SBA call to LBA SetDeviceMask method fails. path. The LBA component detected a card in a PCI slot, but got no response from config register requests to the card. Reseat or replace the PCI card. Platform Events - Table 2 (Windows System Log Event ID, Cause, Recommended Action) 113

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
Contact your HP support representative to check
the processor
Threshold parity errors have been detected in the
Instruction or Data Cache Memory (I-Cache or
D-Cache). The operating system has recovered
from the errors, but this is an abnormally high
failure rate
10823
Contact your HP support representative to check
the processor
Threshold corrected platform errors have been
detected in the cache portion of the memory for
the processor module. The operating system has
recovered from the errors, but this is an
abnormally high failure rate
10824
Contact your HP support representative to check
the processor module or the system bus for the
processor if an excessive number of these errors
are generated
Threshold corrected platform errors have been
detected on the system bus for the processor
module. The operating system has recovered from
the errors, but this is an abnormally high failure
rate
10825
Contact your HP support representative to check
the processor module or the system bus for the
processor if an excessive number of these errors
are generated
Threshold corrected platform errors have been
detected on the processor bus for the processor
module. The operating system has recovered from
the errors, but this is an abnormally high failure
rate
10826
Contact your HP support representative to check
the processor module if an excessive number of
these errors are generated
Threshold corrected platform errors have been
detected in the tag portion of the memory for the
processor module. The operating system has
recovered from the errors, but this is an
abnormally high failure rate.
10827
Use the configuration tool released with the OS
to disable fPars mode or to configure and enable
bootable fPars.
fPars-mode EFI variable is set to enable fPars
operation but no fPars are actually enabled to
boot. So the server boots in hard partition mode.
This is a configuration usage problem, possibly
a user error such as might occur if a previously
bootable config was made unbootable by setting
the enabled fPar existence variables, e.g., 'fPar0',
'fPar1', ... 'fParN' to 0x00 (disabled) and then
rebooting
10830
Use the configuration tool released with the OS
to correctly assign these resources to an fPar and
reset that fPar so they will be claimed.
An fPar was directed to reset using the ESIT
DirectedfParResetAndMigrate() service but the
target (recipient) fPar of the resources is in a state
that cannot receive ownership of these resources.
10832
Reset the server, restore factory default NVRAM
and reconfigure soft partitions.
Firmware could not store to the NVRAM holding
the EFI preferred-bsp variable
10833
Capture IPMI event logs, look for additional
errors. Contact your HP Support Representative
to analyze the fabric
System firmware was unable to write a fabric
hardware register.
10842
Provide console log containing register dump to
HP Customer Engineer.
Probable bug in System Firmware, EFI driver,
EFI app or OS loader (prior to OS launch). The
event data field contains the IVT offset applicable
to the interrupt. See table 5-7 (Interruption Vector
Table) in the Intel ASDM Volume 2.
10853
Disable rope in non-mca path, error exit in MCA
path.
SBA call to LBA SetDeviceMask method fails.
10871
Reseat or replace the PCI card.
The LBA component detected a card in a PCI slot,
but got no response from config register requests
to the card.
10927
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action)
113