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. I have a rather old Acer Aspire 5920 running fully updated F27 with only KDE loaded. The laptop is plugged in 99% of the time since the battery no longer holds a charge and I don't really need it to be portable. I just tried Suspend to Ram from the KDE menu 5 times and it worked perfectly. This machine has a visual indication when suspend to ram is done in that the power button and another LED will flash amber. Does your system have any sort of visual indication? > > 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? > I have a friend that experienced what I think your seeing. Her laptop would go into suspension (her's also had a visual indicator) but later she found it would at times be rebooting on opening the lid. In her case it turned out to be a HW problem I would think the journal would record at least the start of the suspend sequence. -- 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
