Date: Thu, 26 Jun 2003 23:40:24 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Ying-Chieh Liao <ijliao@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: something wrong with fxp driver ? Message-ID: <20030627064024.GA25042@rot13.obsecurity.org> In-Reply-To: <20030627052728.GA1015@terry.dragon2.net> References: <20030627052728.GA1015@terry.dragon2.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030627064024.GA25042>