Description of problem:
First noticed during boot with kexec-tools installed,
also happens with manual "service kexec-tools start".
It spins forever chewing CPU.
I found that running /sbin/mkdumprd is where it happens and doing this by hand hits it too.
I've attached the log of running "bash -x /sbin/mkdumprd ..." where it eventually runs "readlink /sys/class/block/sda5" repeatedly forever.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
could you attach that file please? thanks !
Created attachment 413187 [details]
Oops, thought I'd attached it in the initial report.
Created attachment 413462 [details]
patch to fix how we sift through sysfs
looks like I forgot to port a RHEL patch over to Fedora. Let me know if this fixes your problem. Thanks!
With that, the infinite loop is instead:
++ readlink ./device
Created attachment 413521 [details]
sorry, missed a hunk from the backport.
That fixes mkdumprd I guess. It completed. But "service kdump start" is not happy. It just says "FAILED" with no details. syslog gets:
May 12 12:25:46 magilla kdump: No crashkernel parameter specified for running kernel
May 12 12:25:46 magilla kdump: failed to start up
It told you exactly what the problem was:
"No crashkernel parameter specified for running
you need to specify a crashkernel command line parameter on the kernel command line. For x86 system crashkernel=128M is usually sufficient.
I'll commit this change shortly. Thanks!
I'm using what you get out of the box for booting F-13 with kexec-tools installed. I don't want to fiddle kernel parameters by hand. Either it should just work, or it should not be chkconfig on by default.
kexec-tools-2.0.0-35.fc13 has been submitted as an update for Fedora 13.
kexec-tools-2.0.0-35.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.