Description of problem: Configured kdump on Fedora 12 (guest on VMware Fusion). kexec-tools-2.0.0-28.fc12.x86_64 system-config-kdump-2.0.2-2.fc12.noarch kernel-2.6.31.12-174.2.19.fc12.x86_64 title Fedora (2.6.31.12-174.2.19.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.31.12-174.2.19.fc12.x86_64 ro root=/dev/mapper/VolGroup-lv_root crashkernel=128M initrd /initramfs-2.6.31.12-174.2.19.fc12.x86_64.img couldn't start kdump with: /etc/init.d/kdump start but managed to start it with: sh -x /etc/init.d/kdump start After kdump is operational, I tried to test it with: echo c > /proc/sysrq-trigger panic, reboots, etc... then it seems to block forever at: Waiting for required block device discovery Waiting for sda...
This is a kexec tools problem. Theres not much I can do about it unfortunately until I get the new config mechanism done, until then I have a DISK_TIMEOUT parameter patch that I need to add. I'll get to that shortly.
fixed in -32.fc12
kexec-tools-2.0.0-32.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/kexec-tools-2.0.0-32.fc12
Sorry, an update: I updated fc12, went to sleep, woke up, and retried this. Now it doesn't block at "Waiting for sda", but it stopped at "Available volumes.." part forever.
did you add the appropriate configuration to kdump.conf? If you did and it didn't help, I expect you have found a different issue
Hi Neil, Hmm, what configuration should I be adding to kdump.conf? I'm using the default /var/crash path to store the crash dumps, and /var/crash is on the default / partition. Thanks.
The disk_timeout parameter, see the kdump.conf man page.
Will do that in a moment, thanks.
kexec-tools-2.0.0-32.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.