LinuxPPC Embedded: root nfs boot problems.

I am trying to boot embedded-2.2.5 kernel using a nfsr root filesystem. Here is a log of the console session. I get a "neighbour table overflow" error. What does this mean ? I have a look in the source but can't figure out what is happening.

Thanks,
Brendan Simon.

loaded at:     FF801000 FF813BAC
relocated to:  00100000 00112BAC
board data at: 001001F8 00100214
relocated to:  00200100 0020011C
zimage at:     FF808000 FF8690B9
avail ram:     00201000 00400000

Linux/PPC load: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160 nfsroot=203.21.127.160:/sys/ads-root
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.2.5 (root@k9) (gcc version egcs-2.91.66 19990314 (egcs-1.1.2 rel
ease)) #39 Fri Nov 12 17:49:11 EST 1999
Boot arguments: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160 nfsroot=203
.21.127.160:/sys/ads-root
time_init: decrementer frequency = 93750000/60
Calibrating delay loop... 24.52 BogoMIPS
Memory: 15188k available (700k kernel code, 464k data, 32k init) [c0000000,c1000
000]
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
CPM UART driver version 0.02
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0100 is a SCC
ttyS02 at 0x0200 is a SCC
pty: 256 Unix98 ptys configured
RAM disk driver initialized: 16 RAM disks of 4096K size
eth0: CPM ENET Version 0.2, 00:d0:1f:11:22:33
IP-Config: Guessing netmask 255.255.255.0
neighbour table overflow
neighbour table overflow
neighbour table overflow
neighbour table overflow
portmap: server 203.21.127.160 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default Looking up port of RPC 100005/1 on 203.21.127.160 neighbour table overflow
neighbour table overflow
neighbour table overflow
neighbour table overflow
portmap: server 203.21.127.160 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default neighbour table overflow
neighbour table overflow
neighbour table overflow
neighbour table overflow
mount: server 203.21.127.160 not responding, timed out
Root-NFS: Server returned error -5 while mounting /sys/ads-root
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device 02:00

Kernel panic: VFS: Unable to mount root fs on 02:00

Rebooting in 180 seconds..<0>Kernel panic: Kernel Mode Software FPU Emulation
Rebooting in 180 seconds..Machine check in kernel mode. Caused by (from msr): regs c0f4bb30 Machine check signal - probably due to mm fa
ult

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

I executed "mount -t nfs 203.21.127.160:/sys/ads-root /mnt/test" from another linux box and this worked fine. I could view and edit the files. So I think it is a mpc860 kernel problem. I did have the nfs-root working sometime ago though it would just hang when trying to open the console. The terminal output said that the nfs root was successfully mounted. There is probably something that I have left out of the kernel coniguration but I'm not sure what. I have another look.

Brendan Simon.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Please help me.

[used source]
mpc8xx-2.2.13
I am trying to boot by NFS.

[NFS Server]
Linux 2.2.5-15 for i686 by Redhat ver 6.0 IP=192.168.0.254
defines client's name, MAC, IP, ... in /etc/bootbtab

[status]
I met following console messages,

*************************************************
...
eth0: CPM ENET Version 0.2, 00:00:85:30:30:31
Sending BOOTP and RARP requests.... OK
IP-Config: Got BOOTP answer from 192.168.0.254,

       my address is 192.168.0.100

Looking up port of RPC 100003/2 on 192.168.0.254 Looking up port of RPC 100005/1 on 192.168.0.254
VFS: Mounted root (NFS filesystem) readonly. Freeing unused kernel memory: 40k init
nfs: server 192.168.0.254 not responding, still trying
nfs: server 192.168.0.254 OK
nfs: server 192.168.0.254 not responding, still trying
nfs: task 20 can't get a request slot
nfs: server 192.168.0.254 OK
neighbour table overflow
...
*************************************************

[NFS servers's /var/log/messages says]
bootpd[880]: version 2.4.3
mountd[520]: authenticated mount request from mpc860ads:800

<<Question>>
What is wrong with my setting?
--
[email protected]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

May I ask you some basic question(s)
booting MOTOROLA's FADS board by NFS
related to my last posting

http://lists.linuxppc.org/listarcs/linuxppc-embedded/200001/msg00086.html

<Question>
Q.1
At first, mbxroot.min.tgz can be used for FADS ?

Q.2
Why these messages is out?
(1)repeat of "NFS not responding" and "OK"
(2)"error in loading shared libraries" and
"libc.so.6: Out of memory"

[source]
mpc8xx-2.2.13

[NFS Server]
Linux 2.2.5-15 for i686 by Redhat ver 6.0 IP=192.168.0.254
defines client's name, MAC, IP, ... in /etc/bootbtab

Files in Root_Path are from mbxroot.min.tgz. Those are sh and ls in /bin, /dev , ld.so.1, libc-1.99.so, libc.so.6 -> libc-1.99.so, libtermcap.so.2 -> libtermcap.so.2.0.8, libtermcap.so.2.0.8 in /lib.

[console]
When booting, cosole messages are:

..........................
eth0: CPM ENET Version 0.2, 00:00:85:30:30:31
Sending BOOTP and RARP requests.... OK
IP-Config: Got BOOTP answer from 192.168.0.254,

       my address is 192.168.0.100
  Looking up port of RPC 100003/2 on 192.168.0.254
  Looking up port of RPC 100005/1 on 192.168.0.254
  VFS: Mounted root (NFS filesystem) readonly.
  Freeing unused kernel memory: 40k init
  nfs: server 192.168.0.254 not responding, still trying
  nfs: server 192.168.0.254 OK
       ...... (*)

nfs: server 192.168.0.254 not responding, still trying
nfs: server 192.168.0.254 OK
init: error in loading shared libraries libc.so.6: failed to map segment from shared object:
Out of memory

*: repeats about 20 times.
I tryed some times. About 20 is average value.
Meanwhile there are many transmissions

      FADS's udp-port 800 ------> NFS server's udp-port 2049
                                    128 bytes
      FADS's udp-port 800 <------ NFS server's udp-port 2049
                                    1132 bytes

I don't know NFS protocol in detail.
So I can't understand meaning of datagram.
--
[email protected]

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/