System boot takes ages after upgrading to 6.17 kernel

Everything was great on 6.16, but I started experiencing a slow boot on 6.17-200 with a usb device descriptor read error. Having upgraded to 6.17-300 the usb error only appears once now, but then dracut-initqueue.service takes over a minute to start. Worth noting once it does boot everything works just fine (all usb devices work as expected, etc.) it just then fails to wake from sleep.

Waking the system from sleep is also now suddenly very slow (black screen for 30+ seconds) and when it recovers my keyboard has stopped working and I need to use a different keyboard to restart the system in order for it to fully recover.

Unfortunately, the 6.16 kernel has dropped off the list of saved kernel images at this point so I can’t go back.

Any idea on why this might be happening and/or anything I can do to fix / further diagnose the problem?

USB error on boot from journalctl:

Oct 30 10:16:58 Gondor kernel: usb 1-11: device descriptor read/64, error -110
Oct 30 10:17:14 Gondor kernel: usb 1-11: device descriptor read/64, error -110
Oct 30 10:17:14 Gondor kernel: usb usb1-port11: attempt power cycle
Oct 30 10:17:15 Gondor kernel: usb 1-11: new high-speed USB device number 16 using xhci_hcd
Oct 30 10:17:19 Gondor kernel: usb 1-11: Device not responding to setup address.
Oct 30 10:17:24 Gondor kernel: usb 1-11: Device not responding to setup address.
Oct 30 10:17:25 Gondor kernel: usb 1-11: device not accepting address 16, error -71

Output of lsusb:

> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c547 Logitech, Inc. USB Receiver
Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 005: ID 1852:7022 GYROCOM C&C Co., LTD Fiio E10
Bus 001 Device 006: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 007: ID 0424:4206 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 010: ID 0a12:1243 Cambridge Silicon Radio, Ltd CSRA64210 [TaoTronics Headset BH-22 in charging mode]
Bus 001 Device 011: ID 2f96:0200 Antlion Audio Antlion USB Microphone
Bus 001 Device 014: ID 0424:7260 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 003 Device 004: ID 09ea:0130 Generic Virtual HUB
Bus 003 Device 005: ID 1209:2201 Generic Dygma Shortcut Keyboard
Bus 003 Device 006: ID 09eb:0131 IM Networks, Inc. Virtual HID
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

System Info:

> kinfo
Operating System: Fedora Linux 43
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.5-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 4070
Graphics Processor 2: AMD Ryzen 7 9800X3D 8-Core Processor

systemd-analyze criticalchain

> sudo systemd-analyze --no-pager 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 @11.289s
└─sddm.service @11.289s
  └─plymouth-quit.service @11.258s +30ms
    └─systemd-user-sessions.service @11.243s +12ms
      └─remote-fs.target @11.241s
        └─remote-fs-pre.target @5.293s
          └─nfs-client.target @5.293s
            └─gssproxy.service @5.274s +18ms
              └─network.target @5.273s
                └─wpa_supplicant.service @5.248s +24ms
                  └─basic.target @3.279s
                    └─dbus-broker.service @3.245s +25ms
                      └─dbus.socket @3.243s +220us
                        └─sysinit.target @3.241s
                          └─plymouth-read-write.service @2.663s +577ms
                            └─local-fs.target @2.662s
                              └─opt-piavpn-etc-cgroup-net_cls.mount @5.998s
                                └─local-fs-pre.target @750ms
                                  └─systemd-tmpfiles-setup-dev.service @741ms +9ms
                                    └─systemd-tmpfiles-setup-dev-early.service @699ms +40ms
                                      └─kmod-static-nodes.service @693ms +5ms
                                        └─systemd-journald.socket
                                          └─system.slice
                                            └─-.slice

systemd-analyze blame

> sudo systemd-analyze --no-pager blame
1min 6.952s sys-module-fuse.device
1min 6.878s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.device
1min 6.878s dev-disk-by\x2did-wwn\x2d0x5002538e404be636.device
1min 6.878s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z8NB0K611166L.device
1min 6.878s dev-sda.device
1min 6.878s dev-disk-by\x2ddiskseq-1.device
1min 6.878s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:0d.0-0000:0a:00.0-ata1-host0-target0:0:0-0:0:0:0-block-sda…
1min 6.878s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0.device
1min 6.869s dev-ttyS3.device
1min 6.869s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 6.860s dev-sda1.device
1min 6.860s dev-disk-by\x2dpartuuid-e37aa5f4\x2d0b5f\x2d40f3\x2dbf18\x2d6282b4d6684b.device
1min 6.860s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
1min 6.860s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 6.860s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2duuid-c71c6edc\x2d7d00\x2d4188\x2db356\x2dab396d…
1min 6.860s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1\x2dpart1.device
1min 6.860s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart1.device
1min 6.860s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z8NB0K611166L\x2dpart1.device
1min 6.860s dev-disk-by\x2did-wwn\x2d0x5002538e404be636\x2dpart1.device
1min 6.860s dev-disk-by\x2duuid-c71c6edc\x2d7d00\x2d4188\x2db356\x2dab396d907bbb.device
1min 6.860s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-e37aa5f4\x2d0b5f\x2d40f3\x2dbf18\x2d62…
1min 6.860s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:0d.0-0000:0a:00.0-ata1-host0-target0:0:0-0:0:0:0-block-sda…
1min 6.859s dev-tpm0.device
1min 6.858s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
1min 6.856s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 6.856s dev-tpmrm0.device
1min 6.856s dev-ttyS1.device
1min 6.856s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 6.855s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 6.855s dev-ttyS2.device
1min 6.844s sys-module-configfs.device
1min 6.835s sys-devices-pnp0-00:04-00:04:0-00:04:0.0-tty-ttyS0.device
1min 6.835s dev-ttyS0.device
1min 6.820s dev-nvme0n1p2.device
1min 6.820s dev-disk-by\x2dpartuuid-668272d4\x2dd806\x2d46dc\x2d9193\x2dce5f5a9637ce.device
1min 6.820s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
1min 6.820s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 6.820s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-00a65b29\x2d6e81\x2d4d9f\x2da32e\x2d0aa3dee…
1min 6.820s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 6.820s dev-disk-by\x2did-nvme\x2deui.0025384941402211\x2dpart2.device
1min 6.820s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y\x2dpart2.device
1min 6.820s dev-disk-by\x2ddesignator-xbootldr.device
1min 6.820s dev-disk-by\x2ddiskseq-2\x2dpart2.device
1min 6.820s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-668272d4\x2dd806\x2d46dc\x2d9193\x2dce5…
1min 6.820s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y_1\x2dpart2.device
1min 6.820s dev-disk-by\x2duuid-00a65b29\x2d6e81\x2d4d9f\x2da32e\x2d0aa3deeb6d4d.device
1min 6.816s dev-disk-by\x2duuid-1500f744\x2de8a3\x2d4a43\x2da493\x2d47a426607342.device
1min 6.816s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y\x2dpart3.device
1min 6.816s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1min 6.816s dev-disk-by\x2ddiskseq-2\x2dpart3.device
1min 6.816s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
1min 6.816s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-00e51d0f\x2d934f\x2d408e\x2dbd7e\x2d9fc…
1min 6.816s dev-disk-by\x2did-nvme\x2deui.0025384941402211\x2dpart3.device
1min 6.816s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1min 6.816s dev-nvme0n1p3.device
1min 6.816s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-1500f744\x2de8a3\x2d4a43\x2da493\x2d47a4266…
1min 6.816s dev-disk-by\x2dpartuuid-00e51d0f\x2d934f\x2d408e\x2dbd7e\x2d9fc2856e1f06.device
1min 6.816s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y_1\x2dpart3.device
1min 6.798s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
1min 6.798s dev-disk-by\x2ddiskseq-2\x2dpart1.device
1min 6.798s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-F77C\x2dF194.device
1min 6.798s dev-disk-by\x2duuid-F77C\x2dF194.device
1min 6.798s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 6.798s dev-disk-by\x2dpartuuid-a7176b57\x2dd68c\x2d4c83\x2da173\x2d47a345961f85.device
1min 6.798s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 6.798s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 6.798s dev-disk-by\x2ddesignator-esp.device
1min 6.798s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-a7176b57\x2dd68c\x2d4c83\x2da173\x2d47a…
1min 6.798s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y_1\x2dpart1.device
1min 6.798s dev-disk-by\x2did-nvme\x2deui.0025384941402211\x2dpart1.device
1min 6.798s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y\x2dpart1.device
1min 6.798s dev-nvme0n1p1.device
1min 6.798s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 6.793s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1.device
1min 6.793s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y.device
1min 6.793s dev-disk-by\x2did-nvme\x2deui.0025384941402211.device
1min 6.793s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X905820Y_1.device
1min 6.793s dev-disk-by\x2ddiskseq-2.device
1min 6.793s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
1min 6.793s dev-nvme0n1.device
1min 5.688s dracut-initqueue.service
    12.312s systemd-cryptsetup@luks\x2d1500f744\x2de8a3\x2d4a43\x2da493\x2d47a426607342.service
     5.992s NetworkManager-wait-online.service
     1.555s NetworkManager.service
     1.002s abrtd.service
      869ms initrd-switch-root.service
      636ms boot.mount
      577ms plymouth-read-write.service
      350ms firewalld.service
      350ms boot-efi.mount
      197ms systemd-journal-flush.service
      182ms tuned.service
      128ms akmods.service
      104ms systemd-udev-trigger.service
      101ms user@0.service
       90ms user@1000.service
       89ms upower.service
       87ms plymouth-start.service
       66ms tuned-ppd.service
       54ms udisks2.service
       53ms lvm2-monitor.service
       53ms systemd-tmpfiles-setup.service
       49ms dev-zram0.swap
       47ms var-lib-nfs-rpc_pipefs.mount
       45ms systemd-journald.service
       41ms systemd-resolved.service
       40ms systemd-tmpfiles-setup-dev-early.service
       39ms systemd-udevd.service
       37ms accounts-daemon.service
       37ms polkit.service
       37ms ModemManager.service
       36ms systemd-tmpfiles-clean.service
       35ms chronyd.service
       34ms systemd-fsck-root.service
       30ms plymouth-quit-wait.service
       30ms plymouth-quit.service
       27ms dracut-cmdline.service
       26ms sssd-kcm.service
       25ms dbus-broker.service
       25ms systemd-logind.service
       24ms systemd-binfmt.service
       24ms systemd-random-seed.service
       24ms wpa_supplicant.service
       23ms systemd-vconsole-setup.service
       23ms smartd.service
       22ms avahi-daemon.service
       21ms plymouth-switch-root.service
       21ms rsyslog.service
       18ms systemd-hostnamed.service
       18ms initrd-parse-etc.service
       18ms systemd-zram-setup@zram0.service
       18ms dev-hugepages.mount
       18ms dev-mqueue.mount
       18ms sys-kernel-tracing.mount
       18ms sys-kernel-debug.mount
       18ms gssproxy.service
       17ms systemd-sysctl.service
       17ms auditd.service
       16ms systemd-fsck@dev-disk-by\x2duuid-F77C\x2dF194.service
       16ms lm_sensors.service
       15ms systemd-fsck@dev-disk-by\x2duuid-00a65b29\x2d6e81\x2d4d9f\x2da32e\x2d0aa3deeb6d4d.service
       14ms systemd-oomd.service
       13ms cups.service
       13ms systemd-homed.service
       13ms rpc-statd-notify.service
       13ms bolt.service
       12ms dracut-shutdown.service
       12ms systemd-user-sessions.service
       12ms user-runtime-dir@1000.service
       12ms foomaticrip-upgrade.service
       12ms systemd-userdbd.service
       11ms user-runtime-dir@0.service
       11ms audit-rules.service
       10ms switcheroo-control.service
        9ms systemd-tmpfiles-setup-dev.service
        9ms dracut-pre-pivot.service
        9ms uresourced.service
        9ms dracut-pre-udev.service
        8ms rtkit-daemon.service
        8ms initrd-cleanup.service
        6ms thermald.service
        6ms sshd.service
        5ms kmod-static-nodes.service
        5ms systemd-network-generator.service
        5ms systemd-udev-load-credentials.service
        4ms sys-fs-fuse-connections.mount
        4ms systemd-userdb-load-credentials.service
        4ms modprobe@loop.service
        4ms proc-sys-fs-binfmt_misc.mount
        4ms initrd-udevadm-cleanup-db.service
        4ms systemd-modules-load.service
        3ms systemd-sysusers.service
        3ms systemd-update-utmp.service
        3ms systemd-remount-fs.service
        3ms systemd-rfkill.service
        2ms home.mount
        1ms tmp.mount
        1ms systemd-coredump.socket
      564us systemd-bootctl.socket
      551us sshd-unix-local.socket
      454us systemd-sysext.socket
      449us lvm2-lvmpolld.socket
      441us systemd-ask-password.socket
      398us systemd-factory-reset.socket
      296us systemd-creds.socket
      293us cups.socket
      220us dbus.socket
      215us systemd-udevd-control.socket
      204us systemd-oomd.socket
      171us systemd-userdbd.socket
      153us avahi-daemon.socket
      122us iscsiuio.socket
       95us dm-event.socket
       75us systemd-resolved-monitor.socket
       72us pcscd.socket
       58us sssd-kcm.socket
       53us systemd-hostnamed.socket
       52us systemd-udevd-varlink.socket
       48us systemd-journald-audit.socket
       43us systemd-logind-varlink.socket
       39us iscsid.socket
       37us systemd-rfkill.socket
       28us systemd-journald-dev-log.socket
       27us systemd-homed-activate.service
       20us systemd-resolved-varlink.socket
       12us systemd-journald.socket
        3us systemd-udevd-kernel.socket

At the advice of a forum post from a few years ago that I only saw after making this one I shut down the system and then physically unplugged it from the wall. After waiting 2min and plugging it back in everything works fine. Go figure unplugging and plugging it back in actually fixed it.