[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Yes - I installed Windows 10 on the machine last night to experiment with something else, and saw that I have the same problem with Windows, so must be BIOS related. Thanks for your help and sorry for the wild goose chase, I'll close this ticket. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Thanks - for each of freezer, devices, platform, processors, and core, I was able to run './analyze_suspend.py -rtcwake 20 -f -m mem' and the machine suspends and resumes successfully. When I again return /sys/power/pm_test to none, it doesn't (same behaviour as before). I can upload the output of analyze_suspend.py if they'll be useful (I don't know if they will be, given that they show successful suspends and resumes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
** Attachment added: "dmesg.20171104-0801.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+attachment/5003445/+files/dmesg.20171104-0801.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
** Attachment added: "dmesg.20171104-0757.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+attachment/5003444/+files/dmesg.20171104-0757.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
** Attachment added: "syslog-201711040722.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+attachment/5003443/+files/syslog-201711040722.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
None of the steps in Ch4 of the document describe my problem. The closest is "4.4 System reboots during suspend/resume", but that section's description is "Screen goes dark, and a fresh boot starts without users doing anything" does not describe what happens to me. What I observe is: 1. I choose to suspend (via Xfce menu, or rtcwake) 2. machine powers down. Suspend _appears_ successful (final line per syslog is "systemd-sleep[2160]: Suspending system..." 3. the machine does _not_ automatically reboot. It stays suspended until I power on (or rtcwake alarm). 3. when starting up again, the machine boots instead of resuming. I see the BIOS post screen, then kernel start-up output, then a login prompt. It is clear that the machine has not resumed, since all open processes have closed and syslog and dmesg show that the machine has booted. I have thus far done the following: 1. added 'initcall_debug ignore_loglevel pm_async' to my grub config (confirmed by subsequent syslog output). 2. tested suspend/resume using Xubuntu whisker menu and then later pressing power button to resume. The problem persists. See attached syslog-201711040722.txt for syslog output. Final suspend and then startup lines are: -- Nov 4 07:21:27 maude systemd-sleep[2160]: Selected interface 'p2p-dev-wlp37s0' Nov 4 07:21:27 maude systemd-sleep[2160]: 'SUSPEND' command timed out. Nov 4 07:21:27 maude systemd-sleep[2165]: /lib/systemd/system-sleep/wpasupplicant failed with error code 254. Nov 4 07:21:27 maude systemd-sleep[2160]: Suspending system... Nov 4 07:22:06 maude rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="926" x-info="http://www.rsyslog.com";] start Nov 4 07:22:06 maude rsyslogd: rsyslogd's groupid changed to 108 Nov 4 07:22:06 maude rsyslogd: rsyslogd's userid changed to 104 -- I see numerous syscalls returning with non-0 values but I cannot tell if any are pertinent. 3. I tested with rtcwake -m mem -s 20. - after 20s the machine powered up again, but booted instead of resuming. (ie. the problem persists). - there is no 'suspend' output to syslog prior to suspending. I have attached dmesg.20171104-0757.txt 4. I downloaded and tested with analyse_suspend.py, running ./analyze_suspend.py -rtcwake 20 -f -m mem. - after the 20s system boots instead of resuming (as above) - the script had created a directory suspend-171104-080126, but since it boots instead of resuming, none of the files are written to that directory - it is empty. - I have attached dmesg.20171104-0801.txt. I'm happy to try other steps or provide other info, but don't have cables to try console debugging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Please follow the steps in [1], report which step failed. [1] https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend /hibernate-issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Suspend has never worked on this machine - I started with 17.04 early October and upgraded to 17.10 last week. I've just tested with a mainline kernel (4.14.0-041400rc7-generic #201710292231 SMP Sun Oct 29 22:32:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) - suspending still results in same behaviour. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Relevant lines from /var/log/syslog: Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1000] manager: sleep requested (sleeping: no enabled: yes) Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1000] manager: sleeping... Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1002] manager: NetworkManager state is now ASLEEP Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1005] device (wlp37s0): state change: activated -> deactivating (reas on 'sleeping', internal state 'managed') Oct 29 14:49:35 maude whoopsie[1303]: [14:49:35] offline Oct 29 14:49:35 maude dbus[981]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedes ktop.nm-dispatcher.service' Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1044] device (wlp37s0): state change: deactivating -> disconnected (r eason 'sleeping', internal state 'managed') Oct 29 14:49:35 maude avahi-daemon[969]: Withdrawing address record for fe80::7baf:22da:f32e:783d on wlp37s0. Oct 29 14:49:35 maude avahi-daemon[969]: Leaving mDNS multicast group on interface wlp37s0.IPv6 with address fe80::7baf:22da:f32e:783 d. Oct 29 14:49:35 maude avahi-daemon[969]: Interface wlp37s0.IPv6 no longer relevant for mDNS. Oct 29 14:49:35 maude kernel: [ 61.400711] wlp37s0: deauthenticating from 40:0d:10:44:cc:bf by local choice (Reason: 3=DEAUTH_LEAVI NG) Oct 29 14:49:35 maude systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 29 14:49:35 maude kernel: [ 61.406292] wlp37s0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22) Oct 29 14:49:35 maude wpa_supplicant[1134]: wlp37s0: CTRL-EVENT-DISCONNECTED bssid=40:0d:10:44:cc:bf reason=3 locally_generated=1 Oct 29 14:49:35 maude avahi-daemon[969]: Withdrawing address record for 192.168.0.16 on wlp37s0. Oct 29 14:49:35 maude avahi-daemon[969]: Leaving mDNS multicast group on interface wlp37s0.IPv4 with address 192.168.0.16. Oct 29 14:49:35 maude avahi-daemon[969]: Interface wlp37s0.IPv4 no longer relevant for mDNS. Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1133] sup-iface[0x564a54e79650,wlp37s0]: connection disconnected (rea son -3) Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1135] device (wlp37s0): supplicant interface state: completed -> disc onnected Oct 29 14:49:35 maude NetworkManager[1007]: [1509288575.1138] device (wlp37s0): state change: disconnected -> unmanaged (reas on 'sleeping', internal state 'managed') Oct 29 14:49:35 maude wpa_supplicant[1134]: nl80211: deinit ifname=p2p-dev-wlp37s0 disabled_11b_rates=0 Oct 29 14:49:35 maude dbus[981]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 29 14:49:35 maude nm-dispatcher: req:1 'connectivity-change': new request (1 scripts) Oct 29 14:49:35 maude nm-dispatcher: req:1 'connectivity-change': start running ordered scripts... Oct 29 14:49:35 maude nm-dispatcher: req:2 'down' [wlp37s0]: new request (1 scripts) Oct 29 14:49:35 maude nm-dispatcher: req:2 'down' [wlp37s0]: start running ordered scripts... Oct 29 14:49:35 maude whoopsie[1303]: [14:49:35] Cannot reach: https://daisy.ubuntu.com Oct 29 14:49:35 maude whoopsie[1303]: [14:49:35] Cannot reach: https://daisy.ubuntu.com Oct 29 14:49:35 maude systemd[1]: Started Network Manager Script Dispatcher Service. Oct 29 14:49:35 maude systemd[1]: Reached target Sleep. Oct 29 14:49:35 maude systemd[1]: Starting Suspend... Oct 29 14:49:35 maude systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 29 14:49:35 maude systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 29 14:49:35 maude wpa_supplicant[1134]: nl80211: deinit ifname=wlp37s0 disabled_11b_rates=0 Oct 29 14:49:37 maude lightdm[1069]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 29 14:49:37 maude systemd[1]: Created slice User Slice of lightdm. Oct 29 14:49:37 maude systemd[1]: Starting User Manager for UID 111... Oct 29 14:49:37 maude systemd[1]: Started Session c3 of user lightdm. Oct 29 14:49:37 maude systemd[2761]: Reached target Timers. Oct 29 14:49:37 maude systemd[2761]: Starting D-Bus User Message Bus Socket. Oct 29 14:49:37 maude systemd[2761]: Reached target Paths. Oct 29 14:49:37 maude systemd[2761]: Listening on D-Bus User Message Bus Socket. Oct 29 14:49:37 maude systemd[2761]: Reached target Sockets. Oct 29 14:49:37 maude systemd[2761]: Reached target Basic System. Oct 29 14:49:37 maude systemd[2761]: Reached target Default. Oct 29 14:49:37 maude systemd[2761]: Startup finished in 19ms. Oct 29 14:49:37 maude systemd[1]: Started User Manager for UID 111. Oct 29 14:49:37 maude systemd[2761]: Started D-Bus User Message Bus. Oct 29 14:49:37 maude dbus-daemon[2780]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' Oct 29 14:49:37 maude systemd[2761]: Starting Virtual filesystem service... Oct 29 14:49:37 maude org.a11y.atspi.Registry[2782]: SpiRegistry daemon is running with well-kno
