You may experience the following problems on a Windows Vista-based or Windows Server 2008-based computer that supports the Intelligent Platform Management Interface (IPMI).

Problem 1
You want the system to perform standard software error-processing when a hardware error generates a nonmaskable interrupt (NMI). To do this, you set the NMICrashDump registry entry to “1” under the following registry subkey:


However, after a nonmaskable interrupt (NMI) is caused by the IPMI Watchdog Timer, and the system restarts, the Operating System Boot System Event Log (SEL) messages are not saved in the baseboard management controller (BMC) as expected. Therefore, your IPMI-compliant management software does not capture the correct computer state. This symptom occurs only if the BMC interrupt is enabled.

Note: When the NMICrashDump registry entry is set to “1,” the system should perform standard software error-processing. For example, the system might display a Stop error message in this situation.

Problem 2
The IPMI driver uses an Add SEL command to capture the log header when it tries to log the following SEL messages:

  • Operating System Stop
  • Operating System Boot
  • Operating System Shutdown

However, if the SEL message is compliant with IPMI event message formats, the IPMI driver should use a Platform Event command to capture log headers instead of an Add SEL command. Add SEL commands should only be used to store OEM-format SEL messages.

Problem 3
When Keyboard Controller Style (KCS) communication interrupts are enabled in the BMC, interrupt service routines (ISRs) may be invoked before the IPMI driver finishes the initialization of BMC interrupts. This behavior may cause unnecessary execution of ISRs.

Note: KCS communication interrupts are enabled when the “byte 1 bit 0” of the BMC Global Enables data is set.

Leave a Reply