Bug ID 1183568
Summary ������������������kmod-static-nodes.service @4.168s +10.122s makes init unduly long
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.3
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee screening-team-bugs@suse.de
Reporter mrmazda@earthlink.net
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Original summary:
������������������kmod-static-nodes.service @4.168s +10.122s makes init unduly long

Same PC also has another 15.3 and TW and 15.2. TW takes under 4s to reach
multi-user. 15.2 takes much less than the two 15.3s, but much more than TW, to
same target.  kmod-static-nodes seems the biggest delay in the 15.3s.

Every installation except one 15.3 is on SATA SSD in UEFI. The odd one is on
NVME except for /boot on SATA, and it has its own unshared ESP there. All are
being booted from TW's custom.cfg. Following is from the 15.3 on SATA:
# inxi -SMdy
System:
  Host: asa88 Kernel: 5.3.18-51-default x86_64 bits: 64 Console: tty 3 
  Distro: openSUSE Leap 15.3 Beta 
Machine:
  Type: Desktop Mobo: ASUSTeK model: A88X-PRO v: Rev X.0x 
  serial: 140323952800121 UEFI: American Megatrends v: 2603 date: 03/10/2016 
Drives:
  Local Storage: total: 715.41 GiB used: 728.23 GiB (101.8%) 
  ID-1: /dev/nvme0n1 vendor: TeamGroup model: TM8FP6256G size: 238.47 GiB 
  ID-2: /dev/sda model: T-FORCE 512GB size: 476.94 GiB 
  Message: No Optical or Floppy data was found. 
# systemd-analyze blame | head -n22
10.566s systemd-udev-trigger.service                          
10.385s systemd-modules-load.service                          
10.383s systemd-remount-fs.service                            
10.379s systemd-journald.service                              
10.190s dev-disk-by\x2dlabel-tvgp02swap.swap                  
10.161s modprobe@drm.service                                  
10.144s dev-hugepages.mount                                   
10.144s dev-mqueue.mount                                      
10.143s sys-kernel-debug.mount                                
10.142s sys-kernel-tracing.mount                              
10.131s modprobe@fuse.service                                 
10.125s modprobe@configfs.service                             
10.122s kmod-static-nodes.service                             
 3.967s initrd-switch-root.service                            
 2.183s systemd-random-seed.service                           
 2.076s kbdsettings.service                                   
 1.699s wicked.service                                        
 1.188s dracut-initqueue.service                              
  584ms systemd-logind.service                                
  509ms systemd-udevd.service                                 
  301ms initrd-parse-etc.service                              
  269ms user@0.service                                        
# 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.

������������������multi-user.target @16.889s
  ������������������sshd.service @16.827s +60ms
    ������������������network.target @16.826s
      ������������������wicked.service @15.124s +1.699s
        ������������������wickedd-nanny.service @15.059s +63ms
          ������������������wickedd.service @14.982s +75ms
            ������������������wickedd-auto4.service @14.853s +127ms
              ������������������dbus.service @14.791s
                ������������������basic.target @14.787s
                  ������������������sockets.target @14.787s
                    ������������������dbus.socket @14.786s
                      ������������������sysinit.target @14.781s
                        ������������������systemd-udevd.service @14.271s +509ms
                          ������������������systemd-tmpfiles-setup-dev.service @14.225s +29ms
                            ������������������kmod-static-nodes.service @3.821s +10.122s
                              ������������������systemd-journald.socket
                                ������������������system.slice
                                  ������������������-.slice


You are receiving this mail because: