Date: Wed, 2 Jan 2013 14:27:12 +0100 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Ion-Mihai Tetcu <itetcu@FreeBSD.org> Cc: mij@bitchx.it, freebsd-ports@freebsd.org Subject: Re: sshguard dumping core on 9-STABLE Message-ID: <20130102142712.48e05816@fabiankeil.de> In-Reply-To: <20130102143834.000007c4@unknown> References: <20130102143834.000007c4@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/uawtld5ua6cdlpXkae/OXhK Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Ion-Mihai Tetcu <itetcu@FreeBSD.org> wrote: > I'm seeing shhguard-ipfw sig 10 on start on my machines updated to 9-STAB= LE (eg.=20 > FreeBSD 9.1-STABLE #5 r244924: Tue Jan 1 19:45:55 EET 2013 :/usr/obj/us= r/src/sys/GENERIC amd64 > ) while on some -PRERELEASE it's running fine. > Anyone seeing something similar? I use neither sshguard nor STABLE, so it's a wild guess, but the "locked memory" changes on CURRENT caused geli segfaults for me: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D174831 I believe at least some of the commits are already MFC'd and I wouldn't rule out the possibility that they could also cause SIGBUS crashes in other circumstances. Fabian --Sig_/uawtld5ua6cdlpXkae/OXhK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlDkNbMACgkQBYqIVf93VJ3Y9QCfaiQxFTtekHZHGs8PYQgJXoxG o1IAn1cboRJpTJk2E9maL9HKAEnugwvz =ys9J -----END PGP SIGNATURE----- --Sig_/uawtld5ua6cdlpXkae/OXhK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130102142712.48e05816>