From owner-freebsd-current@FreeBSD.ORG Fri Sep 26 09:55:46 2003 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 4F36416A4B3 for ; Fri, 26 Sep 2003 09:55:46 -0700 (PDT) Received: from mx1.freebsdsystems.com (mx1.FreeBSDsystems.COM [216.138.197.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39CF343FE9 for ; Fri, 26 Sep 2003 09:55:43 -0700 (PDT) (envelope-from lnb@FreeBSDsystems.COM) Received: (qmail 39480 invoked by uid 0); 26 Sep 2003 16:55:28 -0000 Received: from gw.tor.freebsdsystems.com (HELO noemie) (216.138.230.94) by mx1.freebsdsystems.com with SMTP; 26 Sep 2003 16:55:28 -0000 Message-ID: <000c01c3844f$5e03dc60$0200a8c0@noemie> From: "Lanny Baron" To: "Glenn Johnson" , References: <20030926164008.GA31413@node1.cluster.srrc.usda.gov> Date: Fri, 26 Sep 2003 12:58:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: Something is wrong with the fxp network driver 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, 26 Sep 2003 16:55:46 -0000 Hi Glenn, We have several FreeBSD boxes here. Some run -current and some run -5.1-P4 and all have fxp* and em* You must have something else going wrong that is causing you the grief. fxp0: flags=8843 mtu 1500 options=3 inet6 fe80::202:b3ff:fe96:c64b%fxp0 prefixlen 64 scopeid 0x1 ether 00:02:b3:96:c6:4b media: Ethernet autoselect (10baseT/UTP) status: active The above is on: gw-tor# uname -a FreeBSD gw-tor.FreeBSDsystems.COM 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Sep 24 11:07:47 EDT 2003 root@gw-tor.FreeBSDsystems.COM:/usr/src/sys/i386/compile/GW-TOR i386 Because of our network setup, fxp0 does not have any ip address bound to it. Check your logs, like I said, something else is causing the problem. Lanny =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Lanny Baron Proud to be 100% FreeBSD http://www.FreeBSDsystems.COM Toll Free: 1.877.963.1900 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= ----- Original Message ----- From: "Glenn Johnson" To: Sent: Friday, September 26, 2003 12:40 PM Subject: Something is wrong with the fxp network driver > I am having a problem with recent builds of -current with the fxp > driver. A couple of days ago, the 6 machines in my cluster with fxp > interfaces all died at about the same time with fxp timeout errors. The > machines with 3Com xl interfaces kept on going. Today, I am observing > that the throughput is about half of what I am seeing on my machines > with a 3Com xl interface. Is anybody else observing this? What other > information do I need to provide? > > Thanks. > > -- > Glenn Johnson > USDA, ARS, SRRC Phone: (504) 286-4252 > New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >