Date: Fri, 12 Jul 2024 10:45:31 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "Zhenlei Huang" <zlei@freebsd.org> Cc: "FreeBSD Current" <current@freebsd.org> Subject: Re: exited on signal 11 (no core dump - other error) Message-ID: <5bb1505d-65c5-43cb-878c-38ec02271a50@app.fastmail.com> In-Reply-To: <F304BF1C-CFAA-4126-B0A8-6B15EE003495@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote: > Hi > > I observed something weird on Release 14.1. > > When rebooting my dev machine, I got > ... > 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 ? > > If yes, then why they get dead locked ? I see the same on 15.0-CURRENT too here. In my case this is just after syslog-ng is stopped. <6>[1920] pid 6090 (wezterm-gui), jid 0, uid 1002: exited on signal 11 (no core dump - other error) <6>[1920] pid 6039 (polkitd), jid 0, uid 565: exited on signal 11 (no core dump - bad address) <6>[1920] pid 4306 (dbus-daemon), jid 0, uid 556: exited on signal 11 (no core dump - bad address) ... A+ Davehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5bb1505d-65c5-43cb-878c-38ec02271a50>