From owner-freebsd-net@FreeBSD.ORG Tue Nov 7 20:57:49 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.ORG Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A30716A416 for ; Tue, 7 Nov 2006 20:57:49 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from zealot.ksu.ru (zealot.ksu.ru [194.85.245.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E52343D4C for ; Tue, 7 Nov 2006 20:57:46 +0000 (GMT) (envelope-from amarat@ksu.ru) Received: from [127.0.0.1] (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.13.8/8.13.8) with ESMTP id kA7KviH7089854; Tue, 7 Nov 2006 23:57:45 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <4550F348.8040509@ksu.ru> Date: Tue, 07 Nov 2006 23:57:44 +0300 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.13) Gecko/20060514 X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, amarat@ksu.ru References: <200611072019.kA7KJsAm073276@lurza.secnetix.de> In-Reply-To: <200611072019.kA7KJsAm073276@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: a very strange netstat output and problem when using transparent proxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2006 20:57:49 -0000 Oliver Fromme wrote: > Marat N.Afanasyev wrote: > > bge0: flags=8843 mtu 1500 > > Ok, I also have a machine with bge(4) NIC within reach. > I've had a look at it for similar symptoms (see below). > > > bge0 1500 00:50:45:5f:4f:78 2341018 799 3062828 > > 0 0 > > 799 is not good, but I wouldn't call it "huge amount of > ierrs". Is that a typical number, or was that output > taken before the problem (network freeze) appears? more typical is the following: % netstat -I bge0 -w 60 input (bge0) output packets errs bytes packets errs bytes colls 151993 241 111011660 172436 0 120848541 0 169867 388 118858096 192997 0 135783627 0 130524 407 91213775 145884 0 110857756 0 327168 1637 214730921 397193 0 275486626 0 385627 1027 254274520 471177 0 333456526 0 300184 720 198432049 367100 0 271325679 0 261095 5525 166910652 324112 0 251708900 0 278257 11998 176453071 349975 0 268865328 0 314383 8617 203347024 393589 0 301819857 0 195408 11647 129989509 246718 0 195720356 0 7163 23787 6087244 13165 0 7694485 0 2485 24786 1743165 6571 0 4015170 0 2202 26175 1117627 6225 0 3992217 0 and oops. none of two interfaces can any more process any incoming packet. ping drops increase to 99% > > > % uptime > > 7:34PM up 40 mins, 3 users, load averages: 0.14, 0.16, 0.08 > > Ok, 799 ierrs after 40 minuted uptime is definitely not > good. :-) > > > Real IP address. I've already switched forward off and make squid listen > > on 80 instead. Problem persists. > > OK, so it's a NIC problem, not IPFW-related. > > Here's output from my machine with bge(4) NIC: > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > bge0 1500 00:16:35:... 7808595 35 3451475 0 0 > > Uptime is 8 days, the machine is only moderately loaded, > but gets quite some amount of NFS traffic (as a client). > OS is FreeBSD 6.2-PRELELEASE as of October 19th. as I said before, this problem persists on all my machines with 5704. > Whie 35 ierrs in 8 days isn't much, I think it still > indicates a problem somewhere. It should really be 0. > (I haven't experienced any freezes or other problems, > though.) > > Maybe you should ask on the -stable mailing list for > others with bge(4) NICs to check. It looks like a bug > in the driver. > > Oh by the way, do you have polling enabled? Try to > switch in on (if disabled) or off (if enabled) and check > whether it improves the situation for you. > > Best regards > Oliver > polling cannot be "safely" turned on smp, without eating a lot of cpu to interrupt processing. So, I run away from polling. -- SY, Marat