Searched refs:crash (Results 1 – 25 of 107) sorted by relevance
12345
| /Linux-v4.19/Documentation/fault-injection/ |
| D | provoke-crashes.txt | 1 The lkdtm module provides an interface to crash or injure the kernel at
2 predefined crashpoints to evaluate the reliability of crash dumps obtained
4 crashing points, but can also crash the kernel directly without KRPOBE
21 cpoint_type : Indicates the action to be taken on hitting the crash point.
26 cpoint_count : Indicates the number of times the crash point is to be hit
30 <mountpoint>/provoke-crash/<crashpoint>. E.g.,
33 echo EXCEPTION > /mnt/provoke-crash/INT_HARDWARE_ENTRY
36 A special file is `DIRECT' which will induce the crash directly without
|
| /Linux-v4.19/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 65 for boot memory dump preservation in case of a crash.
74 there is crash data available from a previous boot. During
116 and HPTE region, in the case a crash does occur.
133 crash
136 o Memory Reservation during second kernel after crash
198 1 = fadump is registered and ready to handle system crash.
202 fadump. Once the fadump is un-registered, the system crash will not
210 region that are held for saving crash dump. To release the
257 o The fadump implementation introduces a fadump crash info structure
259 this structure is to pass some important crash info data to the second
|
| /Linux-v4.19/Documentation/gpu/ |
| D | msm-crash-dump.rst | 24 The kernel time at crash formated as seconds.microseconds.
33 ID of the GPU that generated the crash formatted as
38 components are in use at the time of crash.
|
| /Linux-v4.19/arch/nios2/ |
| D | Kconfig.debug | 14 You should normally say N here, unless you want to debug such a crash.
|
| /Linux-v4.19/Documentation/kdump/ |
| D | kdump.txt | 44 before a crash. The physical address of the start of the ELF header is
156 1) Enable "kernel crash dumps" support under "Processor type and
193 "kernel crash dumps" is enabled. A suitable value depends upon
214 1) Enable "Build a kdump crash kernel" support under "Kernel" options:
312 kernel will automatically locate the crash kernel image within the
445 system crash is triggered. Trigger points are located in panic(),
448 The following conditions will execute a crash trigger point:
460 For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
|
| /Linux-v4.19/Documentation/power/ |
| D | interface.txt | 72 RTC information), so it will survive a system crash if one occurs right after
73 storing it and it can be used later to identify the driver that caused the crash
|
| /Linux-v4.19/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 37 between a debugging process and its inferior (crash handlers, etc),
42 Firefox's crash handlers, and by Wine for allowing only Wine processes
|
| /Linux-v4.19/arch/unicore32/ |
| D | Kconfig.debug | 12 unless you want to debug such a crash.
|
| /Linux-v4.19/arch/m68k/ |
| D | Kconfig.debug | 24 You should normally say N here, unless you want to debug such a crash.
|
| /Linux-v4.19/fs/proc/ |
| D | Kconfig | 54 underlying devices are initialized in crash recovery kernel.
55 Note that the device driver must be present in the crash
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 32 "crashed" indicates that a problem/crash has been detected on
|
| /Linux-v4.19/arch/ia64/kernel/ |
| D | Makefile | 30 obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | vdso | 9 within their rights to crash.) In addition, if you pass a bad
|
| /Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 11 crash the system.
|
| /Linux-v4.19/arch/x86/xen/ |
| D | Kconfig | 56 The Xen tools and crash dump analysis tools might not support
|
| /Linux-v4.19/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-v4.19/Documentation/device-mapper/ |
| D | dm-integrity.txt | 6 crash, either both sector and integrity tag or none of them is written.
55 separately. In case of crash, it is possible that the data
58 journal and atomicity is guaranteed. In case of crash,
|
| D | dm-log.txt | 33 will not survive a reboot or crash, but there may be a small boost in
|
| /Linux-v4.19/drivers/virtio/ |
| D | Kconfig | 81 address in particular) can crash your system - you have been warned.
|
| /Linux-v4.19/drivers/hv/ |
| D | hyperv_vmbus.h | 412 void vmbus_initiate_unload(bool crash);
|
| D | channel_mgmt.c | 781 void vmbus_initiate_unload(bool crash) in vmbus_initiate_unload() argument
793 !crash); in vmbus_initiate_unload()
799 if (!crash) in vmbus_initiate_unload()
|
| /Linux-v4.19/Documentation/x86/ |
| D | pti.txt | 37 that any missed kernel->user CR3 switch will immediately crash
137 themselves to crash, but they should never crash the kernel.
|
| /Linux-v4.19/arch/sh/ |
| D | Kconfig | 624 bool "kernel crash dumps (EXPERIMENTAL)"
627 Generate crash dump after being started by kexec.
628 This should be normally only set in special crash dump kernels
631 a crash by kdump/kexec. The crash dump kernel must be compiled
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | bug-hunting.rst | 81 planned for a crash. Alternatively, you can take a picture of
189 To debug a kernel, use objdump and look for the hex offset from the crash
202 If you don't have access to the code you can also debug on some crash dumps
203 e.g. crash dump output as shown by Dave Miller::
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ext2.txt | 345 wait for e2fsck to complete after a crash, without requiring a change
354 the time of a crash. If a transaction is complete at the time of a crash
355 (or in the normal case where the system does not crash), then any blocks
358 the time of the crash, then there is no guarantee of consistency for
|
12345
