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.

omap3evm: after upgrading to psp03.00.00.04, nfs mount has problems

Hello,

Up until now, i was working with linux psp 0.9.7, and nfs worked like a charm (boot is from SD ramdisk).

Recently I have upgraded the software on my mistral EVM to psp03.00.00.04 (kernel 2.6.32).

I used to following command to mount NFS (same as 0.9.7):

mount -t nfs -o nolock server_ip:/nfs_dir /mnt/nfs_dir

the mount worked. I was able to go to the directory, run ls and get the result.

When I tried to copy a file from the nfs server, a 16384byte file was created at the target(my EVM), and the following message was presented after a few seconds:

nfs: server server_ip not responding, still trying

I used wireshark, and saw that the server was sending packets.

I even returned to the 0.9.7 psp, and the NFS worked again.

I switched again to 3.0.0.4, but this time i used TCP:

mount -t nfs -o nolock,proto=tcp server_ip:/nfs_dir /mnt/nfs_dir

now everything is working, and i'm able to copy files from the nfs server.

Does anyone have any idea why it doesn't work over UDP using kernel 2.6.32?

Thanks,

Jose.

  • Can you share the Mistral EVM version? I suspect it is rev C or older.

    Are you using any Power Management features in the kernel?

    I have not tried explicitly choosing the UDP; will try and report my observations... after I return to work on WED.

    Since v0.9.7 which was based on 2.6.22 (and custom Linux patches), there have been many changes in the PSP Linux releases. These releases are more closer to the community linux.

     

  • hi Sanjeev,

    I'm using Rev D, so it is supported by this psp (although never tested, as writen in the user manual..)

    Don't know about PM, but i have removed the "sys/power" lines from the rcS file (should be removed after 2.6.29)

    UDP is the default NFS protocol (not all servers support UDP..)

    I know there were a lot of changes, I have seen some myself.. (for example, the MAC address defined in U-boot is no longer passed to the kernel..)

     

    Jose

  • To turn off power management you need to recompile the kernel after disabling CONFIG_PM and CONFIG_CPU_IDLE from the kernel configuration.

    It is required only to narrow the problem context.

  • I can't see any connection between my problem and PM..

    anyway, I checked and CONFIG_CPU_IDLE is disabled. CONFIG_PM is enabled.

  • ...just in case the wait for UDP packets is more and the kernel enters deep idle state - and the packets might be getting lost - leading to the errors you are noticing.