https://bugzilla.novell.com/show_bug.cgi?id=896368 https://bugzilla.novell.com/show_bug.cgi?id=896368#c0 Summary: On triggering crash, system hangs & kdump is not getting generated in /var/crash folder. Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: SLES 12 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: be2net-dev@emulex.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=606075) --> (http://bugzilla.novell.com/attachment.cgi?id=606075) service_kdump_failure User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36 On triggering crash in SLES 12 RC2 OS, the system hangs for eternity and we need to cold boot the system for it to come up. Also observing that the kdump services are failing when we try to restart them. Reproducible: Always Steps to Reproduce: 1. Install SLES 12 RC2 on local hard disk. 2. Enable kdump: chkconfig boot.kdump on 2. Induce a crash by giving the command: echo c > /proc/sysrq-trigger. 3. Observe that the system gets hung and we need to cold boot. 4. Dump is not generated at /var/crash. We observed in the release notes for Sles12 that, the Support for Secure Boot on EFI machines is enabled by default. And the limitations applied as: kexec and kdump are disabled. Although machine hardware does not support a Secureboot, does by default the OS loads into a secureboot mode which is hampering from not collecting the kdump? Actual Results: on triggering the crash, server hangs forever and kdump is not generated. Expected Results: On triggering crash, the kdump data needs to be collected and the machine goes for a reboot. Once it is up, we can see the crash kdump logs at /var/crash folder. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.