Fp (nmi) interrupt, Next steps, Button press events – Kontron S5500 SEL Troubleshooting User Manual
Page 89: 3 button press events

Chassis subsystem
System Event Log Troubleshooting Guide for Intel® S5500/S3420 series Server Boards
80
Intel order number G74211-001
Revision 1.0
Byte
Field
Description
13
Event Direction and
Event Type
[7] Event direction
0b = Assertion Event
1b = Deassertion Event
[6:0] Event Type = 6Fh (Sensor Specific)
14
Event Data 1
[7:6]
– 00b = Unspecified Event Data 2
[5:4]
– 00b = Unspecified Event Data 3
[3:0]
– Event Trigger Offset =0
15
Event Data 2
Not used.
16
Event Data 3
Not used.
12.2.1
FP (NMI) Interrupt – Next Steps
The purpose of this button is for diagnosing software issues
– when a critical interrupt is generated the OS typically saves a memory dump.
This allows for exact analysis of what is going on in system memory, which can be useful for software developers, or for troubleshooting OS,
software and driver issues.
If this button was not actually pressed, you should ensure there is no physical fault with the front panel.
This event only gets logged if a user pressed the NMI button, and although it causes the OS to crash, is not an error.
12.3 Button Press Events
The BMC logs when the front panel power and reset buttons get pressed. This is purely for informational purposes and these events do not
indicate errors.
Table 75: Button Press Events Sensor Typical Characteristics
Byte
Field
Description
11
Sensor Type
14h = Button / Switch
12
Sensor Number
09h