Date: Fri, 12 Jul 2024 07:12:12 +0200 From: Michael Schuster <michaelsprivate@gmail.com> To: Rick Macklem <rick.macklem@gmail.com> Cc: Zhenlei Huang <zlei@freebsd.org>, FreeBSD Current <current@freebsd.org> Subject: Re: exited on signal 11 (no core dump - other error) Message-ID: <CADqw_g%2B3hMOWvr3W08mzARKE-MewvzpWrgCS3ni1aj7WHr5nyw@mail.gmail.com> In-Reply-To: <CAM5tNy7USAarKu4JPUc2VWZYC%2B_SPXEZS7us2ZayZTVD%2BemvKw@mail.gmail.com> References: <F304BF1C-CFAA-4126-B0A8-6B15EE003495@FreeBSD.org> <CAM5tNy7USAarKu4JPUc2VWZYC%2B_SPXEZS7us2ZayZTVD%2BemvKw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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.macklem@gmail.com> wrote: > On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang <zlei@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' [-- Attachment #2 --] <div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">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 :-/</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 12, 2024 at 7:03 AM Rick Macklem <<a href="mailto:rick.macklem@gmail.com">rick.macklem@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang <<a href="mailto:zlei@freebsd.org" target="_blank">zlei@freebsd.org</a>> wrote:<br> ><br> > Hi<br> ><br> > I observed something weird on Release 14.1.<br> ><br> > When rebooting my dev machine, I got<br> ><br> > ---<<BOOT>>---<br> > Copyright (c) 1992-2023 The FreeBSD Project.<br> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994<br> > The Regents of the University of California. All rights reserved.<br> > FreeBSD is a registered trademark of The FreeBSD Foundation.<br> > FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64<br> > FreeBSD clang version 18.1.5 (<a href="https://github.com/llvm/llvm-project.git" rel="noreferrer" target="_blank">https://github.com/llvm/llvm-project.git</a>; llvmorg-18.1.5-0-g617a15a9eac9)<br> > ...<br> ><br> > em0: promiscuous mode enabled<br> > em0: promiscuous mode disabled<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 done<br> > All buffers synced.<br> > pid 50599 (devd), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 35393 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 36947 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 37990 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 80885 (sshd), jid 0, uid 1001: exited on signal 11 (no core dump - bad address)<br> > pid 79883 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad address)<br> > pid 14245 (sshd), jid 0, uid 0: exited on signal 11 (no core dump - bad address)<br> > pid 49213 (ntpd), jid 0, uid 123: exited on signal 11 (no core dump - other error)<br> > pid 37382 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 35315 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 21366 (powerd), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 35735 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 36339 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > pid 37346 (getty), jid 0, uid 0: exited on signal 11 (no core dump - other error)<br> > Uptime: 4d1h33m9s<br> > ukbd0: detached<br> > uhub0: detached<br> > ---<<BOOT>>---<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> I think signal 11 refers to SIGSEGV (segmentation violation).<br> However, I have no idea why a bunch of processes would do that during shutdown?<br> <br> rick<br> <br> ><br> > If yes, then why they get dead locked ?<br> ><br> ><br> > Best regards,<br> > Zhenlei<br> ><br> ><br> <br> </blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Michael Schuster<br><a href="http://recursiveramblings.wordpress.com/" target="_blank">http://recursiveramblings.wordpress.com/</a><br></div><div>recursion, n: see 'recursion'<br></div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADqw_g%2B3hMOWvr3W08mzARKE-MewvzpWrgCS3ni1aj7WHr5nyw>