Created attachment 744028 [details] Serial console output. Description of problem: I'm unable to produce a kdump on Fedora 19 installed in KVM. Version-Release number of selected component (if applicable): kernel-3.9.0-301.fc19-x86_64 kexec-tools-2.0.4-1.fc19-x86_64 dracut-027-45.git20130430.fc19-x86_64 How reproducible: Always. Steps to Reproduce: 1. Install Fedora 19 (used RC4 Alpha) into virt-manager VM. Default disk layout, without LVM, without encryption, ext4 filesystem. 2. In the VM, install kexec-tools. 3. Append "crashkernel=128M" to GRUB_CMDLINE_LINUX variable in /etc/default/grub, run grub2-mkconfig -o /boot/grub2/grub.cfg. 4. Reboot. 5. Edit /etc/kdump.conf to contain (replace the UUID with UUID of your root partition): ext4 UUID=3c1cd5dc-7287-4333-a27f-43ce95aa7650 path /var/crash 6. Run systemctl restart kdump. 7. Run echo c > /proc/sysrq-trigger. Actual results: Virtual machine reboots almost immediately, /var/crash is empty on next boot. Expected results: vmcore saved under /var/crash. Additional info: Attaching serial console output.
Hi, Please add crashkernel_low=64M into your cmdline, and test it again. If you can upgrade your kernel above 3.9-rc8, this problem should have been resolved. Baoquan Thanks
Baoquan, thank you for your quick reply. Adding crashkernel_low=64M to the command line does not seem to change anything. (And if I replace the original crashkernel=128M with it, the line "[ 36.842014] Kernel panic - not syncing: Fatal exception" appears after the usual stack trace and the machine gets stuck instead of reboot.) Also, 3.9.0-301.fc19, isn't it? I tried 3.10.0-0.rc0.git19.1.fc20 but the result seems to be the same: [ 0.000000] do_IRQ: 0.113 No irq handler for vector (irq -1) [ 1.725883] netif_napi_add() called with weight 128 on device eth%d dracut-pre-pivot[89]: ++ KDUMP_PATH=/var/crash dracut-pre-pivot[89]: ++ CORE_COLLECTOR= dracut-pre-pivot[89]: ++ DEFAULT_CORE_COLLECTOR='makedumpfile -c--message-level 1 -d 31' dracut-pre-pivot[89]: ++ DEFAULT_ACTION='reboot -f' dracut-pre-pivot[89]: +++ date +%Y.%m.%d-%T dracut-pre-pivot[89]: ++ DATEDIR=2013.05.07-09:42:16 dracut-pre-pivot[89]: ++ HOST_IP=127.0.0.1 dracut-pre-pivot[89]: ++ DUMP_INSTRUCTION= dracut-pre-pivot[89]: ++ SSH_KEY_LOCATION=/root/.ssh/kdump_id_rsa dracut-pre-pivot[89]: ++ KDUMP_SCRIPT_DIR=/kdumpscripts dracut-pre-pivot[89]: ++ DD_BLKSIZE=512 dracut-pre-pivot[89]: ++ FINAL_ACTION='reboot -f' dracut-pre-pivot[89]: ++ DUMP_RETVAL=0 dracut-pre-pivot[89]: ++ conf_file=/etc/kdump.conf dracut-pre-pivot[89]: ++ KDUMP_PRE= dracut-pre-pivot[89]: ++ KDUMP_POST= dracut-pre-pivot[89]: ++ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/kdumpscripts [ 3.881530] Restarting system.
Instead of "3.9.0-301.fc19, isn't it?" I meant to write "3.9.0-301.fc19 is above 3.9-rc8, isn't it?" ... sorry.
HI Martin, Sorry, in 3.9.0-301.fc19, the crashkernel_low is not needed any more. Normal crashkernel=Y@X is enough. For this problem, it may be caused by NEWROOT bug, could you add NEWROOT=/sysroot at the beginning of /lib/dracut/modules/99kdumpbase/kdump.sh? Sorry for late response. Baoquan Thanks
I can confirm that after editing the file, kdump works correctly. Update to kexec-tools-2.0.4-2.fc19-x86_64 did not seem to solve the issue.
Yeah, it's a dracut issue, a patch has been posted to upstream. Now Dave still discuss with maintainer. Please wait, I will update the info if any progress.