Searched full:crash (Results 1 – 25 of 97) sorted by relevance
1234
| /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
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
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 4 MSM Crash Dump Format
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.
|
| /Documentation/arch/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 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
|
| /Documentation/admin-guide/kdump/ |
| D | kdump.rst | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
46 before a crash. The physical address of the start of the ELF header is
56 you can use analysis tools such as the GNU Debugger (GDB) and the Crash
162 1) Enable "kernel crash dumps" support under "Processor type and
206 "kernel crash dumps" is enabled. A suitable value depends upon
227 1) Enable "Build a kdump crash kernel" support under "Kernel" options::
336 kernel will automatically locate the crash kernel image within the
476 system crash is triggered. Trigger points are located in panic(),
479 The following conditions will execute a crash trigger point:
491 For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
[all …]
|
| 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
45 Offset of the name's member. Crash Utility and Makedumpfile get
360 User-space tools need to know whether the crash kernel was in 5-level
384 address by Crash.
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,
|
| D | index.rst | 3 Documentation for Kdump - The kexec-based Crash Dumping Solution
|
| /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.
|
| 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
|
| /Documentation/trace/ |
| 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.
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-kernel-fadump_release_mem | 10 save the crash dump.
|
| /Documentation/filesystems/ext4/ |
| 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
|
| /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
|
| /Documentation/arch/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
|
| /Documentation/ABI/stable/ |
| D | vdso | 17 within their rights to crash.) In addition, if you pass a bad
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | sysrq.rst | 100 ``c`` 將執行系統 crash，如果配置了系統 crashdump，將執行 crashdump。
181 ``crash(c)`` 可以用於手動觸發一個 crashdump，當系統卡住時。
182 注意當 crashdump 機制不可用時，這個只是觸發一個內核 crash。
|
| /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
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | sysrq.rst | 100 ``c`` 将执行系统 crash，如果配置了系统 crashdump，将执行 crashdump。
181 ``crash(c)`` 可以用于手动触发一个 crashdump，当系统卡住时。
182 注意当 crashdump 机制不可用时，这个只是触发一个内核 crash。
|
| /Documentation/ABI/removed/ |
| D | sysfs-mce | 23 better uptime with the risk of a crash or even corruption
|
| /Documentation/arch/x86/ |
| D | pti.rst | 43 that any missed kernel->user CR3 switch will immediately crash
143 themselves to crash, but they should never crash the kernel.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 10 crash, either both sector and integrity tag or none of them is written.
78 separately. In case of crash, it is possible that the data
82 journal and atomicity is guaranteed. In case of crash,
|
| /Documentation/filesystems/ |
| D | ext2.rst | 356 wait for e2fsck to complete after a crash, without requiring a change
365 the time of a crash. If a transaction is complete at the time of a crash
366 (or in the normal case where the system does not crash), then any blocks
369 the time of the crash, then there is no guarantee of consistency for
|
| D | hpfs.rst | 42 danger. I tried to write it so that it won't crash if check=normal on
336 2.05 Fixed crash when got mount parameters without =
338 Fixed crash when allocation of anode failed due to full disk
341 2.06 Fixed some crash on corrupted disk structures
|
| /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
|
1234