Description of problem: I was setting this machine up to core dump via ssh as all the local partitions are encrypted: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 233.8G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 233.3G 0 part └─luks-38ce91ef-7c74-4fb5-b83f-5523404ca207 253:0 0 233.3G 0 crypt ├─fedora_fante-swap 253:1 0 3.8G 0 lvm [SWAP] ├─fedora_fante-root 253:2 0 50G 0 lvm / └─fedora_fante-home 253:3 0 179.5G 0 lvm /home So I configured everything and also added 'default shell' so that in case of failures I could try and troubleshoot the issue: $ grep -v ^# /etc/kdump.conf ssh root.1.2 sshkey /root/.ssh/kdump_id_rsa core_collector makedumpfile -c --message-level 1 -d 31 default shell What happens is that once I force it to core dump (echo c > /proc/sysrq-trigger) it asks me for my LUKS password and then hangs there for a few minutes and eventually reboots. ssh with the above key and as the root user works ok. Version-Release number of selected component (if applicable): kexec-tools-2.0.4-14.fc20.x86_64 kernel-3.12.5-302.fc20.x86_64 How reproducible: 100% Any hints on how to troubleshoot this one are more than welcome
Might be a bit too late over here. There are some oddities here (asix module not being picked up even when forced), but most likely it is a screwup on my part. Closing