FedoraForum.org - Fedora Support Forums and Community
Results 1 to 13 of 13
  1. #1
    Join Date
    Apr 2011
    Posts
    17
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Incorrect shutdown

    I'm using F16 x86_64 on my intel sandy bridge desktop.
    The problem is that sometimes I can't properly shutdown or restart the system. After I try to do so, it prepares for shutdown/restart propely but somewhere just before the actual halt should occur the system stops with blinking text dash in the right left corner. It looks like it is a systemd issue (only a guess), because the system stops right before it halts, when everything is unloaded and even ctrl-alt-del doesn't work.
    This is quite annoying, 'cause I have to press reset button each time I can't shutdown my PC.

    Does anyone have smth to say on this? Maybe already existing bug?

  2. #2
    Join Date
    Jul 2009
    Posts
    1,234
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    I see this sometimes as well with Fedora 15 Gnome 64-bit on my Sandy Bridge laptop. Doesn't happen with Mageia 1 KDE or Arch Linux Xfce on the same laptop. Never really tried to troubleshoot it yet. Haven't had the opportunity to download F16 yet (cellular connection only atm) to give it a spin.
    Fedora 19 Gnome on a ThinkPad X220, i5-2540M CPU, Intel HD Graphics 3000, Intel N 6205 wireless, and Sierra Wireless 754S Mobile Hotspot (AT&T)

  3. #3
    Join Date
    Apr 2011
    Posts
    17
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Looks like the issue is present at least since F15. Sad...

  4. #4
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Yup - it appears to be endemic to systemd. It has known problems with processes not terminating and hanging the shutdown.

    All you can do is log another bug.

  5. #5
    Join Date
    Aug 2009
    Posts
    11,390
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    you may be able to get some idea of where it's hanging if you get a few more log messages at shutdown.

    add these parameters to your kernel line:

    Code:
    systemd.log_level=debug systemd.log_target=kmsg
    Then create a shutdown script and place it in your /lib/systemd/system-shutdown folder (be sure to mark it as executable +x)

    Code:
    #!/bin/sh
    mount / -orw,remount
    dmesg > /dmesg.shutdown
    mount / -oro,remount
    shutdown and wait for the system to hang, then when you reboot, you should have better log messages either in your /var/log/messages or in the file you created with the shutdown script.

  6. #6
    Join Date
    Oct 2006
    Location
    新加坡
    Posts
    1,010
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    I have F16 x86_64 on Intel SNB as well and my system also has this problem. I have the same opinion with jpollard that the problem might be due to a process too stubborn to be terminated gracefully. I don't know which process or whether it is the same process when it happens. Normally my PC shut downs fine, but I believe after I upgraded to F16 I had encountered this problem a number of times already. Not sure it is a new problem in F16 or is it just because of me shutdown/restart too many times while playing with Grub2 + Plymouth ?

    I don't know how to fix it for good but I have one tip for you which works well for me. Instead of pressing the reset button or holding down the power button, you can enable the kernel system request. Set kernel.sysrq to 1 in /etc/sysctl.conf. After that, when the problem occurs, simply press

    Alt+SysRq+e
    to terminate all processes
    Alt+SysRq+i
    to kill all processes

    That should terminate or kill the problematic process.
    Leave no window unbroken ♪ (^。^) 

  7. #7
    Join Date
    Aug 2009
    Posts
    11,390
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Actually, doing it that way, you really want to try and bring it down safer...

    There is a saying.. REISUB

    You hold down the alt+sysrq key and hit the keys, waiting a few seconds between them..

    R - takes control of the keyboard back
    E - terminates process gracefully
    I - Kills remaining processes
    S - flushes data to disk
    U - remounts all filesystems read only
    B - reboots the system.

    Just thought I would add to your suggestion to make it a little safer

  8. #8
    Join Date
    Oct 2006
    Location
    新加坡
    Posts
    1,010
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Actually I started to use the whole complete combo but on one occasion I waited for a few seconds too long and my system shutdown before I had the chance to complete the whole sequence . So, I suppose the E and I are enough to do the trick. The last two request only makes sense if you want to restart in the first place instead of shutdown. But yes that the combo that I use whenever my Fedora system miss behaves .
    Leave no window unbroken ♪ (^。^) 

  9. #9
    Join Date
    Aug 2009
    Posts
    11,390
    Mentioned
    98 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    I believe you would want the S in there as well, to make sure any data left in the buffers is written to disk.

    But other than that, I agree, the rest is mainly if you intend to reboot instead of shutting down.

  10. #10
    Join Date
    Apr 2011
    Posts
    17
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Well, there is some update. I looked down in /var/log/messages and the last lines are:

    Dec 21 09:06:30 localhost NetworkManager[829]: <info> (wlan0): IP6 addrconf timed out or failed.
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> (wlan0): IP6 addrconf timed out or failed.
    Dec 21 09:06:30 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
    Dec 21 09:06:30 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) started...
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) started...
    Dec 21 09:06:30 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    Dec 21 09:06:30 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
    Dec 21 09:06:30 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    Dec 21 09:06:30 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    Dec 21 09:06:30 localhost avahi-daemon[850]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.33.
    Dec 21 09:06:30 localhost avahi-daemon[850]: New relevant interface wlan0.IPv4 for mDNS.
    Dec 21 09:06:30 localhost avahi-daemon[850]: Registering new address record for 192.168.1.33 on wlan0.IPv4.
    Dec 21 09:06:31 localhost NetworkManager[829]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Dec 21 09:06:31 localhost NetworkManager[829]: NetworkManager[829]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Dec 21 09:06:31 localhost NetworkManager[829]: <info> Policy set 'Автоматическое Rukka' (wlan0) as default for IPv4 routing and DNS.
    Dec 21 09:06:31 localhost NetworkManager[829]: NetworkManager[829]: <info> Policy set 'Автоматическое Rukka' (wlan0) as default for IPv4 routing and DNS.
    Dec 21 09:06:31 localhost NetworkManager[829]: <info> Activation (wlan0) successful, device activated.
    Dec 21 09:06:31 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) successful, device activated.
    Dec 21 09:06:31 localhost NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    Dec 21 09:06:31 localhost dbus[864]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
    Dec 21 09:06:31 localhost NetworkManager[829]: NetworkManager[829]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    Dec 21 09:06:31 localhost dbus-daemon[864]: dbus[864]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
    Dec 21 09:06:31 localhost dbus[864]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Dec 21 09:06:31 localhost dbus-daemon[864]: dbus[864]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    Dec 21 09:06:32 localhost systemd[1]: iscsi.service: control process exited, code=exited status=3
    Dec 21 09:06:32 localhost systemd[1]: Unit iscsi.service entered failed state.
    Dec 21 09:06:32 localhost dbus-daemon[864]: Starting iscsi (via systemctl): Job failed. See system logs and 'systemctl status' for details.
    Dec 21 09:06:32 localhost dbus-daemon[864]: [FAILED]
    Dec 21 09:06:32 localhost nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/04-iscsi' exited with error status 1.
    Dec 21 09:06:32 localhost dbus-daemon[864]: Mounting other filesystems: [ OK ]
    Dec 21 09:06:32 localhost systemd[1]: PID 1064 read from file /run/sm-client.pid does not exist. Your service or init script might be broken.
    Dec 21 09:06:32 localhost nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' exited with error status 3.
    Something wrong with my NetworkManager?

  11. #11
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    Looks to me like systemd tried to restart everything and failed.

    Granted most of the messages are from NetworkManager restart failures, but there is also the iscsi failure, dbus-daemon message "Mounting other filesystems [OK]...

    In some cases, it could be that the order of shutdown is wrong. If you aren't using iscsi for instance, it shouldn't even try. If you are using it, then it should be shutdown before NetworkManager... and it is possible that NetworkManager attempted to restart because iscsi wanted the network...

  12. #12
    Join Date
    Apr 2011
    Posts
    17
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    I don't use iscsi. I guess I should disable some of systemd services. Are they still controlled via system-config-services?

  13. #13
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,343
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Incorrect shutdown

    They should be. You can also query the services to see if they are enabled
    "systemctl list-units" should show whether they are enabled.

    Though why it would try to start things that are disabled is unknown.

Similar Threads

  1. Replies: 1
    Last Post: 18th March 2008, 06:00 PM
  2. Replies: 5
    Last Post: 19th November 2007, 12:00 PM
  3. Replies: 2
    Last Post: 12th February 2007, 07:07 PM
  4. How to hide FC6 shutdown messages or use shutdown spash
    By renjoyhenry in forum Using Fedora
    Replies: 0
    Last Post: 5th November 2006, 06:09 AM
  5. Shutdown -h vs. Poweroff / Shutdown -r vs. Reboot
    By aab45 in forum Using Fedora
    Replies: 1
    Last Post: 19th July 2005, 01:29 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •