SEL Troubleshooting Guide

Miscellaneous Events
System Event Log Troubleshooting Guide for PCSD Platforms Based on Intel
®
Xeon
®
Processor E5 4600/2600/2400/1600/1400 Product Families
102 Intel order number G90620-003 Revision 1.2
Byt
e
Field
Description
02h
Power down
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).
using a third-party IPMI-aware utility such as ipmitool or
ipmiutil along with the OpenIPMI driver).
2. If this is the case, it is likely your OS has hung, and you need
to investigate OS event logs to determine what may have
caused this.
03h
Power cycle
08h
Timer interrupt
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 78: 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
If this event is being logged, it is because the BMC has been
configured to check the watchdog timer.