> 
> I just hung my 1.2G box... by writing too quick to an NFS server.
> 
> Client is P166 running the recent 1.2G snapshot, with 3C509 nic.
> Server is i486/DX33 running a 1.2F kernel (Jun08) and a WD8003 8bit
> NIC.
> 

Mine did the same things, except the server is a P100 and the client is
a 386/40.  The error message and the network card are (oddly) precisely
the same.

> foo/* is a total of about 60K.  Only about 8k made it before I got:
> 
> Jul 12 22:49:40 zen /netbsd: ed0: warning - receiver ring buffer overrun
> Jul 12 22:49:40 zen /netbsd: ed0: warning - receiver ring buffer overrun
> Jul 12 22:50:20 zen last message repeated 3 times
> :
> :
> 
> on the server and the client locked up.  Or at least its filesystem
> did.  tcpdump shows the P166 responding to ping, and the xterms still
> respond to the X server, but I've only seen one nfs packet in several
> minutes and all shells are wedged.
> 

The system with the 8003 is wedged on my end.  Same symptoms as yours.

> I'll remount with write size set at 1k... after I reboot.
> 

Since I'm seeing exactly the same problem, but on the slow machine, I
doubt it is actually NFS.  My guess would be a recent change to the 8003
code, since that is actually the only thing the two set-ups seem to have
in common.

-- 
Dave Burgess                   Network Engineer - Nebraska On-Ramp, Inc.
*bsd FAQ Maintainer / SysAdmin for the NetBSD system in my spare bedroom
"Just because something is stupid doesn't mean there isn't someone that 
doesn't want to do it...."