On Thu, 7 Sep 2000, Steven Grunza wrote:

> raidattach: Asked for 4 units
> Kernelized RAIDframe activated
> root device: hme1
> dump device: hme1
> file system (default generic): nfs
> root on hme1 dumps on hme1h
> nfs_boot: trying RARP (and RPC/bootparam)
> nd6_na_input: duplicate IP6 address fe80:0001::0240:dcff:fe3b:01da
> nfs_boot: client_addr=192.168.0.4 (RARP from 192.168.0.1)
> hme1: error interrupt, status=20101<GOTFRAME,SENTFRAME,NORXD>
> hme1: error interrupt, status=20101<GOTFRAME,SENTFRAME,NORXD>
> nfs_boot: timeout...
> hme1: error interrupt, status=20101<GOTFRAME,SENTFRAME,NORXD>
> nfs_boot: timeout...
> hme1: error interrupt, status=20101<GOTFRAME,SENTFRAME,NORXD>
> nfs_boot: timeout...
> hme1: error interrupt, status=20101<GOTFRAME,SENTFRAME,NORXD>
> nfs_boot: bootparam whoami, error=60
> cannot mount root, error = 60
> root device (default hme1): 
> 
> 
> tcpdump reports the following:
> 
> Sep  7 21:32:20 scrappy rarpd[199]: received packet on ep0
> 21:33:32.098484 vulcan Broadcast rarp 60: rarp who-is vulcan tell vulcan
> 21:33:32.102196 scrappy vulcan rarp 42: rarp reply vulcan at vulcan
> 21:33:32.591124 vulcan Broadcast rarp 60: rarp who-is vulcan tell vulcan
> 21:33:32.594654 scrappy vulcan rarp 42: rarp reply vulcan at vulcan
> 21:33:32.650847 vulcan Broadcast arp 60: arp who-has vulcan tell vulcan
> 21:33:35.652367 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:36.651109 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:38.651033 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:41.690920 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:45.730783 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:50.791544 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:33:55.851281 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96
> 21:34:00.911124 vulcan Broadcast ip 138: vulcan.1023 >
> 192.168.0.255.sunrpc: udp 96

This is a known, and as yet unresolved issue with SBus network
interfaces.  It will eventually be addressed, but at this time I cannot
estimate when that will be.

Eduardo Horvath