Lines Matching full:capture

11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
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
106 Build the system and dump-capture kernels
110 1) Build a separate custom dump-capture kernel for capturing the
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
121 at the same time one might want to build a custom dump capture kernel
125 dump-capture kernels for enabling kdump support.
163 Dump-capture kernel config options (Arch Independent)
177 Dump-capture kernel config options (Arch Dependent, i386 and x86_64)
190    command line when loading the dump-capture kernel because one
214    kexec boot loader will load it in memory region reserved for dump-capture
219    start of memory region reserved for dump-capture kernel.
226 Dump-capture kernel config options (Arch Dependent, ppc64)
239 Dump-capture kernel config options (Arch Dependent, ia64)
242 - No specific options are required to create a dump-capture kernel
245   as a dump-capture kernel if desired.
257 Dump-capture kernel config options (Arch Dependent, arm)
265 Dump-capture kernel config options (Arch Dependent, arm64)
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.
367 Load the Dump-capture Kernel
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
478 * We generally don't have to bring up a SMP kernel just to capture the
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
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