Date: Sun, 23 Jan 2022 16:58:27 -0700 From: Warner Losh <imp@bsdimp.com> To: Dima Panov <fluffy@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, tech-lists <tech-lists@zyxst.net>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: POLLHUP detected on devd socket Message-ID: <CANCZdfoYZGH5ykcKqmsUMtv8dSLOzZroqgOEOnZ0wsYojzN0oQ@mail.gmail.com> In-Reply-To: <d9d85d02-5c2c-476f-99ee-f33e8b069d4b@Canary> References: <YewV/8v7nb78a%2Bg4@ceres.zyxst.net> <8BA9DE0C-81B4-420E-B326-7B7133EC31BA@dons.net.au> <Ye0ZsFgQL8jlAGaF@ceres.zyxst.net> <d9d85d02-5c2c-476f-99ee-f33e8b069d4b@Canary>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Jan 23, 2022 at 1:07 PM Dima Panov <fluffy@freebsd.org> wrote: > Moin! > > > I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT. > Both hosts have zfsd enabled, and after devd die by signal 15 all other > daemons such as sshd, crond, syslogd (almost all runned daemons) stopeed by > signal 15 too. At least, as it shows by system logs. > Signal 15 is SIGTERM, which is the software signal from kill(1).... Warner > Will try to play with zfsd disabled, as suggested. > > -- > Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team > (fluffy@FreeBSD.org, https://t.me/dima_panov) > > On Sunday, Jan 23, 2022 at 12:03 PM, tech-lists <tech-lists@zyxst.net> > wrote: > On Sun, Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote: > > Is it reproducible? ie can you trigger it post boot? > > It is very strange that devd dying would kill anything else running - > I have stopped and started it a lot while testing devd scripts and > I haven't seen anything else break. > > One idea would be to hack up devd's rc.d script and run it under > ktrace and try and get some clues. > > > I can try that, thanks for the suggestion. > > Right now I'm thinking it's tied to zfsd, since disabling that > service I've not seen the issue. > -- > J. > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jan 23, 2022 at 1:07 PM Dima Panov <<a href="mailto:fluffy@freebsd.org">fluffy@freebsd.org</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"> <div style="font-family:Helvetica;color:rgb(0,0,0);font-size:13px"><img id="gmail-m_5433901728503372578597B2328D72BB35BBAC8CD91A1D8EA24" alt="" width="0px" src="https://read-receipts.canarymail.io:8100/track/2BD3A57834F2C18772CBE819A75674B4_597B2328D72BB35BBAC8CD91A1D8EA24.png" height="0px"><div id="gmail-m_5433901728503372578CanaryBody"> <div> Moin!</div><div><br></div><div><br></div><div>I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT. </div><div>Both hosts have zfsd enabled, and after devd die by signal 15 all other daemons such as sshd, crond, syslogd (almost all runned daemons) stopeed by signal 15 too. At least, as it shows by system logs.</div></div></div></blockquote><div><br></div><div>Signal 15 is SIGTERM, which is the software signal from kill(1)....<br></div><div><br></div><div>Warner</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="font-family:Helvetica;color:rgb(0,0,0);font-size:13px"><div id="gmail-m_5433901728503372578CanaryBody"><div>Will try to play with zfsd disabled, as suggested.</div><div><br></div> </div> <div id="gmail-m_5433901728503372578CanarySig"> <div> <div style="font-family:Helvetica">--<br><div>Dima. (desktop, kde, x11, office, ports-secteam)@FreeBSD team</div><div>(fluffy@FreeBSD.org, <a href="https://t.me/dima_panov" target="_blank">https://t.me/dima_panov</a>)</div></div>; <div><br></div> </div> </div> <div id="gmail-m_5433901728503372578CanaryDropbox"> </div> <blockquote id="gmail-m_5433901728503372578CanaryBlockquote"> <div> <div>On Sunday, Jan 23, 2022 at 12:03 PM, tech-lists <<a href="mailto:tech-lists@zyxst.net" target="_blank">tech-lists@zyxst.net</a>> wrote:<br></div> <div>On Sun, Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote: <br> <br><blockquote type="cite">Is it reproducible? ie can you trigger it post boot? <br> <br>It is very strange that devd dying would kill anything else running - <br>I have stopped and started it a lot while testing devd scripts and <br>I haven't seen anything else break. <br> <br>One idea would be to hack up devd's rc.d script and run it under <br>ktrace and try and get some clues. <br></blockquote> <br>I can try that, thanks for the suggestion. <br> <br>Right now I'm thinking it's tied to zfsd, since disabling that <br>service I've not seen the issue. <br>-- <br>J. <br></div> </div> </blockquote> </div></blockquote></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoYZGH5ykcKqmsUMtv8dSLOzZroqgOEOnZ0wsYojzN0oQ>