/openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc/ |
H A D | 0015-vmcore-dmesg-fix-warning.patch | 4 Subject: [PATCH] vmcore-dmesg: fix warning 13 vmcore-dmesg/vmcore-dmesg.c | 3 +++ 16 diff --git a/vmcore-dmesg/vmcore-dmesg.c b/vmcore-dmesg/vmcore-dmesg.c 18 --- a/vmcore-dmesg/vmcore-dmesg.c 19 +++ b/vmcore-dmesg/vmcore-dmesg.c
|
H A D | 0009-vmcore-dmesg.c-work-around-missing-imaxdiv.patch | 4 Subject: [PATCH] vmcore-dmesg.c: work around missing imaxdiv() 10 vmcore-dmesg.c: In function 'dump_dmesg_structured': 11 vmcore-dmesg.c:578:2: error: unknown type name 'imaxdiv_t' 17 vmcore-dmesg/vmcore-dmesg.c | 13 ++++++++++++- 20 diff --git a/vmcore-dmesg/vmcore-dmesg.c b/vmcore-dmesg/vmcore-dmesg.c 22 --- a/vmcore-dmesg/vmcore-dmesg.c 23 +++ b/vmcore-dmesg/vmcore-dmesg.c
|
/openbmc/openbmc/poky/meta/recipes-kernel/kexec/kexec-tools/ |
H A D | kdump | 61 ${MAKEDUMPFILE} ${MAKEDUMPFILE_ARGS} /proc/vmcore ${KDUMP_VMCORE_PATH}/vmcore-"`date +"%H:%M:%S"`" 126 if [ -s /proc/vmcore ]; then
|
H A D | kdump.service | 2 Description=Reboot and dump vmcore via kexec
|
/openbmc/openbmc/meta-openembedded/meta-initramfs/recipes-kernel/kexec/ |
H A D | kexec-tools-klibc_git.bb | 29 file://0009-vmcore-dmesg.c-work-around-missing-imaxdiv.patch \ 35 file://0015-vmcore-dmesg-fix-warning.patch \ 88 PACKAGES =+ "kexec-klibc vmcore-dmesg-klibc" 91 FILES:vmcore-dmesg-klibc = "${sbindir}/vmcore-dmesg"
|
/openbmc/openbmc/poky/meta/recipes-kernel/kexec/ |
H A D | kexec-tools_2.0.30.bb | 60 PACKAGES =+ "kexec kdump vmcore-dmesg" 63 RRECOMMENDS:${PN} = "kexec kdump vmcore-dmesg" 73 FILES:vmcore-dmesg = "${sbindir}/vmcore-dmesg"
|
/openbmc/qemu/scripts/ |
H A D | dump-guest-memory.py | 510 def dump_init(self, vmcore): argument 528 self.elf.to_file(vmcore) 530 def dump_iterate(self, vmcore): argument 543 vmcore.write(chunk) 594 with open(argv[0], "wb") as vmcore: 595 self.dump_init(vmcore) 596 self.dump_iterate(vmcore)
|
/openbmc/linux/Documentation/arch/s390/ |
H A D | zfcpdump.rst | 21 of the /proc/vmcore interface. This interface exports the crashed system's 24 is needed by /proc/vmcore. The tail part of the crashed systems memory which 42 reads from /proc/vmcore or zcore/mem and writes the system dump to a SCSI disk.
|
/openbmc/linux/fs/proc/ |
H A D | vmcore.c | 322 struct vmcore *m = NULL; in __read_vmcore() 579 struct vmcore *m; in mmap_vmcore() 701 static struct vmcore* __init get_new_element(void) in get_new_element() 703 return kzalloc(sizeof(struct vmcore), GFP_KERNEL); in get_new_element() 710 struct vmcore *m; in get_vmcore_size() 1112 struct vmcore *new; in process_ptload_program_headers_elf64() 1155 struct vmcore *new; in process_ptload_program_headers_elf32() 1194 struct vmcore *m; in set_vmcore_list_offsets() 1598 struct vmcore *m; in vmcore_cleanup() 1600 m = list_first_entry(&vmcore_list, struct vmcore, list); in vmcore_cleanup()
|
H A D | Makefile | 33 proc-$(CONFIG_PROC_VMCORE) += vmcore.o
|
H A D | Kconfig | 42 bool "/proc/vmcore support" 61 as ELF notes to /proc/vmcore. You can still disable device
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | kdump.rst | 7 Kdump mechanism is used to capture a corrupted kernel vmcore so that 14 vmcore collection. 34 vmcore dumping can be ignored. On arm64, the low memory upper bound is
|
/openbmc/linux/include/linux/ |
H A D | kcore.h | 23 struct vmcore { struct
|
/openbmc/linux/Documentation/powerpc/ |
H A D | firmware-assisted-dump.rst | 16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore 20 interface while reading /proc/vmcore. 83 - User-space tools will read /proc/vmcore to obtain the contents 194 Used by second /proc/vmcore 206 Currently the dump will be copied from /proc/vmcore to a new file upon 207 user intervention. The dump data available through /proc/vmcore will be 268 be handled and vmcore will not be captured. This interface can be 360 correct data before it gets exported through /proc/vmcore. The current
|
/openbmc/linux/Documentation/ABI/obsolete/ |
H A D | sysfs-kernel-fadump_release_mem | 8 the system is booted to capture the vmcore using FADump.
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-kernel-vmcoreinfo | 12 space as part of ELF note in /proc/vmcore file. This note
|
H A D | sysfs-kernel-fadump | 31 the system is booted to capture the vmcore using FADump.
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/crash/ |
H A D | crash-cross-canadian_8.0.5.bb | 47 …CORE_TARGET_SYSROOT/boot/<vmlinux file> $OECORE_TARGET_SYSROOT/boot/<System.map file> <your vmcore>
|
/openbmc/linux/Documentation/admin-guide/kdump/ |
H A D | kdump.rst | 52 /proc/vmcore. This exports the dump as an ELF-format file that you can 171 2) Enable "/proc/vmcore support" under "Filesystems" -> "Pseudo filesystems":: 191 CPU is enough for kdump kernel to dump vmcore on most of systems. 466 headers. This is necessary because GDB currently cannot open vmcore files 534 cp /proc/vmcore <dump-file> 538 scp /proc/vmcore remote_username@remote_ip:<dump-file> 543 makedumpfile -l --message-level 1 -d 31 /proc/vmcore <dump-file> 551 /proc/vmcore. Use the debug vmlinux built with -g and run the following
|
H A D | vmcoreinfo.rst | 22 find the corresponding vmlinux in order to process vmcore.
|
/openbmc/qemu/qapi/ |
H A D | dump.json | 51 # Dump guest's memory to vmcore. It is a synchronous operation that 70 # @protocol: the filename or file descriptor of the vmcore. The
|
/openbmc/openbmc/poky/meta/recipes-kernel/makedumpfile/ |
H A D | makedumpfile_1.7.6.bb | 4 via /dev/mem or /proc/vmcore (for crashdumps). It is used to get memory \
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/packagegroups/ |
H A D | packagegroup-obmc-apps.bbappend | 41 …hor-post-code-manager phosphor-host-postd kexec-tools makedumpfile kdump vmcore-dmesg debug-trigge…
|
/openbmc/linux/Documentation/bpf/ |
H A D | drgn.rst | 9 Instead it's reading directly from ``/proc/kcore`` or vmcore and pretty prints
|
/openbmc/linux/Documentation/trace/ |
H A D | osnoise-tracer.rst | 128 capture a vmcore.
|