21.02.2025 23:39, Joanne Norman wrote:
Linux distribution: Poky reference distribution from Yocto Project release 5.0 "Scarthgap" systemd version: 255.4 kernel: 6.6.25-intel-pk-standardSystemd is disabling coredumps during bootup, claiming that it's "Due to PID 1 having crashed". However, aside from that log line, I can find no evidence that PID 1 actually crashed, and the system continues to boot normally. Log lines immediately afterward indicate that udevd has crashed at the same time, but again, it appears to recover, as the system boots normally afterward and "systemd[1]:" log statements continue to appear. root@intel-corei7-64:~# journalctl -b | grep coredump -C10 -unrelated context elided- Feb 21 19:00:56 intel-corei7-64 systemd-coredump[396]: Due to PID 1 having crashed coredump collection will now be turned off. Feb 21 19:00:56 intel-corei7-64 systemd-coredump[396]: Resource limits disable core dumping for process 103 (udevd). Feb 21 19:00:56 intel-corei7-64 systemd-coredump[396]: Process 103 (udevd) of user 0 terminated abnormally without generating a coredump. Feb 21 19:00:57 intel-corei7-64 kernel: igb 0000:01:00.0 enp1s0: igb: enp1s0 NIC Link is Up 100 Mbps Half Duplex, Flow Control: None Feb 21 19:00:57 intel-corei7-64 kernel: igb 0000:01:00.0: EEE Disabled: unsupported at half duplex. Re-enable using ethtool when at full duplex. -unrelated context elided- root@intel-corei7-64:~# cat /proc/sys/kernel/core_pattern |/bin/false Setting LogLevel=debug in /etc/systemd/system.conf and rebooting produces a hell of a lot of extra logs, but nothing that mentions PID 1 crashing or provides any additional details about the udevd crash. Same for setting udev_log=debug in /etc/udev/udev.conf. coredumpctl lists the udev crash, but makes no mention of the purported "PID 1" crash (note, this log is from a separate boot, so the PID and times are different from above): root@intel-corei7-64:~# coredumpctl info 102 PID: 102 (udevd) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Thu 2025-02-20 22:29:28 UTC (30min ago) Command Line: udevd --daemon Executable: /usr/bin/udevadm Control Group: /init.scope Unit: init.scope
This is the reason for this message. Normally only systemd itself should be in this cgroup. How exactly do you start systemd?
