From owner-freebsd-current@FreeBSD.ORG Fri Apr 22 18:02:10 2005 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 A7C5E16A4CE for ; Fri, 22 Apr 2005 18:02:10 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC4843D55 for ; Fri, 22 Apr 2005 18:02:10 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) id j3MI2Ag7014536; Fri, 22 Apr 2005 11:02:10 -0700 (PDT) Received: from [10.1.1.245] (nfw1.codefab.com [199.103.21.225]) (authenticated bits=0) by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id j3MI28rT028712; Fri, 22 Apr 2005 11:02:09 -0700 (PDT) In-Reply-To: <17001.9557.627987.505930@roam.psg.com> References: <17001.9557.627987.505930@roam.psg.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Fri, 22 Apr 2005 14:02:07 -0400 To: Randy Bush X-Mailer: Apple Mail (2.622) cc: FreeBSD Current Subject: Re: significant increase in ipfw pullup failed 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: Fri, 22 Apr 2005 18:02:10 -0000 On Apr 22, 2005, at 12:24 PM, Randy Bush wrote: > on a 1ru system with an fxp > yesterday, i cvsupped Apr 21 17:00 and built, first time in a few weeks > previously i got an ipfw pullup failed a couple of times a day > now i get them every few minutes > > anyone else seeing this, or should i start to send someone into > the colo to check cables? What it means is that the IPFW code didn't see a long enough packet to contain enough data to be logged usefully. That could be a sign of hardware problems like a flaky cable or a NIC that is going wonky: if you can check "netstat -i" and look for excessive input errors or collisions. If the machine is connected to a managed switch, look for "runt packets", smaller than 54 bytes (56?, whatever the minimum valid size is).... -- -Chuck