[ On Wednesday, November 5, 2003 at 22:50:39 (+0000), George Peter Staplin wrote: ]
> Subject: Re: fxp bug triggering hung vnlock()'ed NFS client
>
> I have no problems with my card and the fxp driver in NetBSD 1.6.1
> (with cvs stable updates).  I grepped through my logs just to be sure and
> found nothing.
> 
> I'm running:
> fxp0 at pci2 dev 9 function 0: i82559 Ethernet, rev 8
> fxp0: interrupting at irq 11
> fxp0: Ethernet address 00:02:b3:99:69:b2
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

Hmm.... we both have a "rev 8" chip (and we also both have the same PHY
chip too it seems).

I did some testing on the PCI add-on fxp on the same server today
(without changing cables or anthing else -- just moving the one cable
over from the motherboard to the add-on card) and it seems quite
stable:

	fxp1 at pci0 dev 7 function 0: i82550 Ethernet, rev 12
	fxp1: interrupting at irq 9
	fxp1: Ethernet address 00:02:b3:28:1e:ac
	inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
	inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

I'll have to try testing both my NICs at 100baseTX-FDX, but at this
point I'm at a loss as to why problems would "suddenly" appear on a
system where the only thing that's changed is the revision of the driver
code.

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>