Description of problem:
with correct crashkernel settings and kdump.conf in place, service kdump start claims that everything is set up properly (green [OK]).

If you try running kexec -e, it says that nothing has been loaded. Adding -x to the initscript the following line is produced. I tried running it directly in the shell:

$ /sbin/kexec -p --command-line='ro root=/dev/mapper/vg_marathon01-lv_root rd_LVM_LV=vg_marathon01/lv_root rd_LVM_LV=vg_marathon01/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us console=ttyS0,115200n8 console=ttyS0,115200n8 irqpoll maxcpus=1 reset_devices cgroup_disable=memory ' --initrd=/boot/initrd-2.6.32-131.6.1.el6.x86_64kdump.img /boot/vmlinuz-2.6.32-131.6.1.el6.x86_64
UNABLE TO GATHER EFI DATA

$ echo $?
0

So even if kexec can't gather EFI data, it still exits with 0 pretending that everything is correct.

Version-Release number of selected component (if applicable):
kexec-tools-2.0.0-188.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. service kdump start (this must return green [OK])
2. kexec -e does nothing
3. cat /sys/kernel/kexec_loaded shows 0
  
Actual results:
crashkernel not loaded

Expected results:
crashkernel loaded or exit code >0, red [FAILED] etc :)

Additional info:
2.6.32-131.6.1.el6.x86_64

I tried additional kernel params (virtefi, noefi), but still no success in loading the crashkernel.