Hide Forgot
If I issue reboot, systemctl isolate reboot.target or systemctl enable reboot.service the reboot process hangs at the moment before it would normally reboot. The system can be heard ticking over in a loop. Only can reboot by physically using the reset button. This may be a duplicate of bug 688658. http://www.smolts.org/client/show/pub_912bfc89-4884-45de-ba54-367e4bd53433
Installed packages: kernel.x86_6 2.6.38.2-9.fc15 systemd.x86_64 21-2.fc15 systemd-units.x86_64 21-2.fc15
Boot with "systemd.log_level=debug systemd.log_target=kmsg rd_NO_PLYMOUTH", remove the "rhgb quiet" params. Then reproduce the failure to reboot and let us know what is displayed on the screen when it hangs. Use a digital camera perhaps.
Created attachment 489365 [details] screenshot 1
Created attachment 489366 [details] Screenshot 2
Created attachment 489367 [details] Screenshot 3 No problem Unfortunately I can't monitor the serial console on this box. I think I am missing some logging after the screen blanks.
Also, if I initiate shutdown the PC shuts down correctly, however on reboot it enters the same loop where the system can be heard ticking over.
Does you system reboot if you run "reboot -f"? And how about "systemctl --force reboot"?
Hmm, so this seems to freeze somewhere after systemd execs /lib/systemd/systemd-shutdown replacing PID1. That tool kills all remaining processes, detaches all file systems, dm devices, loopback devices, swaps. I wonder if something of that causes the freeze. Do you use LVM, or have any other non-traditional storage setup?
Nothing unusual here, 8 partitions over two drives - I have an F14 install on another partition which reboots OK. In reply to comment 7: will try this later - is remote to me at the moment. UUID=30031351-b13b-442c-a781-636659bf7b3a / ext4 defaults 1 1 UUID=fe891bfd-6dda-409f-9fe2-1ea7a38f7f96 /fedora14 ext4 defaults 1 2 UUID=5ccb4f6c-1342-4f56-bc0a-03849e1c0dd5 /home ext3 defaults 1 2 UUID=309cc473-4c2e-4e14-ac0b-a8577bca07fd /rawhide ext4 defaults 1 2 UUID=8916939a-8e96-4125-b22a-77c4309fa383 /wk ext3 defaults 1 2 UUID=5fe6143b-060a-421c-b596-ed600ad90011 /wk2 ext4 defaults 1 2 UUID=12f6ba0e-43b1-4474-973d-8b082f630682 swap swap defaults 0 0 UUID=506991f0-c94e-f390-c24a-12a6b7aec768 swap swap defaults 0 0
Same behaviour with reboot -f
If not even "reboot -f" works, then it is unlikely to be a systemd problem. Reassigning to kernel. Please attach the output of "lspci -vvvnn" and "dmesg". Perhaps it will provide a clue.
Does changing the kernel reboot options help? reboot=b[ios] | s[mp] | t[riple] | k[bd] | e[fi] [, [w]arm | [c]old] | p[ci] warm Don't set the cold reboot flag cold Set the cold reboot flag bios Reboot by jumping through the BIOS (only for X86_32) smp Reboot by executing reset on BSP or other CPU (only for X86_32) triple Force a triple fault (init) kbd Use the keyboard controller. cold reset (default) acpi Use the RESET_REG in the FADT efi Use efi reset_system runtime service pci Use the so-called "PCI reset register", CF9 force Avoid anything that could hang. I would try "reboot=a" or "reboot=t" first.
Thanks for the reply - so far I've tried a/t/p/ with the same result. As mentioned before, if I power off then power on at a alter time, the system does not reboot but needs to be manually reset. Will try e/w/c/k next
This problem disappeared for me with 2.6.38.3-18