Re: Issues resuming from hibernation
On Saturday, December 24, 2016 2:08:57 PM CET solitone wrote:
> One think I've noticed just today is that now neither hibernation to disk
> nor suspension to RAM work as expected. The laptop goes to sleep, but
> immediately after it automatically resumes without any input from me.
This depends on the lid being open. If I close the lid, the laptop goes to
suspend (thanks to KDE's settings) and stays there. In contrast, when I
suspend from KDE's menu, it suspends but it wakes up immediately after.
I had a look at /proc/acpi/wakeup:
solitone@alan:~$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG0 S3 *disabled
EC S4 *disabled platform:PNP0C09:00
HDEF S3 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
RP02 S3 *disabled pci:0000:00:1c.1
RP03 S3 *disabled pci:0000:00:1c.2
ARPT S4 *enabled pci:0000:03:00.0
RP05 S3 *disabled pci:0000:00:1c.4
RP06 S3 *disabled pci:0000:00:1c.5
SPIT S3 *disabled
XHC1 S3 *enabled pci:0000:00:14.0
ADP1 S4 *disabled platform:ACPI0003:00
LID0 S4 *enabled platform:PNP0C0D:00
So I decided to disable waking up through the lid:
solitone@alan:~$ sudo sh -c "echo LID0 > /proc/acpi/wakeup"
solitone@alan:~$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG0 S3 *disabled
EC S4 *disabled platform:PNP0C09:00
HDEF S3 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
RP02 S3 *disabled pci:0000:00:1c.1
RP03 S3 *disabled pci:0000:00:1c.2
ARPT S4 *enabled pci:0000:03:00.0
RP05 S3 *disabled pci:0000:00:1c.4
RP06 S3 *disabled pci:0000:00:1c.5
SPIT S3 *disabled
XHC1 S3 *enabled pci:0000:00:14.0
ADP1 S4 *disabled platform:ACPI0003:00
LID0 S4 *disabled platform:PNP0C0D:00
Now when I suspend or hibernate with the menu entry it doesn't wake up unless
I press a key or touch the trackpad (when suspended) or press the power button
(when hibernated), as expected. Nice!
> I'm sure some days ago this did not happen. It might be a side effect from
> some recent package upgrade.
Mmm.. most likely I didn't remember it right. Perhaps I never tested it very
carefully, and simply didn't notice the issue.
Reply to: