Re: Can't resume ThinkPad from suspend
On Wed, Jan 29, 2014 at 08:31:23PM +0100, poma wrote: On 29.01.2014 17:59, Steven Rosenberg wrote: 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 SWAP != RAM I'm pretty sure Suvayu wrote systemd-suspend.service i.e. about S3. ;) Indeed, I meant suspend to RAM, not suspend to disk (or hibernation). -- Suvayu Open source is the future. It sets us free. -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
Hi, On Tue, Jan 28, 2014 at 04:44:06PM +0100, poma wrote: On 28.01.2014 14:10, Suvayu Ali wrote: On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: On 27.01.2014 14:46, Suvayu Ali wrote: … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg - ACPI PM Same problem, can't resume. Have to force a reboot. # grep CONFIG_PM_DEBUG /boot/config-$(uname -r) CONFIG_PM_DEBUG=y # cat /sys/power/pm_test [none] core processors platform devices freezer # echo core /sys/power/pm_test # cat /sys/power/pm_test none [core] processors platform devices freezer # dmesg dmesg_before-S3-core; echo mem /sys/power/state; dmesg dmesg_after-resume-core # echo processors /sys/power/pm_test # cat /sys/power/pm_test none core [processors] platform devices freezer # dmesg dmesg_before-S3-procs; echo mem /sys/power/state; dmesg dmesg_after-resume-procs # echo devices /sys/power/pm_test # cat /sys/power/pm_test none core processors platform [devices] freezer # dmesg dmesg_before-S3-devices; echo mem /sys/power/state; dmesg dmesg_after-resume-devices I am a bit preoccupied with other immediate things. I'll get to this problem in a week, and report back how things go. Thank you very much for these pointers! -- Suvayu Open source is the future. It sets us free. -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
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: http://stevenrosenberg.net/blog/linux/fedora/2014_0118_suspend_resume_in_fedora_20 -- Steven Rosenberg http://stevenrosenberg.net/blog http://blogs.dailynews.com/click On Mon, Jan 27, 2014 at 5:46 AM, Suvayu Ali fatkasuvayu+li...@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@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 -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On 29.01.2014 17:59, Steven Rosenberg wrote: 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 SWAP != RAM I'm pretty sure Suvayu wrote systemd-suspend.service i.e. about S3. ;) $ man 8 systemd-suspend.service S3 != S4 S3 == Suspend to RAM(STR) aka Suspension S4 == Suspend to Disk(STD) aka Hibernation Resume == Wake up from S3 Thaw == Wake up from S4 It's common for people to mix all these expressions, hence the confusion. I wrote this up here: http://stevenrosenberg.net/blog/linux/fedora/2014_0118_suspend_resume_in_fedora_20 man 7 dracut.kernel i.e. man 7 dracut.cmdline man 5 dracut.conf - add_device+= /dev/disk/by-uuid/… for swap on LVM, encrypted and RAID1 slices. Besides for me 'thaw' works without that directive, when it works at all. :) poma -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: On 27.01.2014 14:46, Suvayu Ali wrote: … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg - ACPI PM Same problem, can't resume. Have to force a reboot. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On Mon, Jan 27, 2014 at 01:51:41PM +, Hiren Joshi wrote: I had a similar issue when I moved to the 3.12 kernel, this may be unrelated. If you have NVidia and the nouveau driver installed, the workaround: https://ask.fedoraproject.org/en/question/37476/fedora-20-unable-to-boot-after-update-from-kernel-311-to-kernel-312-nouveau-issue/ nouveau.runpm=0 worked. But as I say, your problem may be entirely different. It is a ThinkPad with Intel graphics. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On 28.01.2014 14:10, Suvayu Ali wrote: On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: On 27.01.2014 14:46, Suvayu Ali wrote: … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg - ACPI PM Same problem, can't resume. Have to force a reboot. # grep CONFIG_PM_DEBUG /boot/config-$(uname -r) CONFIG_PM_DEBUG=y # cat /sys/power/pm_test [none] core processors platform devices freezer # echo core /sys/power/pm_test # cat /sys/power/pm_test none [core] processors platform devices freezer # dmesg dmesg_before-S3-core; echo mem /sys/power/state; dmesg dmesg_after-resume-core # echo processors /sys/power/pm_test # cat /sys/power/pm_test none core [processors] platform devices freezer # dmesg dmesg_before-S3-procs; echo mem /sys/power/state; dmesg dmesg_after-resume-procs # echo devices /sys/power/pm_test # cat /sys/power/pm_test none core processors platform [devices] freezer # dmesg dmesg_before-S3-devices; echo mem /sys/power/state; dmesg dmesg_after-resume-devices poma Ref. Debugging hibernation and suspend https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt S3/s2ram https://www.kernel.org/doc/Documentation/power/s2ram.txt kernel.org - docs/power https://kernel.org/doc/Documentation/power/ How to debug suspend-resume issues https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On 28.01.2014 16:44, poma wrote: On 28.01.2014 14:10, Suvayu Ali wrote: On Mon, Jan 27, 2014 at 03:50:53PM +0100, poma wrote: On 27.01.2014 14:46, Suvayu Ali wrote: … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg - ACPI PM Same problem, can't resume. Have to force a reboot. # grep CONFIG_PM_DEBUG /boot/config-$(uname -r) CONFIG_PM_DEBUG=y # cat /sys/power/pm_test [none] core processors platform devices freezer # echo core /sys/power/pm_test # cat /sys/power/pm_test none [core] processors platform devices freezer # dmesg dmesg_before-S3-core; echo mem /sys/power/state; dmesg dmesg_after-resume-core # echo processors /sys/power/pm_test # cat /sys/power/pm_test none core [processors] platform devices freezer # dmesg dmesg_before-S3-procs; echo mem /sys/power/state; dmesg dmesg_after-resume-procs # echo devices /sys/power/pm_test # cat /sys/power/pm_test none core processors platform [devices] freezer # dmesg dmesg_before-S3-devices; echo mem /sys/power/state; dmesg dmesg_after-resume-devices Besides check whether this item affects resume, BIOS - Security - Intel TXT Feature Enable or disable Intel Trusted Execution Technology. poma -- users mailing list users@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
RE: Can't resume ThinkPad from suspend
I had a similar issue when I moved to the 3.12 kernel, this may be unrelated. If you have NVidia and the nouveau driver installed, the workaround: https://ask.fedoraproject.org/en/question/37476/fedora-20-unable-to-boot-after-update-from-kernel-311-to-kernel-312-nouveau-issue/ nouveau.runpm=0 worked. But as I say, your problem may be entirely different. Josh. -Original Message- From: users-boun...@lists.fedoraproject.org [mailto:users-boun...@lists.fedoraproject.org] On Behalf Of Suvayu Ali Sent: 27 January 2014 13:47 To: Fedora users Subject: Can't resume ThinkPad from suspend 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@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 -- users mailing list users@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
Re: Can't resume ThinkPad from suspend
On 27.01.2014 14:46, Suvayu Ali wrote: … How do I debug this? How can I get more information why the resume fails? Thanks for any ideas. First check S3/resume without X11, # systemctl set-default multi-user.target # systemctl isolate multi-user.target # systemctl suspend # dmesg - ACPI PM poma -- users mailing list users@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
