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.
292 where Y specifies how much memory to reserve for the dump-capture kernel
295 starting at physical address 0x01000000 (16MB) for the dump-capture kernel.
303 dump-capture kernel config option notes above.
312 any space below the alignment point may be overwritten by the dump-capture kernel,
319 After booting to the system kernel, dump-capture kernel needs to be
324 of dump-capture kernel. Following is the summary.
339 to load dump-capture kernel.
341 kexec -p <dump-capture-kernel-vmlinux-image> \
342 --initrd=<initrd-for-dump-capture-kernel> --args-linux \
346 to load dump-capture kernel.
348 kexec -p <dump-capture-kernel-bzImage> \
349 --initrd=<initrd-for-dump-capture-kernel> \
353 to load dump-capture kernel.
355 kexec --type zImage -p <dump-capture-kernel-bzImage> \
356 --initrd=<initrd-for-dump-capture-kernel> \
357 --dtb=<dtb-for-dump-capture-kernel> \
366 loading dump-capture kernel.
380 Notes on loading the dump-capture kernel:
392 due to shared interrupts in the dump-capture kernel.
397 * Boot parameter "1" boots the dump-capture kernel into single-user
401 dump. Hence generally it is useful either to build a UP dump-capture
402 kernel or specify maxcpus=1 option while loading dump-capture kernel.
421 After successfully loading the dump-capture kernel as previously
422 described, the system will reboot into the dump-capture kernel if a
429 will boot into the dump-capture kernel ( die_nmi() ).
433 the system will boot into the dump-capture kernel.
436 and the system will boot into the dump-capture kernel.
444 After the dump-capture kernel is booted, write out the dump file with
447 cp /proc/vmcore <dump-file>
453 Before analyzing the dump image, you should reboot into a stable kernel.
455 You can do limited analysis using GDB on the dump file copied out of
459 gdb vmlinux <dump-file>
467 dump kernel.
469 You can also use the Crash utility to analyze dump files in Kdump