-------- Forwarded Message --------
Subject: Confused...!
Date: Tue, 16 May 2017 23:01:46 +1000
From: Sav Mellor
To: Sid Boyce
Hi Sid,
my power management is acting up again. Some times it
works, sometimes not and I'm really not sure what is going on. The
upower is set to disabled and stays disabled across reboots. But when
the machine boots, and if I do a "systemctl status upower", it shows it
disabled but with two lines at the end that show it starting and then
started.
The control settings are set to warn at low battery (which I increased
to 20% to give me a bit more time to check the status) and then at
critical battery (5%), give a second warning and hibernate 60 seconds
later. Both warnings should also play a sound but never do.
Sometimes, I get the warning warning at 20% and if this happens, it
hibernates at 5% plus 60 seconds. But some times, it doesn't and just
runs to zero and powers off without any warnings along the way. May or
may not be relevant but turning the power adaptor on or off always pops
up a message, regardless of whatever else happens.
So for example, today powered up the machine as normal, checked the
status, upower disabled, upower started. It ran down to 20%, no
warning, continued to run down, so I plugged in the adaptor, with a
message, to stop it power off. I let it get to 25 and turned the
adaptor off again, gave a message. Then did a few systemctl's:
Password:
linux-w6k1:~ # systemctl stop upower
linux-w6k1:~ # systemctl status upower
â upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled;
vendor preset: disabled)
Active: inactive (dead)
Docs: man:upowerd(8)
May 16 19:59:24 linux-w6k1 systemd[1]: Stopping Daemon for power
management...
May 16 19:59:24 linux-w6k1 systemd[1]: Stopped Daemon for power management.
May 16 19:59:24 linux-w6k1 systemd[1]: Starting Daemon for power
management...
May 16 19:59:25 linux-w6k1 systemd[1]: Started Daemon for power management.
May 16 19:59:59 linux-w6k1 systemd[1]: Stopping Daemon for power
management...
May 16 19:59:59 linux-w6k1 systemd[1]: Stopped Daemon for power management.
May 16 19:59:59 linux-w6k1 systemd[1]: Starting Daemon for power
management...
May 16 19:59:59 linux-w6k1 systemd[1]: Started Daemon for power management.
May 16 22:06:37 linux-w6k1 systemd[1]: Stopping Daemon for power
management...
May 16 22:06:37 linux-w6k1 systemd[1]: Stopped Daemon for power management.
linux-w6k1:~ # systemctl status upower
â upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled;
vendor preset: disabled)
Active: active (running) since Tue 2017-05-16 22:08:20 AEST; 31s ago
Docs: man:upowerd(8)
Main PID: 6312 (upowerd)
Tasks: 3 (limit: 512)
CGroup: /system.slice/upower.service
ââ6312 /usr/lib/upower/upowerd
May 16 22:08:20 linux-w6k1 systemd[1]: Starting Daemon for power
management...
May 16 22:08:20 linux-w6k1 systemd[1]: Started Daemon for power management.
linux-w6k1:~ #
As you see the stop did, indeed stop it, so it was disabled and Active:
inactive(dead).
But then there was the flood of stops and starts, at the end of the
status report.
Did another status report and as you see, it was now disabled and
started, with no commands in between.
At the end of this status report it showed a final starting/started.
Left it to run down again and at 20% it gave a warning and at 5% plus 60
seconds, hibernated.
I am totally mystified by all this, any suggestions? Is the status
causing it to restart? And why is that different from a cold boot?
Best regards,
Sav.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
