Slow CPU

,

i am Fedora 34 was dnf update and slow CPU. at a HP Laptop. i am upgraded Fedora 35. slow CPU. ~10-30 minutes is login.

i am changing on/off settings KDE , dnf update, and slow CPU.
crontab: no root and no user

p.s. restart or power off – do i is power machine?

top

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3254 perryts+ 20 0 5534236 227316 112156 S 1.7 1.9 13:30.53 cinnamon
2764 perryts+ 20 0 2460948 110300 65388 S 1.5 0.9 7:48.53 Xorg
11231 perryts+ 20 0 690136 49196 37200 S 1.1 0.4 0:05.30 gnome-terminal-
7366 perryts+ 39 19 256.9g 1.0g 576136 D 0.7 8.6 0:57.27 baloo_file_extr
58 root 20 0 0 0 0 S 0.6 0.0 0:10.73 kcompactd0
74 root 20 0 0 0 0 S 0.6 0.0 0:13.65 kswapd0
12721 perryts+ 20 0 1416704 106192 76496 S 0.6 0.9 0:02.68 cpu-x
947 systemd+ 20 0 17244 8760 7876 S 0.2 0.1 0:08.26 systemd-oomd


messages

  1 Feb 27 00:01:40 fedora systemd[1]: logrotate.service: Deactivated successfully.
  2 Feb 27 00:01:40 fedora systemd[1]: Finished Rotate log files.
  3 Feb 27 00:01:40 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_      3 r:init_t:s0 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=      3 success'
  4 Feb 27 00:01:40 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r      4 :init_t:s0 msg='unit=logrotate comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s      4 uccess'
  5 Feb 27 00:01:40 fedora audit: BPF prog-id=0 op=UNLOAD
  6 Feb 27 00:04:16 fedora cupsd[1148]: REQUEST localhost - - "POST / HTTP/1.1" 200 193 Renew-Subscription successf      6 ul-ok
  7 Feb 27 00:07:14 fedora systemd[1]: Starting Generate a daily summary of process accounting...
  8 Feb 27 00:07:15 fedora journal[3316]: JS LOG: [LookingGlass/info] bbcwx (instance 2): refreshing forecast at 00      8 :07:15
  9 Feb 27 00:07:30 fedora systemd[1]: sysstat-summary.service: Deactivated successfully.
 10 Feb 27 00:07:30 fedora systemd[1]: Finished Generate a daily summary of process accounting.
 11 Feb 27 00:07:30 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_     11 r:init_t:s0 msg='unit=sysstat-summary comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=     11 ? res=success'
 12 Feb 27 00:07:30 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r     12 :init_t:s0 msg='unit=sysstat-summary comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?     12  res=success'
 13 Feb 27 00:10:14 fedora systemd[1]: Starting system activity accounting tool...
 14 Feb 27 00:10:40 fedora journal[3257]: secret_password_store_sync() failed: Timeout was reached
 15 Feb 27 00:10:40 fedora journal[3257]: /org/gnome/OnlineAccounts/Accounts/account_1633030131_0: Setting Attentio     15 nNeeded to TRUE because EnsureCredentials() failed with: Failed to store credentials in the keyring (goa-error-     15 quark, 4)
 16 Feb 27 00:10:54 fedora systemd[1]: sysstat-collect.service: Deactivated successfully.
 17 Feb 27 00:10:54 fedora systemd[1]: Finished system activity accounting tool.
 18 Feb 27 00:10:54 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_     18 r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=     18 ? res=success'
 19 Feb 27 00:10:54 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r     19 :init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?     19  res=success'
 20 Feb 27 00:11:06 fedora journal[3257]: secret_password_lookup_sync() failed: Timeout was reached
 21 Feb 27 00:11:31 fedora rsyslogd[1000]: [origin software="rsyslogd" swVersion="8.2102.0-4.fc35" x-pid="1000" x-i     21 nfo="https://www.rsyslog.com"] rsyslogd was HUPed
 22 Feb 27 00:12:00 fedora journal[3316]: JS LOG: [LookingGlass/info] [weather@mockturtl#14]: Weather Information r     22 efreshed
 23 Feb 27 00:12:13 fedora gnome-keyring-daemon[2741]: asked to register item /org/freedesktop/secrets/collection/l     23 ogin/1, but it's already registered
 24 Feb 27 00:18:34 fedora systemd[1]: Starting Package management dnf daemon...
 25 Feb 27 00:20:00 fedora systemd[1]: Starting system activity accounting tool...
 26 Feb 27 00:20:02 fedora systemd[1]: sysstat-collect.service: Deactivated successfully.
 27 Feb 27 00:20:02 fedora systemd[1]: Finished system activity accounting tool.
 28 Feb 27 00:20:02 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-c
 28 ollect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 29 Feb 27 00:20:02 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-co
 29 llect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 30 Feb 27 00:20:04 fedora systemd[1]: dnfdaemon.service: start operation timed out. Terminating.
 31 Feb 27 00:20:04 fedora systemd[1]: dnfdaemon.service: Failed with result 'timeout'.
 32 Feb 27 00:20:04 fedora systemd[1]: Failed to start Package management dnf daemon.
 33 Feb 27 00:20:04 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnfdaemon
 33  comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
 34 Feb 27 00:21:05 fedora systemd[1]: Starting Package management dnf daemon...
 35 Feb 27 00:21:08 fedora systemd[1]: Started Package management dnf daemon.
 36 Feb 27 00:21:08 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnfdaemon     36  comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 37 Feb 27 00:30:14 fedora systemd[1]: Starting system activity accounting tool...
 38 Feb 27 00:30:17 fedora systemd[1]: sysstat-collect.service: Deactivated successfully.
 39 Feb 27 00:30:17 fedora systemd[1]: Finished system activity accounting tool.
 40 Feb 27 00:30:17 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-c     40 ollect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 41 Feb 27 00:30:17 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-co     41 llect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 42 Feb 27 00:33:08 fedora systemd[1]: mlocate-updatedb.service: Deactivated successfully.
 43 Feb 27 00:33:08 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=mlocate-up     43 datedb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 44 Feb 27 00:33:08 fedora systemd[1]: mlocate-updatedb.service: Consumed 4.926s CPU time.
 45 Feb 27 00:33:08 fedora audit: BPF prog-id=0 op=UNLOAD
 46 Feb 27 00:36:47 fedora journal[3316]: JS LOG: [LookingGlass/info] bbcwx (instance 2): refreshing forecast at 00:36:47
 47 Feb 27 00:39:33 fedora systemd[1]: dnfdaemon.service: Deactivated successfully.
 48 Feb 27 00:39:33 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnfdaemon      48 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 49 Feb 27 00:39:33 fedora systemd[1]: dnfdaemon.service: Consumed 6.423s CPU time.
 50 Feb 27 00:40:14 fedora systemd[1]: Starting system activity accounting tool...
 51 Feb 27 00:40:15 fedora journal[3257]: /org/gnome/OnlineAccounts/Accounts/account_1633030131_0: Setting AttentionNeeded to FALSE because Ensure     51 Credentials() succeded
 52 Feb 27 00:40:16 fedora systemd[1]: sysstat-collect.service: Deactivated successfully.
 53 Feb 27 00:40:16 fedora systemd[1]: Finished system activity accounting tool.
 54 Feb 27 00:40:16 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-c     54 ollect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 55 Feb 27 00:40:16 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-co     55 llect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 56 Feb 27 00:42:07 fedora journal[3316]: JS LOG: [LookingGlass/info] [weather@mockturtl#14]: Weather Information refreshed
 57 Feb 27 00:50:14 fedora systemd[1]: Starting system activity accounting tool...
 58 Feb 27 00:50:14 fedora systemd[1]: sysstat-collect.service: Deactivated successfully.
 59 Feb 27 00:50:14 fedora systemd[1]: Finished system activity accounting tool.
 60 Feb 27 00:50:14 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-cmessages.txt lines 24-60/17695 0%

Could you please clarify? Are you generally seeing a slow/laggy system or is it just slow to get to the login screen (which is a separate “slow boot” issue)?

It’s possible that you may be in “Power Save” mode, especially if your battery level is below 20%. Assuming this is Gnome, if you click on the top right, you should see the switch for this around the bottom:
image

If you aren’t using Gnome, you should be able to use powerprofilesctl to change it.

1 Like

“power save” – it is plugin.

login screen – ~10-30 minutes –
slow/laggy system – work it in laggy systems it is worked, and sometimes ~10 minutes, and sometimes shutdown the machine.

That probably explains your low CPU. You can change it to Balanced or Performance (if your computer supports it) and you should see an improvement in performance. It currently doesn’t automatically switch profiles based on power source, though I recently wrote a script to do that.

1 Like

do the kde setting → Hardware → Power Mgmt ?
i am “Power Mgmt config module could not be loaded”.

it is script, error?

$ sudo ./battery
[sudo] password for perrytsacoumis:
signal time=1647457626.025058 sender=:1.17 → destination=(null destination) serial=807 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 124, in get_profiles_property
profiles = proxy.Get(’(ss)’, ‘net.hadess.PowerProfiles’, prop)
File “/usr/lib/python3.10/site-packages/gi/overrides/Gio.py”, line 349, in call
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (3)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 132, in _list
profiles = get_profiles_property(‘Profiles’)
File “/usr/bin/powerprofilesctl”, line 126, in get_profiles_property
raise ReferenceError
ReferenceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 262, in
main()
File “/usr/bin/powerprofilesctl”, line 218, in main
_list()
File “/usr/bin/powerprofilesctl”, line 138, in _list
raise SystemError
SystemError
Changing power level to balanced
Error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
signal time=1647457746.026274 sender=:1.17 → destination=(null destination) serial=810 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 124, in get_profiles_property
profiles = proxy.Get(’(ss)’, ‘net.hadess.PowerProfiles’, prop)
File “/usr/lib/python3.10/site-packages/gi/overrides/Gio.py”, line 349, in call
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (3)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 132, in _list
profiles = get_profiles_property(‘Profiles’)
File “/usr/bin/powerprofilesctl”, line 126, in get_profiles_property
raise ReferenceError
ReferenceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 262, in
main()
File “/usr/bin/powerprofilesctl”, line 218, in main
_list()
File “/usr/bin/powerprofilesctl”, line 138, in _list
raise SystemError
SystemError
Changing power level to balanced

Try it this way:

powerprofilesctl set $(powerprofilesctl list | head -1 | sed 's,[*:],,g')

I have a Kinoite install here and I don’t know how to do this within KDE graphically, but powerprofilesctl works here for me.

A more intuitive way to use it is run powerprofilesctl list to see which profiles yours supports (performance, balanced, power-saver). Use powerprofilectl set balanced (or another level) to change it. You can also use powerprofilectl get to see which mode it is currently running.

It looks like the KDE program that hooks into this is powerdevil.

dnf install powerdevil should install it and then you should be able to do this within Plasma from there.

  •    if [ $BATT_STAT -eq 1 ] || [ $BATT_STAT -eq 4 ]; then
              LEVEL=$(powerprofilesctl set $(powerprofilesctl list | head -1 | sed 's,[*:],,g'))
    

$ sudo powerprofilesctl list

powerprofilesctl list
Couldn’t get Profiles: <class ‘ReferenceError’>
Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 124, in get_profiles_property
profiles = proxy.Get(’(ss)’, ‘net.hadess.PowerProfiles’, prop)
File “/usr/lib/python3.10/site-packages/gi/overrides/Gio.py”, line 349, in call
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (3)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 132, in _list
profiles = get_profiles_property(‘Profiles’)
File “/usr/bin/powerprofilesctl”, line 126, in get_profiles_property
raise ReferenceError
ReferenceError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/bin/powerprofilesctl”, line 262, in
main()
File “/usr/bin/powerprofilesctl”, line 218, in main
_list()
File “/usr/bin/powerprofilesctl”, line 138, in _list
raise SystemError
SystemError

$ sudo dnf install powerdevil
[sudo] password for perrytsacoumis:
aircrack-ng_git 933 B/s | 1.8 kB 00:02
aircrack-ng_git-source 994 B/s | 951 B 00:00
Package powerdevil-5.24.2-1.fc35.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

$ powerdevil
bash: powerdevil: command not found…

$ which powerdevil
bash: type: powerdevil: not found

I’m guessing the power-profiles-daemon isn’t running?

systemctl status power-profiles-daemon.service

You can turn it on with systemctl enable --now power-profiles-daemon

1 Like

$ systemctl status power-profiles-daemon.service
○ power-profiles-daemon.service
Loaded: masked (Reason: Unit power-profiles-daemon.service is masked.)
Active: inactive (dead)

$ systemctl enable --now power-profiles-daemon
Failed to enable unit: Unit file /etc/systemd/system/power-profiles-daemon.service is masked.

Well, we’re getting somewhere now. I’m not sure why it would be masked unless you are using a different power profile service, but if you didn’t mean to disable it, you can run it with:

systemctl unmask power-profiles-daemon
systemctl enable --now power-profiles-daemon
$ systemctl unmask power-profiles-daemon
Removed /etc/systemd/system/power-profiles-daemon.service.
$ systemctl enable --now power-profiles-daemon


$ systemctl status power-profiles-daemon.service
● power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-17 20:30:29 EDT; 1min 46s ago
   Main PID: 202963 (power-profiles-)
      Tasks: 3 (limit: 14139)
     Memory: 1.6M
        CPU: 97ms
     CGroup: /system.slice/power-profiles-daemon.service
             └─202963 /usr/libexec/power-profiles-daemon

Mar 17 20:30:28 fedora systemd[1]: Starting Power Profiles daemon...
Mar 17 20:30:29 fedora systemd[1]: Started Power Profiles daemon.

$ sudo powerprofilesctl list
  performance:
    Driver:     intel_pstate
    Degraded:   no

* balanced:
    Driver:     intel_pstate

  power-saver:
    Driver:     intel_pstate

i am your first script!!

$ sudo ./battery-new
[sudo] password for perrytsacoumis: 
signal time=1647564198.020290 sender=:1.14 -> destination=(null destination) serial=1078 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
Changing power level to performance
()
signal time=1647564318.098404 sender=:1.14 -> destination=(null destination) serial=1080 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
Changing power level to performance
()
....

kde settings → Power Mgmt → “Power Mgmt config module could not loaded” ?
i am restate/shutdown machine?

Thank you!!

question: why it would be masked unless you are using a different power profile service?

1 Like

I’m honestly not sure why it would be masked. It hasn’t been on my gnome or KDE machines. My guess is that message is because the service wasn’t running when the kde plasma loaded in your session. I honestly don’t know as much about how the kde equivalent works as I do the Gnome one.

Are you seeing performance improvements with the change?

1 Like

So, I downloaded the KDE Fedora 35 spin image, and ran it in a virtual machine, and the power-profiles-daemon is not masked. it’s running and is enabled by default in the live image, and so will be in an installed system too.

Have you at some point disabled/masked services? Has another administrator perhaps? If not, how did you install this Fedora Linux system?

Are you seeing performance improvements with the change?

no.

$ systemctl status power-profiles-daemon.service
● power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-03-18 19:44:56 EDT; 12min ago
   Main PID: 990 (power-profiles-)
      Tasks: 3 (limit: 14139)
     Memory: 1.4M
        CPU: 43ms
     CGroup: /system.slice/power-profiles-daemon.service
             └─990 /usr/libexec/power-profiles-daemon

Mar 18 19:44:29 fedora systemd[1]: Starting Power Profiles daemon...
Mar 18 19:44:56 fedora systemd[1]: Started Power Profiles daemon.

i still login screen & slow system:
login screen – ~10-30 minutes –
slow/laggy system – work it in laggy systems it is worked, and sometimes ~10 minutes, and sometimes shutdown the machine.

do i is shutdown machine called /usr/libexec/baloo_file_extractor?

Ah, now we’re getting somewhere. Baloo is an indexer, so you’re getting a ton of disk and cpu I/O while that is running. Generally, the indexer is for speeding up things like searching for files and it isn’t strictly necessary, so it’s definitely safe to stop it when you notice it impacting performance or disable it outright if it’s a continual problem.

1 Like

do i am write any Fedora 35 operating system again?