http://bugzilla.novell.com/show_bug.cgi?id=957053 Bug ID: 957053 Summary: kdump: fails to dump a crash kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: seroton10@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- 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. -- You are receiving this mail because: You are on the CC list for the bug.