Re: exited on signal 11 (no core dump - other error)

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.