Specifications

QSSC-S4R Technical Product Specification BIOS Error Handling
241
The BMC logs this event in the SEL, and the system restarts and goes through POST. There are two differences
between this case and the “OS Load tim
er ” case – first, the Timer Purpose in the BMC SEL Event is different, and
secondly, there is no POST Error Code generated by BIOS during the reboot.
This is not
a BIOS-related event, although it logs a BMC SEL Event that is very similar to the FRB-2 and OS Load
watchdog timer timeouts in which the BIOS does
participate. It is included in this discussion in order to differentiate
between it and BIOS-related timeout events.
For an OS/SMS Watchdog timeout, the timer purpose in the BMC event is “OS/SMS”, and there is no POST Error
Code logged.
Table 165, OS/SMS Watchdog Timeout SEL Events
Generator ID Sensor
Type Code
Sensor
number
T
y
pe code E
v
ent Data1
Bytes Used
+ Offset
E
v
ent Data2 E
v
ent Data3
20h
(BMC
Firmware)
23h
(Watchdog
Timer2)
03h
(Watchdog)
6Fh
(Sensor
Specific Offset)
C1h
(Data2 has
Sensor Specific
Code;
Offset = Hard
Reset)
04h
(Interrupt =
None;
Purpose =
OS/SMS)
FFh
(N/A)
21.2.3.7 Boot Event
The BIOS downloads the system date and time to the BMC during POST and logs a boot event. Software that parses
the event log should not treat the boot event as an error.
21.2.3.8 Timestamp Clock Event
The BIOS and BMC maintain their own real-time clock (RTC). The BIOS RTC gets updated by the user in the setup or
the OS may update the RTC. As such, the BIOS must synchronize its time with the BMC. This is accomplished via
two mechanisms:
x During the DXE phase of the POST process, the BIOS sends the EFI_STORAGE_SET_SEL_TIME (0x49)
command to the BMC after establishing IPMI communications.
x During sleep state transitions other than S0, the BIOS synchronizes the time.
21.2.4 Logging Format Conventions
The BIOS complies with the logging format defined in the IPMI Specification. IPMI specifies the usage of all but three
bytes in each event log entry. Those three bytes are Event Data 1, Event Data 2, and Event Data 3. An event
generator can specify that these bytes contain OEM-
specified values. The system BIOS uses these three bytes to record additional information about the error.
The Generator ID identifies the source of the SEL event, so it is important in interpreting SEL
logs. BIOS uses more than one GID, and there are other sources in the system, especially the
BMC. Common GIDs in the Intel
®
Boxboro-EX Server Board family are:
x 01h – BIOS POST for RAS Configuration/State, Timestamp Synch, OS Boot Event
x 03h – This GID is reserved for Intel validation use
x 33h – BIOS SMI Handler and BIOS POST Error Codes
x 20h – BMC Firmware
x 2Ch – ME Firmware
x 41h – Server Management Software
x C0h – HSC Firmware
As an example, for an FRB2 event, the SEL record contains the following:
Table 166. Example – SEL Log Data For An FRB-2 Error Event
Field IPMI De
f
inition BIOS Implementation example
Generator ID 7:1 System software ID or IPMB
slave address.
1 = ID is System Software ID
33h