You are not logged in.

#1 2023-10-10 17:10:12

David Bruckmüller
Member
Registered: 2023-10-09
Posts: 2

[solved] long boot time and low cpu frequency when booting from BAT

My laptop is booting completely normal when the laptop is plugged into the power supply. But when I'm booting from the battery, then the boot time is very long and the cpu frequency is very low. The performance problem persists until I plug in my power supply. After plugging in, the performance is good. The good performance remains after unplugging.
Can someone please help me? Hopefully all important logs are below, sometimes there are only the links to zerobin.net (Pastebin service), because the log files can be very long.

System Information from the KDE Plasma Info Center:

Operating System: Arch Linux
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop X712UA_D712UA
System Version: 1.0

Logfiles when booting from Battery:

sudo systemd-analyze:

Startup finished in 2.036s (firmware) + 1.661s (loader) + 834ms (kernel) + 48.321s (initrd) + 10.886s (userspace) = 1min 3.740s
graphical.target reached after 10.885s in userspace.

sudo systemd-analyze critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @10.885s
└─multi-user.target @10.884s
  └─libvirtd.service @10.486s +395ms
    └─network.target @10.474s
      └─NetworkManager.service @9.605s +865ms
        └─dbus.service @9.385s +143ms
          └─basic.target @9.300s
            └─sockets.target @9.299s
              └─virtlogd.socket @9.299s
                └─sysinit.target @9.284s
                  └─systemd-resolved.service @8.718s +563ms
                    └─systemd-tmpfiles-setup.service @7.336s +1.315s
                      └─local-fs.target @7.293s
                        └─boot.mount @7.014s +272ms
                          └─systemd-fsck@dev-disk-by\x2duuid-E00B\x2d2ED5.service @5.568s +667ms
                            └─dev-disk-by\x2duuid-E00B\x2d2ED5.device @584542y 2w 2d 20h 1min 4.703s +50.322s

sudo systemd-analyze blame --no-pager:
https://zerobin.net/?b9e94c13dfb88829#N … oX6SpaIWQ=

sudo LANG="EN" journalctl -b -p5 --no-pager:
https://zerobin.net/?61f27893ff9e3f2d#+ … KDZGpR30I=


The CPU Frequency Informations before plugging in & when booting from BAT:
sudo LANG="EN" cpupower frequency-info:

analyzing CPU 14:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 14
  CPUs which need to have their frequency coordinated by software: 14
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 399 MHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

The CPU Frequency Informations after plugging in & when booting from BAT:
sudo LANG="EN" cpupower frequency-info:

analyzing CPU 5:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 2.68 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

Logfiles when booting from Power Supply / AC:

sudo systemd-analyze:

Startup finished in 2.019s (firmware) + 1.584s (loader) + 828ms (kernel) + 13.447s (initrd) + 2.801s (userspace) = 20.681s
graphical.target reached after 2.801s in userspace.

sudo systemd-analyze critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2.801s
└─sddm.service @2.800s
  └─plymouth-quit.service @2.651s +116ms
    └─systemd-user-sessions.service @2.602s +45ms
      └─network.target @2.599s
        └─NetworkManager.service @2.450s +147ms
          └─dbus.service @2.421s +25ms
            └─basic.target @2.417s
              └─sockets.target @2.417s
                └─virtlogd.socket @2.417s
                  └─sysinit.target @2.415s
                    └─systemd-resolved.service @2.357s +57ms
                      └─systemd-tmpfiles-setup.service @1.783s +507ms
                        └─local-fs.target @1.664s
                          └─boot.mount @1.537s +125ms
                            └─systemd-fsck@dev-disk-by\x2duuid-E00B\x2d2ED5.service @1.362s +135ms
                              └─dev-disk-by\x2duuid-E00B\x2d2ED5.device @584542y 2w 2d 20h 1min 39.106s +11.800s

sudo systemd-analyze blame --no-pager:
https://zerobin.net/?0f686d7a68ebe110#5 … EdbBj+OxE=

sudo LANG="EN" journalctl -b -p5 --no-pager:
https://zerobin.net/?1d600c9802829c68#V … RDSdXJE1w=

The CPU Frequency Informations when booting with plugged in power supply / AC:
sudo LANG="EN" cpupower frequency-info:

analyzing CPU 12:
  driver: amd-pstate
  CPUs which run at the same hardware frequency: 12
  CPUs which need to have their frequency coordinated by software: 12
  maximum transition latency: 20.0 us
  hardware limits: 400 MHz - 4.37 GHz
  available cpufreq governors: conservative ondemand userspace powersave performance schedutil
  current policy: frequency should be within 400 MHz and 4.37 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 4.33 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 255. Maximum Frequency: 4.37 GHz.
    AMD PSTATE Nominal Performance: 105. Nominal Frequency: 1.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 65. Lowest Non-linear Frequency: 1.11 GHz.
    AMD PSTATE Lowest Performance: 24. Lowest Frequency: 400 MHz.

Last edited by David Bruckmüller (2023-10-14 09:04:35)

Offline

#2 2023-10-14 09:03:14

David Bruckmüller
Member
Registered: 2023-10-09
Posts: 2

Re: [solved] long boot time and low cpu frequency when booting from BAT

The problem is solved, i think the kernel update from version 6.5.6 to 6.5.7 did that.

Offline

Board footer

Powered by FluxBB