HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 15

was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control, INIT, TOC

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

Page 15 highlights

745 Error TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName: SEL02_IndicationProvider. 746 Error INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 170. WBEM ProviderName: SEL02_IndicationProvider. 746 Error INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 170. WBEM ProviderName: SEL02_IndicationProvider. 747 Warning PCI system error detected. Probable Cause: An I/O device (or host bridge) detected an internal error. OR An I/O device (or host bridge) detected a bus error. Recommended Action: For an I/O device failure, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 172. WBEM ProviderName: SEL02_IndicationProvider. 747 Warning PCI system error detected. Probable Cause: An I/O device (or host bridge) detected an internal error. OR An I/O device (or host bridge) detected a bus error. Recommended Action: For an I/O device failure, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 172. WBEM ProviderName: SEL02_IndicationProvider. 748 Error OS run-time critical shutdown. Probable Cause: The OS caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: 175. WBEM ProviderName: SEL02_IndicationProvider. 748 Error OS run-time critical shutdown. Probable Cause: The OS caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: 175. WBEM ProviderName: SEL02_IndicationProvider. 749 Warning ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been powered OFF with a hard power-down. Recommended Action: HP recommends that when you powered down the system you use the normal shutdown procedure to properly shut down the operating system. Otherwise, data-loss and/or hardware failure can occur. WBEM EventID: 176. WBEM ProviderName: SEL02_IndicationProvider. 749 Warning ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been powered OFF with a hard power-down. Recommended Action: HP recommends that when you powered down the system you use the normal shutdown procedure to properly shut down the operating system. Otherwise, data-loss and/or hardware failure can occur. WBEM EventID: 176. WBEM ProviderName: SEL02_IndicationProvider. 751 Warning PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Recommended Action: For an I/O bus parity error, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 171. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 15

  • 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
TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected
that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer
Of Control (TOC) button was pressed or the interrupt was initiated remotely. The
system will reboot after the interrupt processing is finished. Recommended Action:
If this is unexpected behavior, then check logs for events that would have caused an
INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName:
SEL02_IndicationProvider.
Error
745
INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there
was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control
(TOC) button was pressed or the interrupt was initiated remotely. The system will
reboot after the interrupt processing is finished. Recommended Action: If this is
unexpected behavior, then check logs for events that would have caused an INIT,
TOC, or RESET. WBEM EventID: 170. WBEM ProviderName:
SEL02_IndicationProvider.
Error
746
INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there
was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control
(TOC) button was pressed or the interrupt was initiated remotely. The system will
reboot after the interrupt processing is finished. Recommended Action: If this is
unexpected behavior, then check logs for events that would have caused an INIT,
TOC, or RESET. WBEM EventID: 170. WBEM ProviderName:
SEL02_IndicationProvider.
Error
746
PCI system error detected. Probable Cause: An I/O device (or host bridge) detected
an internal error. OR An I/O device (or host bridge) detected a bus error.
Recommended Action: For an I/O device failure, consult the error logs for additional
information. Determine and replace the failed I/O device. For an I/O host bridge
failure, contact your HP representative to check the I/O host bridge. WBEM EventID:
172. WBEM ProviderName: SEL02_IndicationProvider.
Warning
747
PCI system error detected. Probable Cause: An I/O device (or host bridge) detected
an internal error. OR An I/O device (or host bridge) detected a bus error.
Recommended Action: For an I/O device failure, consult the error logs for additional
information. Determine and replace the failed I/O device. For an I/O host bridge
failure, contact your HP representative to check the I/O host bridge. WBEM EventID:
172. WBEM ProviderName: SEL02_IndicationProvider.
Warning
747
OS run-time critical shutdown. Probable Cause: The OS caused the system to shut
down. Recommended Action: Look at OS logs and crash data to determine why the
system shut down. WBEM EventID: 175. WBEM ProviderName:
SEL02_IndicationProvider.
Error
748
OS run-time critical shutdown. Probable Cause: The OS caused the system to shut
down. Recommended Action: Look at OS logs and crash data to determine why the
system shut down. WBEM EventID: 175. WBEM ProviderName:
SEL02_IndicationProvider.
Error
748
ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been
powered OFF with a hard power-down. Recommended Action: HP recommends
that when you powered down the system you use the normal shutdown procedure
to properly shut down the operating system. Otherwise, data-loss and/or hardware
failure can occur. WBEM EventID: 176. WBEM ProviderName:
SEL02_IndicationProvider.
Warning
749
ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been
powered OFF with a hard power-down. Recommended Action: HP recommends
that when you powered down the system you use the normal shutdown procedure
to properly shut down the operating system. Otherwise, data-loss and/or hardware
failure can occur. WBEM EventID: 176. WBEM ProviderName:
SEL02_IndicationProvider.
Warning
749
PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a
bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and
received a parity error response from the target. Recommended Action: For an I/O
bus parity error, consult the error logs for additional information. Determine and
replace the failed I/O device. For an I/O host bridge failure, contact your HP
representative to check the I/O host bridge. WBEM EventID: 171. WBEM
ProviderName: SEL02_IndicationProvider.
Warning
751
Platform Events
15