Linux 7.5 Adds Tool to Test Kernel Memory Panic

The hwpoison-panic tool deliberately triggers a memory failure to crash the Linux kernel and verify panic-handling behavior.

Updated on Nov. 13, 2026 in Computers

Isometric editorial illustration of bare green memory modules in an open server chassis, one module marked by a warm amber fault accent and a severed trace branching away.
Linux 7.5 adds hwpoison-panic, a kernel tool that deliberately triggers a memory failure to confirm the system panics as configured when unrecoverable memory errors occur. AI Illustration. Upload story photo >

The Linux 7.5 source tree introduces hwpoison-panic, a tool that deliberately induces a memory failure to crash the kernel. It is designed to test whether vm.panic_on_unrecoverable_memory_failure triggers an immediate kernel panic.

Why it matters

Continuing to run a system after hardware-related memory failure can corrupt data or cause unpredictable behavior. The tool gives kernel developers a controlled way to verify that the system halts as intended in such cases.

The tool picks a kernel-owned page frame number, writes its physical address to hard_offline_page, and requires the --yes-panic-my-kernel argument to run. It lives in tools/mm rather than selftests/mm, and the source does not detail performance or hardware requirements.

The players

Linux kernel

The Linux kernel is the core operating system component, developed as open-source software and used across servers, desktops, and embedded devices worldwide.

The details

A user runs hwpoison-panic from the command line and selects a target page type with -k. The tool simulates a memory failure at the chosen physical address, which forces a kernel panic and tests the vm.panic_on_unrecoverable_memory_failure setting.

Timeline

  1. Introduced in the Linux 7.5 source tree; the extraction does not give an exact release date.

The Tech Race

The hwpoison-panic tool tests the vm.panic_on_unrecoverable_memory_failure kernel setting, which governs how Linux responds to unrecoverable memory errors. Adding a dedicated test lets maintainers confirm that this safeguard behaves as designed across kernel releases.

Users running Linux systems get a documented way to confirm that memory-failure handling halts the machine instead of continuing. Developers and administrators who depend on predictable crash behavior can use the tool to validate their configuration.

The takeaway

Verifying that a system stops safely after a memory failure protects data integrity. Administrators who rely on kernel panic behavior should check the vm.panic_on_unrecoverable_memory_failure setting on their systems.

Further reading

For related coverage of system software, browse the Computers section.

Source note: This article includes information reported by The How-To Geek.