From owner-freebsd-current@FreeBSD.ORG Thu Dec 12 11:34:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA70B8FE for ; Thu, 12 Dec 2013 11:34:10 +0000 (UTC) Received: from nm21-vm5.bullet.mail.ird.yahoo.com (nm21-vm5.bullet.mail.ird.yahoo.com [212.82.109.245]) by mx1.freebsd.org (Postfix) with SMTP id C08A916E9 for ; Thu, 12 Dec 2013 11:34:09 +0000 (UTC) Received: from [77.238.189.55] by nm21.bullet.mail.ird.yahoo.com with NNFMP; 12 Dec 2013 11:27:52 -0000 Received: from [46.228.39.93] by tm8.bullet.mail.ird.yahoo.com with NNFMP; 12 Dec 2013 11:27:52 -0000 Received: from [127.0.0.1] by smtp130.mail.ir2.yahoo.com with NNFMP; 12 Dec 2013 11:27:52 -0000 X-Yahoo-Newman-Id: 312774.5632.bm@smtp130.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: hfO4_HUVM1mA2Rq4GvmNQKiLAFQNd4aJeBmUwnjiOxblnVo eKxt2gl26pdgi2BMP7I_WEvXaAgbNYDKfMWDMiLpN2xRbnGv1xbTwcljWORg 3mwWbPFf6ZT_DRzMnSNKkgGRfBF5EXpbMksnKeKuwsw8xPOvjgdlaGHmffm4 Uh6ZfJGI1voVh2.v_2D2B6Or0NZADusqU6vtJmh0N2VG6gJinIS8aJ3Znxzc GWrPNfurg6hxuQfgcTIKb3ywjIZCzmHEdW0PKsCfmvyxkj_30QpIr8_odfMh PB0jq9TbamAlgP1W054Df.Esoj4lQ3Y3u1S6LnDj0GY5BrWvPxNYsLdYeOLo St8w6avPr1sQhl.m7ShF0fW6fbMcjJVVZtcQKXMer6oBX0lJFcnanN0UkcvU loFKJVdzlpC8CWf9ore899dTm10SWkXkkMvcU_.SgYbAtabIde.4juOi8Ret 5xz8plsyvxjGw9cSm9Oge9D37Bksb8CCzDnDygHjHhOBT9XVWIFnsmZ.Jyr1 9uaYNMQX_CO0jekCJwlhjGV8BvfS4Yz4- X-Yahoo-SMTP: iDf2N9.swBDAhYEh7VHfpgq0lnq. X-Rocket-Received: from [192.168.119.11] (se@84.154.107.118 with plain [188.125.69.59]) by smtp130.mail.ir2.yahoo.com with SMTP; 12 Dec 2013 11:27:52 +0000 UTC Message-ID: <52A99DB6.2080708@freebsd.org> Date: Thu, 12 Dec 2013 12:27:50 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Something wrong with -CURRENT? (network problems) X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 12 Dec 2013 11:34:10 -0000 Since about the time of teh NEWCONS commit, freshly built kernels do not work correctly for me. Symptoms are: - long delays opening TCP connections (even to localhost) - TCP transmission errors (e.g. fetchmail aborts because of short transfers, could be due to a timeout being triggered) I first noticed this during multi-user startup, since some of the daemons took tens of seconds to start (especially bad is SpamAssasin), instead of fractions of a second. At first I thought this could be caused by testing NEWCONS, but the symptoms of a kernel with SCONS are identical. Kernel configuration and other parameters are unchanged. I do not have time to bisect the commits, but just wanted to ask whether this is a general problem with -CURRENT, or only affects my test system (my local file-, media-, mail-, and web-server). (I might have time to bisect revisions during the week-end, though.) System information: i7-2660, N67 chipset, 24GB RAM, amd64 ZFS only configuration (ZRAID1, 4*2TB) Kernel config is just a stripped down generic (removing all unnecessary devices) with the following KLDs loaded: Id Refs Address Size Name 1 25 0xffffffff80200000 e0efe8 kernel 2 1 0xffffffff8100f000 22dd88 zfs.ko 3 2 0xffffffff8123d000 5b68 opensolaris.ko 4 1 0xffffffff81412000 1478 fdescfs.ko 5 1 0xffffffff81414000 c250 ipfw.ko 6 1 0xffffffff81421000 3923 linprocfs.ko 7 1 0xffffffff81425000 999 linsysfs.ko Kernel based on SVN rev. 258894 works reliably with latest world. The kernel I built after seeing the initial NEWCONS commits (still with SCONS) worked, but shortly thereafter, when I tried NEWCONS, the symptoms started (but persisted after going back to SCONS). I just checked SVN rev 259250 and the problem persists (without NEWCONS configured into the kernel). So my questions are: - is anybody else affected or is this a local problem? - has there been a commit that touched the network stack or might cause the observed delays? Thanks in advance fpr any insight you might be able to offer! Regards, STefan