OMAP3530 target board panic after booting... NFS issues

Assuming that all network connection is good, that error is usually the NFS server/firewall is not configured properly or the NFS client has come up faster than the Linux network driver.

There is very little information in the original post. Many issues - in isolation / combination - can lead to these errors. I suggest a quick search on this forum for the NFS.

The search yields many posts with similar problem - and suggested steps / solutions.

I tried to search for similar nfs related posts. I looked into some of them but did not help. I am adding some more additional info regarding the issue:

1) My bootargs for the target:

***************************************

OMAP3_EVM # printenv
baudrate=115200
netmask=255.255.254.0
get_kernel=run nand_kernel
get_initrd=run nand_initrd
nand_kernel=nand read.i 0x80000000 280000 220000
nand_initrd=nand read.i 0x81600000 780000 1000000
tftp_kernel=tftpboot 0x80000000 uImage
tftp_initrd=tftpboot 0x81600000 ramdisk.gz
bootargs_rd=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960
bootargs_fs=mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y
bootargs_nfs=mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=/mnt/nfs,nolock
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:on
boot_rd=run get_kernel; run get_initrd; setenv bootargs $(bootargs_rd); run addip; bootm 0x80000000
boot_fs=run get_kernel; setenv bootargs $(bootargs_fs); bootm 0x80000000
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; bootm 0x80000000
bootdelay=6
ethaddr=00:50:C2:7E:96:F6
nfshost=192.168.1.10
rootpath=/home/batwings/targetfs/home/root/omap3530
bootfile=uImage
nfsroot=192.168.1.10:/home/batwings/targetfs
ip=192.168.1.11
serverip=192.168.1.10
ipaddr=192.168.1.10
bootcmd=setenv ipaddr 192.168.1.11; setenv serverip 192.168.1.10;tftpboot;bootm
bootargs=console=ttyS0,115200n8 rw mem=99M@0x80000000 mpurate=720 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M root=/dev/nfs nfsroot=192.168.1.10:/home/batwings/targetfs
stdin=serial
stdout=serial
stderr=serial

Environment size: 1534/131068 bytes
OMAP3_EVM #

***************************************

2) I remounted nfs

***************************************

sudo mount -t nfs -o nolock 192.168.1.10:/home/batwings/targetfs /mnt

I verified that /mnt is mapped properly after the above command

***************************************

3) Output of rpcinfo -p on Ubuntu host

******************************************************************

program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  46981  status
    100024    1   tcp  54416  status
    100021    1   udp  49788  nlockmgr
    100021    3   udp  49788  nlockmgr
    100021    4   udp  49788  nlockmgr
    100021    1   tcp  39038  nlockmgr
    100021    3   tcp  39038  nlockmgr
    100021    4   tcp  39038  nlockmgr
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp  45599  mountd
    100005    1   tcp  37191  mountd
    100005    2   udp  45599  mountd
    100005    2   tcp  37191  mountd
    100005    3   udp  45599  mountd
    100005    3   tcp  37191  mountd

******************************************************************

4) Pings from the host:

- Target is pingable from host from the start of the boot process

- Pings stop during the middle of kernel boot up procedure.. eventually I start seeing these errors

- "Looking up port of RPC 100003/2 on 192.168.1.10"... "rpcbind: server 192.168.1.10 not responding, timed out"....."Root-NFS: Unable to get nfsd port number from server, using default"

- Pings stop during the middle of booting the kernel.

Thanks all for your responses.

Pinging the target works when there is something running on the target to reply. You might be getting responses from u-boot but not the kernel. Usually better to ping the host from the target.

The kernel is not being setup with an ip option as part of its bootargs. Are the setting up the IP in another way? In the bootlog do you see "Link Up" before the NFS messages?

Thanks Norman. I did modify the bootargs by setting the ip. But the problem is trying to do "DHCP" now.  Exact same issue was addressed @http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/50995.aspx

The solution proposes to use a router (which provides DHCP to both host and target). Is this the only way to get this working?

*******************************************

net eth0: SMSC911x/921x identified at 0xc6860000, IRQ: 336
Sending DHCP and RARP requests ...... timed out!
IP-Config: Retrying forever (NFS root)...

*******************************************

You should be able to use a static address. I noticed you have a U-boot addip vairable for that. I don't know quite how use the U-boot shell so I'll hard-code an example:

bootargs=console=ttyS0,115200n8 rw mem=99M@0x80000000 mpurate=720 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M root=/dev/nfs nfsroot=192.168.1.10:/home/batwings/targetfs ip=192.168.1.11:192.168.1.10:192.168.1.1:255.255.255.0:your_target_name:eth0:off

Assumes 192.168.1.11 for your target, 192.168.1.1 for your gateway and 255.255.255.0 for your netmask.

Thank you very much Norman. That worked for me.