From nobody Fri Jul 12 11:15:42 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WL8Cy0hMKz5Q9wG for ; Fri, 12 Jul 2024 11:15:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WL8Cx230wz4fh8 for ; Fri, 12 Jul 2024 11:15:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 46CBFglq065315 for ; Fri, 12 Jul 2024 14:15:45 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 46CBFglq065315 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 46CBFgTE065314 for current@freebsd.org; Fri, 12 Jul 2024 14:15:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 12 Jul 2024 14:15:42 +0300 From: Konstantin Belousov To: FreeBSD Current Subject: Re: exited on signal 11 (no core dump - other error) Message-ID: References: <5bb1505d-65c5-43cb-878c-38ec02271a50@app.fastmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5bb1505d-65c5-43cb-878c-38ec02271a50@app.fastmail.com> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Spamd-Bar: - X-Spamd-Result: default: False [-1.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_SPAM_SHORT(0.99)[0.990]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_SPF_SOFTFAIL(0.00)[~all:c]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1] X-Rspamd-Queue-Id: 4WL8Cx230wz4fh8 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.