EC2 OS/Kernel Symptom Diagnostic Troubleshooter (Part 4)
Use the interactive troubleshooter below to identify your EC2 OS/kernel symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 5 | ENA packets dropped because the PPS allowance limit was exceeded | pps_allowance_exceeded: N | The volume of network traffic exceeded the packets per second (PPS) allowance limit for the specific instance type. | N/A |
| 6 | Connectivity problems due to predictable network interface names breaking eth0 | systemd-208-11.el7_0.2.x86_64 | Systems using systemd or udev versions 197 or greater can rename Ethernet devices and do not guarantee a single interface is named eth0. | sudo sed -i '/^GRUB\_CMDLINE\_LINUX/s/\"$/\ net\.ifnames\=0\"/' /etc/default/grub |
| 7 | Interminable loop condition at startup due to runaway modprobe | request_module: runaway loop modprobe binfmt-464c | Using an unstable or old Linux kernel (for example, 2.6.16-xenU) causes an interminable loop condition at startup. | N/A |
| 8 | Instance has stopped responding, requiring magic SysRq commands | [ 1169.389495] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) | The instance has stopped responding to normal shell inputs, requiring direct kernel commands to troubleshoot via the serial console. | sudo sysctl -w kernel.sysrq=1 |