SEL Troubleshooting Guide

Miscellaneous Events System Event Log Troubleshooting Guide for Intel® S5500/S3420 Series Server Boards
76 Intel order number G74211-002 Revision 1.1
Byte
Field
Description
15
Event Data 2
[7:4] – Interrupt type
0h = None
1h = SMI
2h = NMI
3h = Messaging Interrupt
Fh = Unspecified
All other = Reserved
[3:0] – Timer use at expiration
0h = Reserved
1h = BIOS FRB2
2h = BIOS/POST
3h = OS Load
4h = SMS/OS
5h = OEM
Fh = Unspecified
All other = Reserved
16
Event Data 3
Not used
Table 77: IPMI Watchdog Sensor Event Trigger Offset – Next Steps
Event Trigger Offset
Description
Next Steps
Hex
Description
00h
Timer expired,
status only
Our server systems support a BMC watchdog timer, which can
check to see whether the OS is still responsive. The timer is
disabled by default, and has to be enabled manually. It then
requires an IPMI-aware utility in the operating system that will
reset the timer before it expires. If the timer does expire, the
BMC can take action if it is configured to do so (reset, power
down, power cycle, or generate a critical interrupt).
If this event is being logged, it is because the BMC has been configured to check the
watchdog timer.
1. Make sure you have support for this in your OS (typically using a third-party
IPMI-aware utility like ipmitool or ipmiutil along with the openipmi driver).
2. If this is the case, then it is likely your OS has hung, and you should investigate
OS event logs to determine what may have caused this.
01h
Hard reset
02h
Power down
03h
Power cycle
08h
Timer interrupt