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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
