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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead Status in linux package in Ubuntu: Confirmed Bug description: Suspending my machine (Xubuntu Whisker menu/Log out/Suspend) causes it to shut down instead (or at the very least, to restart when powering on again). Observed: after clicking on 'Suspend', the screen blanks, 10 seconds pass, then the machine powers down. When I power up again, it returns to the BIOS post screen, then Xubuntu boot splash screen, then login. Notes: * machine is a recent build, previously running 17.04. Had the same issue (and suspend error messages in syslog), so this does not appear to be related to the 17.10 upgrade. * given the "wpasupplicant failed with error code 254" line in syslog, and following comments in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=835648, I tried removing wpasupplicant from /lib/systemd/system-suspend. This resulted in the machine suspending sooner (no time-out), but suspend still failed. * Separately, I tried switching to the nouveau driver (I'd seem some mentions of problematic proprietary nvidia drivers). This too made no difference. Please let me know if I can provide any other information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: colin 1460 F.... pulseaudio /dev/snd/controlC1: colin 1460 F.... pulseaudio CurrentDesktop: XFCE Date: Sun Oct 29 15:03:36 2017 InstallationDate: Installed on 2017-10-13 (15 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=dcb5dfa5-9644-4b53-be57-ffadb28e8f45 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
