• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 474 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

NFS problem on OMAP 35x EVM board

Krupa
Prodigy 120 points

Hi,

         I am trying to boot the kernel image from NFS drive through tftpboot. I am facing the following issue...

Texas Instruments X-Loader 1.41
Starting OS Bootloader...


U-Boot 1.1.4 (Jun  5 2008 - 17:53:37)

OMAP3-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3EVM 1.0 Version + mPOP (Boot NAND)
DRAM:  128 MB
NAND:256 MiB

Reading data from 0x25f800 -- 100% complete.
In:    serial
Out:   serial
Err:   serial
Reseting CHIP... Done
LAN9x18 (0x01150002) detected.
Setting mac address: 00:50:c2:7e:8a:9d
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
Hit any key to stop autoboot:  0
OMAP3EVM # tftpboot 80000000 uImage
Reseting CHIP... Done
LAN9x18 (0x01150002) detected.
Setting mac address: 00:50:c2:7e:8a:9d
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
TFTP from server 10.203.92.11; our IP address is 10.203.92.40
Filename 'uImage'.
Load address: 0x80000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

very rarely it loads the images but it fails while booting the image as

........

IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.203.92.130
IP-Config: Complete:
      device=eth0, addr=10.203.92.130, mask=255.255.255.0, gw=10.203.92.1,
     host=10.203.92.130, domain=che.aricent.com, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=10.203.92.11, rootpath=
Looking up port of RPC 100003/2 on 10.203.92.11
rpcbind: server 10.203.92.11 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 10.203.92.11
rpcbind: server 10.203.92.11 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 10.203.92.11 not responding, timed out
Root-NFS: Server returned error -5 while mounting /opt/omap3evm_nfs/
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00        512 mtdblock0 (driver?)
1f01       1792 mtdblock1 (driver?)
1f02        256 mtdblock2 (driver?)
1f03       5120 mtdblock3 (driver?)
1f04     254464 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

 

Before booting the image, I do the following...

setenv serverip <NFS host ip>

setenv ipaddr < device ip>

setenv gatewayip

setenv bootargs console=ttyS0,115200n8 noinitrd ip=dhcp rw root=/dev/nfs nfsroot=10.203.92.11:/opt/omap3evm_nfs/,nolock,wsize=1024,rsize=1024

saveenv

 

The same setup was working fine soemtime back. My network is changed now and so I changed the serverip, gateway and ipaddr. After this, I am facing this issue.

Can anyone pls. help me in resolving this?

 

Thanks.

 

 

 

  • 0
    TI__Mastermind 37340 points

    When trouble shooting such issues, the first thing I normally do is

    1) ping host from target u-boot prompt; this ensures the physical cable connection and ip addresses are ok

    2) make sure tftp service is enabled in your host, make sure firewall is disabled on your host (common issue preventing TFTP) and make sure uImage file is in location specified

    This should be enough to get you pas TFTP, but if you want to continue and NFS mount file system, you should also

    3) make sure nfs mount directory in bootargs matches the one defined in you host's /etc/exports file.

  • 0 in reply to Juan Gonzales
    Prodigy 120 points

    HI,

          I checked all these....

    1. I tried pinging to the host and the host is alive.

    2. tftp service is runing on host and uImage is in the specified location.

    3. nfs mount directory is also mentioned in /etc/exports..

    The problem is , very rarely I can able to boot the image and work. After a while, when running the application on the  board I get a msg, Nfs server is not responding and the board hangs. Again I have to reboot  which is failing with above message.

     I mean once in 15 or 20 times, it is booting but hangs while running the app.

     

  • 0 in reply to Krupa
    TI__Mastermind 37340 points

    apologies, I did not realize it was working some of the time.  In this case, I would consider placing the EVM on its own isolated network using a router which you can buy of the shelf in an electronics store.  I suspect the issue may be due to network traffic, but the isolated network should also tell us if there is something wrong with the board or network configuration....

  • 0 in reply to Juan Gonzales
    Prodigy 120 points

    OK, let me try of this and get back.

    Thanks.

  • 0 in reply to Krupa
    Prodigy 120 points

         I tried connecting to a isolated network through a switch and now I dont see any problem while booting the image. thanks for ur suggestion.

    But while running the application, very rarely I see a msg NFS server is not responding and the board hangs.  what could be the problem?

  • 0 in reply to Krupa
    TI__Mastermind 37340 points

    mmm, not sure what to advice at this point.  I am not aware of any NFS issues with OMAP35x software; but then again, I have not played with their software much.  You can try using another switch or router to see if it makes any difference.  Otherwise, if you can give us a few more details; for example how often do you see this; SDK software version you are using... anything that can help us reproduce this on our side, that would be great.

  • 0 in reply to Juan Gonzales
    TI__Expert 5000 points

    If  you are using 1.0.2 SDK version, then there is a known issue with NFS , which is already release noted in section 3.10.2 of Release notes pdf that is present in the package.

    You need to issue the following command-

    echo 0 > /sys/power/cpu_deepest_idlestate as soon as the kernel boots up.

    If you are using OMAP35x GIT based releases of version less than 02.01.00.04, then you need to compile out the cpu idle option in menuconfig and try.

    Also it would be helpful to have rsize=4096,wsize=4096 proto=tcp as part of your bootargs. Try this as the last option after you have tried out other option listed above.

    Thanks,

    Prathap.

  • 0 in reply to Prathap Srinivas
    Prodigy 120 points

    Hi,

            I restarted the network and nfs service on my server and now I don't see this issue at all.

    Thanks all for the suggestion.