On 2023/1/4 下午8:59, Michal Koutný wrote:
On Wed, Jan 04, 2023 at 07:13:59PM +0800, Heyi Guo <guoheyi@xxxxxxxxxxxxxxxxx> wrote:
Jan 04 16:10:57 ali2600 systemd[1]: Caught <SEGV>, dumped core as pid 7516.
Jan 04 16:10:57 ali2600 systemd[1]: Freezing execution.
Jan 04 16:10:57 ali2600 phosphor-dump-manager[7536]: Failed to list units:
Transport endpoint is not connected
Is it the reason for systemctl fails to work? For the log says "systemd
freezing execution".
Yes, see the line above, there's SIGSEGV in PID 1.
(Given the other SIGSEGVs, it looks like a common cause across different
processes, e.g. screwed libc update or similar.)
Also, based on the same line, you may be able to extract the coredump
from /var/lib/systemd/coredump (depends on coredump.conf:Storage=) and
figure out more.
The core shows something like this:
(gdb) bt
#0 0x00485848 in prioq_peek_by_index (idx=0, q=0x80808080) at
../git/src/basic/prioq.c:272
#1 prioq_peek (q=0x80808080) at ../git/src/basic/prioq.h:25
#2 process_timer (n=<optimized out>, d=d@entry=0x6f6600, e=<optimized
out>) at ../git/src/libsystemd/sd-event/sd-event.c:3181
#3 0x00486594 in process_timer (d=0x6f6600, n=<optimized out>,
e=0x6f65c8) at ../git/src/libsystemd/sd-event/sd-event.c:4124
#4 sd_event_wait (e=e@entry=0x6f65c8, timeout=<optimized out>) at
../git/src/libsystemd/sd-event/sd-event.c:4124
#5 0x00486bb0 in sd_event_run (timeout=18446744073709551615,
e=0x6f65c8) at ../git/src/systemd/sd-event.h:172
#6 sd_event_loop (e=0x6f65c8) at
../git/src/libsystemd/sd-event/sd-event.c:4264
#7 0x0040c59c in main_loop (manager=0x0) at ../git/src/udev/udevd.c:1872
#8 run_udevd (argv=<optimized out>, argc=<optimized out>) at
../git/src/udev/udevd.c:1984
#9 run (argv=<optimized out>, argc=<optimized out>) at
../git/src/udev/udevadm.c:116
#10 main (argc=<optimized out>, argv=<optimized out>) at
../git/src/udev/udevadm.c:133
Thanks,
Heyi
Michal
