Intel® Server System S7000FC4UR TPS BIOS Error Handling
Revision 1.0
229
Byte Field IPMI Description BIOS Implementation
Bit[7:4] = Channel number
Bit[3:2] = reserved (00b)
Bit[1:0] = IPMB device LUN or
00h
001b = Event Data format revision
1
Bit[0]
1b = System Software ID
Byte 9 = 0x00:
Bit[7:4] = 0h (channel = system
interface)
Bit[3:2] = 00b
Bit[1:0] = 00b (Byte 8 is SSID)
10 EvM Rev Event Message format version The BIOS sends this to the BMC:
0x04 = as per the Intelligent Platform
Management Interface Specification,
Version 2.0, Intel Corporation requirement
13 Event Dir |
Event Type
Bit[7] = Event Direction
0b = assertion event
1b = deassertion event
Bit[6:0] = Event Type Code
See the Intelligent Platform
Management Interface
Specification, Version 2.0,
Table 42-1
The BIOS sends this to the BMC:
Bit[7] = 0b – Assertion event
Bit[6:0] = 0x6F – sensor specific type
code
The BIOS logs all events using the sensor-
specific type code category and discrete
event trigger/sensor class.
SEL formats for system errors are created using pre-defined formats for specific the Intelligent
Platform Management Interface Specification, Version 2.0-compliant Sensor Types. The
following list describes the various the Intelligent Platform Management Interface Specification,
Version 2.0-compliant Sensor Types used to report different types of system errors:
IPMI Memory Sensor Events
- Memory ECC Correctable Errors
- Memory ECC Uncorrectable Errors
- Memory Correctable ECC Memory Error Logging Limit Reached
IPMI System Firmware Progress Events
- System Firmware Error (POST Error) on FRB-2 events
IPMI Event Logging Disabled Events
- Correctable Memory Error Logging Disabled
IPMI Critical Interrupt Sensor Events
- PCI Bus Legacy PERR events
- PCI Bus Legacy SERR events
Software NMI Events
Note: Technically, the FRB-2 event is not logged by the SMI handler, but it uses the same
Generator ID range as memory errors. This makes it easier for the BIOS and the event log
parser code.