You are not logged in.
Pages: 1
I performed a full system upgrade on my laptop the other day (had not done for about two weeks prior) - included a kernel update so I performed a reboot and on next boot discovered udev is failing at startup (or if attempting to start service manually) journalctl reports:
systemd-udevd-kernel.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit systemd-udevd-kernel.socket has entered the 'failed' state with result 'service-start-limit-hit'.
6月 12 23:26:22 exps13arch systemd-coredump[534]: Process 531 (systemd-udevd) of user 0 dumped core.
Stack trace of thread 531:
#0 0x00007f650d54c65b __brk (/usr/lib/ld-2.31.so + 0x1c65b)
#1 0x00007f650d54b192 _dl_sysdep_start (/usr/lib/ld-2.31.so + 0x1b192)
#2 0x00007f650d532f4c _dl_start (/usr/lib/ld-2.31.so + 0x2f4c)
#3 0x00007f650d532108 _start (/usr/lib/ld-2.31.so + 0x2108)
-- Subject: Process 531 (systemd-udevd) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 531 (systemd-udevd) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
I assume this means it is not loading the relevant modules for networking either because I also have no network connectivity, so I cannot even do another pacman -Syu and hope to upgrade my way out of the problem.
6月 12 23:22:04 exps13arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
6月 12 23:22:04 exps13arch systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
6月 12 23:22:04 exps13arch systemd[1]: systemd-fsck@dev-nvme0n1p7.service: Job systemd-fsck@dev-nvme0n1p7.service/start failed with result 'dependency'.
6月 12 23:22:04 exps13arch systemd[1]: dev-nvme0n1p7.device: Job dev-nvme0n1p7.device/start failed with result 'timeout'.
6月 12 23:22:04 exps13arch systemd[1]: sys-subsystem-net-devices-wlp58s0.device: Job sys-subsystem-net-devices-wlp58s0.device/start timed out.
6月 12 23:22:04 exps13arch systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlp58s0.
Any ideas on what is wrong or how to fix would be most appreciated. Many thanks.
EDIT - duplicate of https://bbs.archlinux.org/viewtopic.php?id=256334
Last edited by onkehh (2020-06-14 22:46:27)
Offline
pacman -Q linux && uname -r
Offline
pacman -Q linux && uname -r
Ah apologies, forgot to add:
linux 5.7.2-arch1-1
Offline
jasonwryan wrote:pacman -Q linux *** && uname -r ***
Ah apologies, forgot to add:
linux 5.7.2-arch1-1
Last edited by jasonwryan (2020-06-12 07:34:42)
Offline
onkehh wrote:jasonwryan wrote:pacman -Q linux *** && uname -r ***
Ah apologies, forgot to add:
linux 5.7.2-arch1-1
I'm sorry I do not follow. That does not appear to be a valid command.
I tried asking over at the systemd mailing list but they just said it was glibc packaging error on the Arch side, though that seems unlikely considering the package (2.31-5) is almost 3 weeks old.
Offline
I was able to use this wiki page to manually load the required modules for my wireless adapter (brcmfmac, lib80211) and from there get online run another pacman -Syu which completed without issue.
https://wiki.archlinux.org/index.php/Broadcom_wireless
However on reboot the issue remains.
Offline
Could this be related https://bbs.archlinux.org/viewtopic.php?id=256334 ?
Although udevd seems to be waiting for a different piece of hardware to come up.
Offline
Could this be related https://bbs.archlinux.org/viewtopic.php?id=256334 ?
Although udevd seems to be waiting for a different piece of hardware to come up.
YES thank you this was indeed the issue.
Offline
Pages: 1