[opensuse] Hibernate broken since yesterday
Hi, I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally). When I now try to hibernate, nothing happens. I tried (as root): # /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist I also tried (as root) # /usr/sbin/pm-hibernate which doesn't do anything anymore. That worked yesterday. # rpm -qi pm-utils-1.4.1-38.4.1.x86_64 Name : pm-utils Version : 1.4.1 Release : 38.4.1 Architecture: x86_64 Install Date: Sa 06 Dez 2014 00:20:48 CET Package hasn't changed, though. Using the button in my KDE start menu locks the screen and then displays a dialog "Legitimierung ist zum Aktivieren des Ruhezustands des Systems notwendig, während andere Benutzer angemeldet sind" (English: Give me root password to suspend while other users are logged in). Action: "Hibernate the system while other users are logged in" Vendor: The systemd Project The action is a link. When I hover over it, it says "Click to edit org.freedesktop.login1.hibernate-multiple-sessions" Clicking doesn't do anything. But grepping in /etc eventually pointed me to /etc/polkit-default-privs.local where I added this line: org.freedesktop.login1.hibernate-multiple-sessions auth_self:auth_self:yes I then looked into /var/log/pm-suspend.log: Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate: INFO: checking for suspend-to-disk prerequisites... ERROR: no resume parameter on kernel commandline, can not suspend WARNING: /var/run/pm-utils/pm-suspend/storage/inhibit will be created to prevent suspending! Yast says: resume=/dev/sda2 splash=verbose quiet showopts elevator=cfq console=tty0 plymouth.enable=0 I also see these values in grub.cfg and they look right to me. Any ideas? How can I see the current init parameters of the kernel? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running) -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-) 13.2. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment. If this problem still exists after a normal (full) reboot, then there is a real cause to investigate. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846 Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 7 Feb 2015 21:34, John Andersen <jsamyth@...> wrote:
On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846
Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services
At my system, the file /usr/lib/systemd/system/dbus-org.freedesktop.login1.service is just a symlink to systemd-logind.service So if "systemctl status dbus-org.freedesktop.login1.service" says no-good, check that first, and if it is a link at your system, too, try "systemctl status systemd-logind.service" at my system this gives back an "ok, working". And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 12:54 PM, Yamaban wrote:
On Sat, 7 Feb 2015 21:34, John Andersen <jsamyth@...> wrote:
On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846
Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services
At my system, the file /usr/lib/systemd/system/dbus-org.freedesktop.login1.service is just a symlink to systemd-logind.service
So if "systemctl status dbus-org.freedesktop.login1.service" says no-good, check that first, and if it is a link at your system, too, try "systemctl status systemd-logind.service" at my system this gives back an "ok, working".
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
- Yamaban.
After a reboot, the link did exist. and the systemctl command worked, but I never see the "ok working". Rather I see the following spew, which I translate as "ok working"
sa@poulsbo:~> systemctl status systemd-logind.service systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Active: active (running) since Sat 2015-02-07 13:47:41 PST; 6min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 877 (systemd-logind) Status: "Processing requests..." CGroup: /system.slice/systemd-logind.service └─877 /usr/lib/systemd/systemd-logind
And sure enough # /usr/sbin/pm-hibernate works now to hibernate and shut down. (And, suspend (lid close) still works too, as does And Lid open (resume) after suspend). However power on (after hibernate) goes through a couple of quick lines on the console, then quickly goes to black screen, and I am totally screwed at that point because it just hangs, all disk activity ceases, the machine is running but I have no idea what it wants me to do. Does it want mu login password, does it want my encrypted home directory password? I have no clue because screen is totally black. Power off (is my only option, and the hibernated session is lost). -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 12:54 PM, Yamaban wrote:
On Sat, 7 Feb 2015 21:34, John Andersen <jsamyth@...> wrote:
On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846
Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services
At my system, the file /usr/lib/systemd/system/dbus-org.freedesktop.login1.service is just a symlink to systemd-logind.service
So if "systemctl status dbus-org.freedesktop.login1.service" says no-good, check that first, and if it is a link at your system, too, try "systemctl status systemd-logind.service" at my system this gives back an "ok, working".
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
- Yamaban.
Googleing around I found that my problem with resume from hibernation was solved by removing the package pm-utils which systemd will use if it is there but apparently it is not needed any more. I simply deleted the package and used the kde (gecko button) leave / hibernate instead of the /usr/sbin/pm-hibernate command. It hibernated. Upon power on, it resumed. So far all working. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 8 Feb 2015 01:17, John Andersen <jsamyth@...> wrote:
On 02/07/2015 12:54 PM, Yamaban wrote:
On Sat, 7 Feb 2015 21:34, John Andersen <jsamyth@...> wrote:
On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen <jsamyth@...> wrote:
On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla: > Hi, > > I installed a bunch of patches and updated packages yesterday. I could > hibernate yesterday evening but couldn't resume (Linux would just boot > normally). > > When I now try to hibernate, nothing happens. > > I tried (as root): > > # /usr/bin/powersave --suspend-to-disk > Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with > signature "" on interface "org.freedesktop.UPower" doesn't exist > > I also tried (as root) > > # /usr/sbin/pm-hibernate > > which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846
Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services
At my system, the file /usr/lib/systemd/system/dbus-org.freedesktop.login1.service is just a symlink to systemd-logind.service
So if "systemctl status dbus-org.freedesktop.login1.service" says no-good, check that first, and if it is a link at your system, too, try "systemctl status systemd-logind.service" at my system this gives back an "ok, working".
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
- Yamaban.
Googleing around I found that my problem with resume from hibernation was solved by removing the package pm-utils which systemd will use if it is there but apparently it is not needed any more.
I simply deleted the package and used the kde (gecko button) leave / hibernate instead of the /usr/sbin/pm-hibernate command.
It hibernated. Upon power on, it resumed. So far all working.
Nice! Thanks for sharing that info, some old systems (e.g. BIOS only systems) need pm-utils to be happy, But it's good to know that there are now systems that work better without. As replacement for /usr/sbin/pm-hibernate you can use: "/usr/bin/systemctl hibernate" If you want to be lazy, create a shell script "/usr/sbin/pm-hibernate" and mark it executeable, with the content [code] #!/bin/sh exec /usr/bin/systemctl hibernate [/code] The shell script "/usr/bin/powersave" (also pm-utils) you can replace by a similar script. But that would be more work, with all that options. - Yamaban -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 04:54 PM, Yamaban wrote:
Nice! Thanks for sharing that info, some old systems (e.g. BIOS only systems) need pm-utils to be happy, But it's good to know that there are now systems that work better without.
As replacement for /usr/sbin/pm-hibernate you can use: "/usr/bin/systemctl hibernate"
If you want to be lazy, create a shell script "/usr/sbin/pm-hibernate" and mark it executeable, with the content [code] #!/bin/sh exec /usr/bin/systemctl hibernate [/code]
The shell script "/usr/bin/powersave" (also pm-utils) you can replace by a similar script.
But that would be more work, with all that options.
I'm almost always going to be happy to use the kde triggers (in the start menu or the power management portion of configure desktop, especially for the critical battery level part). My (Dell Laptop) has a FN-key combo for Hibernate, and occasionally it would be nice to have that work as well. The Fn-Standby key combo works fine for suspend to ram, but the Fn-hibernate is ignored. (Come to think of it, thats the only FN-key combo that doesn't seem to work). -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.02.2015 um 01:17 schrieb John Andersen:
Googleing around I found that my problem with resume from hibernation was solved by removing the package pm-utils which systemd will use if it is there but apparently it is not needed any more.
I simply deleted the package and used the kde (gecko button) leave / hibernate instead of the /usr/sbin/pm-hibernate command.
That doesn't work for me; I have to use pm-hibernate because the normal hibernate just locks the screen and then aborts. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-07 21:54, Yamaban wrote:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTWwcsACgkQja8UbcUWM1xvjQD/XujOLD46YZJ69TOHW4uRvM1l +jVgs3yM0Izlg9u6IOMBAIvelBZZfRvSyi29uzM3E0EcVO/2lqu1VvK0vT5GNLbN =FuZ8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/07/2015 05:54 PM, Carlos E. R. wrote:
On 2015-02-07 21:54, Yamaban wrote:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update.
I'll go you one better..... It should recommend either a logout and in again, or a reboot anytime there is any thing running modules that have been deleted. The message could say either reboot or logout depending on who has the modules locked. Most of the time these aren't big issues but sometimes crazy hard to debug issues crop up when you don't logout. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTWw2MACgkQv7M3G5+2DLJrDgCfcu4PIpN3Lpndw3gq3SUwBP3W nkoAoJyflWWJkPX9rIrCoaeRj5vbJxOW =W10C -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-08 03:01, John Andersen wrote:
On 02/07/2015 05:54 PM, Carlos E. R. wrote:
I'll go you one better..... It should recommend either a logout and in again, or a reboot anytime there is any thing running modules that have been deleted. The message could say either reboot or logout depending on who has the modules locked.
It is not as clear cut as that. The actual action to do differs, depending on what was updated. Sometimes log out/in is the thing to do. Sometimes some system services need to be restarted, while log off/in does nothing, or not enough. Often the exact sequence of subsystems to be restarted is not easy to determine; often "init 3 ; init 5" does it, but others the trick is going to level 1 and back to 5. All that to avoid a reboot, which although being most often an overkill, it is the only thing that always works. Thus it is the admin which has to determine what to do. Zypper helps by suggesting you run "zypper ps" in order to find out what may be affected. Only on some crucial updates it suggests a reboot. But they forget to suggest that with glibc. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTWyNIACgkQja8UbcUWM1x47QD/dX8qPD4RLM0SU6UKGY4D+RYa kmSW4TA2IHFthvzQpx0A+gIgb2oB4lq9PSs7IQA6n50VgN7+3UZ03qCK2vTKWblg =18P4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/07/2015 06:24 PM, Carlos E. R. wrote:
It is not as clear cut as that. The actual action to do differs,
True, but most of the time, (the vast majority of the time) if ALL the deleted modules are in use by joe user, simply logging out and back in is all that is needed. If one or more is loaded by root, you just about always have to reboot. (Gone are the days you can just issue rcsmb restart and expect it to work correctly. It might or it might not, because systemd. But it user is the owner, I've never seen it fail. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTW08IACgkQv7M3G5+2DLLZpQCfcaZXqFCfh1+7LcPCvQpGOwIE owwAniuoU32NqoBzrTbiY7ki+K0hPZmu =ixHA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.02.2015 um 03:01 schrieb John Andersen:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update.
Reboot didn't help and exposed a new problem: GRUB2 (2.02~beta2-20.5.1) doesn't allow me to select which kernel to boot from or see the kernel options. It just boots directly, no matter what I do. So I can't see why it's not paying attention to the resume option which should be passed to the kernel. In yast, I have selected one kernel, "hide boot menu" is OFF and the timeout is 8 seconds. But no boot menu. How do I fix this? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sun, 08 Feb 2015 13:45:08 +0100 Aaron Digulla <digulla@hepe.com> пишет:
Am 08.02.2015 um 03:01 schrieb John Andersen:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update.
Reboot didn't help and exposed a new problem: GRUB2 (2.02~beta2-20.5.1) doesn't allow me to select which kernel to boot from or see the kernel options. It just boots directly, no matter what I do. So I can't see why it's not paying attention to the resume option which should be passed to the kernel.
In yast, I have selected one kernel, "hide boot menu" is OFF and the timeout is 8 seconds. But no boot menu. How do I fix this?
The quickest workaround is to delete /boot/grub2/grubenv. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.02.2015 um 16:49 schrieb Andrei Borzenkov:
In yast, I have selected one kernel, "hide boot menu" is OFF and the timeout is 8 seconds. But no boot menu. How do I fix this? The quickest workaround is to delete /boot/grub2/grubenv.
So that's where GRUB saves the last selected entry. Thanks, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Feb 08, 2015 at 02:54:19AM +0100, Carlos E. R. wrote:
On 2015-02-07 21:54, Yamaban wrote:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update.
It actually should not ... Is there some form of proof? Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-08 08:57, Marcus Meissner wrote:
On Sun, Feb 08, 2015 at 02:54:19AM +0100, Carlos E. R. wrote:
On 2015-02-07 21:54, Yamaban wrote:
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
IMO, YaST/Zypper should recommend a reboot after a glibc update, same as it does after a kernel update.
It actually should not ... Is there some form of proof?
What proof do you want? It is a well known fact, since ever, that things break after upgrading glibc, sometimes in weird manners, till you reboot. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTcC2YACgkQja8UbcUWM1xP+wD/fcv2BP5rBwvuwNVDCX/Cfhf7 at2sJ4Am09ZKBBYDofAA/2Ei15HEl0oKlkfABKliMwk5cWLXqK9vbJTnaogJZxTr =+Fzd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 07.02.2015 um 17:51 schrieb Freek de Kruijf:
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
I get: # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) I think this is the case since some time. Which is why I started to use /usr/sbin/pm-hibernate. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2015 02:42 PM, Aaron Digulla wrote:
Am 07.02.2015 um 17:51 schrieb Freek de Kruijf:
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
I get:
# systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
I think this is the case since some time. Which is why I started to use /usr/sbin/pm-hibernate.
Regards,
The command needs to be different. I get the same as you, but if I enter it in a different form it works: Fails:
jsa@poulsbo:~> systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
Works (service, not services)
jsa@poulsbo:~> systemctl status dbus-org.freedesktop.login1.service systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Active: active (running) since Sat 2015-02-07 14:09:42 PST; 35min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 891 (systemd-logind) Status: "Processing requests..." CGroup: /system.slice/systemd-logind.service └─891 /usr/lib/systemd/systemd-logind
The command (as root) /usr/sbin/pm-hibernate does hibernate for me, but if you read the thread you will see where awakening from hibernate leaves me dead. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-07 16:33, Aaron Digulla wrote:
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Here you had to look at the log, which you did later:
I then looked into /var/log/pm-suspend.log:
Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate: INFO: checking for suspend-to-disk prerequisites... ERROR: no resume parameter on kernel commandline, can not suspend WARNING: /var/run/pm-utils/pm-suspend/storage/inhibit will be created to prevent suspending!
Interesting. Other clues could be in /var/log/messages.
Yast says:
resume=/dev/sda2 splash=verbose quiet showopts elevator=cfq console=tty0 plymouth.enable=0
Don't ask YaST. Instead, do "cat /proc/cmdline"
How can I see the current init parameters of the kernel?
See above. The reason why removing pm-utils works for you might be related to the 30s2disk-check script failure shown by the log excerpt above: the script is removed, so it can not block the process. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTWxNgACgkQja8UbcUWM1xuwwD7BQuK/z2mmwqELy7aaBWaeVEn ekzFnVk25rWxLYwQ9rAA/im/gUsocpK1+Axkk1E0ckABmqu43hBU4dzhercmrPkA =WJ8l -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.02.2015 um 03:07 schrieb Carlos E. R.:
Yast says:
resume=/dev/sda2 splash=verbose quiet showopts elevator=cfq console=tty0 plymouth.enable=0
Don't ask YaST. Instead, do "cat /proc/cmdline"
Which gives me: BOOT_IMAGE=/boot/vmlinuz-3.16.7-7-desktop root=UUID=623a3f37-66d2-4e80-b17d-28261b3a6692 ro showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe which is wrong on many levels. First of all, I have 3.18.3 installed, so why is it using 3.16.7? And why is it automatically selecting this old kernel? In /etc/default/grub, I see GRUB_TIMEOUT=0 which may explain why I don't get a boot menu. Why doesn't YAST allow me to change this value? GRUB_DEFAULT=saved probably means "use the last kernel" which feels wrong; what is supposed to happen when I install a new kernel? I've deleted the DEFAULT and I'm setting the timeout to 8, let's see if that helps. -> reboot. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.02.2015 um 13:56 schrieb Aaron Digulla:
resume=/dev/sda2 splash=verbose quiet showopts elevator=cfq console=tty0 plymouth.enable=0
Don't ask YaST. Instead, do "cat /proc/cmdline"
Which gives me:
BOOT_IMAGE=/boot/vmlinuz-3.16.7-7-desktop root=UUID=623a3f37-66d2-4e80-b17d-28261b3a6692 ro showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
which is wrong on many levels. First of all, I have 3.18.3 installed, so why is it using 3.16.7? And why is it automatically selecting this old kernel?
In /etc/default/grub, I see
GRUB_TIMEOUT=0
which may explain why I don't get a boot menu. Why doesn't YAST allow me to change this value?
GRUB_DEFAULT=saved
probably means "use the last kernel" which feels wrong; what is supposed to happen when I install a new kernel?
I've deleted the DEFAULT and I'm setting the timeout to 8, let's see if that helps. -> reboot.
Hi, I have now solved my problems. There is a recap in my blog: http://blog.pdark.de/2015/02/08/hibernating-opensuse-13-2-harlequin/ Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-08 13:56, Aaron Digulla wrote:
Am 08.02.2015 um 03:07 schrieb Carlos E. R.:
Don't ask YaST. Instead, do "cat /proc/cmdline"
Which gives me:
BOOT_IMAGE=/boot/vmlinuz-3.16.7-7-desktop root=UUID=623a3f37-66d2-4e80-b17d-28261b3a6692 ro showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
which is wrong on many levels.
It is the safemode entry also. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTcDAsACgkQja8UbcUWM1yIrwD+JcSpLc1ZA7wOrwHF3ksDjs2K /+cXPPau7/PCbRmubQAA+wdGhjovzoIDqKBF5eSbThXk4jbUAgnxMHWCzTgN2cmW =nFuV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Aaron Digulla -
Andrei Borzenkov -
Carlos E. R. -
Carlos E. R. -
Freek de Kruijf -
John Andersen -
Marcus Meissner -
Yamaban