[systemd-devel] systemd-udevd.service cannot start, core dump

[Lennart Poettering]

On Sa, 13.06.20 04:56, Ed Strong (onkyonky83 at outlook.com) wrote:

> Hello! As of about a week ago udev cannot start, journalctl -xe gives the below output. The stack trace references the glibc library but not sure if red herring or not. Any ideas on how to troubleshoot this would be most appreciated.
>
> I am running on Arch Linux kernel 5.7.2
>
> Many thanks,
>
>  6月 12 23:26:22 exps13arch systemd[1]: 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)

This process dies during earliest initialization in the dynamic
loader. No systemd code has run at that point yet.

Something is wrong with your libc/dynamic loader. Or maybe you have a
corrupted udev binary?

Either way, please contact your downstream distro about that first.

Lennart

--
Lennart Poettering, Berlin