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