From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 19:59:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5A6A16A418 for ; Wed, 22 Aug 2007 19:59:22 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 8679C13C465 for ; Wed, 22 Aug 2007 19:59:22 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l7MKbb0V060195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2007 16:37:44 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: David Malone Date: Wed, 22 Aug 2007 16:02:32 -0400 User-Agent: KMail/1.9.6 References: <200708210928.aa80674@walton.maths.tcd.ie> In-Reply-To: <200708210928.aa80674@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2033423.lNeCjCqxub"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200708221602.42191.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.90.3/4025/Tue Aug 21 19:37:57 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Can't create TCP connections to certain IP addresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 22 Aug 2007 19:59:22 -0000 --nextPart2033423.lNeCjCqxub Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 21 August 2007, David Malone wrote: > > What's the PR number? > > The PR that I am thinking of is: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Di386/69257 > > > COPTFLAGS+=3D-O2 > > CPUTYPE=3Di586/mmx > > I guess you may not be directly be effected, as you're using -O2, > but it might be another interaction with gcc, so I'd try compiling > a kernel with -O, just to see if you get a different result. > > (Record the output of building the kernel, just to make sure it is > using the flags you think it is.) I had to specify CFLAGS=3D-O -pipe in make.conf to force the kernel to build without -O2 even after=20 removing the COPTFLAGS and CPUTYPE. It's fixed now by forcing -O, but this seems to be a serious issue=20 as -O2 is the default. Is this fixed in 4.2.1? And will that make it=20 into 7.0? =2D-=20 Anish Mistry --nextPart2033423.lNeCjCqxub Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBGzJZixqA5ziudZT0RAqYsAJ0YJ4ESV23T7tCvZx3j/midIiRiogCfQtG/ R0sreihTck3/9aBATUnUTIY= =mism -----END PGP SIGNATURE----- --nextPart2033423.lNeCjCqxub--