Home
last modified time | relevance | path

Searched refs:crash (Results 1 – 25 of 79) sorted by relevance

1234

/linux/Documentation/fault-injection/
H A Dprovoke-crashes.rst7 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 Dsysfs-kernel-kexec-kdump23 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 Dsysfs-class-remoteproc32 "crashed" indicates that a problem/crash has been detected on
104 without it, debugging a crash is substantially harder.
H A Ddebugfs-driver-dcc32 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 Dhw-recoverable-errors.rst16 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/Documentation/ABI/obsolete/
H A Dsysfs-kernel-kexec-kdump33 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 Dsysfs-kernel-fadump_release_mem10 save the crash dump.
/linux/kernel/
H A DKconfig.kexec3 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/gpu/
H A Dmsm-crash-dump.rst26 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/arch/powerpc/
H A Delfnote.rst29 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/filesystems/ext4/
H A Dorphan.rst7 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 DMakefile12 obj-$(CONFIG_CRASH_DUMP) += crash.o
/linux/arch/nios2/
H A DKconfig.debug12 You should normally say N here, unless you want to debug such a crash.
/linux/tools/testing/selftests/lkdtm/
H A Dstack-entropy.sh7 TRIGGER=/sys/kernel/debug/provoke-crash/DIRECT
H A Drun.sh10 TRIGGER=/sys/kernel/debug/provoke-crash/DIRECT
/linux/fs/proc/
H A DKconfig55 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/m68k/
H A DKconfig.debug24 You should normally say N here, unless you want to debug such a crash.
/linux/Documentation/admin-guide/LSM/
H A DYama.rst38 between a debugging process and its inferior (crash handlers, etc),
43 Firefox's crash handlers, and by Wine for allowing only Wine processes
/linux/Documentation/ABI/removed/
H A Dsysfs-mce23 better uptime with the risk of a crash or even corruption
/linux/arch/arm64/kernel/
H A Dsmp.c898 bool crash = IS_ENABLED(CONFIG_KEXEC_CORE) && crash_stop; in arm64_nmi_cpu_stop() local
911 if (crash && regs) in arm64_nmi_cpu_stop()
920 if (crash && die_on_crash) in arm64_nmi_cpu_stop()
/linux/Documentation/ABI/stable/
H A Dvdso17 within their rights to crash.) In addition, if you pass a bad
/linux/Documentation/driver-api/usb/
H A Dpersist.rst44 instantly crash.
65 suspended -- but it will crash as soon as it wakes up, which isn't
161 data corruption and to crash your system. You'll have no one to blame
/linux/Documentation/arch/x86/
H A Dpti.rst43 that any missed kernel->user CR3 switch will immediately crash
143 themselves to crash, but they should never crash the kernel.
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-log.rst36 will not survive a reboot or crash, but there may be a small boost in
/linux/arch/mips/kernel/
H A DMakefile93 obj-$(CONFIG_KEXEC_CORE) += machine_kexec.o relocate_kernel.o crash.o

1234