What worked for me was adding a line pointing to my swap space to the
GRUB bootline:
resume=/dev/path/to/swap
Find where your swap is with swapon:
$ swapon -s
I wrote this up here:
On Mon, Jan 27, 2014 at 5:46 AM, Suvayu Ali <fatkasuvayu+linux(a)gmail.com> wrote:
Hi,
I have a new ThinkPad (x240) running 3.12.8-300.fc20.x86_64. I can
suspend it just fine, but I can't resume. This is what I see in the
journal:
Jan 27 03:49:05 localhost systemd[1]: Starting Sleep.
-- Subject: Unit sleep.target has begun with start-up
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun starting up.
Jan 27 03:49:05 localhost systemd[1]: Reached target Sleep.
-- Subject: Unit sleep.target has finished start-up
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has finished starting up.
--
-- The start-up result is done.
Jan 27 03:49:05 localhost systemd[1]: Starting Suspend...
-- Subject: Unit systemd-suspend.service has begun with start-up
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-suspend.service has begun starting up.
Jan 27 03:49:05 localhost systemd[1]: Starting Network Manager Script Dispatcher
Service...
-- Subject: Unit NetworkManager-dispatcher.service has begun with start-up
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Jan 27 03:49:05 localhost dbus-daemon[574]: dbus[574]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Jan 27 03:49:05 localhost dbus[574]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Jan 27 03:49:05 localhost systemd-sleep[29852]: Suspending system...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The system has now entered the suspend sleep state.
After this, I can't see anything when I tried to wake up my laptop. The
next thing I see is when I had to force a reboot.
-- Reboot --
Jan 27 11:51:44 localhost systemd-journal[93]: Runtime journal is using 8.0M (max 383.8M,
leaving 575.8M of free 3.7G, current limit 383.8M).
Jan 27 11:51:44 localhost systemd-journal[93]: Runtime journal is using 8.0M (max 383.8M,
leaving 575.8M of free 3.7G, current limit 383.8M).
Jan 27 11:51:44 localhost kernel: Initializing cgroup subsys cpuset
Jan 27 11:51:44 localhost kernel: Initializing cgroup subsys cpu
Jan 27 11:51:44 localhost kernel: Initializing cgroup subsys cpuacct
... and so on.
How do I debug this? How can I get more information why the resume
fails? Thanks for any ideas.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct:
http://fedoraproject.org/code-of-conduct
Guidelines:
http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away:
http://ask.fedoraproject.org