[opensuse-factory] TW 20180314 - system suspending: upower.service cannot be disabled
Since installing 20180314 I see the system suspending unexpectedly: 2018-03-17T13:12:46.493671+00:00 jabberwock kernel: [ 12.444695] ip_tables: (C) 2000-2006 Netfilter Core Team 2018-03-17T13:12:46.577669+00:00 jabberwock kernel: [ 12.529414] ip6_tables: (C) 2000-2006 Netfilter Core Team 2018-03-17T13:12:46.665686+00:00 jabberwock kernel: [ 12.617786] Ebtables v2.0 registered 2018-03-17T13:23:49.606667+00:00 jabberwock kernel: [ 675.867790] BTRFS info (device sda3): qgroup scan completed (inconsistency flag cleared) 2018-03-17T13:33:13.028041+00:00 jabberwock kernel: [ 1239.302819] PM: suspend entry (deep) 2018-03-17T13:44:50.583802+00:00 jabberwock kernel: [ 1239.302821] PM: Syncing filesystems ... done. 2018-03-17T13:44:50.583874+00:00 jabberwock kernel: [ 1239.313415] Freezing user space processes ... (elapsed 0.001 seconds) done. 2018-03-17T13:44:50.583877+00:00 jabberwock kernel: [ 1239.315284] OOM killer disabled. 2018-03-17T13:44:50.583878+00:00 jabberwock kernel: [ 1239.315285] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2018-03-17T13:44:50.583879+00:00 jabberwock kernel: [ 1239.316514] Suspending console(s) (use no_console_suspend to debug) 2018-03-17T13:44:50.583880+00:00 jabberwock kernel: [ 1239.317616] nuvoton-cir 00:05: disabled 2018-03-17T13:44:50.583881+00:00 jabberwock kernel: [ 1239.321624] e1000e: EEE TX LPI TIMER: 00000011 2018-03-17T13:44:50.583882+00:00 jabberwock kernel: [ 1239.321707] br0: port 1(eno1) entered disabled state I find that upower.service is running, although it is supposedly disabled: # systemctl status upower.service ● upower.service - Daemon for power management Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; vendor preset: disabled) Active: active (running) since Sat 2018-03-17 15:24:43 GMT; 9min ago Docs: man:upowerd(8) Main PID: 1886 (upowerd) Tasks: 3 (limit: 4915) CGroup: /system.slice/upower.service └─1886 /usr/lib/upower/upowerd Mar 17 15:24:43 jabberwock systemd[1]: Starting Daemon for power management... Mar 17 15:24:43 jabberwock systemd[1]: Started Daemon for power management. I have explicitly disabled it and rebooted and see the same behaviour. Hardware is a NUC (not a laptop). Have others seen this, and should I create a bug? -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 17, 2018 at 03:37:07PM +0000, Roger Whittaker wrote:
Since installing 20180314 I see the system suspending unexpectedly:
[...]
I did the following which seems to have cured it: systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target Which I hope permanently prevents any suspend or hibernate on this system, which I really want to be alive at all times. But I don't understand which of the several ways of configuring this stuff I should really have been looking at. I was using gdm as display manager (updated in 20180314 from 3.26 to 3.28), but actually using plasma as desktop. I suspected a gnome setting being picked up by gdm might have been the problem and went into gnome control centre and unset the suspend after inactivity option there. That didn't make a difference. I also had suspicions about systemd-logind, but systemd was not updated in 20180314, and experimentally making changes in /etc/systemd/logind.conf (where anyway everything seemed correct) did not change the behaviour. Something definitely seems to have changed this behaviour in 20180314 which I particularly noticed as I often log into this system remotely. If anyone has also seen this I would be interested. -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 17.03.2018 um 16:37 schrieb Roger Whittaker:
Since installing 20180314 I see the system suspending unexpectedly:
2018-03-17T13:12:46.493671+00:00 jabberwock kernel: [ 12.444695] ip_tables: (C) 2000-2006 Netfilter Core Team 2018-03-17T13:12:46.577669+00:00 jabberwock kernel: [ 12.529414] ip6_tables: (C) 2000-2006 Netfilter Core Team 2018-03-17T13:12:46.665686+00:00 jabberwock kernel: [ 12.617786] Ebtables v2.0 registered 2018-03-17T13:23:49.606667+00:00 jabberwock kernel: [ 675.867790] BTRFS info (device sda3): qgroup scan completed (inconsistency flag cleared) 2018-03-17T13:33:13.028041+00:00 jabberwock kernel: [ 1239.302819] PM: suspend entry (deep) 2018-03-17T13:44:50.583802+00:00 jabberwock kernel: [ 1239.302821] PM: Syncing filesystems ... done. 2018-03-17T13:44:50.583874+00:00 jabberwock kernel: [ 1239.313415] Freezing user space processes ... (elapsed 0.001 seconds) done. 2018-03-17T13:44:50.583877+00:00 jabberwock kernel: [ 1239.315284] OOM killer disabled. 2018-03-17T13:44:50.583878+00:00 jabberwock kernel: [ 1239.315285] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2018-03-17T13:44:50.583879+00:00 jabberwock kernel: [ 1239.316514] Suspending console(s) (use no_console_suspend to debug) 2018-03-17T13:44:50.583880+00:00 jabberwock kernel: [ 1239.317616] nuvoton-cir 00:05: disabled 2018-03-17T13:44:50.583881+00:00 jabberwock kernel: [ 1239.321624] e1000e: EEE TX LPI TIMER: 00000011 2018-03-17T13:44:50.583882+00:00 jabberwock kernel: [ 1239.321707] br0: port 1(eno1) entered disabled state
Check the journal what triggered the suspend.
I find that upower.service is running, although it is supposedly disabled:
# systemctl status upower.service
Upower is dbus-activated, see /usr/share/dbus-1/system-services/org.freedesktop.UPower.service You probably have some power management stuff running in your desktop environment which triggers this.
● upower.service - Daemon for power management Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; vendor preset: disabled) Active: active (running) since Sat 2018-03-17 15:24:43 GMT; 9min ago Docs: man:upowerd(8) Main PID: 1886 (upowerd) Tasks: 3 (limit: 4915) CGroup: /system.slice/upower.service └─1886 /usr/lib/upower/upowerd
Mar 17 15:24:43 jabberwock systemd[1]: Starting Daemon for power management... Mar 17 15:24:43 jabberwock systemd[1]: Started Daemon for power management.
I have explicitly disabled it and rebooted and see the same behaviour.
I don't think that upower is responsible for suspend nowadays (but am not sure, lots of things have changed since I last took a closer look at such issues :-) I think suspend is handled by systemd and keyboard or button triggers are handled either by systemd-logind or by the desktop sessions. My machine is running all day and night without autosuspending, but with XFCE where I know that everything is configured correctly. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 17, 2018 at 11:27:48PM +0100, Stefan Seyfried wrote:
Check the journal what triggered the suspend.
Thanks very much for your comments. Mar 17 14:18:50 jabberwock gnome-shell[1874]: Screen lock is locked down, not locking Mar 17 14:18:50 jabberwock systemd[1]: Reached target Sleep. Mar 17 14:18:50 jabberwock systemd[1]: Starting Suspend... Mar 17 14:18:50 jabberwock systemd-sleep[2629]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Mar 17 14:18:50 jabberwock systemd-sleep[2629]: Suspending system... Mar 17 14:18:50 jabberwock kernel: PM: suspend entry (deep) Mar 17 14:18:50 jabberwock kernel: PM: Syncing filesystems ... done. Mar 17 15:09:18 jabberwock kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 17 15:09:18 jabberwock kernel: OOM killer disabled. Mar 17 15:09:18 jabberwock kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 17 15:09:18 jabberwock kernel: Suspending console(s) (use no_console_suspend to debug) Mar 17 15:09:18 jabberwock kernel: nuvoton-cir 00:05: disabled So it looks like gnome-shell. Although I was not actually running gnome... - but gdm was the displaymanager. And gdm got an update from 3.26 to 3.28 today. -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, Mar 17, 2018 at 11:27:48PM +0100, Stefan Seyfried wrote:
Am 17.03.2018 um 16:37 schrieb Roger Whittaker:
Since installing 20180314 I see the system suspending unexpectedly:
[...]
Check the journal what triggered the suspend.
Mar 17 13:33:13 jabberwock gnome-shell[1892]: Screen lock is locked down, not locking Mar 17 13:33:13 jabberwock systemd[1]: Reached target Sleep. Mar 17 13:33:13 jabberwock systemd[1]: Starting Suspend... Mar 17 13:33:13 jabberwock systemd-sleep[3233]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Mar 17 13:33:13 jabberwock systemd-sleep[3233]: Suspending system... Mar 17 13:33:13 jabberwock kernel: PM: suspend entry (deep) Mar 17 13:44:50 jabberwock kernel: PM: Syncing filesystems ... done. Mar 17 13:44:50 jabberwock kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 17 13:44:50 jabberwock kernel: OOM killer disabled. Mar 17 13:44:50 jabberwock kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 17 13:44:50 jabberwock kernel: Suspending console(s) (use no_console_suspend to debug) Mar 17 13:44:50 jabberwock kernel: nuvoton-cir 00:05: disabled Mar 17 13:44:50 jabberwock kernel: e1000e: EEE TX LPI TIMER: 00000011 Mar 17 13:44:50 jabberwock kernel: br0: port 1(eno1) entered disabled state Looks like gnome-shell although a gnome session was not running. Could this actually be caused by the new gdm? -- ============================ Roger Whittaker roger@disruptive.org.uk ============================ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Roger Whittaker -
Stefan Seyfried