Unlike the KernelSuspend, this time I tried to start the trace, but suspend not via pm-suspend but via closing the lid.
- sudo sh -c "sync && echo 1 > /sys/power/pm_trace
- closed lid
- once system suspended opend the lid
- system frozen. Hard-reset by prressing and holding the power button
- on reboot system appeared to catch fsck which I canceled (good sign RTC is tampered).
- loged-in and captured the dmesg log (see attached as dmesg3.txt)
Chris, I just tried the following:
Unlike the KernelSuspend, this time I tried to start the trace, but suspend not via pm-suspend but via closing the lid.
- sudo sh -c "sync && echo 1 > /sys/power/pm_trace
- closed lid
- once system suspended opend the lid
- system frozen. Hard-reset by prressing and holding the power button
- on reboot system appeared to catch fsck which I canceled (good sign RTC is tampered).
- loged-in and captured the dmesg log (see attached as dmesg3.txt)
:~$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
P0P1 S4 *disabled
LID0 S3 *enabled platform:PNP0C0D:00
EHC1 S0 *enabled pci:0000:00:1d.0
XHC S0 *enabled pci:0000:00:14.0
PXSX S4 *disabled
RP03 S3 *disabled pci:0000:00:1c.0
PEG0 S4 *disabled
PEGP S4 *disabled
PEG1 S4 *disabled
PEG2 S4 *disabled