Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jul 2024 22:02:51 -0700
From:      Rick Macklem <rick.macklem@gmail.com>
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:  <CAM5tNy7USAarKu4JPUc2VWZYC%2B_SPXEZS7us2ZayZTVD%2BemvKw@mail.gmail.com>
In-Reply-To: <F304BF1C-CFAA-4126-B0A8-6B15EE003495@FreeBSD.org>
References:  <F304BF1C-CFAA-4126-B0A8-6B15EE003495@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 11, 2024 at 8:40=E2=80=AFPM Zhenlei Huang <zlei@freebsd.org> wr=
ote:
>
> 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 ll=
vmorg-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 - othe=
r error)
> pid 36947 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 37990 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 80885 (sshd), jid 0, uid 1001: exited on signal 11 (no core dump - ba=
d address)
> pid 79883 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad a=
ddress)
> pid 14245 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad a=
ddress)
> pid 49213 (ntpd), jid 0, uid 123: exited on signal 11 (no core dump - oth=
er error)
> pid 37382 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 35315 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 21366 (powerd), jid 0, uid 0: exited on signal 11 (no core dump - oth=
er error)
> pid 35735 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 36339 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> pid 37346 (getty), jid 0, uid 0: exited on signal 11 (no core dump - othe=
r error)
> Uptime: 4d1h33m9s
> ukbd0: detached
> uhub0: detached
> ---<<BOOT>>---
>
> IIUC all processes will get signal to quit on system reboot. But what doe=
s 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 shutd=
own?

rick

>
> If yes, then why they get dead locked ?
>
>
> Best regards,
> Zhenlei
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy7USAarKu4JPUc2VWZYC%2B_SPXEZS7us2ZayZTVD%2BemvKw>