Subject: Re: fxp issues
To: Daniel Carosone <dan@geek.com.au>
From: Sean Davis <dive@endersgame.net>
List: current-users
Date: 09/16/2004 05:28:01
--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 16, 2004 at 06:57:01PM +1000, Daniel Carosone wrote:
> On Tue, Jul 20, 2004 at 09:35:59AM -0400, Sean Davis wrote:
> > Hello, I have a machine here running 2.0G (the snapshot from the 17th,
> > from releng, with a custom kernel), and I'm having some problems with
> > the fxp driver.
> >=20
> > Every <regular interval> (not sure what the interval is, but it is
> > regular), my fxp NIC drops right off the network, then comes back a
> > few seconds later, without any errors or printing anything to dmesg,
> > even with debug turned on in ifconfig. It's an onboard card, so I
> > can't just swap it out (nor can I disable it, unless there is a BIOS
> > option I missed...)
>=20
> "me too"
>=20
> FWIW, also an on-board NIC on a Compaq desktop.  I have other
> machines, with other revs of fxp in, that are working fine; this is
> the problem one:
>=20
> fxp0 at pci0 dev 10 function 0: i82558 Ethernet, rev 5
> fxp0: interrupting at irq 11
> fxp0: Enabling receiver lock-up workaround
> fxp0: Ethernet address 00:50:8b:4d:c6:bb
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0

Same one I have here:
fxp0 at pci0 dev 9 function 0: i82558 Ethernet, rev 5
fxp0: interrupting at irq 10
fxp0: Enabling receiver lock-up workaround
fxp0: Ethernet address 00:50:ba:00:00:33
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0


fxp0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:50:ba:00:00:33
        media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpau=
se,txpause)
        status: active
        input: 62347 packets, 6774375 bytes, 7148 multicasts
        output: 76794 packets, 12001931 bytes
        inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255

My revision of if_fxp_pci.c is newer than yours, but still has the
problem...

     $NetBSD: i82557.c,v 1.86 2004/05/16 02:59:04 thorpej Exp $
     $NetBSD: if_fxp_pci.c,v 1.39 2004/08/21 23:48:33 thorpej Exp $

I have no idea what to do about it though... I just leave a ping 192.168.1.3
running on my nat machine, as (regular enough, ie every second) activity on=
 the
interface keeps it from dropping off.
-Sean

--
/~\ The ASCII
\ / Ribbon Campaign                   Sean Davis
 X  Against HTML                       aka dive
/ \ Email!

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFBSVyhncZv+931Zb8RAsvSAKCNC2a4Gt+WfnmhG/95JzCH4YxVcwCdH9J1
v2YGNVinhphXxXD065fyRwM=
=X/Yv
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--