a very, very long time ago (late '90s) I reported something like that to Jordan Hubbard. He suggested HW issues ... honestly can't remember whether he was right :-/
On Fri, Jul 12, 2024 at 7:03 AM Rick Macklem <rick.mack...@gmail.com> wrote: > On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang <z...@freebsd.org> wrote: > > > > 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 > llvmorg-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 - > other error) > > pid 36947 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 37990 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 80885 (sshd), jid 0, uid 1001: exited on signal 11 (no core dump - > bad address) > > pid 79883 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad > address) > > pid 14245 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad > address) > > pid 49213 (ntpd), jid 0, uid 123: exited on signal 11 (no core dump - > other error) > > pid 37382 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 35315 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 21366 (powerd), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 35735 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 36339 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > pid 37346 (getty), jid 0, uid 0: exited on signal 11 (no core dump - > other error) > > Uptime: 4d1h33m9s > > ukbd0: detached > > uhub0: detached > > ---<<BOOT>>--- > > > > 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 ? > I think signal 11 refers to SIGSEGV (segmentation violation). > However, I have no idea why a bunch of processes would do that during > shutdown? > > rick > > > > > If yes, then why they get dead locked ? > > > > > > Best regards, > > Zhenlei > > > > > > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'
