| Summary: | systemd-logind should make sure 'CanHibernate' is false if not enough swap space for all of RAM | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Wolfgang Ulbrich <fedora> |
| Component: | systemd | Assignee: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 18 | CC: | fedora, johannbg, lnykryn, msekleta, plautrba, rdieter, systemd-maint, vpavlin, zbyszek |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-204-16.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-09 02:16:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Wolfgang Ulbrich
2013-09-11 19:57:04 UTC
f18 outputs: [rave@mother ~]$ qdbus --system org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.CanHibernate false [rave@mother ~]$ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanHibernate yes f20 outputs: [rave@mother ~]$ qdbus --system org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.CanHibernate false [rave@mother ~]$ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanHibernate challenge If you need more info's or debuging results please let me know. What does "cat /sys/power/state" say for you? Hmm, so UPower seems to report hibernate support only if the RAM in the system is 98% or less of the swap space. We probably should something similar in logind. Ugly... The OP said that he has now swap... So I don't think swap size is an issue here. Where did he say that? f19 output: [rave@mother ~]$ cat /sys/power/state freeze standby mem disk I 've 8 GB ram, for this reason i don't use a swap partiton which is useless in most cases if ram is overload, before the ram is save to disk the system crashed, imo But this has never been happen here. For me is hibernate a old remnant from the last century. (In reply to Wolfgang Ulbrich from comment #9) > f19 output: > [rave@mother ~]$ cat /sys/power/state > freeze standby mem disk > > I 've 8 GB ram, for this reason i don't use a swap partiton which is useless > in most cases if ram is overload, before the ram is save to disk the system > crashed, imo > But this has never been happen here. For me is hibernate a old remnant from > the last century. i meant using a swap partition is a remnant from the last century. By the way, our friends from gentoo/mate uptream did confirmed this, exactly the same results. Hmm, i'm still wondering about the new title. I never said swap < ram !!! I said swap = 0 My old mathematics teachers said this is different :P Again in clear words. I don't have a swap partition. (In reply to Wolfgang Ulbrich from comment #12) > Hmm, i'm still wondering about the new title. > I never said swap < ram !!! > I said swap = 0 > My old mathematics teachers said this is different :P > > Again in clear words. > > I don't have a swap partition. But then your swap is still smaller than your ram. So all is fine. :) Upstream fix in http://cgit.freedesktop.org/systemd/systemd/commit/?id=69ab808. new results f20 with systemd-207-3.fc20 [rave@mother ~]$ qdbus --system org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.CanHibernate false [rave@mother ~]$ qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanHibernate na The hibernate button in MATE's shutdown dialog is also gone. Fixed for me. Hopefully you will also update f19/18 with the fix for 'fixed swap activation' rhbz#1008604 systemd-208-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-1.fc20 Can we expect also a fix for f18/19 ? Package systemd-208-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-2.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18172/systemd-208-2.fc20 then log in and leave karma (feedback). systemd-208-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. This issue exists on f19 boxes! systemd-204-16.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/systemd-204-16.fc19 Thanks for fixing it for f19, do you plan an update for f18 too? systemd-204-16.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. F18 needs also to be fixed. It is just too much work. The file that this code lives in wasn't even there in systemd-201, and those patches generate copious conflicts when applied. F20 is round the corner, and we have too many bugs present in current releases. Sorry. |