On a freshly installed Tumbleweed 20151124, I install the yast2 kdump module,
and use it to enable kdump. The only configuration parameter set is the size of
memory allocated to the crash kernel (384M in my case), all other settings are
left at their default values.

After a reboot, the kdump service successfully starts - this is verified using
"systemctl status kdump":

When I run "echo c >/proc/sysrq-trigger" (in a console terminal) to manually
trigger a kernel oops, the usual oops data is printed (cause, module list,
hardware name, register dump, stack dump, call trace, etc.), but then the
system hangs.

Normal behaviour after an oops is that the crash kernel is run, it writtes out
the crash data, and finally the system reboots; but none of these things
happen.

The hardware used for this test is a Dell Latitude D505.