Re: exited on signal 11 (no core dump - other error)
Date: Fri, 12 Jul 2024 08:20:19 UTC
On 12/07/2024 07:02, Rick Macklem wrote: > On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang <zlei@freebsd.org> wrote: >> >> Hi >> >> I observed something weird on Release 14.1. >> >> When rebooting my dev machine, I got >> >> ---<<BOOT>>--- >> Copyright (c) 1992-2023 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 >> FreeBSD clang version 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9) >> ... >> >> em0: promiscuous mode enabled >> em0: promiscuous mode disabled >> Waiting (max 60 seconds) for system process `vnlru' to stop... done >> Waiting (max 60 seconds) for system process `syncer' to stop... >> Syncing disks, vnodes remaining... 0 0 0 0 done >> All buffers synced. >> pid 50599 (devd), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 35393 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 36947 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 37990 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 80885 (sshd), jid 0, uid 1001: exited on signal 11 (no core dump - bad address) >> pid 79883 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad address) >> pid 14245 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad address) >> pid 49213 (ntpd), jid 0, uid 123: exited on signal 11 (no core dump - other error) >> pid 37382 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 35315 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 21366 (powerd), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 35735 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 36339 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> pid 37346 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error) >> Uptime: 4d1h33m9s >> ukbd0: detached >> uhub0: detached >> ---<<BOOT>>--- >> >> IIUC all processes will get signal to quit on system reboot. But what does the >> signal 11 mean ? Is it EDEADLK in sys/sys/errno.h ? > I think signal 11 refers to SIGSEGV (segmentation violation). > However, I have no idea why a bunch of processes would do that during shutdown? Something similar happens to me, but when logging into KDE Plasma. Sometimes it happens that desktop applications that start from a saved session (Firefox, Thunderbird, Telegram, Signal...) start loading and then everything crashes. The login screen reappears and when I log in again, everything crashes again until I restart the machine. The machine gets into this state randomly, about once a week. Jul 5 12:24:52 xxx kernel: pid 1647 (packagekitd), jid 0, uid 0: exited on signal 11 (core dumped) Jul 5 12:25:28 xxx kernel: pid 1897 (kalarm), jid 0, uid 1001: exited on signal 6 (core dumped) Jul 5 12:25:36 xxx kernel: pid 1467 (Xorg), jid 0, uid 0: exited on signal 6 (core dumped) Jul 5 12:25:37 xxx kernel: pid 1772 (signal-desktop), jid 0, uid 1001: exited on signal 5 (core dumped) Jul 5 12:25:39 xxx pulseaudio[1630]: [] core-util.c: Failed to create secure directory (/var/run/user/1001/pulse): No such file or directory Jul 5 12:25:40 xxx kernel: pid 1776 (audacious), jid 0, uid 1001: exited on signal 6 (core dumped) Jul 5 12:25:41 xxx kernel: pid 1915 (drkonqi), jid 0, uid 1001: exited on signal 6 (core dumped) Jul 5 12:25:42 xxx kernel: pid 1914 (kwin_x11), jid 0, uid 1001: exited on signal 6 (core dumped) My system is 13.3-p3 amd64. Kind regards Miroslav Lachman