Trigger a Kernel Panic on AWS EC2 Nitro Instances by NMI method.

Solution Verified - Updated

Environment

  • Red Hat Enterprise Linux
  • AWS Nitro Platform(C,M,R,T,Z series)
    e.g- C5, C5d, C5n, i3.metal, I3en, M5, M5a, M5ad, M5d, p3dn.24xlarge, R5, R5a, R5ad, R5d, T3, T3a, and Z1d, except A1 (Arm-based)

Issue

  • Unable to generate a Vmcore of the hung system on the RHEL server resides on the AWS Nitro platform.
  • How to send a non-maskable interrupt (NMI) on the RHEL Nitro Instance on AWS platform.

Resolution

  • To handle NMIs properly and initiate kdump, perform either of the following:
    • Set the following parameter in /etc/sysctl.conf:
kernel.panic_on_io_nmi = 1
kernel.panic_on_unrecovered_nmi = 1
kernel.unknown_nmi_panic = 1

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

 

SBR
Components
Category

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.