Searched refs:crash (Results 1 – 25 of 82) sorted by relevance
1234
| /linux-3.4.99/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-3.4.99/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 70 there is crash data available from a previous boot. During
112 crash does occur.
129 crash
132 o Memory Reservation during second kernel after crash
191 1 = fadump is registered and ready to handle system crash.
195 fadump. Once the fadump is un-registered, the system crash will not
203 region that are held for saving crash dump. To release the
250 o The fadump implementation introduces a fadump crash info structure
252 this structure is to pass some important crash info data to the second
|
| /linux-3.4.99/Documentation/security/ |
| D | Yama.txt | 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-3.4.99/Documentation/filesystems/ |
| D | ext3.txt | 153 The journal supports the transactions start and stop, and in case of a crash,
167 mode - metadata journaling. A crash+recovery can cause incorrect data to
168 appear in files which were written shortly before the crash. This mode will
181 In the event of a crash, the journal can be replayed, bringing both data and
|
| D | ext2.txt | 346 wait for e2fsck to complete after a crash, without requiring a change
355 the time of a crash. If a transaction is complete at the time of a crash
356 (or in the normal case where the system does not crash), then any blocks
359 the time of the crash, then there is no guarantee of consistency for
|
| D | hpfs.txt | 34 danger. I tried to write it so that it won't crash if check=normal on
283 2.05 Fixed crash when got mount parameters without =
284 Fixed crash when allocation of anode failed due to full disk
286 2.06 Fixed some crash on corrupted disk structures
|
| /linux-3.4.99/arch/tile/ |
| D | Kconfig.debug | 15 unless you want to debug such a crash.
|
| /linux-3.4.99/arch/m68k/ |
| D | Kconfig.debug | 22 You should normally say N here, unless you want to debug such a crash.
|
| /linux-3.4.99/Documentation/kdump/ |
| D | kdump.txt | 44 before a crash. The physical address of the start of the ELF header is
163 1) Enable "kernel crash dumps" support under "Processor type and
200 "kernel crash dumps" is enabled. A suitable value depends upon
221 1) Enable "Build a kdump crash kernel" support under "Kernel" options:
399 system crash is triggered. Trigger points are located in panic(),
402 The following conditions will execute a crash trigger point:
414 For testing purposes, you can trigger a crash by using "ALT-SysRq-c",
|
| /linux-3.4.99/fs/ext3/ |
| D | Kconfig | 11 crash. The journal keeps track of any changes that were being made
39 unwritten data to appear in files after an system crash or
|
| /linux-3.4.99/arch/s390/kernel/ |
| D | Makefile | 54 S390_KEXEC_OBJS := machine_kexec.o crash.o
|
| /linux-3.4.99/Documentation/ABI/stable/ |
| D | vdso | 9 within their rights to crash.) In addition, if you pass a bad
|
| /linux-3.4.99/arch/unicore32/ |
| D | Kconfig.debug | 28 unless you want to debug such a crash.
|
| /linux-3.4.99/Documentation/ |
| D | BUG-HUNTING | 152 To debug a kernel, use objdump and look for the hex offset from the crash
163 If you don't have access to the code you can also debug on some crash dumps
164 e.g. crash dump output as shown by Dave Miller.
|
| /linux-3.4.99/arch/powerpc/platforms/cell/ |
| D | beat.c | 176 void beat_kexec_cpu_down(int crash, int secondary) in beat_kexec_cpu_down() argument
|
| /linux-3.4.99/Documentation/sound/oss/ |
| D | PSS | 22 machines and will cause a crash on them.
|
| /linux-3.4.99/Documentation/usb/ |
| D | persist.txt | 41 instantly crash.
62 suspended -- but it will crash as soon as it wakes up, which isn't
155 data corruption and to crash your system. You'll have no one to blame
|
| /linux-3.4.99/arch/ia64/kernel/ |
| D | Makefile | 30 obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o
|
| /linux-3.4.99/arch/sh/ |
| D | Kconfig | 641 bool "kernel crash dumps (EXPERIMENTAL)"
644 Generate crash dump after being started by kexec.
645 This should be normally only set in special crash dump kernels
648 a crash by kdump/kexec. The crash dump kernel must be compiled
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | dm-log.txt | 33 will not survive a reboot or crash, but there may be a small boost in
|
| /linux-3.4.99/arch/x86/kernel/ |
| D | Makefile | 69 obj-$(CONFIG_KEXEC) += relocate_kernel_$(BITS).o crash.o
|
| /linux-3.4.99/Documentation/ia64/ |
| D | kvm.txt | 56 In the event of strange host crash issues, try to solve it through either of the following ways:
|
| /linux-3.4.99/Documentation/power/ |
| D | video.txt | 77 bios, you'll get a hard crash during resume. Be careful. Also it is
79 and radeonfb (etc) drivers have a tendency to crash the machine during
|
| /linux-3.4.99/Documentation/s390/ |
| D | s390dbf.txt | 12 One purpose of this is to inspect the debug logs after a production system crash
13 in order to analyze the reason for the crash.
462 a system crash.
467 system and after a system crash is to look at the raw memory
|
| /linux-3.4.99/net/irda/ |
| D | Kconfig | 90 verifications which will usually prevent the kernel to crash in case of
|
1234