Shut Down - Reboot Problems

[sgage]

Originally Posted by Fenrin

What happens to the reboot time, if you stop the network service before reboot?

su
service network stop

No difference. Though, instead of the blinking cursor in the upper left, I get an instant "no signal" to the display. But the reboot is still delayed for nearly 2 minutes.

[sgage]

Just for the record:

I booted into last night's Nightly Build Live Desktop, and it shuts down/reboots just fine.

It uses kernel 3.3.4-3 and systemd 44-8.

I'm thinking of installing it to HD to see if it still works properly.

Edit: OK, I installed from the Nightly Build, and shutdown/reboot works fine. What is going on?

[puntarenas]

I ran into this problem after updating an RC1 install a few days ago. This finaly did the trick for me:

# yum distro-sync --enablerepo=updates-testing

Without updates-testing enabled, downgrading network-manager failed with conflicting files in fftw-libs-double.

The bug is dead!

[RupertPupkin]

Originally Posted by RaiTulo

Successfully changed into root pivot.
/shutdoum: 8: /lib/dracut/hooks/shutdoun/30dm-shutdoun.sh: dmsetup: not found
/shutdoun: 9: /lib/dracut/hooks/shutdoun/30md-shutdown.sh: mdadm: not found
/shutdoun: 8: /lib/dracut/hooks/shutdoun/38dm-shutdoun.sh: dmsetup: not found
/shutdoun: 9: /lib/dracut/hooks/shutdown/38md-shutdown.sh: mdadm: not found
/shutdoun: 13: /Hb/dracut/hooks/shutdoun/38md-shutdoun.sh: cat: not found
/shutdoun: 88: /shutdoun: reboot: not found
dracut Warning: Signal caught!

/lib/udev/console_init: 14: /lib/udeu/console_init: kbd.mode: not found
/lib/udev/console_init: 22: /lib/udev/console_init: stty: not found
/lib/udev/console_init: 49: /lib/udev/console_init: setfont: not found
/Iib/udev/console_init: 39: /lib/udev/console_init: loadkeys: not found
Dropping to debug shell.

/shutdoun: 33: /shutdoun: sh: not found

[ 689.7761459 Kernel panic - not syncing: Attempted to kili initt
[ 689.776163] panic occurred, suitching back to text console

I ran into the same problem today doing an ordinary F16 -> F17 upgrade. I did some searching and found this bug: https://bugzilla.redhat.com/show_bug...iple&id=822760
The solution mentioned there worked for me:

dracut -f

After running that as root you'll still get the kernel panic when you reboot immediately afterwards, but it won't happen anymore after that.