Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1367181

Summary: kdump fails to start on boot owing to lack of memory or inability to load latest kernel
Product: [Fedora] Fedora Reporter: Rubén Lledó <ruben.lledo.calatayud>
Component: grubAssignee: Orphan Owner <extras-orphan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dcantrell, extras-orphan, jonathan, lkundrak, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 16:33:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
no memory reserved for crash kernel
cannot load /boot/vmlinuz none

Description Rubén Lledó 2016-08-15 19:29:00 UTC
Created attachment 1190964 [details]
no memory reserved for crash kernel

Description of problem:
While booting, message "Failed to start crash recovery kernel arming" can be read.

Version-Release number of selected component (if applicable):

How reproducible:
According to bug 1337626, and after googling a bit, it seems that the problem is a lack of memory reserved to crash kernel (see attachment "boot_1.png"). It is supposed to be fixed by appending "crashkernel=128M" to default grub2 command line or by executing system-config-kdump. For example:

GRUB_CMDLINE_LINUX=" SYSFONT=True rd.luks=0 crashkernel=128M KEYTABLE=es LANG=en_US.UTF-8 rhgb quiet"

However, another error comes up. This time is about the inability to load the default kernel (see attachment "boot_2.png")



Comment 1 Rubén Lledó 2016-08-15 19:29:42 UTC
Created attachment 1190965 [details]
cannot load /boot/vmlinuz

Comment 2 Fedora End Of Life 2017-07-25 22:26:34 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 16:33:32 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.