I tried changing the crashkernel value but nothing happened.
I got the information about the problem and I searched it and found that it might be due to graphic drivers.
But the problem is that I don't know which config settings are used for that.
Processor - AMD® Ryzen 5 1600 six-core processor × 12
Graphic card - GeForce GT 710/PCIe/SSE2
-------------------------Info-------------------------
[ 30.547978] xfs filesystem being remounted at /var/tmp supports timestamps until 2038 (0x7fffffff)
[ 31.227538] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.[ 31.255101] tun: Universal TUN/TAP device driver, 1.6
[ 31.257233] virbr0: port 1(virbr0-nic) entered blocking state
[ 31.257237] virbr0: port 1(virbr0-nic) entered disabled state
[ 31.257383] device virbr0-nic entered promiscuous mode
[ 31.404748] virbr0: port 1(virbr0-nic) entered blocking state
[ 31.404751] virbr0: port 1(virbr0-nic) entered listening state
[ 31.440572] virbr0: port 1(virbr0-nic) entered disabled state
[ 45.183565] xfs filesystem being remounted at /tmp supports timestamps until 2038 (0x7fffffff)
[ 45.184357] xfs filesystem being remounted at /var/tmp supports timestamps until 2038 (0x7fffffff)
[ 76.297401] xfs filesystem being remounted at /tmp supports timestamps until 2038 (0x7fffffff)
[ 76.297834] xfs filesystem being remounted at /var/tmp supports timestamps until 2038 (0x7fffffff)
On Sat, 20 Jun 2020 at 09:46, Sebastian Fricke <sebastian.fricke.linux@xxxxxxxxx> wrote:
On 19.06.2020 23:31, Harsh chopra wrote:
>I cloned the kernel from "git clone git://
>git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git".
>I selected the branch 5.7.y for building the kernel, I used the command
>"make menuconfig" to select specific modules and to avoid other options
>that come up while making the .config file.
>
>I was able to successfully install the kernel but when I started the kernel
>version 5.8.3+ , the system freezes with the message "see systemctl status
>kdump.service".
>When I looked in the logs I found this message "Failed to start Crash
>recovery kernel arming"
>My operating system is Centos 7.8.2003 kernel 3.10.
>Any help will be appreciated.
Hey,
This superuser post presents a solution, that might be helpful:
(https://superuser.com/questions/1463319/how-to-fix-failed-to-start-crash-recovery-kernel-arming-when-can-not-enter-the)
from Juli.2019
And as stated in this forum post, you can maybe find a bit more information
on your problem by disabling the `rhgb quiet` option.
(https://forums.centos.org/viewtopic.php?f=47&t=58745)
from august.2016
Sebastian
(Sorry for double post forgot to CC kernelnewbies)
>_______________________________________________
>Kernelnewbies mailing list
>Kernelnewbies@xxxxxxxxxxxxxxxxx
>https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
