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.
Description of problem:
System fails to boot kdump kernel 2.6.32-131.0.13.el6
Version-Release number of selected component (if applicable):
2.6.32-131.0.13.el6
How reproducible:
Everytime
Steps to Reproduce:
See details in following comment.
Actual results:
See details in following comment.
Expected results:
System should successfully boot kdump kernel.
Additional info:
System hostname and details provided in following comment.
-pbunyan
Comment 4RHEL Program Management
2011-05-06 06:01:14 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 5RHEL Program Management
2011-10-07 15:34:07 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
I tried to reserve beaker machine, the log shows reserved address can not be satisfied because it has been used.
"crashkernel reservation failed - memory is in use"
From code, this could happen if you can't make sure the specified reserve address is not used for other usage earlier. So please use crashkernel=YM without "@XM", this will be helpful.
I would like to close this bug as NOTABUG, please feel free to reopen it if anyone has different thought.
Thanks
Baoquan
OK, I was mistaken. Paul reported this bug is about the kdump kernel can't startup successfully. I will try reserving without "@xxx", then try again.
So reopen it.