Table 85. Event Data Field Contents For Pci Errors; Table 86. Frb-2 Error Events - Intel SE7520AF2 Technical Product Specification

Error Reporting and Handling
Event Data 1 7:6 00 = unspecified byte 2;
code in byte 2.
5:4 00 = unspecified byte 3;
code in byte 3 (BIOS will not use encodings
01 and 11 for errors covered by this
document.)
3:0 Offset from Event Trigger for discrete
event state.
Event Data 2 7:0 OEM code 2 or unspecified
Event Data 3 7:0 OEM code 3 or unspecified.
7.2.2.8 Examples of Event Data Field Contents for PCI Errors
PCI PERR, failing device is not known
PCI SERR, failing device is not known
PCI PERR, device 3, function 1 on PCI bus 5 reported the error
An unknown device on PCI bus 0 reported the SERR
7.2.2.9 FRB-2 Error Events
Field
Generator ID 7:1 System software ID or IPMB
address. 1=ID is system software ID; 0=ID is
IPMB slave address.
Sensor Type See Table 30.3 in Intelligent Platform
Management Interface Specification, v1.5.
196

Table 85. Event Data Field Contents for PCI Errors

Error Type

Table 86. FRB-2 Error Events

IPMI Definition
Intel order number C77866-003
Intel® Server Board SE7520AF2 TPS
10 = OEM Follow IPMI definition.
If either of the two data bytes following this do not have
10 = OEM 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 Intelligent Platform
Management Interface Specification, 3:0 is 04 for PCI
PERR and 05 for PCI SERR.
For format rev 0, if this byte is specified, it contains the
PCI bus number on which the failing device resides. If
the source of the PCI error cannot be determined, this
byte contains 0xff and the event data 1 byte indicates
that byte 2 is unspecified.
For format rev 0, if this byte is specified, it contains the
PCI device/function address in the standard format:
7:3 Device number of the failing PCI device
2:0 PCI function number. Will always contain a
zero if the device is not a multifunction
If the source of the PCI error cannot be determined, this
byte contains 0xff and the event data 1 byte indicates
that byte 3 is unspecified.
Event Data 1
04
05
0xA4
0x85
BIOS Specific Implementation
slave 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
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.
0x7 for processor related errors
Event Data 2 Event Data 3
0xFF 0xFF
0xFF 0xFF
0x05 0x19
(Bits 7:3 = 03
Bits 2:0 = 01)
0x00 0xFF
Revision 1.2
device.
0. All