
Intel® Server Board SE7520AF2 TPS
Error Reporting and Handling
Revision 1.2
195
Intel order number C77866-003
Field
IPMI definition
BIOS-Specific Implementation
Event Data 1
7:6 00 = unspecified byte 2
10 = OEM code in byte 2.
5:4 00 = unspecified byte 3
10 = OEM code in byte 3. (The
BIOS will not use encodings 01 and
11 for errors coveredby this
document.).
3:0 Offset from Event Trigger for
discrete event state.
Follow IPMI definition. If either of the two data bytes
following this do not have any data, that byte should be set
to 0xff, and the appropriate filed in event data 1 should
indicate that that it is unspecified.
According to Table 30.3 in the Intelligent Platform
Management Specification, Version 1.5, 3:0 is 0 for single
bit error and 1 for multi-bit error.
Event Data 2
7:0 OEM code 2 or unspecified.
For format rev 0, if this byte is specified,
7:6 Zero-based memory card number. Matches the
number of type 16 entry in SMBIOS table. For example,
card 0 corresponds to the first type 16 entry in SMBIOS
tables. If all DIMMs are onboard, this field will always be
0.5:0 zero-based DIMM number on the card.
DIMM 0 corresponds to the first type 17 record in SMBIOS
tables for that memory card.
Event Data 3
7:0 OEM code 3 or unspecified.
If format rev is 0 and if this byte is specified, syndrome
byte.
Table 83. Examples of Event Data Field Contents for Memory Errors
Error Type
Event Data 1
Event Data 2
Event Data 3
Single bit error; no information about the error is available.
00
0xFF
0xFf
Multi bit memory error, failed DIMM is the fifth DIMM on the
second memory card.
0x81 0x44
(Bits 7:6 = 01
Bits 5:0 = 04)
0xFF
Single bit error. Syndrome is 0x54, DIMM location is not known.
0x20
0xFF
0x54
Multi-bit error, Syndrome byte is 0x1c. DIMMs are onboard, and
the second DIMM has failed.
0xA1 0x01
(Bits 7:6 = 00
Bits 5:0 = 01)
0x1C
Table 84. PCI error events
Field
IPMI Definition
BIOS Specific Implementation
Generator ID
7:1 System software ID or IPMB slave
address. 1=ID is system software ID; 0=ID is
IPMB slave address.
7:4 0x3 for system BIOS
3:1 0 Format revision, Revision of the data
format for OEM data bytes 2 and 3, For this
revision of the specification, set this field to 0. All other
revisions are reserved for now.
0 1=ID is system software ID
As a result, the generator ID byte will start from 0x31
and go up to 0x3f, in increments of 2 for events logged
by the BIOS.
Sensor Type
See Table 30.3 in
Intelligent Platform
Management Interface Specification
0x13 for critical interrupt
Sensor number
Number of sensor that generated this event
Unique value for each type of event because IPMI
specification requires it that way. This field has no other
significance. Should not be displayed to the end user if
the event is logged by BIOS.
Type code
0x6F if event offsets are specific to the sensor 0x6F