After upgrade 364 packages on 20 Jul 2020 system boot slowly

I install last manjaro gnome edition and it has some update everyday . but on 20 Jul 2020 my system has 364 upgrade for all packages . something like kernel upgrade too. but after upgrade my system boot slowly and take time to start login page.
Can I remove everything in home folder and reboot system. maybe this this.

~ >>> sudo inxi -Fxxxz                                                                                                                               
[sudo] password for mostafa: 
System:    Host: faridi Kernel: 5.6.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: Gnome 3.36.4 wm: gnome-shell 
           dm: GDM 3.36.3 Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 20NB0057UE v: ThinkPad E590 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: LENOVO model: 20NB0057UE serial: <filter> UEFI: LENOVO v: R0YET32W (1.15 ) date: 06/10/2019 
Battery:   ID-1: BAT0 charge: 37.0 Wh condition: 47.4/45.3 Wh (105%) volts: 11.8/11.1 model: SMP 01AV446 type: Li-poly 
           serial: <filter> status: Discharging cycles: 42 
CPU:       Topology: Dual Core model: Intel Core i3-8145U bits: 64 type: MT MCP arch: Kaby Lake rev: C L1 cache: 128 KiB 
           L2 cache: 4096 KiB L3 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 18406 
           Speed: 1300 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 1212 2: 1200 3: 1200 4: 1200 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 
           Display: server: X.org 1.20.8 driver: i915 compositor: gnome-shell resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:9dc8 
           Sound Server: ALSA v: k5.6.19-2-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel port: 2000 
           bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: enp4s0 state: down mac: <filter> 
           Device-2: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: 2000 bus ID: 05:00.0 chip ID: 8086:2526 
           IF: wlp5s0 state: up mac: <filter> 
           IF-ID-1: ip_vti0 state: down mac: <filter> 
           IF-ID-2: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 931.51 GiB used: 78.15 GiB (8.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: LFM1 scheme: GPT 
Partition: ID-1: / size: 915.60 GiB used: 78.15 GiB (8.5%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 0.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 251 Uptime: 20m Memory: 3.69 GiB used: 1.68 GiB (45.4%) Init: systemd v: 245 Compilers: gcc: 10.1.0 
           Shell: bash (sudo) v: 5.0.18 running in: gnome-terminal inxi: 3.0.37 

Have you checked the known issues section of the stable announcement?

The home folder is not even accessed until you log in. That wouldn't speed up the boot time. Maybe there were some things from the update that had to be completed on the first reboot. Have you tried rebooting again to see if the problem persists?

Please, post output of

systemd-analyze critical-chain

Are you using baloo file indexing and searching framework? This could slow down your system for a short period of time after a big update depending on settings.

https://wiki.archlinux.org/index.php/Baloo

~ >>> sudo systemd-analyze critical-chain                                                                                                            
[sudo] password for mostafa: 
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 @21.013s
└─multi-user.target @21.013s
  └─ModemManager.service @19.784s +1.228s
    └─polkit.service @15.949s +3.832s
      └─basic.target @15.936s
        └─sockets.target @15.936s
          └─snapd.socket @15.935s +1ms
            └─sysinit.target @15.775s
              └─systemd-update-utmp.service @15.660s +115ms
                └─systemd-tmpfiles-setup.service @15.096s +561ms
                  └─systemd-journal-flush.service @4.129s +10.966s
                    └─systemd-journald.service @3.628s +499ms
                      └─systemd-journald.socket @3.445s
                        └─system.slice @3.369s
                          └─-.slice @3.369s

can you returns

sudo systemd-analyze blame
sudo mhwd-kernel -li
sudo cat /sys/block/*/queue/scheduler

check also
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_T590

~ >>> sudo systemd-analyze blame                                                                                                                     
[sudo] password for mostafa: 
13.054s NetworkManager-wait-online.service                   
10.966s systemd-journal-flush.service                        
 5.627s lvm2-monitor.service                                 
 5.084s dev-sda2.device                                      
 3.832s polkit.service                                       
 3.666s snapd.service                                        
 3.010s NetworkManager.service                               
 2.658s apparmor.service                                     
 2.626s systemd-logind.service                               
 1.492s user@120.service                                     
 1.436s systemd-udevd.service                                
 1.265s udisks2.service                                      
 1.228s ModemManager.service                                 
 1.196s ipsec.service                                        
  964ms accounts-daemon.service                              
  926ms fprintd.service                                      
  877ms org.cups.cupsd.service                               
  862ms systemd-tmpfiles-setup-dev.service                   
  814ms upower.service                                       
  810ms lm_sensors.service                                   
13.054s NetworkManager-wait-online.service                   
10.966s systemd-journal-flush.service                        
 5.627s lvm2-monitor.service                                 
 5.084s dev-sda2.device                                      
 3.832s polkit.service                                       
 3.666s snapd.service                                        
 3.010s NetworkManager.service                               
 2.658s apparmor.service                                     
 2.626s systemd-logind.service                               
 1.492s user@120.service                                     
 1.436s systemd-udevd.service                                
 1.265s udisks2.service                                      
 1.228s ModemManager.service                                 
 1.196s ipsec.service                                        
  964ms accounts-daemon.service                              
  926ms fprintd.service                                      
  877ms org.cups.cupsd.service                               
  862ms systemd-tmpfiles-setup-dev.service                   
  814ms upower.service                                       
  810ms lm_sensors.service                                   
  695ms systemd-tmpfiles-clean.service                       
  582ms gdm.service                                          
  561ms systemd-tmpfiles-setup.service                       
  542ms tlp.service                                          
  499ms systemd-journald.service                             
  496ms systemd-random-seed.service                          
  420ms systemd-sysctl.service                               
  406ms wpa_supplicant.service                               
  403ms systemd-fsck@dev-disk-by\x2duuid-9267\x2dCF22.service
  402ms systemd-modules-load.service                         
  381ms linux-module-cleanup.service                         
  336ms systemd-udev-trigger.service                         
  331ms systemd-rfkill.service                               
  210ms swapfile.swap                                        
  208ms dev-hugepages.mount                                  
  207ms dev-mqueue.mount                                     
  205ms sys-kernel-debug.mount

and

  ~ >>> sudo mhwd-kernel -li                                                                                                                           
Currently running: 5.6.19-2-MANJARO (linux56)
The following kernels are installed in your system:
   * linux56

and

~ >>> sudo cat /sys/block/*/queue/scheduler                                                                                                          
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none

see this
https://wiki.archlinux.org/index.php/Improving_performance#The_scheduling_algorithms
add this file
/etc/udev/rules.d/60-ioschedulers.rules

# set scheduler for NVMe
ACTION=="add|change", KERNEL=="nvme[0-9]*", ATTR{queue/scheduler}="none"
# set scheduler for SSD and eMMC
ACTION=="add|change", KERNEL=="sd[a-z]|mmcblk[0-9]*", ATTR{queue/rotational}=="0", ATTR{queue/scheduler}="mq-deadline"
# set scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", ATTR{queue/scheduler}="bfq"

and no need for theses services

sudo systemctl mask ModemManager.service
sudo systemctl mask lvm2-monitor.service
sudo systemctl mask NetworkManager-wait-online.service 

next time see for an SSD disk and Ram 8Go or more

3 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by