resume failed for the 2nd time since I upgraded to F18

Julian Sikorski belegdol at gmail.com
Sat Dec 15 09:02:45 UTC 2012


Hi,

since I upgraded to F18, resume from S3 has failed for me 2 times
already. It worked many more times, but still it is a bit concerning,
and also makes it way harder to pinpoint. All I can see in the logs is this:

Dec 15 04:19:55 snowball2 systemd-logind[753]: Lid closed.
Dec 15 04:19:55 snowball2 systemd-logind[753]: Suspending...
Dec 15 04:19:57 snowball2 systemd[1]: SELinux Got Sender :1.0
Dec 15 04:19:57 snowball2 systemd[1]: Starting Sleep.
Dec 15 04:19:57 snowball2 systemd[1]: Reached target Sleep.
Dec 15 04:19:57 snowball2 systemd[1]: Starting Suspend...
Dec 15 04:19:57 snowball2 systemd-sleep[8033]:
/usr/lib/systemd/system-sleep/notify-upower.sh exited with exit status 1.
Dec 15 04:19:57 snowball2 systemd-sleep[8033]: Suspending system...

When I tried to resume the machine in the morning, all I could see was a
blinking cursor. Where should I look in order to debug this problem and
investigate what is going on?

Regards,
Julian


More information about the test mailing list