Arch Linux

brapcity

Member

Registered: 2023-03-12

Posts: 7

Hanging on boot screen

Hi, I am having a problem when I boot up my system
It hangs on the following message

A start job is running for Journal Service (42s / 1min 30s)

then I have to wait for the full 90 seconds until it finishes booting.
I have tried running the command:

systemd-analyze blame
1min 21.731s systemd-journald.service
       728ms NetworkManager.service
       190ms dev-nvme0n1p3.device
       153ms systemd-tmpfiles-setup.service
       142ms systemd-journal-flush.service
       117ms lvm2-monitor.service
       112ms upower.service
        97ms systemd-udev-trigger.service
        91ms plymouth-start.service
        84ms systemd-tmpfiles-clean.

I don't know what further steps would be to continue troubleshooting this issue

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,939

Re: Hanging on boot screen

https://bbs.archlinux.org/viewtopic.php?id=297440
https://bbs.archlinux.org/viewtopic.php?id=297185

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

brapcity

Member

Registered: 2023-03-12

Posts: 7

Re: Hanging on boot screen

http://0x0.st/Xp8M.txt

here is the output

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,939

Re: Hanging on boot screen

Jul 21 13:23:25 moo kernel: Linux version 6.9.9-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Fri, 12 Jul 2024 00:06:53 +0000
Jul 21 13:24:47 moo systemd[1]: Listening on Journal Socket (/dev/log).
Jul 21 13:24:47 moo systemd[1]: Listening on Journal Sockets.
Jul 21 13:24:47 moo systemd[1]: Starting Journal Service...
Jul 21 13:24:47 moo systemd-journald[367]: Collecting audit messages is disabled.
Jul 21 13:24:47 moo systemd-journald[367]: Journal started
Jul 21 13:24:47 moo systemd-journald[367]: Runtime Journal (/run/log/journal/3e8fcd4265424bb3b991ddda158f7286) is 8M, max 1.5G, 1.5G free.
Jul 21 13:24:47 moo systemd[1]: Starting Flush Journal to Persistent Storage...
Jul 21 13:24:47 moo systemd[1]: Started Journal Service.
Jul 21 13:24:47 moo systemd-journald[367]: Time spent on flushing to /var/log/journal/3e8fcd4265424bb3b991ddda158f7286 is 71.411ms for 1481 entries.

Journald is a red herring, the cause is

Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: xHCI Host Controller
Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: new USB bus registered, assigned bus number 5
Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: hcc params 0x0120ffc5 hci version 0x120 quirks 0x0000000200000010
Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: xHCI Host Controller
Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: new USB bus registered, assigned bus number 6
Jul 21 13:23:26 moo kernel: xhci_hcd 0000:0e:00.4: Host supports USB 3.1 Enhanced SuperSpeed
Jul 21 13:24:47 moo kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.09
Jul 21 13:24:47 moo kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 21 13:24:47 moo kernel: usb usb5: Product: xHCI Host Controller
Jul 21 13:24:47 moo kernel: usb usb5: Manufacturer: Linux 6.9.9-arch1-1 xhci-hcd
Jul 21 13:24:47 moo kernel: usb usb5: SerialNumber: 0000:0e:00.4

what fits known patterns in the linked threads

The problem is likely

Jul 21 13:24:47 moo kernel: usb 5-1: device descriptor read/64, error -110
Jul 21 13:24:47 moo kernel: usb 5-1: device descriptor read/64, error -110
Jul 21 13:24:47 moo kernel: usb 5-1: new full-speed USB device number 3 using xhci_hcd
Jul 21 13:24:47 moo kernel: usb 5-1: device descriptor read/64, error -110
Jul 21 13:24:47 moo kernel: usb 5-1: device descriptor read/64, error -110
Jul 21 13:24:47 moo kernel: usb usb5-port1: attempt power cycle
Jul 21 13:24:47 moo kernel: usb 5-1: new full-speed USB device number 4 using xhci_hcd
Jul 21 13:24:47 moo kernel: usb 5-1: device not accepting address 4, error -62
Jul 21 13:24:47 moo kernel: usb 5-1: WARN: invalid context state for evaluate context command.
Jul 21 13:24:47 moo kernel: usb 5-1: new full-speed USB device number 5 using xhci_hcd
Jul 21 13:24:47 moo kernel: usb 5-1: device not accepting address 5, error -62
Jul 21 13:24:47 moo kernel: usb 5-1: WARN: invalid context state for evaluate context command.
Jul 21 13:24:47 moo kernel: usb usb5-port1: unable to enumerate USB device

Try the LTS kernel, is there a parallel windows?
Do you miss any USB device in "lsusb"?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc