On 01/24/18 10:47, InvalidPath wrote: > Fully updated F27, Dell XPS 15 9550. > > So last year on F26 I could safely and reliably suspend to ram from the menu, then > after the upgrade to F27 all that stopped. I just dealt with it until last night. > So Google let em down again with the VAST majority.. if not damned near all of the > results centered around Hibernation. It seems as if Suspending to ram just > magically works for most people. > > So I know that using the menu (KDE Plasma) Suspend to Ram in all fairness just > shuts down. > > Now testing last night I could 'sudo systemctl suspend' and it worked. First tkme > for a minute, second time for 10 and the third overnight. > > Fast-forward to this evening, I ran 'sudo systemctl suspend' upon leaving the > office. Get home and about an hour later I open the lid and it's shut down and > rebooted yet again. > > So my question is, where are the most effective places (logs, config files) to look > to troubleshoot WTF is happening? > Thanks! Oh, also note.... [root@acer log]# systemctl status systemd-suspend.service ● systemd-suspend.service - Suspend Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static; vendor Active: inactive (dead) Docs: man:systemd-suspend.service(8) Jan 24 11:20:44 acer.greshko.com systemd[1]: Starting Suspend... Jan 24 11:20:44 acer.greshko.com systemd-sleep[1713]: Suspending system... Jan 24 11:21:09 acer.greshko.com systemd[1]: Started Suspend. Jan 24 11:31:51 acer.greshko.com systemd[1]: Starting Suspend... Jan 24 11:31:51 acer.greshko.com systemd-sleep[2102]: Suspending system... Jan 24 11:32:21 acer.greshko.com systemd[1]: Started Suspend. So, there is a record of starting the suspends with no errors being record. -- A motto of mine is: When in doubt, try it out
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
