Bug 702404

Summary:	[RHEL6.1] kdump kernel failed to startup
Product:	Red Hat Enterprise Linux 6	Reporter:	PaulB <pbunyan>
Component:	kernel	Assignee:	Baoquan He <bhe>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	bhe, jburke, kdump-team-bugs, nhorman, pbunyan, ruyang, vgoyal
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-24 02:00:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description PaulB 2011-05-05 15:10:19 UTC

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 4 RHEL 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 5 RHEL 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.

Comment 6 Baoquan He 2014-04-15 13:22:06 UTC

The reservation of crashkernel in 1st kernel failed, I will debug the code by adding some printk info to see what happened.

Comment 7 Baoquan He 2014-04-21 02:15:52 UTC

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

Comment 8 Baoquan He 2014-04-21 07:07:38 UTC

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.

Comment 9 Baoquan He 2014-04-24 02:00:51 UTC

Didn't reproduce on 2.6.32-431.el6, I would like to close it as NOTABUG. Please free free to reopen it if any concern.

Thanks
Baoquan