Hide Forgot
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
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.
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.
The reservation of crashkernel in 1st kernel failed, I will debug the code by adding some printk info to see what happened.
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.
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