Red Hat Bugzilla – Bug 1280187
kdump failed to reboot
Last modified: 2015-12-11 02:34:12 EST
Created attachment 1092591 [details]
Description of problem:
After trigger crash,kdump saved vmcore successfully,but failed to reboot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This bug is caused by that systemd refuses to reboot during booting up.
kdump-capture.service will call "reboot" to boot back to first kernel, without executing the following init tasks. But systemd thinks it's a conflict that kdump-capture.service is wanted by initrd.target and initrd.target is implicitly conflicted with shutdown.target (reboot.target), thus refuses to reboot.
initrd ----want---> kdump ----call---> reboot ----requires---> shutdown
OK, a super easy solution: use 'systemctl -f -f reboot' instead of 'reboot'.
We used force reboot previously, but turned to systemd reboot later for safe unmount filesystems etc.
How does one reboot in initrd, is there any example we can refer to?
Another problem is why this only happens in rawhide, what changes cause it.
(In reply to Dave Young from comment #3)
> We used force reboot previously, but turned to systemd reboot later for safe
> unmount filesystems etc.
> How does one reboot in initrd, is there any example we can refer to?
1. Stop all services that are conflicting with "shutdown.target"
2. Call "reboot -f"
"reboot -f" will
1. Send SYSTERM (then SYSKILL) to all processes
2. Unmount all mountpoints and swapoff
3. call "reboot -f -f"
So maybe we can call "reboot -f" since most startup services are oneshots and don't need to be stopped.
Fixed by change reboot to "systemctl reboot -f"
But it originaly works we are still not sure if it is cause by which systemd change and why.
Will clone a bug for systemd for tracking the issue.