Home
last modified time | relevance | path

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

12345

/Linux-v5.4/Documentation/fault-injection/
Dprovoke-crashes.rst5 The lkdtm module provides an interface to crash or injure the kernel at
6 predefined crashpoints to evaluate the reliability of crash dumps obtained
8 crashing points, but can also crash the kernel directly without KRPOBE
30 Indicates the action to be taken on hitting the crash point.
36 Indicates the number of times the crash point is to be hit
40 <mountpoint>/provoke-crash/<crashpoint>. E.g.::
43 echo EXCEPTION > /mnt/provoke-crash/INT_HARDWARE_ENTRY
46 A special file is `DIRECT` which will induce the crash directly without
/Linux-v5.4/Documentation/powerpc/
Dfirmware-assisted-dump.rst66 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 …]
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-v5.4/Documentation/gpu/
Dmsm-crash-dump.rst26 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.4/Documentation/admin-guide/kdump/
Dvmcoreinfo.rst11 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
282 User-space tools need to know whether the crash kernel was in 5-level
312 mask. Makedumpfile tools need to know whether the crash kernel was
313 encrypted. If SME is enabled in the first kernel, the crash kernel's
336 crash kernel when converting virtual addresses to physical addresses.
365 User-space tools need to know whether the crash kernel was in 3-level or
402 It indicates whether the crash kernel supports large physical address
443 vmemmap address translation information is stored in the crash kernel,
Dkdump.rst44 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",
/Linux-v5.4/arch/nios2/
DKconfig.debug11 You should normally say N here, unless you want to debug such a crash.
/Linux-v5.4/Documentation/admin-guide/LSM/
DYama.rst37 between a debugging process and its inferior (crash handlers, etc),
42 Firefox's crash handlers, and by Wine for allowing only Wine processes
/Linux-v5.4/Documentation/power/
Dinterface.rst74 RTC information), so it will survive a system crash if one occurs right after
75 storing it and it can be used later to identify the driver that caused the crash
/Linux-v5.4/arch/unicore32/
DKconfig.debug12 unless you want to debug such a crash.
/Linux-v5.4/Documentation/s390/
Ds390dbf.rst14 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.
271 crash Interface
273 The ``crash`` tool since v5.1.0 has a built-in command
277 a system crash.
282 system and after a system crash is to look at the raw memory
/Linux-v5.4/arch/m68k/
DKconfig.debug24 You should normally say N here, unless you want to debug such a crash.
/Linux-v5.4/fs/proc/
DKconfig55 underlying devices are initialized in crash recovery kernel.
56 Note that the device driver must be present in the crash
/Linux-v5.4/arch/ia64/kernel/
DMakefile29 obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o
/Linux-v5.4/Documentation/ABI/stable/
Dvdso9 within their rights to crash.) In addition, if you pass a bad
/Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/
Drenesas,dbsc.txt11 crash the system.
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-remoteproc32 "crashed" indicates that a problem/crash has been detected on
/Linux-v5.4/arch/x86/xen/
DKconfig58 The Xen tools and crash dump analysis tools might not support
/Linux-v5.4/drivers/hv/
Dhyperv_vmbus.h364 void vmbus_initiate_unload(bool crash);
/Linux-v5.4/Documentation/driver-api/usb/
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-v5.4/Documentation/x86/
Dpti.rst43 that any missed kernel->user CR3 switch will immediately crash
145 themselves to crash, but they should never crash the kernel.
/Linux-v5.4/arch/sh/
DKconfig617 bool "kernel crash dumps (EXPERIMENTAL)"
620 Generate crash dump after being started by kexec.
621 This should be normally only set in special crash dump kernels
624 a crash by kdump/kexec. The crash dump kernel must be compiled
/Linux-v5.4/Documentation/admin-guide/
Dbug-hunting.rst81 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-v5.4/drivers/virtio/
DKconfig93 address in particular) can crash your system - you have been warned.
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-log.rst36 will not survive a reboot or crash, but there may be a small boost in

12345