From owner-freebsd-net@FreeBSD.ORG Thu Jun 26 23:40:26 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 B07CE37B401; Thu, 26 Jun 2003 23:40:26 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA71E43FBD; Thu, 26 Jun 2003 23:40:25 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 8F05666BE5; Thu, 26 Jun 2003 23:40:25 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 3436FB97; Thu, 26 Jun 2003 23:40:24 -0700 (PDT) Date: Thu, 26 Jun 2003 23:40:24 -0700 From: Kris Kennaway To: Ying-Chieh Liao Message-ID: <20030627064024.GA25042@rot13.obsecurity.org> References: <20030627052728.GA1015@terry.dragon2.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: <20030627052728.GA1015@terry.dragon2.net> User-Agent: Mutt/1.4.1i cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: something wrong with fxp driver ? 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: Fri, 27 Jun 2003 06:40:27 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 01:27:28PM +0800, Ying-Chieh Liao wrote: > my previous kernel is about May 10, and the fxp works fine for me > but I cvsuped and make world/kernel yesterday (6/26), and then terrible t= hing > happens... the connection becomes v...e...r...y... s...l...o...w... > my ping time to the gateway is about 8000ms (but sometimes 20ms) >=20 > I've browse the mail archive of -current and -net, and I've noticed some > similar problems with fxp (device timeout), and I also get this message > (fxp0 device timeout) in my dmesg output, but I cant find out any solutio= n :< > Is there any workaround, or patches ? Check that it's negotiating the media type and options correctly. On the gohan machines it has been failing to negotiate full-duplex mode for the past few months, leading to LAN transfer speeds on the order of 20kps unless I set the media options explicitly. Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+++bYWry0BWjoQKURAsGeAJ9wUCeiFBP1OHlonz+ymSnb3e/HSwCdETy/ VOo0IkxwpWt/E9EEc07EKMg= =Q2h8 -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS--