You are not logged in.

Pages: 1

#1 2025-03-03 01:23:53

last2braincells
Member
Registered: 2025-01-22
Posts: 5

[SOLVED] Boot Delay at triggering uevents step

After updating from kernel 6.11.x to 6.13.4 my system hangs for 1-2 minutes at the "triggering uevents" step during boot.
The system does eventually boot, but having to wait the extra time has started to annoy me.
I found a similar post about this on the Arch forums here, but no real solution was offered.
To capture some logs I've enabled 'udev_log=debug' in /etc/udev/udev.conf, then ran mkinitcpio and rebooted.

Here is the output from 

sudo journal -b

without 'udev_log=debug': http://0x0.st/8MwT.txt

I'm not knowledgeable enough to understand the relevance of most of the messages. I would appreciate any help in parsing the log, or guidance to other resources which would help resolve this.

Additional Context:
I do not use GRUB or any other boot manager, instead I'm using EFI boot stubs.

System info:

System:
  Kernel: 6.13.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.3.1 Distro: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: B650I AORUS ULTRA v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: B650I AORUS ULTRA v: x.x
    serial: <superuser required> UEFI: American Megatrends LLC. v: F32
    date: 08/14/2024
CPU:
  Info: 12-core model: AMD Ryzen 9 9900X bits: 64 type: MT MCP arch: N/A
    rev: 0 cache: L1: 960 KiB L2: 12 MiB L3: 64 MiB
  Speed (MHz): avg: 2999 min/max: 600/5658 boost: enabled cores: 1: 2999
    2: 2999 3: 2999 4: 2999 5: 2999 6: 2999 7: 2999 8: 2999 9: 2999 10: 2999
    11: 2999 12: 2999 13: 2999 14: 2999 15: 2999 16: 2999 17: 2999 18: 2999
    19: 2999 20: 2999 21: 2999 22: 2999 23: 2999 24: 2999 bogomips: 210786
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
    XTX/7900 GRE/7900M] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-3
    bus-ID: 03:00.0
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: Gigabyte driver: amdgpu v: kernel bus-ID: 13:00.0 temp: 40.0 C
  Device-3: EMEET SmartCam C960 4K
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB bus-ID: 5-2:2
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
    compositor: kwin_wayland driver: X: loaded: modesetting dri: radeonsi
    gpu: amdgpu resolution: 1: 2560x1440~75Hz 2: 2560x1440~75Hz
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XT (radeonsi
    navi31 LLVM 19.1.7 DRM 3.60 6.13.4-arch1-1)
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib,wayland devices: 2
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
    driver: snd_hda_intel v: kernel bus-ID: 03:00.1
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
    Definition Audio driver: snd_hda_intel v: kernel bus-ID: 13:00.1
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 13:00.6
  Device-4: Kingston HyperX Cloud Alpha S
    driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-2:2
  Device-5: Elgato Systems GmbH Wave:3 driver: snd-usb-audio type: USB
    bus-ID: 1-9:11
  Device-6: Giga-Byte USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB bus-ID: 3-2:2
  Device-7: EMEET SmartCam C960 4K
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB bus-ID: 5-2:2
  API: ALSA v: k6.13.4-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active
Network:
  Device-1: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel
    port: N/A bus-ID: 0e:00.0
  IF: enp14s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel bus-ID: 0f:00.0
  IF: wlp15s0 state: down mac: <filter>
  IF-ID-1: wgpia0 state: unknown speed: N/A duplex: N/A mac: N/A
Drives:
  Local Storage: total: 9.1 TiB used: 366.97 GiB (3.9%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    temp: 53.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 PRO with Heatsink 4TB
    size: 3.64 TiB temp: 43.9 C
  ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    temp: 43.9 C
  ID-4: /dev/sda vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
  ID-5: /dev/sdb vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
Partition:
  ID-1: / size: 78.19 GiB used: 29.93 GiB (38.3%) fs: ext4 dev: /dev/dm-0
    mapped: vg_primary-lv_root
  ID-2: /home size: 1.97 TiB used: 336.3 GiB (16.7%) fs: ext4 dev: /dev/dm-2
    mapped: vg_primary-lv_home
Swap:
  ID-1: swap-1 type: partition size: 64 GiB used: 0 KiB (0.0%) dev: /dev/dm-1
    mapped: vg_primary-lv_swap
Sensors:
  System Temperatures: cpu: 47.5 C mobo: 46.0 C
  Fan Speeds (rpm): N/A
  GPU: device: amdgpu temp: 40.0 C device: amdgpu temp: 44.0 C fan: 1
Info:
  Memory: total: 60 GiB note: est. available: 60.44 GiB used: 3.84 GiB (6.4%)
  Processes: 468 Uptime: 1h 23m Init: systemd
  Packages: 1037 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.37

Last edited by last2braincells (2025-03-09 08:25:00)

Offline

#2 2025-03-03 09:11:35

seth
Member
Registered: 2012-09-03
Posts: 61,712

Re: [SOLVED] Boot Delay at triggering uevents step

the full output is too long to post here):the full output is too long to post here):

Disable 'udev_log=debug' and post the journal.

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

Offline

#3 2025-03-04 17:02:58

last2braincells
Member
Registered: 2025-01-22
Posts: 5

Re: [SOLVED] Boot Delay at triggering uevents step

seth wrote:

the full output is too long to post here):the full output is too long to post here):

Disable 'udev_log=debug' and post the journal.

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

Here is the journal log:
http://0x0.st/8MwT.txt

Just FYI, I had a power outage last night. The first boot after power returned did not hang at 'triggering uevents', like before. This may just have been an anomalous boot, but if it continues without issue I'll come back and mark this as solved.

Last edited by last2braincells (2025-03-04 17:15:31)

Offline

#4 2025-03-04 20:42:15

seth
Member
Registered: 2012-09-03
Posts: 61,712

Re: [SOLVED] Boot Delay at triggering uevents step

Mar 04 10:29:06 arch-itx kernel: Linux version 6.13.4-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Sat, 22 Feb 2025 00:37:05 +0000
…
Mar 04 10:29:08 arch-itx systemd-logind[814]: New session c1 of user sddm.
…
Mar 04 10:29:20 arch-itx systemd-logind[814]: New session 2 of user john.

That boot reached your DM in 2s and you logges in 12s later.
You can access older boots, eg. 

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

for three boots ago.

On a formal note, please avoid bloating the thread with pointless full-quotes.

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

Offline

#5 2025-03-05 14:31:15

last2braincells
Member
Registered: 2025-01-22
Posts: 5

Re: [SOLVED] Boot Delay at triggering uevents step

seth wrote:

On a formal note, please avoid bloating the thread with pointless full-quotes.

Noted.

As you suggested, I did some digging into older boot logs and found something which may have been the culprit:

1 Feb 24 07:14:27 arch-itx kernel: Linux version 6.13.4-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Sat, 22 Feb 2025 00:37:05 +0000
.....
1727 Feb 24 07:14:29 arch-itx systemd-logind[807]: New session c1 of user sddm.
.....
1823 Feb 24 07:14:38 arch-itx systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
1824 Feb 24 07:14:58 arch-itx systemd[1]: systemd-hostnamed.service: Deactivated successfully.
1825 Feb 24 07:15:47 arch-itx sddm-greeter-qt6[1916]: file:///usr/lib/qt6/qml/SddmComponents/PictureBox.qml:106:13 Parameter "event" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript fu
1825 nctions with formal parameters instead.
.....
1838 Feb 24 07:15:49 arch-itx systemd-logind[807]: New session 2 of user john.

Until logind logged the new session for my user, these were the only entries taking > 1 second.
Interestingly, the logs showed logind starting a new session for sddm only 2 seconds after loading the kernel, but from my perspective it took over a minute to reach the SDDM login screen.
I have 'quiet' removed from my boot parameters, and it's during those initial kernel logging messages where I was hanging. Maybe the logs were capturing stuff in the background before the screen refreshed and control was relinquished?

Regardless, since my power outage, the hanging behavior has ceased. I should have remembered the old IT adage "Did you try unplugging it and plugging it back in?"

Solving this mystery is entirely academic at this point, though. I appreciate your time and input on this. If there is anything else you'd like me to look into, I'd be happy to oblige. Otherwise, I'm going to mark this as solved.

Offline

Pages: 1

Board footer

Powered by FluxBB