Searched refs:crash (Results 1 – 25 of 121) sorted by relevance
12345
| /Linux-v5.10/Documentation/fault-injection/ |
| 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
36 Indicates the action to be taken on hitting the crash point.
39 See the contents of `/sys/kernel/debug/provoke-crash/DIRECT` for
43 Indicates the number of times the crash point is to be hit
48 <debugfs>/provoke-crash/<crashpoint>. E.g.::
51 echo EXCEPTION > /sys/kernel/debug/provoke-crash/INT_HARDWARE_ENTRY
58 cat <(echo WRITE_RO) >/sys/kernel/debug/provoke-crash/DIRECT
|
| /Linux-v5.10/Documentation/powerpc/ |
| 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
142 HPTE region, in the case a crash does occur.
144 Since this reserved memory area is used only after the system crash,
169 time of crash. | |
[all …]
|
| 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-v5.10/Documentation/gpu/ |
| D | msm-crash-dump.rst | 26 The kernel time at crash formated 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-v5.10/Documentation/ABI/testing/ |
| D | sysfs-kernel-fadump | 33 save the crash dump.
40 FADump to save the crash dump in bytes.
|
| D | sysfs-class-remoteproc | 32 "crashed" indicates that a problem/crash has been detected on
104 without it, debugging a crash is substantially harder.
|
| /Linux-v5.10/Documentation/admin-guide/kdump/ |
| 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.
443 User-space tools need to know whether the crash kernel was in 3-level or
497 It indicates whether the crash kernel supports large physical address
538 vmemmap address translation information is stored in the crash kernel,
|
| D | kdump.rst | 44 before a crash. The physical address of the start of the ELF header is
155 1) Enable "kernel crash dumps" support under "Processor type and
195 "kernel crash dumps" is enabled. A suitable value depends upon
216 1) Enable "Build a kdump crash kernel" support under "Kernel" options::
316 kernel will automatically locate the crash kernel image within the
465 system crash is triggered. Trigger points are located in panic(),
468 The following conditions will execute a crash trigger point:
480 For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
514 https://github.com/crash-utility/crash
517 https://crash-utility.github.io/
|
| /Linux-v5.10/arch/powerpc/kexec/ |
| D | Makefile | 6 obj-y += core.o crash.o core_$(BITS).o
|
| /Linux-v5.10/arch/nios2/ |
| D | Kconfig.debug | 11 You should normally say N here, unless you want to debug such a crash.
|
| /Linux-v5.10/Documentation/ABI/obsolete/ |
| D | sysfs-kernel-fadump_release_mem | 10 save the crash dump.
|
| /Linux-v5.10/tools/testing/selftests/lkdtm/ |
| D | run.sh | 10 TRIGGER=/sys/kernel/debug/provoke-crash/DIRECT
|
| /Linux-v5.10/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 38 between a debugging process and its inferior (crash handlers, etc),
43 Firefox's crash handlers, and by Wine for allowing only Wine processes
|
| /Linux-v5.10/Documentation/s390/ |
| 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.
268 crash Interface
270 The ``crash`` tool since v5.1.0 has a built-in command
274 a system crash.
279 system and after a system crash is to look at the raw memory
|
| /Linux-v5.10/arch/ia64/kernel/ |
| D | Makefile | 28 obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o
|
| /Linux-v5.10/arch/m68k/ |
| D | Kconfig.debug | 24 You should normally say N here, unless you want to debug such a crash.
|
| /Linux-v5.10/fs/proc/ |
| D | Kconfig | 55 underlying devices are initialized in crash recovery kernel.
56 Note that the device driver must be present in the crash
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | vdso | 15 within their rights to crash.) In addition, if you pass a bad
|
| /Linux-v5.10/arch/x86/xen/ |
| D | Kconfig | 59 The Xen tools and crash dump analysis tools might not support
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | persist.rst | 44 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-v5.10/arch/sh/ |
| D | Kconfig | 573 bool "kernel crash dumps (EXPERIMENTAL)"
576 Generate crash dump after being started by kexec.
577 This should be normally only set in special crash dump kernels
580 a crash by kdump/kexec. The crash dump kernel must be compiled
|
| /Linux-v5.10/drivers/hv/ |
| D | channel_mgmt.c | 803 void vmbus_initiate_unload(bool crash) in vmbus_initiate_unload() argument
818 !crash); in vmbus_initiate_unload()
824 if (!crash) in vmbus_initiate_unload()
|
| D | hyperv_vmbus.h | 374 void vmbus_initiate_unload(bool crash);
|
| /Linux-v5.10/Documentation/x86/ |
| D | pti.rst | 43 that any missed kernel->user CR3 switch will immediately crash
145 themselves to crash, but they should never crash the kernel.
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | bug-hunting.rst | 85 planned for a crash. Alternatively, you can take a picture of
193 To debug a kernel, use objdump and look for the hex offset from the crash
206 If you don't have access to the source code you can still debug some crash
207 dumps using the following method (example crash dump output as shown by
|
12345
