http://bugzilla.novell.com/show_bug.cgi?id=810133
http://bugzilla.novell.com/show_bug.cgi?id=810133#c46
--- Comment #46 from Olav Reinert
You likely need a bit more memory to assign. Try 128M, for example. I needed even more on my machine. Then check the output of "systemctl status kdump". If the status is OK (successfully loaded), then kdump should be able to be triggered in general.
You're right about the memory - assigning 256M makes the kdump service start successfully, as I have verified by "systemctl status kdump". Other than the memory setting, the default settings selected by "yast2 kdump" are used. Nevertheless, when I crash the kernel with "echo c >/proc/sysrq-trigger", it doesn't produce a kernel dump. All I see is the standard stack trace, register dump, etc. I have tested this on both Tumbleweed 20151124 and a fully updated 13.2, with exactly the same behaviour in both cases. No dump ever appears in /var/crash. -- You are receiving this mail because: You are on the CC list for the bug.