Date: Fri, 12 Jul 2024 13:36:09 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: exited on signal 11 (no core dump - other error) Message-ID: <298825087.4944.1720784169535@localhost> In-Reply-To: <ZpEPAqVFSsts59QV@kib.kiev.ua> References: <F304BF1C-CFAA-4126-B0A8-6B15EE003495@FreeBSD.org> <5bb1505d-65c5-43cb-878c-38ec02271a50@app.fastmail.com> <ZpEPAqVFSsts59QV@kib.kiev.ua>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Van: Konstantin Belousov <kostikbel@gmail.com>
Datum: vrijdag, 12 juli 2024 13:15
Aan: FreeBSD Current <current@freebsd.org>
Onderwerp: Re: exited on signal 11 (no core dump - other error)
>
> On Fri, Jul 12, 2024 at 10:45:31AM +0000, Dave Cottlehuber wrote:
> > 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)
>
> Most natural cause for SIGSEGV during shutdown is because root is unmounted
> while the processes are still handling signals (SIGTERM) from init. The
> text vnodes for the process binary and shared libraries are force-reclaimed,
> and any page-in request results in the unhandled fault.
>
> I regularly see these SIGSEGVs on nfs-booted crash boxes.
>
>
>
>
I can also easily reproduce this on my RPI4/15-CURRENT using 2 ZFS disks via USB.
Just did a shutdown -r now to check and appended the serial output here.
FreeBSD/arm64 (rpi4) (ttyu0)
login: Jul 7 23:47:46 rpi4 shuStopping jails: jail14 jail13 jenkins monitoring loghost.
Stopping node_exporter.
Stopping sshd.
Waiting for PIDS: 1910.
Stopping cron.
Waiting for PIDS: 1863.
Stopping powerd.
Waiting for PIDS: 1832.
Stopping rtsold.
Waiting for PIDS: 1484.
Stopping devd.
Waiting for PIDS: 1475.
Writing RTC file: /var/db/fakertc.
Writing entropy file: .
Writing early boot entropy file: .
.
Terminated
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 0 done
All buffers synced.
pid 23288 (sshd), jid 0, uid 1001: exited on signal 4 (no core dump - bad address)
pid 23329 (bash), uid (0): Path `/var/tmp/0.bash.0.23329.core' failed on initial open test, error = 2
pid 23286 (sshd), jid 0, uid 0: exited on signal 4 (no core dump - bad address)
pid 23329 (bash), jid 0, uid 0: exited on signal 4 (no core dump - other error)
pid 23328 (su), jid 0, uid 0: exited on signal 4 (no core dump - bad address)
pid 23289 (bash), uid (1001): Path `/var/tmp/1001.bash.0.23289.core' failed on initial open test, error = 2
pid 23289 (bash), jid 0, uid 1001: exited on signal 4 (no core dump - other error)
Uptime: 23h48m34s
Resetting system ... pid 1769 (syslogd), uid (0): Path `/var/tmp/0.syslogd.0.1769.core' failed on initial open test, error = 2
pid 1769 (syslogd), jid 0, uid 0: exited on signal 4 (no core dump - other error)
To me it looks like the sshd process in which I typed 'shutdown -r now' is still available somehow.
Regards,
Ronald.
[-- Attachment #2 --]
<html><head></head><body><br>
<p><strong>Van:</strong> Konstantin Belousov <kostikbel@gmail.com><br>
<strong>Datum:</strong> vrijdag, 12 juli 2024 13:15<br>
<strong>Aan:</strong> FreeBSD Current <current@freebsd.org><br>
<strong>Onderwerp:</strong> Re: exited on signal 11 (no core dump - other error)</p>
<blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">
<div class="MessageRFC822Viewer" id="P">
<div class="TextPlainViewer" id="P.P">On Fri, Jul 12, 2024 at 10:45:31AM +0000, Dave Cottlehuber wrote:<br>
> On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote:<br>
> > Hi<br>
> ><br>
> > I observed something weird on Release 14.1.<br>
> ><br>
> > When rebooting my dev machine, I got<br>
> > ...<br>
> > IIUC all processes will get signal to quit on system reboot. But what does the<br>
> > signal 11 mean ? Is it EDEADLK in sys/sys/errno.h ?<br>
> ><br>
> > If yes, then why they get dead locked ?<br>
><br>
> I see the same on 15.0-CURRENT too here. In my case this is just after syslog-ng is stopped.<br>
><br>
> <6>[1920] pid 6090 (wezterm-gui), jid 0, uid 1002: exited on signal 11 (no core dump - other error)<br>
> <6>[1920] pid 6039 (polkitd), jid 0, uid 565: exited on signal 11 (no core dump - bad address)<br>
> <6>[1920] pid 4306 (dbus-daemon), jid 0, uid 556: exited on signal 11 (no core dump - bad address)<br>
<br>
Most natural cause for SIGSEGV during shutdown is because root is unmounted<br>
while the processes are still handling signals (SIGTERM) from init. The<br>
text vnodes for the process binary and shared libraries are force-reclaimed,<br>
and any page-in request results in the unhandled fault.<br>
<br>
I regularly see these SIGSEGVs on nfs-booted crash boxes.<br>
</div>
<hr></div>
</blockquote>
<br>
<br>
I can also easily reproduce this on my RPI4/15-CURRENT using 2 ZFS disks via USB.<br>
Just did a shutdown -r now to check and appended the serial output here.<br>
<br>
FreeBSD/arm64 (rpi4) (ttyu0) <br>
<br>
login: Jul 7 23:47:46 rpi4 shuStopping jails: jail14 jail13 jenkins monitoring loghost. <br>
Stopping node_exporter. <br>
Stopping sshd. <br>
Waiting for PIDS: 1910. <br>
Stopping cron. <br>
Waiting for PIDS: 1863. <br>
Stopping powerd. <br>
Waiting for PIDS: 1832.<br>
Stopping rtsold.<br>
Waiting for PIDS: 1484.<br>
Stopping devd.<br>
Waiting for PIDS: 1475.<br>
Writing RTC file: /var/db/fakertc.<br>
Writing entropy file: .<br>
Writing early boot entropy file: .<br>
.<br>
Terminated<br>
Waiting (max 60 seconds) for system process `vnlru' to stop... done<br>
Waiting (max 60 seconds) for system process `syncer' to stop...<br>
Syncing disks, vnodes remaining... 0 0 0 0 0 done<br>
All buffers synced.<br>
pid 23288 (sshd), jid 0, uid 1001: exited on signal 4 (no core dump - bad address)<br>
pid 23329 (bash), uid (0): Path `/var/tmp/0.bash.0.23329.core' failed on initial open test, error = 2<br>
pid 23286 (sshd), jid 0, uid 0: exited on signal 4 (no core dump - bad address)<br>
pid 23329 (bash), jid 0, uid 0: exited on signal 4 (no core dump - other error)<br>
pid 23328 (su), jid 0, uid 0: exited on signal 4 (no core dump - bad address)<br>
pid 23289 (bash), uid (1001): Path `/var/tmp/1001.bash.0.23289.core' failed on initial open test, error = 2<br>
pid 23289 (bash), jid 0, uid 1001: exited on signal 4 (no core dump - other error)<br>
Uptime: 23h48m34s<br>
Resetting system ... pid 1769 (syslogd), uid (0): Path `/var/tmp/0.syslogd.0.1769.core' failed on initial open test, error = 2<br>
pid 1769 (syslogd), jid 0, uid 0: exited on signal 4 (no core dump - other error)<br>
<br>
To me it looks like the sshd process in which I typed 'shutdown -r now' is still available somehow.<br>
<br>
Regards,<br>
Ronald.<br>
</body></html>
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?298825087.4944.1720784169535>
