Description of problem: NFS Root computer no longer enters suspend correctly. Seems to suspend the network first so the rest cannot proceed. This was working perfectly prior to the yum upgrade. Tried a yum downgrade of systemd that did not help. Update of Fedora 20 that updated these packages: abrt.i686 0:2.2.0-1.fc20 abrt-addon-ccpp.i686 0:2.2.0-1.fc20 abrt-addon-kerneloops.i686 0:2.2.0-1.fc20 abrt-addon-pstoreoops.i686 0:2.2.0-1.fc20 abrt-addon-python.i686 0:2.2.0-1.fc20 abrt-addon-vmcore.i686 0:2.2.0-1.fc20 abrt-addon-xorg.i686 0:2.2.0-1.fc20 abrt-dbus.i686 0:2.2.0-1.fc20 abrt-desktop.i686 0:2.2.0-1.fc20 abrt-gui.i686 0:2.2.0-1.fc20 abrt-gui-libs.i686 0:2.2.0-1.fc20 abrt-libs.i686 0:2.2.0-1.fc20 abrt-plugin-bodhi.i686 0:2.2.0-1.fc20 abrt-python.i686 0:2.2.0-1.fc20 abrt-retrace-client.i686 0:2.2.0-1.fc20 control-center.i686 1:3.10.3-1.fc20 control-center-filesystem.i686 1:3.10.3-1.fc20 coreutils.i686 0:8.21-21.fc20 cryptsetup.i686 0:1.6.4-1.fc20 cryptsetup-libs.i686 0:1.6.4-1.fc20 cryptsetup-python.i686 0:1.6.4-1.fc20 cups.i686 1:1.7.1-6.fc20 cups-filesystem.noarch 1:1.7.1-6.fc20 cups-libs.i686 1:1.7.1-6.fc20 curl.i686 0:7.32.0-6.fc20 file.i686 0:5.14-17.fc20 file-libs.i686 0:5.14-17.fc20 fltk.i686 0:1.3.2-4.fc20 gnutls.i686 0:3.1.20-4.fc20 hicolor-icon-theme.noarch 0:0.13-1.fc20 iproute.i686 0:3.12.0-2.fc20 kernel-headers.i686 0:3.13.6-200.fc20 langtable.noarch 0:0.0.24-1.fc20 langtable-data.noarch 0:0.0.24-1.fc20 langtable-python.noarch 0:0.0.24-1.fc20 libcurl.i686 0:7.32.0-6.fc20 libdrm.i686 0:2.4.52-1.fc20 libgudev1.i686 0:208-15.fc20 librepo.i686 0:1.6.0-1.fc20 libreport.i686 0:2.2.0-1.fc20 libreport-anaconda.i686 0:2.2.0-1.fc20 libreport-cli.i686 0:2.2.0-1.fc20 libreport-fedora.i686 0:2.2.0-1.fc20 libreport-filesystem.i686 0:2.2.0-1.fc20 libreport-gtk.i686 0:2.2.0-1.fc20 libreport-plugin-bugzilla.i686 0:2.2.0-1.fc20 libreport-plugin-kerneloops.i686 0:2.2.0-1.fc20 libreport-plugin-logger.i686 0:2.2.0-1.fc20 libreport-plugin-reportuploader.i686 0:2.2.0-1.fc20 libreport-plugin-ureport.i686 0:2.2.0-1.fc20 libreport-python.i686 0:2.2.0-1.fc20 libreport-web.i686 0:2.2.0-1.fc20 mariadb-libs.i686 1:5.5.36-1.fc20 nss.i686 0:3.15.5-1.fc20 nss-softokn.i686 0:3.15.5-2.fc20 nss-softokn-freebl.i686 0:3.15.5-2.fc20 nss-sysinit.i686 0:3.15.5-1.fc20 nss-tools.i686 0:3.15.5-1.fc20 nss-util.i686 0:3.15.5-1.fc20 ntfs-3g.i686 2:2014.2.15-1.fc20 ntfsprogs.i686 2:2014.2.15-1.fc20 python-librepo.i686 0:1.6.0-1.fc20 simple-scan.i686 0:3.10.2-1.fc20 systemd.i686 0:208-15.fc20 systemd-libs.i686 0:208-15.fc20 systemd-python.i686 0:208-15.fc20 vpnc.i686 0:0.5.3-20.svn457.fc20 vpnc-script.noarch 0:0.5.3-20.svn457.fc20 xorg-x11-drv-wacom.i686 0:0.23.0-4.fc20 xorg-x11-server-Xephyr.i686 0:1.14.4-7.fc20 xorg-x11-server-Xorg.i686 0:1.14.4-7.fc20 xorg-x11-server-Xvfb.i686 0:1.14.4-7.fc20 Version-Release number of selected component (if applicable): How reproducible: Every time suspend is initiated. pm-suspend hangs immediately and eventually starts complaining about the nfs root server Steps to Reproduce: 1. pm-suspend 2. 3. Actual results: Computer hangs and must be reset. Expected results: Clean suspend and return from suspend. Additional info:
Another yum update and a bit more testing, pm-suspend & systemctl suspend works correctly, systemctl suspend seems to recover better than pm-suspend. but dbus-send --system --print-reply --dest="org.freedesktop.login1" /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true drops the network first and cannot be recovered. I've changed my script to use systemctl suspend instead of dbus-send. Strange how dbus-send... was working fine prior to the update the other day.
Found it. NetworkManager was installed but disabled orginally. After the update NetworkManager was re-enabled which must drop the network early in the suspend cycle which then drops access to the filesystems. systemctl disable NetworkManager returned the original good behaviour
There is pm-suspend that is "Syncing filesystems" after NetworkManager had already put the network down, while NFS still needs the network to do that fsync operation. On console there were following messages: [ 516.704955] PM: Syncing filesystems ... [ 705.824039] nfs: server srv1 not responding, still trying The almost 190 sec delay is quite consistent between messages. In journal the entries landed with same timestamps for some reason: Nov 03 15:31:58 client1 kernel: PM: Syncing filesystems ... Nov 03 15:31:58 client1 kernel: nfs: server srv1 not responding, still trying It look like syncing in advance (before NetworkManager had put network down) and letting pm-suspend do the sync again later (with nothing to write via network) should save the situation. The only problem is to force NFS start blocking all write requests, before initial sync operation. Any ideas of how to request NFS do that?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.