About 30 second Delay between boot and able to login

I have no problem with the time it takes to boot to the login screen but once it has the system is frozen (no mouse or keyboard control) on the login screen for about 30 seconds.

The funny thing is that if I modify the boot to go to the command line and then do an

init 5

then there seems to be no problem with a delay.

I don’t see any delay in the system logs but here are the logs so you can see for yourself - any clue as to what could be the cause of this would be appreciated.


systemd-analyze time
Startup finished in 24.411s (firmware) + 2.624s (loader) + 10.201s (kernel) + 2.581s (initrd) + 4.206s (userspace) = 44.025s 


systemd-analyze critical-chain
graphical.target @4.202s
└─display-manager.service @3.643s +558ms
  └─apache2.service @2.894s +748ms
    └─remote-fs.target @2.893s
      └─iscsi.service @2.876s +16ms
        └─network.target @2.873s
          └─network-pre.target @2.417s


systemd-analyze blame
          1.164s srv.mount
           895ms btrfsmaintenance-refresh.service
           790ms plymouth-quit-wait.service
           748ms apache2.service
           713ms tmp.mount
           712ms \x2esnapshots.mount
           685ms postfix.service
           669ms root.mount
           630ms boot-grub2-i386\x2dpc.mount
           595ms var.mount
           558ms boot-grub2-x86_64\x2defi.mount
           558ms display-manager.service
           496ms opt.mount
           492ms ca-certificates.service
           351ms lvm2-monitor.service
           272ms jexec.service
           267ms chronyd.service
           261ms mcelog.service
           253ms initrd-switch-root.service
           242ms kbdsettings.service
           235ms rsyslog.service
           220ms systemd-logind.service
           208ms apparmor.service
           165ms ToRestore.mount
           152ms home.mount
           132ms udisks2.service
           112ms systemd-udev-trigger.service
           105ms usr-local.mount                                                                                                                 
            99ms upower.service                                                                                                                  
            87ms systemd-fsck@dev-disk-by\x2duuid-b30ffeb6\x2d23cf\x2d40c0\x2d8a08\x2d71a5aa06ed2b.service                                       
            62ms boot-efi.mount                                                                                                                  
            59ms initrd-parse-etc.service                                                                                                        
            50ms systemd-vconsole-setup.service                                                                                                  
            44ms sshd.service                                                                                                                    
            40ms systemd-udevd.service                                                                                                           
            33ms sysroot.mount                                                                                                                   
            32ms dracut-cmdline.service                                                                                                          
            32ms dracut-pre-trigger.service                                                                                                      
            28ms user@1000.service                                                                                                               
            17ms klog.service                                                                                                                    
            17ms auditd.service                                                                                                                  
            16ms iscsi.service                                                                                                                   
            16ms plymouth-start.service                                                                                                          
            15ms sys-kernel-debug.mount                                                                                                         
            14ms systemd-journal-flush.service                                                                                                  
            14ms nscd.service                                                                                                                   
            14ms systemd-tmpfiles-setup.service                                                                                                 
            14ms dev-mqueue.mount                                                                                                              
            14ms dracut-pre-udev.service                                                                                                       
            13ms dev-disk-by\x2duuid-6f7781f5\x2d5caf\x2d4dd9\x2daa59\x2d00f9ec46136c.swap                                                     
            13ms dev-hugepages.mount                                                                                                           
            12ms systemd-remount-fs.service                                                                                                    
            12ms initrd-cleanup.service                                                                                                      
            11ms plymouth-read-write.service                                                                                                 
            11ms avahi-daemon.service                                                                                                        
            11ms systemd-tmpfiles-clean.service                                                                                              
            10ms dracut-pre-pivot.service                                                                                                    
             9ms systemd-modules-load.service                                                                                              
             9ms systemd-tmpfiles-setup-dev.service                                                                                        
             9ms systemd-journald.service                                                                                                  
             7ms dracut-pre-mount.service                                                                                                  
             7ms systemd-sysctl.service                                                                                                    
             7ms mdmonitor.service                                                                                                         
             5ms sys-fs-fuse-connections.mount                                                                                             
             4ms systemd-fsck-root.service                                                                                                
             4ms systemd-user-sessions.service                                                                                            
             4ms plexmediaserver.service                                                                                                  
             4ms systemd-random-seed.service                                                                                              
             3ms initrd-udevadm-cleanup-db.service                                                                                        
             3ms rtkit-daemon.service                                                                                                     
             3ms ext4.mount                                                                                                              
             3ms proc-sys-fs-binfmt_misc.mount                                                                                           
             3ms systemd-update-utmp.service                                                                                            
             3ms systemd-update-utmp-runlevel.service                                                                                   
             2ms dracut-shutdown.service                                                                                                
             1ms kmod-static-nodes.service

I’ve never seen that kind of systemd-analyze output (firmware/loader/kernel/initrd/userspace … I only ever get kernel/initd/userspace, that’s it). Obviously an overwhelming span of time is spent within firmware initialisation (»24.411s (firmware)«, much too long) which I would find inacceptable even for a complex server setup (with non-local iSCSI/RAID hardware and/or NUMA and/or external clusters of computing cores on gfx cards whatnot) nowadays. Frankly, this feels more like a long timeout after not being able to find some missing firmware. What could it be?

Reg_gie, could you describe your hardware in more detail, please?
During Leap 15 installation, was any hardware attached that now isn’t anymore?

For comparison, here’s my rather minimal setup (4–5 years old Core i5, Samsung SSD, Mini-ITX ASUS board, NVidia 1050, 8GB RAM):

▶ **systemd-analyze time**
Startup finished in 215ms (kernel) + 727ms (initrd) + 748ms (userspace) = 1.691s

rig:~ ▶ **systemd-analyze blame**
           531ms dev-sda1.device
           290ms display-manager.service
           172ms systemd-journal-flush.service
           112ms NetworkManager.service
            95ms systemd-udevd.service
            81ms upower.service
            71ms polkit.service
            45ms klog.service
            41ms systemd-logind.service
            26ms systemd-udev-trigger.service
            23ms rtkit-daemon.service
            20ms user@1000.service
            19ms sys-kernel-debug.mount
            18ms dev-hugepages.mount
            17ms udisks2.service
            17ms systemd-remount-fs.service
            16ms systemd-modules-load.service
            14ms systemd-tmpfiles-setup.service
            12ms systemd-tmpfiles-setup-dev.service
            12ms dev-mqueue.mount
            11ms systemd-update-utmp.service
            10ms systemd-fsck-root.service
            10ms systemd-tmpfiles-clean.service
             9ms systemd-sysctl.service
             9ms systemd-journald.service
             6ms dracut-shutdown.service
             5ms dev-disk-by\...]08ff.swap
             4ms systemd-random-seed.service
             3ms systemd-user-sessions.service
             2ms systemd-update-utmp-runlevel.service
             2ms kmod-static-nodes.service
             1ms systemd-vconsole-setup.service

▶ **systemd-analyze critical-chain**
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @745ms
└─display-manager.service @454ms +290ms
  └─systemd-user-sessions.service @450ms +3ms
    └─network.target @449ms
      └─NetworkManager.service @337ms +112ms
        └─dbus.service @302ms
          └─basic.target @301ms
            └─sockets.target @300ms
              └─dbus.socket @300ms
                └─sysinit.target @300ms
                  └─swap.target @300ms
                    └─dev-disk-by\…]08ff.swap @294ms +5ms
                      └─dev-disk-by\…]08ff.device @294ms

(These are values from this morning; my best boot time under Leap 15 was 1.378s about a week ago; I’ve adopted several boot-time optimisations, e.g. generating a custom, uncompressed initrd using dracut etc.)

As systemd is not showing a possible culprit I would look at the boot log using “sudo journalctl -b” and keeping the time in mind, check if you see any suspicious messages around the 30 seconds freeze.

I suggest you try booting with “plymouth.enable=0” on the kernel command line. This is just as a test, to see if plymouth is involved.

On the boot menu, hit ‘e’. Scroll down to the line that starts “linux” (or possibly “linuxefi”). Scroll to the right. If there is a string “splash=silent” replace that with “plymouth.enable=0”. Otherwise just append " plymouth.enable=0" to the end of the line. Don’t include the quotes that I show there.

I remember seeing something similar on a system with a fuzzy bluetooth adapter that on occasion hijacked the USB bus for tens of seconds preventing the keyboard input from being read during that time.
If that is your case, make sure that USB peripherals, even internal ones, are disabled and see if that makes a difference.

Nope, no change in hardware with the only exception being the usb stick that I used into install Leap but that is disabled in the repo. manager so I don’t see that being an issue. Here is a summary of my hardware:

hwinfo --short
cpu:
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
                       Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 3060 MHz
keyboard:
  /dev/input/event1    Logitech Illuminated Keyboard
                       Logitech Unifying Receiver
mouse:
                       Logitech Unifying Receiver
monitor:
                       BenQ GL2706PQ
                       Acer K272HUL
                       Acer K272HUL
                       Acer K272HUL
                       Acer K272HUL
                       Acer K272HUL
graphics card:
                       ATI Radeon HD 5870 Eyefinity⁶ Edition
                       Multimedia video controller
sound:
                       Creative SB1550 Audigy 5/Rx
                       ATI Cypress HDMI Audio [Radeon HD 5830/5850/5870 / 6850/6870 Rebrand]
                       Intel C610/X99 series chipset HD Audio Controller
storage:
                       ASMedia ASM1062 Serial ATA Controller
                       Intel C610/X99 series chipset sSATA Controller [AHCI mode]
                       ASMedia ASM1062 Serial ATA Controller
                       Intel C610/X99 series chipset 6-Port SATA Controller [AHCI mode]
network:
  eth1                 Intel Ethernet Connection (2) I218-LM
  eth0                 Intel I210 Gigabit Network Connection
network interface:
  lo                   Loopback network interface
  eth0                 Ethernet network interface
  eth1                 Ethernet network interface
disk:
  /dev/sdf             TS512GSSD370
  /dev/sdd             Samsung SSD 860
  /dev/sdb             TOSHIBA MD04ACA4
  /dev/sdg             TOSHIBA MD04ACA4
  /dev/sde             TS512GSSD370
  /dev/sdc             Samsung SSD 860
  /dev/sda             TOSHIBA MD04ACA4
  /dev/sdh             TOSHIBA MD04ACA4
partition:
  /dev/sdf1            Partition
  /dev/sdf2            Partition
  /dev/sdf3            Partition
  /dev/sdd1            Partition
  /dev/sdd2            Partition
  /dev/sdb1            Partition
  /dev/sdg1            Partition
  /dev/sde1            Partition
  /dev/sde2            Partition
  /dev/sde3            Partition
  /dev/sdc1            Partition
  /dev/sdc2            Partition
  /dev/sda1            Partition
  /dev/sdh1            Partition
cdrom:
  /dev/sr0             HL-DT-ST DVDRAM GH24NS90
  /dev/sr1             ATAPI iHAS120   6
usb controller:
                       Intel C610/X99 series chipset USB Enhanced Host Controller #2
                       Intel C610/X99 series chipset USB Enhanced Host Controller #1
                       Intel C610/X99 series chipset USB xHCI Host Controller
bios:
                       BIOS
bridge:
                       Intel C610/X99 series chipset PCI Express Root Port #4
                       ASMedia PCI bridge
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DMI2
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3
                       ASMedia PCI bridge
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       PLX PEX8112 x1 Lane PCI Express-to-PCI Bridge
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       Intel C610/X99 series chipset PCI Express Root Port #5
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 2
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
                       Intel C610/X99 series chipset PCI Express Root Port #1
                       ASMedia PCI bridge
                       Intel C610/X99 series chipset LPC Controller
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1
                       PLX PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
hub:
                       ASMedia ASM1074 SuperSpeed hub
                       Intel Hub
                       Linux Foundation 2.0 root hub
                       Realtek 4-Port USB 2.0 Hub
                       Linux Foundation 2.0 root hub
                       ASMedia ASM1074 High-Speed hub
                       Linux Foundation 3.0 root hub
                       Intel Hub
                       Realtek 4-Port USB 3.0 Hub
                       ASMedia ASM1074 SuperSpeed hub
                       Linux Foundation 2.0 root hub
memory:
                       Main Memory
unknown:
                       FPU
                       DMA controller
                       PIC
                       Keyboard controller
                       PS/2 Controller
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 ERROR Registers
                       Intel C610/X99 series chipset SMBus Controller
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 Thermal Control
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 ERROR Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 Thermal Control
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1
                       Intel C610/X99 series chipset SPSR
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 ERROR Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 0/1 Broadcast
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 ERROR Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 Thermal Control
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 VCU
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 2/3 Broadcast
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 Thermal Control
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 VCU
                       Intel C610/X99 series chipset MEI Controller #1
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers
                       Intel Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1
                       Logitech Unifying Receiver
  /dev/input/event0    ROCCAT Kave Headset
  /dev/input/event2    Logitech Illuminated Keyboard

Unfortunately that didn’t seem to make any difference but thanks for the idea.

So I rebooted and took note of exactly when it froze and then looked with “sudo journalctl -b” and although this doesn’t represent the fully 30+ secs. it does cover about 20 secs so it could be something to do with it. The only problem is I don’t know how to determine what should be or is at usb 3-10. I tried putting “usbcore.autosuspend=-1” on the kernel boot command line but that didn’t make any difference.

Jan 21 20:01:05 quark NetworkManager[1515]: <info>  [1548126065.3405] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 21 20:01:05 quark nm-dispatcher[1773]: req:4 'connectivity-change': new request (3 scripts)
Jan 21 20:01:05 quark nm-dispatcher[1773]: req:4 'connectivity-change': start running ordered scripts...
Jan 21 20:01:08 quark kernel: usb 3-10: device descriptor read/all, error -110
Jan 21 20:01:08 quark kernel: usb usb3-port10: attempt power cycle
Jan 21 20:01:09 quark kernel: usb 3-10: new high-speed USB device number 9 using xhci_hcd
Jan 21 20:01:14 quark kernel: usb 3-10: device descriptor read/8, error -110
Jan 21 20:01:20 quark kernel: usb 3-10: device descriptor read/8, error -110
Jan 21 20:01:20 quark kernel: usb 3-10: new high-speed USB device number 10 using xhci_hcd
Jan 21 20:01:25 quark kernel: usb 3-10: device descriptor read/8, error -110
Jan 21 20:01:30 quark kernel: usb 3-10: device descriptor read/8, error -110
Jan 21 20:01:30 quark kernel: usb usb3-port10: unable to enumerate USB device

I pulled up my motherboard layout and traced USB 3-10 and it goes to the USB connectors on the front of my case and there is nothing plugged in there. It’s possible that the port is just bad so I’m going to disable it in my BIOS and see if that makes any difference and then I’ll edit this with the result.

Okay that didn’t work it’s still detecting the port. Come to think of it I remember thinking that one or two of the front ports wasn’t working anymore, this might be a hardware failure.

Is there anyway to tell Leap to ignore/not wait on a particular USB port?

https://askubuntu.com/questions/741760/is-it-possible-to-turn-off-a-specific-usb-port-so-it-doesnt-accept-any-device

EDIT: I think you’ll need to tee ‘disabled’ to …/runtime_enabled on openSUSE.

@Reg_gie:
On this Leap 15.0 system, the runtime power status of the USB devices is:


 > cat /sys/bus/usb/devices/usb*/power/runtime_status
active
suspended
active
suspended
suspended
suspended
suspended
 > 

Where, the two active devices are the Keyboard and the Mouse …

All the USB power “level” values are ‘auto’ and, the “wakeup” values are ‘disabled’.
The “runtime_enabled” values are all ‘enabled’.
[HR][/HR]There’s also the Kernel documentation <https://www.kernel.org/doc/html/v4.16/driver-api/usb/power-management.html>.

Unplug the cable going to those front ports?

Funny enough before I saw this answer I just changed my CPU cooler, the pump was dying and the new one had a USB connection… one with LEDs is not something I wanted it was just what Corsair had available as a warranty replacement, anyway, I had no free USB ports on the mother board so I pulled the plug to ports 9/10 which wasn’t the USB 3.0s going to the front but the 2.0 ones that were going to spare unused USB ports on the back. I plugged in the USB connection from the Corsair cooler and the problem just went away.

How never used ports being changed out could fix this problem I don’t know but it’s fixed.