-----Original Messages----- From: "Benjamin Hauger" hauger@noao.edu Sent Time: 2019-03-28 01:31:40 (Thursday) To: wuzhouhui wuzhouhui14@mails.ucas.ac.cn, centos@centos.org Cc: Subject: Re: [CentOS] How to specify kernel version when restart kdump
What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted?
Suppose the running kernel is 2.6.32, and then I installed kernel 3.10.0. The files under /boot includes (exclude some unimportant files): initramfs-2.6.32.img initramfs-3.10.0.img vmlinuz-2.6.32 vmlinuz-3.10.0 initrd-2.6.32kdump.img We can see that there is no initrd-3.10.0kdump.img for newly installed kernel 3.10.0, and kdump will generate initrd-3.10.0kdump.img only when booted as kernel 3.10.0. However, I want kdump to generate initrd-3.10.0kdump.img now (the current running kernel is 2.6.32).
Ben
On 3/26/19 6:16 PM, wuzhouhui wrote:
-----Original Messages----- From: "Benjamin Hauger" hauger@noao.edu Sent Time: 2019-03-27 00:15:21 (Wednesday) To: centos@centos.org Cc: Subject: Re: [CentOS] How to specify kernel version when restart kdump
kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel.
You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence:
echo 1 > /proc/sys/kernel/sysrq echo c > /proc/sysrq-triggerCheers, Ben
Hi, Ben
I think your response doesn't answered my question. I'm not asking how to trigger kernel crash and see whether the kdump is works, but asking how to specifying kernel version when start kdump service.
Thanks.
On 3/25/19 7:19 PM, wuzhouhui wrote: CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
--
Benjamin Hauger SysAdmin/CSDC-DMO Rm. 94 x8371