From owner-freebsd-net@FreeBSD.ORG Wed Jun 25 12:42:51 2003 Return-Path: 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 731A437B401 for ; Wed, 25 Jun 2003 12:42:51 -0700 (PDT) Received: from mail.buzzardnews.com (mail.buzzardnews.com [64.235.227.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3FCA43FF2 for ; Wed, 25 Jun 2003 12:42:50 -0700 (PDT) (envelope-from shawn@cpl.net) Received: from shawn ([216.117.221.133]) by mail.buzzardnews.com (8.11.3/8.11.3) with SMTP id h5PJgn404495 for ; Wed, 25 Jun 2003 12:42:50 -0700 (PDT) Message-ID: <05c301c33b51$3d2db020$85dd75d8@shawn> From: "Shawn Ramsey" To: Date: Wed, 25 Jun 2003 12:37:33 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Lots of input errors... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 19:42:52 -0000 > netstat -I xl0 -w 1 input (xl0) output packets errs bytes packets errs bytes colls 6918 22 8525822 5631 0 2770466 0 7317 21 9262852 6041 0 2696855 0 7839 26 10090955 6426 0 2686936 0 7260 14 9318261 5789 0 2407180 0 6653 14 8255322 5552 0 2693452 0 7818 17 9966908 6323 0 2693943 0 7003 12 9056270 5406 0 2250436 0 7104 17 8904400 5963 0 2815142 0 7287 12 9185995 5937 0 2747249 0 This seems excessive. What are the likely causes of this other than say = a bad cable or switch ? I believe the same thing was happening on our = other interface when we had this much traffic going into it, and its = plug into a different switch entirely. I suppose its possible both = cables are bad, but seems unlikely. Before enableing "polling" in the = kernel, I was seeing 90+% usage on interupts in top, which also seems = excessive given we are moving less than FE traffic.=20