Hi,
A new bug has cropped up on my system Dell Precision 5510 running Fedora 25 Plasma Desktop. Anytime I suspend my device it shutdowns and obviously I lose all my unsaved work.
I have tried all the kernel currently installed on my system 4.10.10-200.fc25.x86_64, 4.10.9, and 4.10.8. I have also tried downgrading systemd to systemd-231-10.fc25.x86_64. I continue to have the problem.
sysinfo - https://paste.fedoraproject.org/paste/9nY1-YH4IKXt4wJhyIbMGV5M1UNdIGYhyRLivL... dmesg - https://paste.fedoraproject.org/paste/WK2NAqy3PRxrR6Fze2baIl5M1UNdIGYhyRLivL...
What I can do to troubleshoot the problem?
Allegedly, on or about 23 April 2017, Sudhir Khanger sent:
Anytime I suspend my device it shutdowns and obviously I lose all my unsaved work.
I always thought it would be wiser if suspend also did the RAM dump to drive, so that when the computer was woken up, it would first try to resume from RAM, then try to resume from storage, finally cold booting if the other options weren't do-able.
As general debugging advice, you'd want to look at the system logs to see what it says it's doing as it suspends/shuts-down.
Your hardware has to support suspend mode, in that it has to supply standby power continuously.
There are/were BIOS settings about that on some computers. If your PC is one that requires enabling it in the BIOS, and you haven't changed BIOS settings, it might suggest that the CMOS battery might need replacing.
Hi,
How do I figure out that it is not a CMOS problem but a software one? It was working a couple of days ago and now it is not. There were several updates in between.
This is a four months old laptop, supposedly, Linux certified which seems to have all the problem in the world.
Regards, Sudhir.
Allegedly, on or about 24 April 2017, Sudhir Khanger sent:
How do I figure out that it is not a CMOS problem but a software one? It was working a couple of days ago and now it is not. There were several updates in between.
Well, go into your BIOS, and see if there are power options about suspending, or types of suspending. If there aren't any, then chances are that the problem isn't caused by changed setting. If there are options, then check the meanings of the set selections. If the problem is caused by a setting that has changed without you changing it, then that can be down to a bad battery (even on a new computer), or just simply that some random error poked it.
There was an update 4.10.12-200.fc25.x86_64 after which my suspend problem went away.
CMOS battery is very deep under the motherboard. It would have sucked big time to replace it.
As far as BIOS option is concerned there was only which was to block S3 sleep which is what I wanted to work. I did enable and later disable it. I am not sure if that has anything to do with it.
On 04/22/2017 10:00 PM, Sudhir Khanger wrote:
A new bug has cropped up on my system Dell Precision 5510 running Fedora 25 Plasma Desktop. Anytime I suspend my device it shutdowns and obviously I lose all my unsaved work.
I saw this on someone's laptop that was running F24. But when he upgraded to F25 last week, it went away. Do you have the latest kernel?
https://linux.die.net/man/1/pm-is-supported http://www.linuxfromscratch.org/blfs/view/cvs/general/pm-utils.html
in combination with dnf history undo
1. check your /etc/default/grub: GRUB_CMDLINE_LINUX=" resume=/dev/sdXN rhgb quiet" 2. run all three pm-is-supported [{--suspend | --hibernate | --suspend-hybrid}] now (echo $?) 3. dnf history undo ( does this work for kernels too ?) up to the date where your system hibernates/suspends 4. single re-install the packages one by one and test between each install again with pm-is-supported
P.S. I don't know why pm-utils isn't packaged for Fedora 25, maybe redeemed by another package ??? https://koji.fedoraproject.org/koji/packageinfo?packageID=580
Suspend started working on its own after 4.10.12-200.fc25.x86_64 update.
What is the status of pm-utils? I suppose it is deprecated in favor of pm-utils.
And the issue is back again. I can't suspend on battery. Suspend, hibernate, hybrid sleep, etc. work just fine on power. Only suspend doesn't work on battery but hibernate and hybrid-sleep do.
On 07/19/2018 11:52 PM, Sudhir Khanger wrote:
And the issue is back again. I can't suspend on battery. Suspend, hibernate, hybrid sleep, etc. work just fine on power. Only suspend doesn't work on battery but hibernate and hybrid-sleep do.
It's ambiguous to say "and xxxx is back again" without telling us where you were and are now. What kernel are you running? There appears to be problems in this area with kernels 4.17.4-200 through 4.17.6-200.
Theoretically 4.17.7-200 fixes them, but it's still in koji and hasn't been pushed to updates yet. Most people with this issue continue to run 4.17.3-200 or take the plunge and grab the .7-200 from koji. I'm still running 4.17.3-200 myself. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - To err is human. To forgive, a large sum of money is needed. - ----------------------------------------------------------------------
On 07/20/2018 12:34 PM, Rick Stevens wrote:
On 07/19/2018 11:52 PM, Sudhir Khanger wrote:
And the issue is back again. I can't suspend on battery. Suspend, hibernate, hybrid sleep, etc. work just fine on power. Only suspend doesn't work on battery but hibernate and hybrid-sleep do.
It's ambiguous to say "and xxxx is back again" without telling us where you were and are now. What kernel are you running? There appears to be problems in this area with kernels 4.17.4-200 through 4.17.6-200.
Theoretically 4.17.7-200 fixes them, but it's still in koji and hasn't been pushed to updates yet. Most people with this issue continue to run 4.17.3-200 or take the plunge and grab the .7-200 from koji. I'm still running 4.17.3-200 myself.
I am also running 4.17.3. At least until I get home Monday evening.
Just too many suspends during the day.
On 07/20/2018 10:54 AM, Patrick O'Callaghan wrote:
On Fri, 2018-07-20 at 09:34 -0700, Rick Stevens wrote:
Theoretically 4.17.7-200 fixes them, but it's still in koji and hasn't been pushed to updates yet.
I got it from updates-testing this morning.
Ok, so it is wending its way through the full release cycle. Good to know. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - I doubt, therefore I might be. - ----------------------------------------------------------------------
On Fri, Jul 20, 2018 at 10:04 PM Rick Stevens ricks@alldigital.com wrote:
On 07/19/2018 11:52 PM, Sudhir Khanger wrote:
And the issue is back again. I can't suspend on battery. Suspend,
hibernate, hybrid sleep, etc. work just fine on power. Only suspend doesn't work on battery but hibernate and hybrid-sleep do.
It's ambiguous to say "and xxxx is back again" without telling us where you were and are now. What kernel are you running? There appears to be problems in this area with kernels 4.17.4-200 through 4.17.6-200.
Theoretically 4.17.7-200 fixes them, but it's still in koji and hasn't been pushed to updates yet. Most people with this issue continue to run 4.17.3-200 or take the plunge and grab the .7-200 from koji. I'm still running 4.17.3-200 myself.
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
-
- To err is human. To forgive, a large sum of money is needed. -
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
I am on Fedora 28. I have tried every kernel update from 4.17.4-200 .fc28.x86_64 to 4.17.7-200.fc28.x86_64 (from updates-testing). None of them can suspend on battery. When connected to power suspend works just fine.
On 07/21/18 11:09, Sudhir Khanger wrote:
I am on Fedora 28. I have tried every kernel update from 4.17.4-200.fc28.x86_64to 4.17.7-200.fc28.x86_64 (from updates-testing). None of them can suspend on battery. When connected to power suspend works just fine.
I've got an old Acer laptop that can survive on its ancient battery for about 45 minutes.
I just tested it with 4.17.7-200.fc28.x86_64 and it immediately went into suspend to RAM when I unplugged power since I forgot to raise the lid. It also went into suspend when I test by doing echo mem > /sys/power/state.
If you cat /sys/power/mem_sleep and state are the different from when they are mains and battery?
When on battery, if you "echo mem > /sys/power/state" does it also fail to suspend?
I use KDE and in its "Power Management" it has the ability to select what to do if the lid is closed. The choices can be different for Battery and Plugged In. Does your Desktop Environment also allow for differences?
On Sat, Jul 21, 2018 at 9:26 AM Ed Greshko ed.greshko@greshko.com wrote:
On 07/21/18 11:09, Sudhir Khanger wrote:
I am on Fedora 28. I have tried every kernel update from 4.17.4-200.fc28.x86_64to 4.17.7-200.fc28.x86_64 (from
updates-testing). None
of them can suspend on battery. When connected to power suspend works
just fine.
I've got an old Acer laptop that can survive on its ancient battery for about 45 minutes.
I just tested it with 4.17.7-200.fc28.x86_64 and it immediately went into suspend to RAM when I unplugged power since I forgot to raise the lid. It also went into suspend when I test by doing echo mem > /sys/power/state.
If you cat /sys/power/mem_sleep and state are the different from when they are mains and battery?
When on battery, if you "echo mem > /sys/power/state" does it also fail to suspend?
I use KDE and in its "Power Management" it has the ability to select what to do if the lid is closed. The choices can be different for Battery and Plugged In. Does your Desktop Environment also allow for differences?
-- Conjecture is just a conclusion based on incomplete information. It isn't a fact.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
I am also on KDE. Suspend to RAM doesn't work on battery. Until this problem is mitigated I am using hybrid sleep for now which done both Suspend to RAM and Suspend to Disk. The former is used to wake up the system if the device is connected to an AC adapter and the latter is used if it is on the battery.
When on battery, if you "echo mem > /sys/power/state" does it also fail to
suspend?
echo mem > /sys/power/state - this suspended and then didn't wake up.
If you cat /sys/power/mem_sleep and state are the different from when they
are mains and battery?
$ cat /sys/power/mem_sleep s2idle [deep]
mem_sleep has the above output irrespective of the power state.
I use KDE and in its "Power Management" it has the ability to select what
to do if the lid is closed. The choices can be different for Battery and Plugged In. Does your Desktop Environment also allow for differences?
Lid is not an issue. You can suspend however you want but the end result is the same. It doesn't wake up. It starts as a fresh boot.
Allegedly, on or about 21 July 2018, Sudhir Khanger sent:
None of them can suspend on battery. When connected to power suspend works just fine.
Does the system check whether your battery is sufficient to stay on suspend, first?
On Sat, Jul 21, 2018 at 9:34 AM Tim via users users@lists.fedoraproject.org wrote:
Allegedly, on or about 21 July 2018, Sudhir Khanger sent:
None of them can suspend on battery. When connected to power suspend works just fine.
Does the system check whether your battery is sufficient to stay on suspend, first?
-- [tim@localhost ~]$ uname -rsvp Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64
Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list.
Linux servers are always being dæmonised... _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
My system usually lasts for several hours on battery. That would probably mean the battery is fine. I have no way to tell if my system is checking whether the battery is sufficient to stay suspended. There's enough battery for it be able to suspend.
I have tried both systemctl suspend and KDE's power menu to suspend.
users@lists.stg.fedoraproject.org