CONFIG_KDB_CONTINUE_CATASTROPHIC: KDB: continue after catastrophic errors

General informations

The Linux kernel configuration item CONFIG_KDB_CONTINUE_CATASTROPHIC:

• prompt: KDB: continue after catastrophic errors
• type: int
• depends on: CONFIG_KGDB_KDB
• defined in lib/Kconfig.kgdb
• found in Linux kernels: 3.9–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Help text

This integer controls the behaviour of kdb when the kernel gets a catastrophic error, i.e. for a panic or oops. When KDB is active and a catastrophic error occurs, nothing extra will happen until you type 'go'. KDB_CONTINUE_CATASTROPHIC == 0 (default). The first time you type 'go', you will be warned by kdb. The secend time you type 'go', KDB tries to continue. No guarantees that the kernel is still usable in this situation. KDB_CONTINUE_CATASTROPHIC == 1. KDB tries to continue. No guarantees that the kernel is still usable in this situation. KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot. If you are not sure, say 0.

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: