| /linux/Documentation/fault-injection/ |
| H A D | provoke-crashes.rst | 7 The lkdtm module provides an interface to disrupt (and usually crash)
9 the kernel's exception handling and to test crash dumps obtained using
14 You can select the location of the trigger ("crash point name") and the
15 type of action ("crash point type") either through module arguments when
35 Indicates the action to be taken on hitting the crash point.
38 See the contents of `/sys/kernel/debug/provoke-crash/DIRECT` for
42 Indicates the number of times the crash point is to be hit
47 <debugfs>/provoke-crash/<crashpoint>. E.g.::
50 echo EXCEPTION > /sys/kernel/debug/provoke-crash/INT_HARDWARE_ENTRY
57 cat <(echo WRITE_RO) >/sys/kernel/debug/provoke-crash/DIRECT
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-kexec-kdump | 23 Indicates whether a crash (kdump) kernel is currently
24 loaded into memory. It shows 1 if a crash kernel has been
25 successfully loaded for panic handling, or 0 if no crash
33 Shows the amount of memory reserved for loading the crash
35 crash kernel area defined by the crashkernel= parameter.
46 ELF core header used by the crash (kdump) kernel. It defines
59 to the crash (kdump) kernel. It lists the start and end physical
|
| H A D | sysfs-kernel-fadump | 33 save the crash dump.
40 FADump to save the crash dump in bytes.
|
| H A D | sysfs-class-remoteproc | 32 "crashed" indicates that a problem/crash has been detected on
104 without it, debugging a crash is substantially harder.
|
| H A D | debugfs-driver-dcc | 32 can be read in case of a hardware crash or manual
125 on manual or crash induced triggers. Lists must
|
| /linux/Documentation/driver-api/ |
| H A D | hw-recoverable-errors.rst | 16 crash dump notes, this infrastructure aids post-mortem crash analysis tools in
37 - It is exposed via vmcoreinfo crash dump notes and can be read using tools
38 like `crash`, `drgn`, or other kernel crash analysis utilities.
39 - There is no other way to read these data other than from crash dumps.
|
| /linux/kernel/ |
| H A D | Kconfig.kexec | 3 menu "Kexec and crash features"
98 bool "kernel crash dumps"
105 Generate crash dump after being started by kexec.
106 This should be normally only set in special crash dump kernels
109 a crash by kdump/kexec. The crash dump kernel must be compiled
119 bool "Support saving crash dump to dm-crypt encrypted volume"
137 tristate "Unit Tests for kernel crash dumps" if !KUNIT_ALL_TESTS
141 This option builds KUnit unit tests for kernel crash dumps. The unit
148 bool "Update the crash elfcorehdr on system configuration changes"
153 Enable direct update to the crash elfcorehdr (which contains
[all …]
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-kernel-kexec-kdump | 33 Indicates whether a crash (kdump) kernel is currently
34 loaded into memory. It shows 1 if a crash kernel has been
35 successfully loaded for panic handling, or 0 if no crash
43 Shows the amount of memory reserved for loading the crash
45 crash kernel area defined by the crashkernel= parameter.
56 ELF core header used by the crash (kdump) kernel. It defines
69 to the crash (kdump) kernel. It lists the start and end physical
|
| H A D | sysfs-kernel-fadump_release_mem | 10 save the crash dump.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | firmware-assisted-dump.rst | 66 for boot memory dump preservation in case of a crash.
76 there is crash data available from a previous boot. During
107 userspace support to process crash data. Such kernel needs to
108 preserve previously crash'ed kernel's memory for the subsequent
109 capture kernel boot to process this crash data. Kernel config
111 to ensure that crash data is preserved to process later.
114 CONFIG_OPAL_CORE=y, OPAL memory at the time of crash is also
164 a crash does occur.
166 Since this reserved memory area is used only after the system crash,
191 time of crash. | |
[all …]
|
| H A D | elfnote.rst | 29 being run on a machine with ultravisor, the kernel will probably crash
30 trying to access ultravisor resources. For instance, it may crash in early
|
| /linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | sysrq.rst | 100 ``c`` 将执行系统 crash，如果配置了系统 crashdump，将执行 crashdump。
181 ``crash(c)`` 可以用于手动触发一个 crashdump，当系统卡住时。
182 注意当 crashdump 机制不可用时，这个只是触发一个内核 crash。
|
| /linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | sysrq.rst | 100 ``c`` 將執行系統 crash，如果配置了系統 crashdump，將執行 crashdump。
181 ``crash(c)`` 可以用於手動觸發一個 crashdump，當系統卡住時。
182 注意當 crashdump 機制不可用時，這個只是觸發一個內核 crash。
|
| /linux/Documentation/gpu/ |
| H A D | msm-crash-dump.rst | 26 The kernel time at crash formatted as seconds.microseconds.
35 ID of the GPU that generated the crash formatted as
40 components are in use at the time of crash.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-pcache.rst | 11 high-performance, crash-persistent cache in front of a slower block
24 * *Log-structured write-back* that preserves backend crash-consistency
131 and are themselves crash-safe (CRC).
163 * *System crash* – on attach, the driver replays ksets from *key_tail* to
|
| /linux/Documentation/admin-guide/kdump/ |
| H A D | kdump.rst | 46 before a crash. The physical address of the start of the ELF header is
162 1) Enable "kernel crash dumps" support under "Processor type and
202 "kernel crash dumps" is enabled. A suitable value depends upon
223 1) Enable "Build a kdump crash kernel" support under "Kernel" options::
316 Reserve additional crash kernel memory from CMA. This reservation is
324 to hold the crash kernel and initrd.
353 kernel will automatically locate the crash kernel image within the
493 system crash is triggered. Trigger points are located in panic(),
496 The following conditions will execute a crash trigger point:
508 For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
[all …]
|
| H A D | vmcoreinfo.rst | 11 section and used by user-space tools like crash and makedumpfile to
21 code from which the kernel has been built. For example, crash uses it to
360 User-space tools need to know whether the crash kernel was in 5-level
390 mask. Makedumpfile tools need to know whether the crash kernel was
391 encrypted. If SME is enabled in the first kernel, the crash kernel's
414 crash kernel when converting virtual addresses to physical addresses.
475 It indicates whether the crash kernel supports large physical address
516 vmemmap address translation information is stored in the crash kernel,
|
| /linux/Documentation/trace/ |
| H A D | debugging.rst | 59 crash occurs. This could be from the oops message in printk, or one could
60 use kexec/kdump. But these just show what happened at the time of the crash.
61 It can be very useful in knowing what happened up to the point of the crash.
63 overwrite older events with newer ones. When a crash happens, the content of
64 the ring buffer will be all the events that lead up to the crash.
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | orphan.rst | 7 are still alive because they are open. In case of crash the filesystem has to
11 track the inode as orphan so that in case of crash extra blocks allocated to
|
| /linux/arch/powerpc/kexec/ |
| H A D | Makefile | 12 obj-$(CONFIG_CRASH_DUMP) += crash.o
|
| /linux/fs/proc/ |
| H A D | Kconfig | 55 underlying devices are initialized in crash recovery kernel.
56 Note that the device driver must be present in the crash
79 in the crash dump.
|
| /linux/arch/nios2/ |
| H A D | Kconfig.debug | 12 You should normally say N here, unless you want to debug such a crash.
|
| /linux/tools/testing/selftests/lkdtm/ |
| H A D | stack-entropy.sh | 7 TRIGGER=/sys/kernel/debug/provoke-crash/DIRECT
|
| H A D | run.sh | 10 TRIGGER=/sys/kernel/debug/provoke-crash/DIRECT
|
| /linux/Documentation/arch/s390/ |
| H A D | s390dbf.rst | 14 One purpose of this is to inspect the debug logs after a production system crash
15 in order to analyze the reason for the crash.
267 crash Interface
269 The ``crash`` tool since v5.1.0 has a built-in command
273 a system crash.
278 system and after a system crash is to look at the raw memory
|