Lines Matching refs:dump

11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
14 the reboot and is accessible to the dump-capture kernel.
17 the memory image to a dump file on the local disk, or across the network
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
52 /proc/vmcore. This exports the dump as an ELF-format file that you can
57 tool to debug the dump file. This method ensures that the dump pages are
106 Build the system and dump-capture kernels
110 1) Build a separate custom dump-capture kernel for capturing the
111    kernel core dump.
113 2) Or use the system kernel binary itself as dump-capture kernel and there is
114    no need to build a separate dump-capture kernel. This is possible
120 one does not have to build a second kernel for capturing the dump. But
121 at the same time one might want to build a custom dump capture kernel
125 dump-capture kernels for enabling kdump support.
159    This causes the kernel to be built with debug symbols. The dump
161    and analyze a dump file.
190    command line when loading the dump-capture kernel because one
191    CPU is enough for kdump kernel to dump vmcore on most of systems.
214    kexec boot loader will load it in memory region reserved for dump-capture
219    start of memory region reserved for dump-capture kernel.
242 - No specific options are required to create a dump-capture kernel
245   as a dump-capture kernel if desired.
268 - Please note that kvm of the dump-capture kernel will not be enabled
276    Here 'size' specifies how much memory to reserve for the dump-capture kernel
279    starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
353    dump-capture kernel config option notes above.
370 After booting to the system kernel, dump-capture kernel needs to be
375 of dump-capture kernel. Following is the summary.
403 to load dump-capture kernel::
405    kexec -p <dump-capture-kernel-vmlinux-image> \
406    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
410 to load dump-capture kernel::
412    kexec -p <dump-capture-kernel-bzImage> \
413    --initrd=<initrd-for-dump-capture-kernel> \
417 to load dump-capture kernel::
419    kexec --type zImage -p <dump-capture-kernel-bzImage> \
420    --initrd=<initrd-for-dump-capture-kernel> \
421    --dtb=<dtb-for-dump-capture-kernel> \
425 to load dump-capture kernel::
427    kexec -p <dump-capture-kernel-Image> \
428    --initrd=<initrd-for-dump-capture-kernel> \
436 loading dump-capture kernel.
458 Notes on loading the dump-capture kernel:
470   due to shared interrupts in the dump-capture kernel.
475 * Boot parameter "1" boots the dump-capture kernel into single-user
479   dump. Hence generally it is useful either to build a UP dump-capture
480   kernel or specify maxcpus=1 option while loading dump-capture kernel.
484 * You should enable multi-cpu support in dump-capture kernel if you intend
485   to use multi-thread programs with it, such as parallel dump feature of
488   SMP dump-capture kernel and specify maxcpus/nr_cpus, disable_cpu_apicid=[X]
508 After successfully loading the dump-capture kernel as previously
509 described, the system will reboot into the dump-capture kernel if a
516 will boot into the dump-capture kernel ( die_nmi() ).
520 the system will boot into the dump-capture kernel.
523 and the system will boot into the dump-capture kernel.
531 After the dump-capture kernel is booted, write out the dump file with
534    cp /proc/vmcore <dump-file>
536 You can also use makedumpfile utility to write out the dump file
539    makedumpfile -l --message-level 1 -d 31 /proc/vmcore <dump-file>
544 Before analyzing the dump image, you should reboot into a stable kernel.
546 You can do limited analysis using GDB on the dump file copied out of
550    gdb vmlinux <dump-file>
558 dump kernel.
560 You can also use the Crash utility to analyze dump files in Kdump