Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 676758

Summary: firstboot doesn't recognize the new crashkernel syntax
Product: Red Hat Enterprise Linux 6 Reporter: Cong Wang <amwang>
Component: kexec-toolsAssignee: Cong Wang <amwang>
Status: CLOSED ERRATA QA Contact: Chao Ye <cye>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0CC: cye, phan, rkhan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: kexec-tools-2_0_0-165_el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:16:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Proposed patch none

Description Cong Wang 2011-02-11 03:28:39 UTC
Description of problem:
Boot with the new crashkernel= syntax, e.g. crashkernel=4G-:256M, firstboot kdump will crash.

How reproducible:
Always

Comment 1 Cong Wang 2011-02-11 06:12:51 UTC
Created attachment 478186 [details]
Proposed patch

This patch can fix the problem.

Comment 3 Chao Ye 2011-02-14 02:16:18 UTC
Verified with kexec-tools-2.0.0-165.el6:
=======================================
[root@dell-pesc440-01 ~]# rpm -q kexec-tools
kexec-tools-2.0.0-165.el6.x86_64
[root@dell-pesc440-01 ~]# cat /boot/grub/grub.conf 
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_dellpesc44001-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
serial --port=0x03f8 --speed=115200
terminal --timeout=5 serial console
title Red Hat Enterprise Linux (2.6.32-71.el6.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=/dev/mapper/vg_dellpesc44001-lv_root rd_LVM_LV=vg_dellpesc44001/lv_root rd_LVM_LV=vg_dellpesc44001/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200n81 crashkernel=1G-:256M
	initrd /initramfs-2.6.32-71.el6.x86_64.img
[root@dell-pesc440-01 ~]# firstboot

No crash was found. Change status to VERIFIED.

Comment 4 errata-xmlrpc 2011-05-19 14:16:03 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0736.html