Well, that's odd. I wonder if we have to figure out which cards are having
troubles and which cards aren't. Mine's PCI (and there were several
versions of Intel I-forget-the-designation-100 cards in the short time I
worked there), Atstushi's is on-board, and yours is PCMCIA/Cardbus, I'm
guessing.

On Wed, 2 Oct 2002, Steven M. Bellovin wrote:

> In message <Pine.NEB.4.33.0210021932560.11298-100000@jonagold.astrakan.hig.se>,
>  Petter Lindquist writes:
> >On Thu, 3 Oct 2002, Charlie Allom wrote:
> >
> >> On Wed, Oct 02, 2002 at 08:33:19AM -0700, Hisashi T Fujinaka wrote:
> >> > 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
> >> >
> >> > I'm not doing anything new. I was downloading the current RH8.0 iso.
> >>
> >> Weird - I saw this for the first time a few days back.
> >
> >I just upgraded my fxp box to 1.6 today. When booting the 1.6 CD the
> >kernel fiddled some with the eeprom on my fxp, and it told me I couldn't
> >use the device until my machine was restarted.
> >
>
> I've had no fxp0 problems, either with my laptop (a Thinkpad T21) or a
> generic i386 desktop with an Intel card.  Both are running 1.6.  I just
> sent the laptop a gigabyte of data using ttcp (from another machine with
> an ex0 interface); it accepted it at about 50 Mbps.
>
>
> 		--Steve Bellovin, http://www.research.att.com/~smb (me)
> 		http://www.wilyhacker.com ("Firewalls" book)
>
>
>

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