Open kshepherd opened 4 years ago
Further to this, my systemd sleep.conf
is just all the defaults, as shipped, but I may play around with it to see if I get any different behaviour or clues:
[Sleep]
AllowSuspend=yes
AllowHibernation=yes
AllowSuspendThenHibernate=yes
AllowHybridSleep=yes
SuspendMode=
SuspendState=mem standby freeze
HibernateMode=platform shutdown
HibernateState=disk
HybridSleepMode=suspend platform shutdown
HybridSleepState=disk
HibernateDelaySec=180min
I have the same issue with the same laptop running on PopOs 20.04 and with external monitors connected. I think the problem mostly happens when the laptop is on battery and/not when plugged in.
I get the following error:
PCI post-resume error -19 HC died: cleaning up thunderbolt 000.x.x.x.x failed to send driver ready to ICM iwlwifi 000.x.x.x.x BIOS contains WGDS but no WRDS hub 4-1:1.0: set hub depth failed
I find a sure way to recreate this problem is leaving your device in Suspend or Hibernate mode +2 or more hours System76 Thelio Just installed Pop Os 22.04
After a new install or good cleaning it would last overnight for a short time, a week or two
I am in my 1st week since I stopped using my beautiful desktop for about 8 Mo while dealing with sick family member.
I have added less than 10 apps
Warning for other new users like myself, I am very careful about it working when apparently asleep. heating up without SOMETIMES W/OUT a fan that is probably fixed new user mistakes e.g.loading up to many apps to fast? Sorry I didn't leave a log - had to!! take a year off Learning Linux - must peddle faster I changed my setting carefully, I thought at the time. 3/4 into my 1st year, in effort to solve. I will follow kshepherd excellent example ASAP
Distribution (run
cat /etc/os-release
): NAME="Pop!_OS" VERSION="19.10" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.10" VERSION_ID="19.10" HOME_URL="https://system76.com/pop" SUPPORT_URL="http://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=eoan UBUNTU_CODENAME=eoan LOGO=distributor-logo-pop-osRelated Application and/or Package Version (run
apt policy $PACKAGE NAME
): N/AIssue/Bug Description: When taking laptop out of suspend (eg. opening lid if it was suspended while closed, or waking up with the power button if I manually suspended), the system will sometimes freeze.
I see the last few messages on the console (usually some wifi adaptor warnings), but other than that it is a full system freeze - capslock keys won't toggle, and the normally-blinking _ cursor is frozen. I have included some syslog clues at the end of the report. I'm not yet sure whether it's a case of freezing while attempting to wake up, or something going wrong when it is suspending. The logs do seem to indicate that in the failures, the suspension never really completes properly (although it's hard to tell with this sort of issue because some log writing is obviously paused, waiting to be written once the system is woken up)
I've seen similar reports for other Thinkpads or Lenovos but I thought I'd try to share some more info and logs here about my specific issue.
Steps to reproduce (if you know): Suspend the Thinkpad with the suspend menu option or by closing the lid and waiting for the configured sleep time. Wake the Thinkpad either by opening the lid if closed, or with a tap on the power button if already open.
Expected behavior: The system wakes up and the gnome session is resumed
Other Notes: I have copied in some snippets from syslog with some inline comments. Apologies if it is an annoyingly long paste. Happy to investigate further logs or look into system-sleep or system-suspend debugging if that will help
This first log snippet shows an example of the freezing / failing suspend. Log begins just as I have clicked the suspend button
Here, presumably, is the crash. Nothing appears to have been logged when I pressed the button (though I do at least see the display wake up to show a TTY with some wifi log messages). And indeed, the systemd-sleep process doesn't appear to have actually ended? Or at least didn't get logged as such. As below, you can see I've now cold-restarted the system, so the next lines are startup logs from around 2 minutes later
The second log snippets below show a successful suspend and restart, again beginning at button click
There is no activity in the logs until I wake the system -- this makes sense since the system is suspended! I assume the first set of lines below, referring to stopping devices were just lines queued to be logged.
I tap the power button to wake it up, and apart from the slight confusion around mixed stop/start messages (see above), you can see things do wake up properly
Finally, the system sleep / suspend services report a successful resumption