i've now reproduced the issue on an untained 4.1.0 kernel (4.1.2-1~exp1). the logged events have been started with `echo mem > /sys/power/state` this time; however, i've seen similar behavior with systemd managed suspends as well (in that case, the system needs the powerkey wakeup described in the earlier mail; a plain /sys/power/state suspend fails without entering that state). a full dmesg output is attached. the suspend event around 5088 (dmesg time stamp) worked, the event around 5114 failed. best regards chrysn -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom
Attachment:
dmesg.out.xz
Description: application/xz
Attachment:
signature.asc
Description: Digital signature