Lines Matching refs:system

12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
18 a remote system.
23 When the system kernel boots, it reserves a small section of memory for
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
42 All of the necessary information about the system kernel's core image is
105 Build the system and dump-capture kernels
112 2) Or use the system kernel binary itself as dump-capture kernel and there is
123 Following are the configuration setting required for system and
129 1) Enable "kexec system call" in "Processor type and features."
133 2) Enable "sysfs file system support" in "Filesystem" -> "Pseudo
138    Note that "sysfs file system support" might not appear in the "Pseudo
229   above. This means that it is possible to use the system kernel
232   The crashkernel region can be automatically placed by the system
258 the kernel command line to avoid a unbootable system after some memory has
291 2) Boot the system kernel with the boot parameter "crashkernel=Y@X",
294    "crashkernel=64M@16M" tells the system kernel to reserve 64 MB of memory
307    on the memory consumption of the kdump system. In general this is not
308    dependent on the memory size of the production system.
319 After booting to the system kernel, dump-capture kernel needs to be
422 described, the system will reboot into the dump-capture kernel if a
423 system crash is triggered.  Trigger points are located in panic(),
428 If a hard lockup is detected and "NMI watchdog" is configured, the system
433 the system will boot into the dump-capture kernel.
436 and the system will boot into the dump-capture kernel.