my system includes AM1808+LAN8720A. (my system is linux 2.6.37, all code sources are from TI website.
when i test it with nfs, I found that:
1，u-boot startup, sometimes can not tftp uimage from server. at this time, I can not ping server.
when i test it with nfs, I found that:
1，u-boot startup, sometimes can not tftp uimage from server. at this time, I can not ping server.
and then normally u-boot can tftp after reset or power-off/power-on.
2，u-boot run well, and then tftp uimage, and then start linux kernel. at this time, sometimes, kernel can not connect nfs, sometimes can. the percantage is about 50% vs 50%. once failed, reset or power-off/power-on ARM system it can work well again. But sometimes, I need tried some times, kernel then can conncect nfs.
2，u-boot run well, and then tftp uimage, and then start linux kernel. at this time, sometimes, kernel can not connect nfs, sometimes can. the percantage is about 50% vs 50%. once failed, reset or power-off/power-on ARM system it can work well again. But sometimes, I need tried some times, kernel then can conncect nfs.
I don't think my nfs has issues, if it has, I think kernel can not connect nfs at all.
someone said it maybe is because of 8720's reset problem. I has monitored the rst pin of 8720 with oscilloscope, I can not find any difference between the failure and success of connection of nfs.
and I also think the hardware has no issues, for I test ping when I started my system when kernel connect nfs:
ping 192.168.xx.xx -s 65000
when ping about 500 times, these is no any loss, and the time of ping is similar.
please help on where the issues are, or how can i test it.
thanks!
*************************************
here is some of log information when kernel failed to connect nfs:
.....
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:53 UTC (946684853)
usb 2-1: new full speed USB device using ohci and address 2
usb 2-1: not running at top speed; connect to a high speed hub
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=0:00, id=7c0f1)
usb 2-1.1: new full speed USB device using ohci and address 3
IP-Config: Complete:
device=eth0, addr=192.168.20.213, mask=255.255.255.0, gw=192.168.20.254,
host=192.168.20.213, domain=, nis-domain=(none),
bootserver=192.168.20.222, rootserver=192.168.20.222, rootpath=
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:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c00349b4>] (dump_backtrace+0x0/0x110) from [<c0395c34>] (dump_stack+0x18/0x1c)
r6:00008000 r5:00000000 r4:c04dfab8 r3:c7828010
[<c0395c1c>] (dump_stack+0x0/0x1c) from [<c0395d10>] (panic+0x74/0x198)
[<c0395c9c>] (panic+0x0/0x198) from [<c0008ea0>] (mount_block_root+0x1c4/0x204)
r3:00000030 r2:00000000 r1:c7829f58 r0:c04492d5
r7:c0027e34
[<c0008cdc>] (mount_block_root+0x0/0x204) from [<c0009084>] (mount_root+0xac/0xd0)
r8:00000000 r7:00000013 r6:c00496c4 r5:c0027e49 r4:00200000
[<c0008fd8>] (mount_root+0x0/0xd0) from [<c0009218>] (prepare_namespace+0x170/0x1c4)
r4:c04df544
[<c00090a8>] (prepare_namespace+0x0/0x1c4) from [<c0008a94>] (kernel_init+0x114/0x14c)
r5:c0008980 r4:c04df4e0
[<c0008980>] (kernel_init+0x0/0x14c) from [<c00496c4>] (do_exit+0x0/0x6c4)
r4:00000000 r3:00000000