Op woensdag 3 februari 2016 23:47:06 CET schreef Francesco Montesano:

Hi All,

A few days ago I did dist-upgrade my TW laptop to 20160121 (the last 3 or 4 snapshot all at once) and the computer stopped sleeping. Today (03.02.16) I did an other dist-upgrade and rebooted: just after reboot the computer went to sleep. But now is back to no sleep.

I've tried closing the lid, hit the suspend button, sudo /usr/lib/systemd/systemd-sleep suspend, systemctl suspend to no avail. The pattern is always the same: * screen goes black * leds blink a bit * screen comes back to life with a translucent login screen on top of what I had open before the suspension * the computer freezes for about a minute or more. * then I can log in again.

sudo journalctl shows >400 lines in the couple of minutes that it takes not to go to sleep. Here they are in all their glory: http://paste.opensuse.org/66545417

Anyone has any clue of what's going on and if/how can I get more info?

Besides what shown here, my journalctl output is littered by "kscreen: Primary output" messages:

-> sudo journalctl --since "1 month ago" --no-pager | grep "kscreen: Primary output" | wc -l 25313

[apparently before about one month ago no such messages where passed to the journal]

Should I file a bug report?

Thanks in advance for any help.

Cheers,

Fra I see suspend to RAM failure too. Found it's a kernel bug related to XFS. IIRC the fix is in 4.4.1

-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org