From nobody Sun Jan 23 19:38:09 2022 X-Original-To: freebsd-arm@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 E2A001975F06; Sun, 23 Jan 2022 19:38:16 +0000 (UTC) (envelope-from fluffy@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jhk1N4T9Jz3klf; Sun, 23 Jan 2022 19:38:16 +0000 (UTC) (envelope-from fluffy@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642966696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RB1RYEYLpNEAoAw0Jo9G1BKqQjAAB6E7u/hL6CR1GQ0=; b=dhsCu/cFbgtLUgb5UdPJxm6dDiQHVo4AKp6buPpQzeWSCX/UhdZDW0Lg51p3w7dnoI2Bzm XxhmzVB3G4zG6LgCNJiJ4/4Q+U22kZ3b/ZSDnq1bjcUwCgIrE7Ho52R7FRfdTTVaXHxFCF TJjzErFFuLjtTOoPJAw1HYgx4PYBZBbvIUUeyClNEmX1JsO4XrBnj4d0cBJDWX7JCkzY4d 7+yUWrcJKZ7g+/zXD5+iNfCGM/tNCDjTk6MOUjnAN3rt6VEzkuze4ZhMRRrwUgkfud8gUq jy6fwnjzrmQZDh6fgVCihOvcC48WZuu9zEN2A1VtwnYQ3tHRTKt5gb6IKoMMsQ== Received: from [10.100.224.144] (unknown [5.101.143.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: fluffy) by smtp.freebsd.org (Postfix) with ESMTPSA id BFB9D25C9C; Sun, 23 Jan 2022 19:38:14 +0000 (UTC) (envelope-from fluffy@FreeBSD.org) Date: Sun, 23 Jan 2022 22:38:09 +0300 From: Dima Panov To: freebsd-current@freebsd.org, tech-lists , freebsd-arm@freebsd.org Message-ID: In-Reply-To: References: <8BA9DE0C-81B4-420E-B326-7B7133EC31BA@dons.net.au> Subject: Re: POLLHUP detected on devd socket List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="61edaea1_12200854_7d7d"; protocol="application/pgp-signature" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642966696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=RB1RYEYLpNEAoAw0Jo9G1BKqQjAAB6E7u/hL6CR1GQ0=; b=Fjxopk/iEuMKFWqrjX+QHoODV/SBTXNA/38x6DdOGxcbmFqspuVbaEGWaMS5qEmcvxrXdu hiZKGfiPUOa8daSE540Cs+gdzY8+KjjVNFRedWp6Gsb6GRcjkBTtJlrgwxleQYhZxLoqML Q2YY+AnnUDFzKdYb/QlWpmVKHgZ6noiAIEvcLPtk6mEO1UTdGvaIJoGyUJmSUyPYQwM1/D ZCYTNfjIELDkrhHey6t6RfOwjp4LiEGuakBeJfWAr7/rlmgbcXOGYcN3HYXRv4kEEdYNQf q5RpREltb3Ue4z2nBZtDyGgiB5l3Vg3CpCmHJoRzUBZw9536KocHUmVi23Z3Cw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1642966696; a=rsa-sha256; cv=none; b=qTew6g2T733lhmRZdR+8izhWb/RR8uHphAP3R1i8HwUn5Y7E5JRKn0ewRhag7BcKz9fd+F 1T/LwO3ResxMoxCj23cqRAuR9qTbal64Pv/cQur2QrtLdEI1oLxVGF5wnTNBHD1/vLvDHp L/0p7IBzKJxz2WfA8GM1UgWRa/c5hXv1HM+wkOFuMbZfH8WQYaMMlh1lriUR8tWK9OePhO ajuujRDS/Z8zOguRts3cUgcQkzPZEO8Q3ylVovd9rfwNRvaycFJfGYCMdZ4s6LOSEq8mZC 1ivjSamghgjwDPPgRg2fAzV5fk1ouWzzqzy9ZZ+CKa4Y9nQBL8SwysHWzoYlSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --61edaea1_12200854_7d7d Content-Type: multipart/alternative; boundary="61edaea1_5bd062c2_7d7d" --61edaea1_5bd062c2_7d7d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Moin=21 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 d= aemons such as sshd, crond, syslogd (almost all runned daemons) stopeed b= y signal 15 too. At least, as it shows by system logs. Will try to play with zfsd disabled, as suggested. -- Dima. (desktop, kde, x11, office, ports-secteam)=40=46reeBSD team (fluffy=40=46reeBSD.org, https://t.me/dima=5Fpanov) > On Sunday, Jan 23, 2022 at 12:03 PM, tech-lists wrote: > On Sun, Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote: > > > Is it reproducible=3F ie can you trigger it post boot=3F > > > > 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. --61edaea1_5bd062c2_7d7d Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <= meta name=3D=22viewport=22 content=3D=22width=3Ddevice-width, initial-sca= le=3D1.0, user-scalable=3Dno=22> 3D=22=22
Moin=21


I saw a s= uch issue on amd64, both 13.0-RELEASE and -CURRENT.=C2=A0
Both = hosts have zfsd enabled, and after devd die by signal 15 all other daemon= s such as sshd, crond, syslogd (almost all runned daemons) stopeed by sig= nal 15 too. At least, as it shows by system logs.

Will try to play with zfsd disabled, as suggested.

--
Dima. (desktop, kde, x11, office, ports-secteam)=40= =46reeBSD team
(fluffy=40=46reeBSD.org, https://t.me/dima=5Fpan= ov)

On Sunday, J= an 23, 2022 at 12:03 PM, tech-lists <tech-lists=40zyxst.net> wrote:
On Sun,= Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote:

Is it reproducible=3F ie can you trigger it post = boot=3F

It is very strange that devd dying would kill anything e= lse running -
I have stopped and started it a lot while testing devd = scripts and
I haven't seen anything else break.

One idea wou= ld be to hack up devd's rc.d script and run it under
ktrace and try a= nd get some clues.

I can try that, thanks for the s= uggestion.

Right now I'm thinking it's tied to zfsd, since disab= ling that
service I've not seen the issue.
--
J.
<= /div> --61edaea1_5bd062c2_7d7d-- --61edaea1_12200854_7d7d Content-Type: application/pgp-signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: Canary PGP V3 iQJVBAABCgA/OBxEaW1hIFBhbm92IChGcmVlQlNELk9SRyBDb21taXR0ZXIpIDxm bHVmZnlARnJlZUJTRC5PUkc+BQJh7a6hAAoJEPuLoJ3VOY8peNgP/R0jq+eWgHaU dqZOuRE98wTHP+oEI+Zb0MhSkOFQ/NTHsCDZcLjt6Gt8S/U6pDFAY5gGtHSFXINP vQjiFjVjh5pOiDisInXEzJxIojgoC/Lws3OwTWFgmjVCyG4dre/MxquJv7r3CxSZ Sk4jfhX1nfg0+WsRaVQyOuet/hcrA/AiIfjiFcBhkk1Y5S9rwUcARJyN5s3vS4lc knuKMZHPAKXVPWLKXfV+8sKuUTr4Lkvsv4omXgV2oi+B1eWPaUzmdr9sLjRXohG4 fJojDT1/Di4Ak8I4pqBM1jUfduCxRrkHYa/D50pd4JIL2BAG1xubTpjBLjkAP//f 7VwONwUMuiJGpJCZDrXXHh4NrnTvwTsueotqLWTOL69Kzsw00HuXFEA7G9ITxNp6 tKQyGToOT0qqp4qRbqfIZnb15PsEBv3w3ZY/RgL56BaZe/QHNvb9erF0RpHd1fKk SQA7I+YlAIbQ9BT0WAaIRFvPma7UeMq7GmvyiBOIJJkovwpKlqReK8XqJxF3ddC7 PYaMPIeQ3Ecb1N3sSE/yIudMFKNQ5hb611o36Wo6nprCt5tnrhoRMtKZ5cJuPiVS PHtrYKnF6ixdL6WLzEsaukmYxoZKPZNXkeYTCmltppBUhTVYb4F5cmig7IVgxokP G30/gY/RYXXs1dY1HI0B1U1FTl6d6OvN =OZ4V -----END PGP SIGNATURE----- --61edaea1_12200854_7d7d--