> OK at this point I have gotten the machine to swallow both nfsnetbsd 
> and smallnet.ecoff-
>
> There are hundreds of lines of:
> ?IO: LANCE  ste 0xa6b3 - - - - - - - - - - - - - - - - - - - - - - - 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> ?IO: LANCE  ste 0xa6b3 
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> ?IO: LANCE  ste 0xa6b3 | | | | | | | | | | | | | | | | | | | | | | | 
> | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 
> | | | | | | | |
> ?IO: LANCE  ste 0xa6b3 
> //////////////////////////////////////////////////////////////////
> ?IO: LANCE  ste 0xa6b3  - - - - - - - - - - - - - - - - - - - - - - - 
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

LANCE status register complains there were network transaction error
which should not have happen in correctly configured Ethernet network.

> Repeated many times. I am supposing that it's waiting for the NFS 
> stuff that I have not had time to look at. I put it off when I saw 
> that I did not understand Linux's new NFS implementation without some 
> research.

The messages are generated by LANCE network driver built in DECstation
PROM monitor.  At this point NetBSD kernel is not active yet, so Linux
NFS server implementation is not related with this errorous behavior.

Tohru Nishimura