CONFIG_HARDLOCKUP_DETECTOR: Detect Hard Lockups

General informations

The Linux kernel configuration item CONFIG_HARDLOCKUP_DETECTOR has multiple definitions:

Detect Hard Lockups found in lib/Kconfig.debug

The configuration item CONFIG_HARDLOCKUP_DETECTOR:

• prompt: Detect Hard Lockups
• type: bool
• depends on: ( CONFIG_DEBUG_KERNEL && ! CONFIG_S390 && ! CONFIG_HARDLOCKUP_DETECTOR_SPARC64 ) && ( CONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF || CONFIG_HAVE_HARDLOCKUP_DETECTOR_BUDDY || CONFIG_HAVE_HARDLOCKUP_DETECTOR_ARCH )
• defined in lib/Kconfig.debug
• found in Linux kernels: 4.13–4.20, 5.0–5.19, 6.0–6.12

Help text

Say Y here to enable the kernel to act as a watchdog to detect hard lockups.

Hardlockups are bugs that cause the CPU to loop in kernel mode for more than 10 seconds, without letting other interrupts have a chance to run. The current stack trace is displayed upon detection and the system will stay locked up.

found in lib/Kconfig.debug

The configuration item CONFIG_HARDLOCKUP_DETECTOR:

• prompt:
• type: bool
• depends on: ( CONFIG_LOCKUP_DETECTOR && ! CONFIG_HAVE_NMI_WATCHDOG ) && ( CONFIG_PERF_EVENTS && CONFIG_HAVE_PERF_EVENTS_NMI )
• defined in lib/Kconfig.debug
• found in Linux kernels: 2.6.36–2.6.39, 3.0–3.19, 4.0–4.12

Help text

(none)

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: