Intel SE7525GP2 Product Specification - Page 138

Error Reporting and Handling

Page 138 highlights

Error Reporting and Handling Intel® Server Boards SE7320SP2 and SE7525GP2 6. Error Reporting and Handling The BIOS indicates the current testing phase during POST by writing a hex code to I/O location 80h. If errors are encountered, error messages or codes are either displayed to the video screen, or if an error has occurred prior to video initialization, errors are reported through a series of audio beep codes. The error codes are defined by Intel and whenever possible are backward compatible with error codes used on earlier platforms. 6.1 Error Logging This section defines how errors are handled by the system BIOS. Also discussed is the role of the BIOS in error handling and the interaction between the BIOS, platform hardware, and server management firmware with regard to error handling. In addition, error-logging techniques are described and beep codes for errors are defined. 6.1.1 Error Sources and Types One of the major requirements of server management is to correctly and consistently handle system errors. System errors can be categorized as follows: ƒ PCI bus ƒ Memory multi-bit errors (single-bit errors are not logged) ƒ Sensors ƒ Processor internal errors, bus/address errors, thermal trip errors, temperatures and voltages, and GTL voltage levels ƒ Errors detected during POST, logged as POST errors Sensors are managed by the mBMC. The mBMC is capable of receiving event messages from individual sensors and logging system events. 6.1.2 SMI Handler The SMI handler handles and logs system-level events that are not visible to the server management firmware. If SEL error logging is disabled in the BIOS Setup utility, no SMI signals are generated on system errors. If error logging is enabled, the SMI handler preprocesses all system errors, even those that are normally considered to generate an NMI. The SMI handler sends a command to the BMC to log the event and provides the data to be logged. For example, The BIOS programs the hardware to generate an SMI on a single-bit memory error and logs the location of the failed DIMM in the system event log. 6.1.2.1 PCI Bus Error The PCI bus defines two error pins, PERR# and SERR#, for reporting PCI parity errors and system errors, respectively. The BIOS can be instructed to enable or disable reporting the 126 Revision 4.0

  • 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
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184

Error Reporting and Handling
IntelĀ® Server Boards SE7320SP2 and SE7525GP2
Revision 4.0
126
6.
Error Reporting and Handling
The BIOS indicates the current testing phase during POST by writing a hex code to I/O location
80h. If errors are encountered, error messages or codes are either displayed to the video
screen, or if an error has occurred prior to video initialization, errors are reported through a
series of audio beep codes.
The error codes are defined by Intel and whenever possible are backward compatible with error
codes used on earlier platforms.
6.1
Error Logging
This section defines how errors are handled by the system BIOS. Also discussed is the role of
the BIOS in error handling and the interaction between the BIOS, platform hardware, and server
management firmware with regard to error handling. In addition, error-logging techniques are
described and beep codes for errors are defined.
6.1.1
Error Sources and Types
One of the major requirements of server management is to correctly and consistently handle
system errors. System errors can be categorized as follows:
PCI bus
Memory multi-bit errors (single-bit errors are not logged)
Sensors
Processor internal errors, bus/address errors, thermal trip errors, temperatures and
voltages, and GTL voltage levels
Errors detected during POST, logged as POST errors
Sensors are managed by the mBMC. The mBMC is capable of receiving event messages from
individual sensors and logging system events.
6.1.2
SMI Handler
The SMI handler handles and logs system-level events that are not visible to the server
management firmware. If SEL error logging is disabled in the BIOS Setup utility, no SMI signals
are generated on system errors. If error logging is enabled, the SMI handler preprocesses all
system errors, even those that are normally considered to generate an NMI.
The SMI handler sends a command to the BMC to log the event and provides the data to be
logged. For example, The BIOS programs the hardware to generate an SMI on a single-bit
memory error and logs the location of the failed DIMM in the system event log.
6.1.2.1
PCI Bus Error
The PCI bus defines two error pins, PERR# and SERR#, for reporting PCI parity errors and
system errors, respectively. The BIOS can be instructed to enable or disable reporting the