CONFIG_LOCKUP_DETECTOR:

General informations

The Linux kernel configuration item CONFIG_LOCKUP_DETECTOR has multiple definitions:

found in lib/Kconfig.debug

The configuration item CONFIG_LOCKUP_DETECTOR:

• prompt:
• type: bool
• depends on: (none)
• defined in lib/Kconfig.debug
• found in Linux kernels: 4.13–4.20, 5.0–5.19, 6.0–6.12

Help text

(none)

Detect Hard and Soft Lockups found in lib/Kconfig.debug

The configuration item CONFIG_LOCKUP_DETECTOR:

• prompt: Detect Hard and Soft Lockups
• type: bool
• depends on: CONFIG_DEBUG_KERNEL && ! CONFIG_S390
• 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

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

Softlockups are bugs that cause the kernel to loop in kernel mode for more than 20 seconds, without giving other tasks a chance to run. The current stack trace is displayed upon detection and the system will stay locked up.

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.

The overhead should be minimal. A periodic hrtimer runs to generate interrupts and kick the watchdog task every 4 seconds. An NMI is generated every 10 seconds or so to check for hardlockups.

The frequency of hrtimer and NMI events and the soft and hard lockup thresholds can be controlled through the sysctl watchdog_thresh.

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: