Kdump fails to complete due to Asserting NMI on System Error
Environment
- Red Hat Enterprise Linux 5
- Red Hat Enterprise Linux 6
- Cisco Blade Server
Issue
- Kdump begins to create a vmcore when manually triggered; however, the process is interrupted 60 seconds after it begins and no core file is created.
Resolution
- Disable the BIOS option,
Assert NMI on System Errorto prevent the server from sending a NMI which will force a NMI from the kdump kernel.
Root Cause
- The server had a BIOS option,
Assert NMI on System Error, to reboot automatically when the system crashed.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments