diff options
-rw-r--r-- | lib/Kconfig.kgdb | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb index 43cb93fa2651..960fa2ecd6e0 100644 --- a/lib/Kconfig.kgdb +++ b/lib/Kconfig.kgdb | |||
@@ -79,4 +79,22 @@ config KDB_KEYBOARD | |||
79 | help | 79 | help |
80 | KDB can use a PS/2 type keyboard for an input device | 80 | KDB can use a PS/2 type keyboard for an input device |
81 | 81 | ||
82 | config KDB_CONTINUE_CATASTROPHIC | ||
83 | int "KDB: continue after catastrophic errors" | ||
84 | depends on KGDB_KDB | ||
85 | default "0" | ||
86 | help | ||
87 | This integer controls the behaviour of kdb when the kernel gets a | ||
88 | catastrophic error, i.e. for a panic or oops. | ||
89 | When KDB is active and a catastrophic error occurs, nothing extra | ||
90 | will happen until you type 'go'. | ||
91 | CONFIG_KDB_CONTINUE_CATASTROPHIC == 0 (default). The first time | ||
92 | you type 'go', you will be warned by kdb. The secend time you type | ||
93 | 'go', KDB tries to continue. No guarantees that the | ||
94 | kernel is still usable in this situation. | ||
95 | CONFIG_KDB_CONTINUE_CATASTROPHIC == 1. KDB tries to continue. | ||
96 | No guarantees that the kernel is still usable in this situation. | ||
97 | CONFIG_KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot. | ||
98 | If you are not sure, say 0. | ||
99 | |||
82 | endif # KGDB | 100 | endif # KGDB |