There were several people reporting this error back when I posted this a
week ago and my problems disappeared after a few days. I'm guessing
someone fixed things so I didn't bother to go searching through the CVS
logs to see what it was.

On Tue, 8 Oct 2002, Matthias Scheler wrote:

> In article <Pine.GSO.4.44.0210020830200.27604-100000@fls.i8u.org>,
> 	Hisashi T Fujinaka <htodd@twofifty.com> writes:
> > Under semi-heavy usage, the link lights stay on but I get the error
> > message:
> > Oct  1 21:31:27 allison /netbsd: fxp0: device timeout
>
> Mine work like a charm:
>
> Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls
> fxp0  1500  <DEFANGED_Link>        00:d0:b7:b9:48:d1  9335294     0  7564847     0     0
> [...]
> fxp1  1500  <DEFANGED_Link>        00:d0:b7:b9:48:d2 11757583     0 16428903     0 70347
> [...]
>
> There are many different versions of Intel's ethernet chip and they get
> combined with different PHYs. It's probably not a generic problem but
> related to your hardware.
>
> BTW: my card uses i82558 chips with Intel PHYs:
>
> fxp0 at pci2 dev 4 function 0: i82558 Ethernet, rev 5
> fxp0: interrupting at irq 12
> fxp0: Ethernet address 00:d0:b7:b9:48:d1
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0
> fxp1 at pci2 dev 5 function 0: i82558 Ethernet, rev 5
> fxp1: interrupting at irq 15
> fxp1: Ethernet address 00:d0:b7:b9:48:d2
> inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 0
>
> 	Kind regards
>
>

-- 
Hisashi T Fujinaka - htodd@twofifty.com
BSEE (6/86) + BSChem (3/95) + BAEnglish (8/95) + $2.50 = mocha latte