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 memory image to a dump file on the local disk, or across the network to
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
31 region just before rebooting into the dump-capture kernel.
45 passed to the dump-capture kernel through the elfcorehdr= boot
50 With the dump-capture kernel, you can access the memory image through
51 /proc/vmcore. This exports the dump as an ELF-format file that you can
54 debug the dump file. This method ensures that the dump pages are correctly
105 Build the system and dump-capture kernels
109 1) Build a separate custom dump-capture kernel for capturing the
110 kernel core dump.
112 2) Or use the system kernel binary itself as dump-capture kernel and there is
113 no need to build a separate dump-capture kernel. This is possible
119 one does not have to build a second kernel for capturing the dump. But
120 at the same time one might want to build a custom dump capture kernel
124 dump-capture kernels for enabling kdump support.
149 This causes the kernel to be built with debug symbols. The dump
151 and analyze a dump file.
182 when loading the dump-capture kernel, see section "Load the Dump-capture
199 kexec boot loader will load it in memory region reserved for dump-capture
204 start of memory region reserved for dump-capture kernel.
227 - No specific options are required to create a dump-capture kernel
230 as a dump-capture kernel if desired.
255 - Please note that kvm of the dump-capture kernel will not be enabled
293 where Y specifies how much memory to reserve for the dump-capture kernel
296 starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
304 dump-capture kernel config option notes above.
321 After booting to the system kernel, dump-capture kernel needs to be
326 of dump-capture kernel. Following is the summary.
343 to load dump-capture kernel.
345 kexec -p <dump-capture-kernel-vmlinux-image> \
346 --initrd=<initrd-for-dump-capture-kernel> --args-linux \
350 to load dump-capture kernel.
352 kexec -p <dump-capture-kernel-bzImage> \
353 --initrd=<initrd-for-dump-capture-kernel> \
357 to load dump-capture kernel.
359 kexec --type zImage -p <dump-capture-kernel-bzImage> \
360 --initrd=<initrd-for-dump-capture-kernel> \
361 --dtb=<dtb-for-dump-capture-kernel> \
365 to load dump-capture kernel.
367 kexec -p <dump-capture-kernel-Image> \
368 --initrd=<initrd-for-dump-capture-kernel> \
376 loading dump-capture kernel.
393 Notes on loading the dump-capture kernel:
405 due to shared interrupts in the dump-capture kernel.
410 * Boot parameter "1" boots the dump-capture kernel into single-user
414 dump. Hence generally it is useful either to build a UP dump-capture
415 kernel or specify maxcpus=1 option while loading dump-capture kernel.
419 * You should enable multi-cpu support in dump-capture kernel if you intend
420 to use multi-thread programs with it, such as parallel dump feature of
423 SMP dump-capture kernel and specify maxcpus/nr_cpus, disable_cpu_apicid=[X]
443 After successfully loading the dump-capture kernel as previously
444 described, the system will reboot into the dump-capture kernel if a
451 will boot into the dump-capture kernel ( die_nmi() ).
455 the system will boot into the dump-capture kernel.
458 and the system will boot into the dump-capture kernel.
466 After the dump-capture kernel is booted, write out the dump file with
469 cp /proc/vmcore <dump-file>
475 Before analyzing the dump image, you should reboot into a stable kernel.
477 You can do limited analysis using GDB on the dump file copied out of
481 gdb vmlinux <dump-file>
489 dump kernel.
491 You can also use the Crash utility to analyze dump files in Kdump