You are not logged in.

#1 2024-03-29 01:25:42

KiYugadgeter
Member
Registered: 2020-10-22
Posts: 9

30-systemd-udev-reload.hook taking long then timeout

Since 2024-03-28T23:03:17+0900, (This is a time of I did pacman -Syu),
30-systemd-udev-reload.hook taking long time then be timeout.
Before that there is not any like that.

I can found an error message in /var/log/pacman.log:

[ALPM-SCRIPTLET] Timed out for waiting the udev queue being empty.

How do I fix it?

Offline

#2 2024-03-29 09:04:40

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: 30-systemd-udev-reload.hook taking long then timeout

This is going to be caused by a (likely local) udev rule ending up running a long-term or stallign job, https://wiki.archlinux.org/title/Udev#About_udev_rules

You can block the hook w/

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

but preferably check what rule is actually causing the timeout and fix that.

Edit: https://bbs.archlinux.org/viewtopic.php?id=294349

Last edited by seth (2024-04-02 07:50:50)

Offline

#3 2024-03-30 02:14:12

KiYugadgeter
Member
Registered: 2020-10-22
Posts: 9

Re: 30-systemd-udev-reload.hook taking long then timeout

I do not have any udev rule created by me,
so `/etc/udev/rules.d/` is empty.

The below is a list of upgraded before be cause the timeout.
```
[2024-03-28T23:03:14+0900] [ALPM] upgraded libvirt (1:10.1.0-1 -> 1:10.1.0-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-common (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-alsa (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-dbus (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-jack (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-oss (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-pa (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-pipewire (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-sdl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-opengl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-spice-core (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-audio-spice (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-img (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-x86-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-x86 (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-base (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-block-curl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-block-dmg (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-block-nfs (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-block-ssh (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-chardev-spice (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-qxl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-gpu (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-gpu-gl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-gpu-pci (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-gpu-pci-gl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-vga (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-display-virtio-vga-gl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-usb-host (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-usb-redirect (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-hw-usb-smartcard (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-curses (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-dbus (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-egl-headless (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-gtk (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-sdl (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-ui-spice-app (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-vhost-user-gpu (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-desktop (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-aarch64 (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-alpha-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-alpha (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-arm-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-arm (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-avr (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-cris (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-hppa-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-hppa (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-loongarch64 (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-m68k (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-microblaze-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:14+0900] [ALPM] upgraded qemu-system-microblaze (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-mips (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-nios2 (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-or1k (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-ppc-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-ppc (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-riscv-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-riscv (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-rx (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-s390x-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-s390x (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-sh4 (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-sparc-firmware (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-sparc (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-tricore (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-system-xtensa (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-user (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-emulators-full (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-guest-agent (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-hw-s390x-virtio-gpu-ccw (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-pr-helper (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded qemu-tools (8.2.2-1 -> 8.2.2-2)
[2024-03-28T23:03:15+0900] [ALPM] upgraded wireshark-cli (4.2.3-1 -> 4.2.4-1)
[2024-03-28T23:03:16+0900] [ALPM] upgraded wireshark-qt (4.2.3-1 -> 4.2.4-1)
```

Offline

#4 2024-03-30 07:25:59

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: 30-systemd-udev-reload.hook taking long then timeout

Please use [code][/code] tags, bbs predates markdown by your lifetime. Edit your post in this regard.

Did you see the linked thread, udev is "victim" to hanging nouveau there.
Your package list is mostly qemu, I don't think that's related at all, iff it's even udev itself, it's more likely an existing rule.

Please post your complete system journal for the boot:

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

Offline

#5 2024-04-02 06:10:46

KiYugadgeter
Member
Registered: 2020-10-22
Posts: 9

Re: 30-systemd-udev-reload.hook taking long then timeout

This is my log.

https://0x0.st/Xzwz.txt

Offline

#6 2024-04-02 07:51:42

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: 30-systemd-udev-reload.hook taking long then timeout

 4月 02 15:02:20 kiyupadx13 kernel: Linux version 6.8.2-arch2-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000
 4月 02 15:02:22 kiyupadx13 systemd-logind[614]: New session 1 of user gdm.
 4月 02 15:02:37 kiyupadx13 systemd-logind[614]: New session 3 of user kiyugad.

System boots to GDM in 2s and 15s later you login, thre's no relevant timeout.
Assuming this is only a problem during system updates, feel lucky that the system doesn't fatally crash on you.

sudo touch /etc/systemd/do-not-udevadm-trigger-on-update

The presence of the file in /etc/systemd should™ prevent this

Offline

#7 2024-04-02 10:54:40

Vincent D
Member
From: France
Registered: 2012-04-12
Posts: 17

Re: 30-systemd-udev-reload.hook taking long then timeout

Hello,

I have the same issue as described in the first post. My pacman.log ends with

40042 [2024-04-02T12:39:07+0200] [PACMAN] Running 'pacman --color=always --sync systemd'
40043 [2024-04-02T12:39:07+0200] [ALPM] transaction started
40044 [2024-04-02T12:39:07+0200] [ALPM] reinstalled systemd (255.4-2)
40045 [2024-04-02T12:39:08+0200] [ALPM] transaction completed
40046 [2024-04-02T12:39:08+0200] [ALPM] running '20-systemd-sysusers.hook'...
40047 [2024-04-02T12:39:08+0200] [ALPM] running '30-systemd-catalog.hook'...
40048 [2024-04-02T12:39:08+0200] [ALPM] running '30-systemd-daemon-reload-system.hook'...
40049 [2024-04-02T12:39:09+0200] [ALPM] running '30-systemd-daemon-reload-user.hook'...
40050 [2024-04-02T12:39:09+0200] [ALPM] running '30-systemd-hwdb.hook'...
40051 [2024-04-02T12:39:09+0200] [ALPM] running '30-systemd-sysctl.hook'...
40052 [2024-04-02T12:39:09+0200] [ALPM] running '30-systemd-tmpfiles.hook'...
40053 [2024-04-02T12:39:09+0200] [ALPM] running '30-systemd-udev-reload.hook'...
40054 [2024-04-02T12:41:10+0200] [ALPM-SCRIPTLET] Timed out for waiting the udev queue being empty.
40055 [2024-04-02T12:41:10+0200] [ALPM] running '30-systemd-update.hook'...
40056 [2024-04-02T12:41:10+0200] [ALPM] running 'dbus-reload.hook'...
40057 [2024-04-02T12:41:10+0200] [ALPM] running 'eos-reboot-required.hook'...
40058 [2024-04-02T12:41:10+0200] [ALPM] running 'rebuild-detector.hook'...

- /etc/udev/rules.d/ is also empty for me.
- my log is here.
- @Seth, I also saw this post https://bbs.archlinux.org/viewtopic.php?id=294349, but I have an Intel graphics card.

Last edited by Vincent D (2024-04-02 10:57:33)

Offline

#8 2024-04-02 12:41:53

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: 30-systemd-udev-reload.hook taking long then timeout

Those udev stalls were in a boot context and udev wasn't even stalling but just victim to the nouveau crash.

As for the pacman hook, try to add the file as in #2 - you're kinda lucky if it "only" stalls and not causes complete havoc, https://bbs.archlinux.org/viewtopic.php … 6#p2161736

Offline

#9 2024-04-03 07:10:54

Vincent D
Member
From: France
Registered: 2012-04-12
Posts: 17

Re: 30-systemd-udev-reload.hook taking long then timeout

This solved my issue: after creating this file, I reinstalled together the packages given here and rebooted. Some error messages that I got during boot are gone.

Offline

#10 2024-04-03 07:39:52

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: 30-systemd-udev-reload.hook taking long then timeout

Do you have more exact errors than "some"? wink
(They might still be in previous system journals, eg. "sudo journalctl -b -1" for the previous one)

Out of curiosity, do either of you use the nvidia driver?

lsmod | grep nvidia

Offline

#11 2024-04-03 18:32:52

gary8588
Member
Registered: 2022-08-09
Posts: 24

Re: 30-systemd-udev-reload.hook taking long then timeout

Hello guys,

I have the same timeout issue during upgrading my system. Started seeing this issue on Sat 30th.

Hardware: Tuxedo Infinitybook S14 Gen6 (Intel Tiger Lake i5)

* /etc/udev/rules.d/ is empty
* I do NOT use any nvidia or nuveau driver
* Log file: http://0x0.st/XzdB.txt

Additionally I suffer from the stuck at shutdown/reboot issue that is described here: https://bbs.archlinux.org/viewtopic.php?id=294377
Additionally I ran into strange USB port issue that might be related to bluetooth as mentioned on reddit here: old.reddit.com/r/archlinux
USB Port did not recognize my keyboard anymore on any ports altough a ethernet dongle was plugged in and _worked_. Reboot fixed this and issue did not come back (yet)

Should I open a separate topic for this or just wait since this looks to be a upstream issue?

Last edited by gary8588 (2024-04-03 18:52:17)

Offline

#12 2024-04-04 01:37:33

KiYugadgeter
Member
Registered: 2020-10-22
Posts: 9

Re: 30-systemd-udev-reload.hook taking long then timeout

In the https://bbs.archlinux.org/viewtopic.php?id=294377,
Author mentioned that has ThinkPad X13 Gen 1 + AMD Ryzen 5 PRO 4650U.

My laptop is almost same config laptop just different CPU is installed that ThinkPad X13 Gen1 Ryzen 7 4750U.
My laptop has same AX200 Bluetooth/Wifi Card too.
So Now I suffer same problem about reboot and shutdown too.

Offline

Board footer

Powered by FluxBB