Re: Linux doesn't create /proc/vmcore

From: Atsushi Kumagai
Date: Mon May 20 2013 - 20:34:26 EST


Hello matt,

> CONFIG_PROC_VMCORE=y

Is it specified for the capture kernel ?
By any chance, did you run kdump-config on the system kernel,
not on the capture kernel ?

> DESCRIPTION
> kdump-config manages the kdump feature of the Linux kernel. When a
> kdump enabled kernel panics, it immediately boots into a clean kernel
> called the kdump kernel. The memory image of the panicked kernel will
> be presented in /proc/vmcore while the kdump kernel (or "capture
> kernel") is running.

/proc/vmcore doesn't be created on the system kernel, this tool should be
run on the capture kernel.

And this document may help you:

Documentation/kdump/kdump.txt


Thanks
Atsushi Kumagai

>
> my error on the kdump:
> kdump-config savecore
> running makedumpfile -c -d 31 /proc/vmcore
> /var/crash/201305180259/dump-incomplete.
> open_dump_memory: Can't open the dump memory(/proc/vmcore). No such
> file or directory
>
> makedumpfile Failed.
> kdump-config: makedumpfile failed, falling back to 'cp' ... failed!
> cp: cannot stat `/proc/vmcore': No such file or directory
> kdump-config: failed to save vmcore in /var/crash/201305180259 ... failed!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/