Re: Something is wrong with the fxp network driver

From: Lanny Baron <lnb_at_FreeBSDsystems.COM>
Date: Fri, 26 Sep 2003 12:58:10 -0400
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.
        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_at_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 Baron
Proud to be 100% FreeBSD
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:
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to ""
Received on Fri Sep 26 2003 - 07:55:46 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:23 UTC