Delayed boot with 3 dots displayed instead of plymouth spinner

[litemotiv (Olivier)]

Since last week my AMD laptop shows 3 dots while booting instead of the default Fedora spinner. The boot process takes a lot more time too, and shows a large red row of blocking services:

Systemd boot chart (svg)

After a while the GDM login screen does turn up and the system then appears to work normally.

I tried the suggestions from another thread with similar issues, but they didn’t provide a resolution:

Plymouth boot screen with three dots (again)

Sorry I don’t want to bother anyone but I have just installed F41 from scratch and when it boots I am not shown the usual “Fedora rotating thingy”, I get a grey screen with three dots, same as: Plymouth boot screen with three dots Problem is I have got Intel. I did not have any problem with F39 (current) and F40 (at the time it was relased, I don’t know if something changed later). My configuration is: System Details Report Report details Date generated: 2024-1…

Things i looked at:

• Both the current and previous kernel show the same issue
• Increasing the plymouth timeout only increases the boot time
• Regenerating dracut doesn’t appear to have an effect

Does anyone perhaps have an idea where i could best start to debug this?

[barryascott]

Remove the grub rhgb and quiet options when booting so that you can see kernel and systemd messages.

Do you see the boot process get stuck?

Also systemd-analyse critical-chain and systemd-analyse blame often give more concise info on boot timing issues.

[litemotiv (Olivier)]

Thanks Barry i’ll give that a look tomorrow (it’s bedtime here now )

[litemotiv (Olivier)]

Okay it appears the legacy USB port is not working, that’s a weird regression.

It isn’t related to the kernel version since all installed kernels show the same issue. I’ve also booted into Windows and the port works there.

Below are the probe errors:

systemd-analyze blame shows no clues:

46.983s dev-disk-by\x2did-nvme\x2dMTFDKBA1T0QFM\x2d1BD1AABGB_242048EC3E85_1.device
46.983s dev-disk-by\x2dpath-pci\x2d0000:c1:00.0\x2dnvme\x2d1.device
46.983s dev-disk-by\x2did-nvme\x2deui.000000000000000100a0752448ec3e85.device
46.983s dev-disk-by\x2ddiskseq-1.device
46.983s dev-nvme0n1.device
12.297s plymouth-quit-wait.service
 1.090s firewalld.service
  760ms NetworkManager.service
  556ms initrd-switch-root.service
  320ms systemd-journal-flush.service
  248ms mnt-readyshare.mount
  165ms plymouth-start.service
  156ms systemd-vconsole-setup.service
  135ms tuned.service

systemd-analyze critical-chain

graphical.target @15.931s
└─multi-user.target @15.930s
  └─plymouth-quit-wait.service @3.631s +12.297s
    └─systemd-user-sessions.service @3.623s +5ms
      └─remote-fs.target @3.622s
        └─remote-fs-pre.target @3.621s
          └─nfs-client.target @3.620s
            └─gssproxy.service @3.597s +22ms
              └─network.target @3.593s
                └─wpa_supplicant.service @3.562s +30ms
                  └─basic.target @1.619s
                    └─dbus-broker.service @1.582s +35ms
                      └─dbus.socket @1.577s
                        └─sysinit.target @1.572s
                          └─systemd-resolved.service @1.541s +30ms
                            └─systemd-tmpfiles-setup.service @1.468s +49ms
                              └─local-fs.target @1.465s
                                └─boot-efi.mount @1.441s +24ms
                                  └─boot.mount @1.430s +9ms
                                    └─systemd-fsck@dev-disk-by\x2duuid-b9409339\x2d8d23\x2d4f80\x2db804\x2de2ecb36d4177.service @849ms +34ms
                                      └─dev-disk-by\x2duuid-b9409339\x2d8d23\x2d4f80\x2db804\x2de2ecb36d4177.device

Errors in the regular journal (the ACPI errors were pre-existing):

journalctl -b 0 -p 3

jun 16 14:32:57 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._S0W], AE_ALREADY_EXISTS (20240827/dswload2-326)
jun 16 14:32:57 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
jun 16 14:32:57 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR0], AE_ALREADY_EXISTS (20240827/dswload2-326)
jun 16 14:32:57 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
jun 16 14:32:57 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP4._PR3], AE_ALREADY_EXISTS (20240827/dswload2-326)
jun 16 14:32:57 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
jun 16 14:33:03 fedora kernel: usb 3-1: device descriptor read/64, error -110
jun 16 14:33:19 fedora kernel: usb 3-1: device descriptor read/64, error -110
jun 16 14:33:24 fedora kernel: usb 3-1: device descriptor read/64, error -110
jun 16 14:33:40 fedora kernel: usb 3-1: device descriptor read/64, error -110
jun 16 12:33:51 fedora kernel: usb 3-1: device not accepting address 4, error -62
jun 16 12:33:54 fedora wpa_supplicant[1363]: bgscan simple: Failed to enable signal strength monitoring
jun 16 12:34:03 fedora kernel: usb 3-1: device not accepting address 5, error -62
jun 16 12:34:03 fedora kernel: usb usb3-port1: unable to enumerate USB device
jun 16 12:34:11 fedora gdm-password][2173]: gkr-pam: unable to locate daemon control file
jun 16 12:34:22 fedora polkitd[1173]: Error converting subject to JS object: Process 1670 terminated

What would be a good next step to take from here?

[barryascott]

I think that the slow boot is because of the USB issue slowing down probing for your hardware.

Is anything plugged in to failing USB? Try unplugging that device and see if the errors go away.
It might be the device that is faulty and not the port.
It might be issues with the amount of power being taken from the port.

[litemotiv (Olivier)]

@barryascott

Is anything plugged in to failing USB? Try unplugging that device and see if the errors go away.

There is nothing in the port, but after the system has booted the port is unoperational. The port works as intended under Windows.

[barryascott]

@litemotiv

There is nothing in the port, but after the system has booted the port is unoperational. The port works as intended under Windows.

To see what the kernel thinks is going on have a look for “usb” messages in dmesg output.

sudo dmesg | grep -i usb

[litemotiv (Olivier)]

It doesn’t provide much more information it appears:

[    0.251322] ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
[    0.251322] ACPI: USB4 _OSC: OS controls USB3+ DisplayPort+ PCIe+ XDomain+
[    0.283119] ACPI: bus type USB registered
[    0.283119] usbcore: registered new interface driver usbfs
[    0.283119] usbcore: registered new interface driver hub
[    0.283119] usbcore: registered new device driver usb
[    2.621633] xhci_hcd 0000:c4:00.4: new USB bus registered, assigned bus number 1
[    2.622691] xhci_hcd 0000:c4:00.4: new USB bus registered, assigned bus number 2
[    2.622696] xhci_hcd 0000:c4:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    2.622783] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.14
[    2.622790] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.622794] usb usb1: Product: xHCI Host Controller
[    2.622798] usb usb1: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.622801] usb usb1: SerialNumber: 0000:c4:00.4
[    2.622935] hub 1-0:1.0: USB hub found
[    2.623221] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.623250] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.14
[    2.623255] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.623258] usb usb2: Product: xHCI Host Controller
[    2.623261] usb usb2: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.623264] usb usb2: SerialNumber: 0000:c4:00.4
[    2.623349] hub 2-0:1.0: USB hub found
[    2.623768] xhci_hcd 0000:c6:00.0: new USB bus registered, assigned bus number 3
[    2.624680] xhci_hcd 0000:c6:00.0: new USB bus registered, assigned bus number 4
[    2.624685] xhci_hcd 0000:c6:00.0: Host supports USB 3.1 Enhanced SuperSpeed
[    2.624738] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.14
[    2.624742] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.624746] usb usb3: Product: xHCI Host Controller
[    2.624749] usb usb3: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.624752] usb usb3: SerialNumber: 0000:c6:00.0
[    2.624853] hub 3-0:1.0: USB hub found
[    2.625455] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.625481] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.14
[    2.625486] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.625489] usb usb4: Product: xHCI Host Controller
[    2.625492] usb usb4: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.625495] usb usb4: SerialNumber: 0000:c6:00.0
[    2.625578] hub 4-0:1.0: USB hub found
[    2.626031] xhci_hcd 0000:c6:00.3: new USB bus registered, assigned bus number 5
[    2.627029] xhci_hcd 0000:c6:00.3: new USB bus registered, assigned bus number 6
[    2.627034] xhci_hcd 0000:c6:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    2.627084] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.14
[    2.627089] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.627093] usb usb5: Product: xHCI Host Controller
[    2.627095] usb usb5: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.627098] usb usb5: SerialNumber: 0000:c6:00.3
[    2.627177] hub 5-0:1.0: USB hub found
[    2.627397] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.627423] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.14
[    2.627427] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.627430] usb usb6: Product: xHCI Host Controller
[    2.627433] usb usb6: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.627436] usb usb6: SerialNumber: 0000:c6:00.3
[    2.627509] hub 6-0:1.0: USB hub found
[    2.628050] xhci_hcd 0000:c6:00.4: new USB bus registered, assigned bus number 7
[    2.629028] xhci_hcd 0000:c6:00.4: new USB bus registered, assigned bus number 8
[    2.629032] xhci_hcd 0000:c6:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    2.629083] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.14
[    2.629088] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.629091] usb usb7: Product: xHCI Host Controller
[    2.629094] usb usb7: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.629097] usb usb7: SerialNumber: 0000:c6:00.4
[    2.629173] hub 7-0:1.0: USB hub found
[    2.629381] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.629408] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.14
[    2.629411] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.629415] usb usb8: Product: xHCI Host Controller
[    2.629417] usb usb8: Manufacturer: Linux 6.14.6-300.fc42.x86_64 xhci-hcd
[    2.629420] usb usb8: SerialNumber: 0000:c6:00.4
[    2.629493] hub 8-0:1.0: USB hub found
[    2.629960] usbcore: registered new interface driver usbserial_generic
[    2.629969] usbserial: USB Serial support registered for generic
[    2.638972] usbcore: registered new interface driver usbhid
[    2.638979] usbhid: USB HID core driver
[    2.861559] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    2.862297] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    2.991037] usb 1-1: New USB device found, idVendor=3277, idProduct=0059, bcdDevice= 1.01
[    2.991458] usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.991800] usb 1-1: Product: ASUS FHD webcam
[    2.992114] usb 1-1: Manufacturer: Shinetech
[    2.992425] usb 1-1: SerialNumber: 200901010001
[    3.010989] hid-generic 0003:3277:0059.0001: hiddev96,hidraw0: USB HID v1.11 Device [Shinetech ASUS FHD webcam] on usb-0000:c4:00.4-1/input4
[    3.042504] hid-sensor-hub 0003:3277:0059.0001: hiddev96,hidraw0: USB HID v1.11 Device [Shinetech ASUS FHD webcam] on usb-0000:c4:00.4-1/input4
[    8.357333] usb 3-1: device descriptor read/64, error -110
[   24.229107] usb 3-1: device descriptor read/64, error -110
[   24.446298] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[   29.862388] usb 3-1: device descriptor read/64, error -110
[   45.733061] usb 3-1: device descriptor read/64, error -110
[   45.837485] usb usb3-port1: attempt power cycle
[   46.216503] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[   50.620542] usb 1-1: Found UVC 1.10 device ASUS FHD webcam (3277:0059)
[   50.629897] usb 1-1: Found UVC 1.50 device ASUS FHD webcam (3277:0059)
[   50.632295] usbcore: registered new interface driver uvcvideo
[   57.093623] usb 3-1: device not accepting address 4, error -62
[   57.209091] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[   68.454456] usb 3-1: device not accepting address 5, error -62
[   68.454675] usb usb3-port1: unable to enumerate USB device

One thing that confuses me is that all installed kernels (.6 / .8 / .9) exhibit the same problem, while this issue only started last week. So something else outside of the kernel appears to cause it.

[barryascott]

This SO talks about these messages https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110

It suggests that a USB stick that draw too much power was the problem in the SO.

Is this a laptop? Is it on mains power?

[litemotiv (Olivier)]

@barryascott

Is this a laptop? Is it on mains power?

Laptop on mains power, no other devices inserted except for an USB-C power cable.

The port that appears to block is the (empty) USB-3 port, it is unoperational after startup.

[barryascott]

That So talked about updating the BIOS helped resolve the issue.

Have you check for a BIOS firmware update?

[litemotiv (Olivier)]

I did a bios update a few weeks ago

The USB port also seems to work okay in Windows, so i’m somewhat at a loss…

[barryascott]

@litemotiv

The USB port also seems to work okay in Windows, so i’m somewhat at a loss…

Windows driver may have “quirk” for that USB chipset that is not in linux kernel.
A quirk is a work around for a bug in a chipset.

[litemotiv (Olivier)]

That’s possible, but the USB-3 port and the Plymouth spinner worked fine on my system until last week, something must have changed?

So the situation is:

1 USB port worked fine on both Windows and Fedora
2 I upgraded the bios and the USB port still worked fine on both OS’es
3 There were a bunch of package updates on Fedora
4 The USB port now gives a blocking error in Fedora and breaks Plymouth, including on a kernel that worked fine before

[jrredho (john r red-horse)]

Not sure it would help, but I wonder if you’d see this effect if you booted the live ISO for f42 since that version doesn’t change from the time of upgrade release.

[litemotiv (Olivier)]

That’s not a bad idea to try!

[Edit:] the results are in and they are a bit weird:

I can live boot Fedora 42 from USB without problems, the Plymouth spinner appears normally.

After login i can however see a few similar errors about the USB port in the journal:

It didn’t appear to stall the boot process though in the same way as on my actualized Fedora installation. So i don’t really know what the deal is…

[Edit 2] One difference appears to be that on the live USB, the four failed tests to initialize the USB all happen within one second. On the actualized Fedora installation, there are 5-10 seconds between each attempt.

[grumpey (Joe)]

Maybe the amd firmware?

[litemotiv (Olivier)]

I have a feeling that something in the udev probing retry/timeout changed in a recent update, which causes it to take a lot longer and Plymouth to not engage.

I don’t really mind the USB port itself failing, since i don’t really use legacy USB that much and it does seem to work okay when booting from it. So if i can avoid the probe to retry for 30-40 seconds it would be good enough for now…

[jrredho (john r red-horse)]

Hmmmm. In one of your early journalctl output photos, it seemed to be having problems with a usb hub, too. Did you notice that?

Fwiw, at least a few people solved this error code combination on their systems by disconnecting their power cable, shutting down their computer, and waiting 5-7 mins for some motherboard or usb device capacitors to discharge. It sounds a little far fetched, but would seem to be an easy thing to try.

Good luck!

[litemotiv (Olivier)]

@jrredho

In one of your early journalctl output photos, it seemed to be having problems with a usb hub, too. Did you notice that?

Yes i think that is the internal USB controller that the USB port is attached to, perhaps the SD-card port is connected to that as well. I’m not sure though, but it is internal to the machine so i have no access to it for any adjustments.