| /OK3568_Linux_fs/yocto/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 11 vmcore-dmesg/vmcore-dmesg.c | 3 +++ 14 diff --git a/vmcore-dmesg/vmcore-dmesg.c b/vmcore-dmesg/vmcore-dmesg.c 16 --- a/vmcore-dmesg/vmcore-dmesg.c 17 +++ 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
|
| /OK3568_Linux_fs/yocto/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
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-initramfs/recipes-kernel/kexec/ |
| H A D | kexec-tools-klibc_git.bb | 28 file://0009-vmcore-dmesg.c-work-around-missing-imaxdiv.patch \ 34 file://0015-vmcore-dmesg-fix-warning.patch \ 87 PACKAGES =+ "kexec-klibc vmcore-dmesg-klibc" 90 FILES:vmcore-dmesg-klibc = "${sbindir}/vmcore-dmesg"
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/kexec/ |
| H A D | kexec-tools_2.0.23.bb | 60 PACKAGES =+ "kexec kdump vmcore-dmesg" 63 RRECOMMENDS:${PN} = "kexec kdump vmcore-dmesg" 73 FILES:vmcore-dmesg = "${sbindir}/vmcore-dmesg"
|
| /OK3568_Linux_fs/kernel/Documentation/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.
|
| /OK3568_Linux_fs/kernel/fs/proc/ |
| H A D | vmcore.c | 305 struct vmcore *m = NULL; in __read_vmcore() 558 struct vmcore *m; in mmap_vmcore() 680 static struct vmcore* __init get_new_element(void) in get_new_element() 682 return kzalloc(sizeof(struct vmcore), GFP_KERNEL); in get_new_element() 689 struct vmcore *m; in get_vmcore_size() 1091 struct vmcore *new; in process_ptload_program_headers_elf64() 1134 struct vmcore *new; in process_ptload_program_headers_elf32() 1173 struct vmcore *m; in set_vmcore_list_offsets() 1579 struct vmcore *m; in vmcore_cleanup() 1581 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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | kcore.h | 26 struct vmcore { struct
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/obsolete/ |
| H A D | sysfs-kernel-fadump_release_mem | 8 the system is booted to capture the vmcore using FADump.
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-kernel/makedumpfile/ |
| H A D | makedumpfile_1.7.1.bb | 4 via /dev/mem or /proc/vmcore (for crashdumps). It is used to get memory \
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/kdump/ |
| H A D | kdump.rst | 51 /proc/vmcore. This exports the dump as an ELF-format file that you can 160 2) Enable "/proc/vmcore support" under "Filesystems" -> "Pseudo filesystems":: 421 headers. This is necessary because GDB currently cannot open vmcore files 489 cp /proc/vmcore <dump-file> 498 /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.
|
| /OK3568_Linux_fs/kernel/Documentation/bpf/ |
| H A D | drgn.rst | 9 Instead it's reading directly from ``/proc/kcore`` or vmcore and pretty prints
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/ |
| H A D | ..install.cmd | 1 ….h bsg.h nfs_mount.h thermal.h vm_sockets_diag.h arcfb.h smc.h ethtool.h vmcore.h tls.h mtio.h atm…
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/ |
| H A D | ..install.cmd | 1 ….h bsg.h nfs_mount.h thermal.h vm_sockets_diag.h arcfb.h smc.h ethtool.h vmcore.h tls.h mtio.h atm…
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 802 is useful to define the root cause of RCU stalls using a vmcore.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | devices.txt | 18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
|
| H A D | kernel-parameters.txt | 3285 append dump data to vmcore so you can collect driver
|
| /OK3568_Linux_fs/kernel/ |
| H A D | MAINTAINERS | 9527 F: fs/proc/vmcore.c 9530 F: include/uapi/linux/vmcore.h
|