0
This procedure has worked for me for years flawlessly:
- Close lid to cause sleep/suspend.
- Undock laptop
- Leave lid closed
- Redock laptop
- Open lid to wakeup/unsuspend/resume/thaw
However, after a recent update (I'm on Debian buster, going from stretch), step #5 above causes the laptop to reboot instead of wakeup.
I'm at a loss to diagnose the problem. The end of /var/log/syslog is always:
Aug 28 18:20:40 robert-linlap NetworkManager[771]: <info> [1567041640.6606] manager: NetworkManager state is now ASLEEP
Aug 28 18:20:40 robert-linlap systemd[1]: Reached target Sleep.
Aug 28 18:20:40 robert-linlap systemd[1]: Starting Suspend...
Aug 28 18:20:40 robert-linlap systemd-sleep[19425]: Suspending system...
I.e., no indication of why there was a restart instead of a waking up.
I'm at a loss how to diagnose what is happening or how to fix it: that is my main motivation behind asking this question.
There is a workaround:
- Leave lid open.
- Undock laptop
- Close lid to cause sleep/suspend
- Open lid to trigger a wakeup/unsuspend
- Dock laptop
- Never close lid :-)
The downside of this workaround is that I have to re-set-up my external monitor configuration; not a big deal, but annoying.
Anyway, again, my goal would be to figure out how to diagnose the problem so that I can fix it, hopefully through looking at a magic log file or turning on some diagnostics.