From owner-freebsd-questions@FreeBSD.ORG Tue Feb 15 01:09:35 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D7DB16A4CE for ; Tue, 15 Feb 2005 01:09:35 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B9D43D49 for ; Tue, 15 Feb 2005 01:09:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7801B52BFA; Mon, 14 Feb 2005 17:09:33 -0800 (PST) Date: Mon, 14 Feb 2005 17:09:33 -0800 From: Kris Kennaway To: Kara Chapman Message-ID: <20050215010932.GA28763@xor.obsecurity.org> References: <5C7BFA11917D504C90B39AD593859525098270@hurricane.systemmetrics.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <5C7BFA11917D504C90B39AD593859525098270@hurricane.systemmetrics.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: SMP kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 01:09:35 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 14, 2005 at 02:08:25PM -1000, Kara Chapman wrote: > Hi, >=20 > =20 >=20 > I am running FreeBSD 5.3 and have recently rebuilt the kernel to use > SMP. Ever since, I get these error messages from postfix on a regular > basis: >=20 > =20 >=20 > postfix/smtpd[49491]: fatal: accept connection: Invalid argument >=20 > =20 >=20 > Does anyone know what this means and if it's at all related to the new > kernel? Other than adding SMP, the kernel is using all the defaults. Do the messages persist if you set debug.mpsafenet=3D0 in your /boot/loader.conf and reboot (this is only a workaround since it causes relative performance degradation, but it will help to identify where the problem might be)? Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCEUvMWry0BWjoQKURAiGGAJ99gmqEV9gfJVIrIkwxF5Zld9kVGwCfXj/l SiWwNQAhg8ZNMso7Hw4esZk= =YOU3 -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--