Red Hat Bugzilla – Bug 858761
x86: CONFIG_RELOCATABLE is not set
Last modified: 2012-12-20 10:34:23 EST
Description of problem:
kernel isn't relocatable. feature required for kdump to work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. $ grep RELOCATABLE /boot/config-3.5.3-1.fc17.i686
# CONFIG_RELOCATABLE is not set
It was disabled for 3.3. I believe it can be enabled back on on 3.5 -- though I'm not sure. On http://fedora.12.n6.nabble.com/Crash-kernel-x86-32-BzImage-is-not-relocatable-Can-t-be-used-as-capture-kernel-td4988599.html Josh Boyer-3 said:
«It was disabled for 32-bit kernels in the 3.3 timeframe. There was a
binutils bug that caused silent kernel corruption on 32-bit relocatable
kernels and the best option at the time was to disable it.
You can probably enable it by removing the CONFIG_RELOCATABLE line in
config-x86-32-generic and rebuilding the kernel.»
Want to test it for us and report back results?
It works. It compiles and, after a crash, works.
P.S.: I needed "rpmbuild (...) --without perf" to be able to compile it.
OK. I'll look at turning it back on in a bit.
This is re-enabled with the 3.6.1 build.
kernel-3.6.1-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.6.1-1.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Fixed in kernel-3.6.1-1.fc17
Fedora Bugzappers volunteer triage team
kernel-3.6.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.