Shut Down - Reboot Problems

Magickman · #1 26th April 2012, 02:59 PM

Running Fedora 17 86_64 KDE. Starting yesterday, Fedora will not halt, or reboot. The KDE window disappears, but only a blinking cursor in the top leaft corner of the screen shows. I have two Kernels, the default one that came with the install, and the one that came with the update. Tried them both, same results. Is this a bug? Is there a work around for it?

nonamedotc · #2 26th April 2012, 04:31 PM

Are you sure about this? I thought I had the same problem last night - but it turned out reboot was just incredibly slow - it took full 2-3 minutes for that blinking cursor to vanish and messages to appear.

Is this not the case with your install? I am using F17 x86_64 GNOME.

Boricua · #3 26th April 2012, 05:22 PM

I have seen exactly that same behavior using Gnome. Next time I will wait a little longer to see if it actually reboots.

Fenrin · #4 26th April 2012, 07:37 PM

I have experienced the same the last two days. Also something I noticed was that my opera bookmarks and liferea feedlist was broken, maybe this data loss is related to the messy shutdown (with the bookmarks it happend three times so far). I use xfs filesystem for my home partition.
I would report this bookmarks and feedlist data loss as bug, but I have no idea how to reproduce nor because of which component these data loss happens.

---------- Post added at 08:37 PM ---------- Previous post was at 07:24 PM ----------

It looks like systemd versions 44-6 and 44-7 both have any bug which didn't let my system reboot or halt. After downgrading to 44-5 it seems to work again

I opened a bugreport here: https://bugzilla.redhat.com/show_bug.cgi?id=816714

I have no idea how to reproduce this issue exactly, it seems that most F17 testers with systemd 44-6 or 44-7 don't have this issue.

hadrons123 · #5 27th April 2012, 02:52 AM

It happens to me too. But I just do a hard reset.

But its random . Sometimes it does shutdown real fast.

***DBelton*** · #6 27th April 2012, 03:58 AM

I believe it was fixed in the update for tonight.

Systemd had an update and seems to have corrected the slow shutdown issue for me.

nonamedotc · #7 27th April 2012, 04:39 AM

That would definitely be a relief! I have not updated yet - The bug remains open still though?

***DBelton*** · #8 27th April 2012, 05:23 AM

Interesting..

The bug report specifies that systemd 44-6 and 44-7 both had the hang at shutdown.

On my system here, systemd 44-6 hung on shutdown and 44-7 fixed it.

44-7 is the update that I got tonight, and fixed it here. All I can tell you is to try the update and see if it fixes it for you.

Fenrin · #9 27th April 2012, 04:05 PM

I tested version 44-7 again. One time it worked and then it didn't work two times in a row. Seems to me like the bug is still not fixed.

Magickman · #10 28th April 2012, 03:19 AM

I am still not sure what happened. I took the advive of the member who suggested leaving the cursor blink and see if it would shut down. Well, I had an update this morning, Apper and a few other programs, and clicked to reboot. When the cursor started, I got up and went to use the bathroom, and get a soda. When I got back, about 5 minutes later, the machine had in fact rebooted. So, I logged in, checked for updates, and again rebooted. Fedora now shuts down amazingly fast! I don't believe I have ever seen any Linux Distro shut down that fast. Somehow, the problem fixed itself.

Riotvan · #11 28th April 2012, 11:46 AM

Same problem after all the latest updates, sometimes it works but mostly it does not.

RaiTulo · #12 28th April 2012, 05:15 PM

Quote:

Originally Posted by Riotvan

Same problem after all the latest updates, sometimes it works but mostly it does not.

Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting f Ile systems.
Unmounted /sys/kernel/config.
Unmounted /sys/kerne1/security.
Unmounted /deu/hugepages.
Unmounted /dev/mqueue.
Unmounted /sys/kerne1/debug.
Disabling swaps.
Detaching loop devices.
Detaching DM devices.
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

(F16 to F17 PreUpgrade)

RupertPupkin · #13 24th May 2012, 05:57 PM

Quote:

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:

Code:

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.

Magickman · #14 28th April 2012, 11:03 PM

Preupgrade is something I failed at. Mine is a DVD fresh install. It still hangs for a few seconds sometimes, but mostly reboots, or shuts down fast.

mkudro · #15 29th April 2012, 03:28 PM

Hi everyone,
I did fresh network installation last night, my reboot is extremely slow (2-3 minutes) every time. On top of that sometimes my wireless network seems to be disabled when i reboot the system, and only when i turn WiFi off and on again (hardware button), network manager only then connects to network. But this is not every time.
Same goes for normal boot - very slow with same network issues.