From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 13:26:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 954CC16A4CE for ; Sat, 17 Jan 2004 13:26:18 -0800 (PST) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CC6143D3F for ; Sat, 17 Jan 2004 13:26:16 -0800 (PST) (envelope-from Peter_Losher@isc.org) Received: from dhcp-2.sql1.plosh.net (tardis-nat.plosh.net [64.139.14.228]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 0AA8FA82B for ; Sat, 17 Jan 2004 21:26:16 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: freebsd-current@freebsd.org Date: Sat, 17 Jan 2004 13:26:20 -0800 User-Agent: KMail/1.5.94 References: <200401160250.54593.Peter_Losher@isc.org> <20040116091901.V92448@carver.gumbysoft.com> In-Reply-To: <20040116091901.V92448@carver.gumbysoft.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200401171326.27264.Peter_Losher@isc.org> Subject: Updating 5.1->5.2 (Was - Re: Fatal trap under heavy load on 5.1-p10...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 21:26:18 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 16 January 2004 09:24 am, Doug White wrote: > You're using ZERO_COPY_SOCKETS, which isn't a common option. =46air enough - By the time you had sent this yesterday , I had already=20 reverted to kernel.old, which doesn't have ZERO_COPY_SOCKETS enabled. > Are you going to upgrade freebsd.isc.org to 5.2, or what? 5.1 is crusy > old by comparison :-) I was going to do it when the load went down from the 5.2 release over=20 this weekend. After updating the src tree, make buildworld dies w/ =2D -=3D- =3D=3D=3D> lib/libpam/modules/pam_echo cc -O2 -pipe -mcpu=3Dpentiumpro =2D -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/incl= ude =2D -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers=20 =2D -Werror -Wall =2D -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes=20 =2D -Wpointer-arith -Wreturn-type =2D -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align=20 =2D -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning:=20 dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_echo. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. sf1% =2D -=3D- I have done the 5.1->5.2 upgrade on several machines now, so this error=20 is perplexing. =2E=20 > You're the heaviest load thats ever been put on that code :)=20 Part of our work here with this box is to help make 5.x more robust and=20 make sure it's battle hardened, so we are happy to provide the load=20 testing. :) Best Wishes - Peter =2D --=20 Peter_Losher@isc.org | ISC | OpenPGP Key E8048D08 | "The bits must flow" =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFACaiCPtVx9OgEjQgRAnI3AKDY1wf7oMZasNZEOGYADkamAmAzMgCfTubZ 7cEMkbVnWHPKP6G9iMPiBSE=3D =3DXaCY =2D----END PGP SIGNATURE-----