Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: 15.2 login VERY slow

  1. #1

    Default 15.2 login VERY slow

    On a new installation of 15.2 on a i9-10900k dual monitor system using kernel 64 5.3.18-lp152.57.1 (using nvidia drivers 390.138-lp152.33.1 for a GTX 1080 Ti), I have encountered a delay problem that I can't seem to isolate. The symptoms are:

    Power on to solicitation of user id and password is less that 10 seconds
    From entering password to presentation of desktop is 90 seconds

    What? Looking in the systemd journal, /var/log/messages, /var/log/boot.log, and the X log, I can find no problems. The display does exhibit some unusual behavior during the delay: each screen goes all black at different times only to return to the login solicitation, the KDE logo is displayed briefly, then the normal desktop is presented. From this time forward, all functions are normal and the system performs perfectly. This behavior was not observer on 15.1. Any help on how to fix this problem, monitor it during the 90 second delay, or where to look for log information would be greatly appreciated. Thank you...

  2. #2
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    851

    Default Re: 15.2 login VERY slow

    Can you show your output from
    Code:
    systemd-analyze blame

  3. #3

    Default Re: 15.2 login VERY slow

    (I have tried disabling all autostarts, removing non-essentials in fstab, changing/removing all themes, and disabling all network connections. All to no effect whatsoever.)

    This is it:

    systemd-analyze blame
    5.915s NetworkManager-wait-online.service
    2.374s systemd-fsck@dev-disk-by\x2dlabel-DataRAID.service
    2.161s data.mount
    1.569s btrfsmaintenance-refresh.service
    1.535s smartd.service
    1.172s dracut-initqueue.service
    1.157s lvm2-monitor.service
    883ms display-manager.service
    871ms postfix.service
    569ms NAS.mount
    378ms sshd.service
    373ms plymouth-quit-wait.service
    363ms vboxdrv.service
    306ms initrd-switch-root.service
    298ms udisks2.service
    296ms firewalld.service
    229ms GAMING.mount
    226ms apparmor.service
    167ms systemd-vconsole-setup.service
    136ms upower.service
    93ms plymouth-switch-root.service
    91ms mcelog.service
    76ms rsyslog.service
    75ms lm_sensors.service
    69ms initrd-parse-etc.service
    64ms boot-efi.mount
    48ms nscd.service
    47ms user@1000.service
    46ms kbdsettings.service
    42ms systemd-udevd.service
    42ms klog.service
    41ms systemd-journal-flush.service
    41ms dev-disk-by\x2dlabel-swap.swap
    37ms vboxautostart.service
    36ms chronyd.service
    36ms ModemManager.service
    35ms user-runtime-dir@1000.service
    35ms systemd-udev-trigger.service
    35ms iscsi.service
    33ms systemd-user-sessions.service
    31ms avahi-daemon.service
    30ms NetworkManager.service
    29ms systemd-fsck@dev-disk-by\x2dlabel-VMachines.service
    28ms bluetooth.service
    23ms systemd-fsck@dev-disk-by\x2dlabel-EFI.service
    23ms sys-fs-fuse-connections.mount
    23ms rtkit-daemon.service
    21ms auditd.service
    20ms dracut-cmdline.service
    19ms srv.mount
    19ms boot-grub2-x86_64\x2defi.mount
    18ms plymouth-start.service
    18ms systemd-tmpfiles-clean.service
    18ms apcupsd.service
    18ms boot-grub2-i386\x2dpc.mount
    17ms wpa_supplicant.service
    16ms systemd-update-utmp-runlevel.service
    15ms tmp.mount
    15ms sysroot.mount
    15ms usr-local.mount
    14ms systemd-fsck-root.service
    13ms var.mount
    13ms home.mount
    12ms dracut-shutdown.service
    12ms systemd-update-utmp.service
    12ms systemd-tmpfiles-setup.service
    11ms systemd-journald.service

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,255

    Default Re: 15.2 login VERY slow

    Blame is for pre-login OP indicates problem after login before desktop. May have to do with video drivers since he uses multiple monitors.
    does problem happen if you log out then back in??? Does it happen with a different user???

  5. #5

    Default Re: 15.2 login VERY slow

    I agree that the problem is after logon. Logoff/logon yields a repeat of the same problem. Other users see the same behavior. I can't seem to find any logs or other records or displays (like ESC during boot) of what occurs between logon and desktop. I really appreciate any help here...

  6. #6
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    851

    Default Re: 15.2 login VERY slow

    As gogalthorp mentioned, blame isn't showing anything after login. I asked for it because I've had issues when it took forever the system to be ready after login and the issue was due to fstrim trimming for >~15 minutes on each boot.

    How did you install the Nvidia driver? 390 is rather old for the 1080Ti I think.

  7. #7
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,407

    Default Re: 15.2 login VERY slow

    Quote Originally Posted by qqwasder View Post
    From entering password to presentation of desktop is 90 seconds

    The display does exhibit some unusual behavior during the delay: each screen goes all black at different times only to return to the login solicitation, the KDE logo is displayed briefly, then the normal desktop is presented.
    Take a look at ‘~/.local/share/sddm/????.log’ – you can write a startup script to
    Code:
    echo "$(printf '%(%Y-%m-%d %H:%M:%S)T' -1)"
    which will drop time-stamps into the SDDM log file – add some “sleep” statements to spread the time-stamps through the log file …

  8. #8

    Default Re: 15.2 login VERY slow

    I updated nvidia today to 390.141 (from 390.138) through yast. Same problem - sigh. I was hoping for magic...

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,992

    Default Re: 15.2 login VERY slow

    Quote Originally Posted by qqwasder View Post
    (I have tried disabling all autostarts, removing non-essentials in fstab, changing/removing all themes, and disabling all network connections. All to no effect whatsoever.)

    This is it:

    systemd-analyze blame
    5.915s NetworkManager-wait-online.service
    2.374s systemd-fsck@dev-disk-by\x2dlabel-DataRAID.service
    2.161s data.mount
    1.569s btrfsmaintenance-refresh.service
    1.535s smartd.service
    1.172s dracut-initqueue.service
    1.157s lvm2-monitor.service
    883ms display-manager.service
    871ms postfix.service
    569ms NAS.mount
    378ms sshd.service
    373ms plymouth-quit-wait.service
    363ms vboxdrv.service
    306ms initrd-switch-root.service
    298ms udisks2.service
    296ms firewalld.service
    229ms GAMING.mount
    226ms apparmor.service
    167ms systemd-vconsole-setup.service
    136ms upower.service
    93ms plymouth-switch-root.service
    91ms mcelog.service
    76ms rsyslog.service
    75ms lm_sensors.service
    69ms initrd-parse-etc.service
    64ms boot-efi.mount
    48ms nscd.service
    47ms user@1000.service
    46ms kbdsettings.service
    42ms systemd-udevd.service
    42ms klog.service
    41ms systemd-journal-flush.service
    41ms dev-disk-by\x2dlabel-swap.swap
    37ms vboxautostart.service
    36ms chronyd.service
    36ms ModemManager.service
    35ms user-runtime-dir@1000.service
    35ms systemd-udev-trigger.service
    35ms iscsi.service
    33ms systemd-user-sessions.service
    31ms avahi-daemon.service
    30ms NetworkManager.service
    29ms systemd-fsck@dev-disk-by\x2dlabel-VMachines.service
    28ms bluetooth.service
    23ms systemd-fsck@dev-disk-by\x2dlabel-EFI.service
    23ms sys-fs-fuse-connections.mount
    23ms rtkit-daemon.service
    21ms auditd.service
    20ms dracut-cmdline.service
    19ms srv.mount
    19ms boot-grub2-x86_64\x2defi.mount
    18ms plymouth-start.service
    18ms systemd-tmpfiles-clean.service
    18ms apcupsd.service
    18ms boot-grub2-i386\x2dpc.mount
    17ms wpa_supplicant.service
    16ms systemd-update-utmp-runlevel.service
    15ms tmp.mount
    15ms sysroot.mount
    15ms usr-local.mount
    14ms systemd-fsck-root.service
    13ms var.mount
    13ms home.mount
    12ms dracut-shutdown.service
    12ms systemd-update-utmp.service
    12ms systemd-tmpfiles-setup.service
    11ms systemd-journald.service
    From the top post I see your machine has one of the lastest and greatest Intel processors. But your output of systemd-analyze blame shows really abysmal performance. Compare your output to the following:
    Code:
    3400G:~ # systemd-analyze blame |head -55 
    916ms dracut-pre-udev.service                         
    795ms dracut-initqueue.service                        
    679ms display-manager.service                         
    388ms systemd-journal-flush.service                   
    363ms initrd-switch-root.service                      
    327ms postfix.service                                 
    307ms plymouth-quit-wait.service                      
    213ms mcelog.service                                  
    199ms user@1000.service                               
    184ms systemd-resolved.service                        
    183ms initrd-parse-etc.service                        
    183ms udisks2.service                                 
    138ms sysroot.mount                                   
    111ms polkit.service                                  
    101ms apache2.service                                 
     98ms home.mount                                      
     90ms systemd-udev-trigger.service                    
     86ms systemd-udevd.service                           
     85ms upower.service                                  
     80ms issue-generator.service                         
     76ms systemd-networkd.service                        
     74ms lm_sensors.service                              
     66ms ModemManager.service                            
     64ms kbdsettings.service                             
     55ms avahi-daemon.service                            
     44ms systemd-logind.service                          
     37ms chronyd.service                                 
     32ms plymouth-read-write.service                     
     26ms plymouth-switch-root.service                    
     25ms systemd-fsck-root.service                       
     24ms modprobe@fuse.service                           
     24ms dracut-cmdline.service                          
     24ms systemd-journald.service                        
     24ms systemd-tmpfiles-clean.service                  
     22ms boot-efi.mount                                  
     19ms systemd-tmpfiles-setup.service                  
     16ms modprobe@configfs.service                       
     14ms plymouth-start.service                          
     13ms \x2esnapshots.mount                             
     12ms systemd-vconsole-setup.service                  
     12ms initrd-cleanup.service                          
     12ms dev-hugepages.mount                             
     12ms dev-mqueue.mount                                
     12ms boot-grub2-i386\x2dpc.mount                     
     11ms sys-kernel-debug.mount                          
     11ms systemd-tmpfiles-setup-dev.service              
     11ms systemd-sysctl.service                          
     11ms modprobe@drm.service                            
     11ms sys-kernel-tracing.mount                        
     11ms boot-grub2-x86_64\x2defi.mount                  
      9ms opt.mount                                       
      9ms systemd-remount-fs.service                      
      9ms kmod-static-nodes.service                       
      9ms user-runtime-dir@1000.service                   
      9ms systemd-random-seed.service                     
    3400G:~ #
    Startup times are:

    Code:
    3400G:~ # 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 @1.688s 
    └─display-manager.service @1.008s +679ms
      └─apache2.service @906ms +101ms
        └─time-sync.target @898ms 
          └─chronyd.service @860ms +37ms
            └─nss-lookup.target @859ms 
              └─systemd-resolved.service @673ms +184ms
                └─systemd-tmpfiles-setup.service @652ms +19ms
                  └─systemd-journal-flush.service @263ms +388ms
                    └─var.mount @255ms +6ms
                      └─local-fs-pre.target @246ms 
                        └─systemd-tmpfiles-setup-dev.service @234ms +11ms
                          └─kmod-static-nodes.service @215ms +9ms
                            └─systemd-journald.socket 
                              └─-.mount 
                                └─system.slice 
                                  └─-.slice 
    3400G:~ #
    
    






    You can show details of your hardware by running:
    Code:
    3400G:~ # inxi -zFm 
    System:    Kernel: 5.11.0-rc3-1.g840b25f-vanilla x86_64 bits: 64 Console: tty 1 Distro: openSUSE Tumbleweed 20210108  
    Machine:   Type: Desktop Mobo: Gigabyte model: B450 AORUS ELITE v: x.x serial: N/A UEFI: American Megatrends v: F52  
               date: 07/29/2020  
    Memory:    RAM:total: 29.32 GiB used: 2.33 GiB (8.0%)  
               Array-1:capacity: 128 GiB slots: 4 EC: None  
               Device-1: DIMM 0 size: No Module Installed  
               Device-2: DIMM 1 size: 16 GiB speed: 2133 MT/s  
               Device-3: DIMM 0 size: No Module Installed  
               Device-4: DIMM 1 size: 16 GiB speed: 2133 MT/s  
    CPU:       Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP L2 cache: 2048 KiB  
               Speed: 1258 MHz min/max: 1400/3700 MHz Core speeds (MHz):1: 1261 2: 1259 3: 1259 4: 1259 5: 1349 6: 1326 7: 1258  
               8: 1258  
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel  
               Display:server: X.Org 1.20.10 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1200~60Hz  
               OpenGL:renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.11.0-rc3-1.g840b25f-vanilla LLVM 11.0.0)  
               v: 4.6 Mesa 20.3.2  
    Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel  
               Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel  
               Sound Server: ALSA v: k5.11.0-rc3-1.g840b25f-vanilla  
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169  
               IF: eth0 state: down mac: <filter>  
               Device-2: Qualcomm Atheros AR9287 Wireless Network Adapter driver: ath9k  
               IF: wlan0 state: up mac: <filter>  
    Drives:    Local Storage:total: 2.50 TiB used: 307.46 GiB (12.0%)  
               ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB  
               ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB  
               ID-3: /dev/sdc vendor: Seagate model: ST2000DM001-1CH164 size: 1.82 TiB  
    Partition: ID-1: / size: 40.00 GiB used: 15.73 GiB (39.3%) fs: btrfs dev: /dev/sda3  
               ID-2: /home size: 427.82 GiB used: 291.70 GiB (68.2%) fs: ext4 dev: /dev/sdb3  
               ID-3: /opt size: 40.00 GiB used: 15.73 GiB (39.3%) fs: btrfs dev: /dev/sda3  
               ID-4: /tmp size: 40.00 GiB used: 15.73 GiB (39.3%) fs: btrfs dev: /dev/sda3  
               ID-5: /var size: 40.00 GiB used: 15.73 GiB (39.3%) fs: btrfs dev: /dev/sda3  
    Swap:      Alert: No Swap data was found.  
    Sensors:   System Temperatures:cpu: 30.5 C mobo: 27.0 C gpu: amdgpu temp: 30 C  
               Fan Speeds (RPM):cpu: 0 fan-1: 0 fan-3: 0  
    Info:      Processes: 282 Uptime: N/A Shell: bash inxi: 3.1.00  
    3400G:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  10. #10

    Default Re: 15.2 login VERY slow

    The confusing thing is that the time from power-on to solicitation for login credentials is normal, but from login enter to desktop presentation is 90 seconds. Investigating what is going on during that delay is what I can't find any information or tools for...

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •