http://bugzilla.opensuse.org/show_bug.cgi?id=1172670 Bug ID: 1172670 Summary: kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: shung-hsi.yu@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 838585 --> http://bugzilla.opensuse.org/attachment.cgi?id=838585&action=edit journalctl output (colored) The system is configured to capture core dump on crash with `yast2 kdump`. This is confirmed by looking at /proc/cmdline (contains ' crashkernel=256M,high crashkernel=72M,low'), output of `dmesg`, and the status of kdump.service. Triggering a crash dump manually with `echo c >/proc/sysrq-trigger` shows the stacktrace, but fails to correctly boot up the dump-capturing kernel. Below is an excerpt of the output of `journalctl` before the emergency shell was started. Jun 08 14:13:35 localhost systemd[1]: Starting Switch Root... Jun 08 14:13:35 localhost systemctl[377]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. Jun 08 14:13:35 localhost systemd[1]: Failed to start Switch Root. Jun 08 14:13:35 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= d ependencies. Jun 08 14:13:35 localhost systemd[1]: Starting Setup Virtual Console... Jun 08 14:13:35 localhost systemd[1]: Finished Setup Virtual Console. Jun 08 14:13:35 localhost systemd[1]: Started Emergency Shell. Jun 08 14:13:35 localhost systemd[1]: Reached target Emergency Mode. This issue looks a bit similar to https://bugzilla.redhat.com/show_bug.cgi?id=1812393 but I'm not too sure. -- You are receiving this mail because: You are the assignee for the bug.