NFS issue with ETH0 on PowerQuicc MPC8248 Processor Board

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NFS issue with ETH0 on PowerQuicc MPC8248 Processor Board

1,025 Views
gsatish10
Contributor I

MPC8248 Processor related  board supports 10/100MB T Full duplex with kernel 3.10

ETH1 is working fine for Kernel 3.10 to mount NFS , with same configuration ETH0 is not working.

Data sheet is saying both ETH0 & ETH1supports 10/100MB .

But it is stopping with following messages on one of custom board using MPC8248 Processor

IP-Config: Complete:
     device=eth0, hwaddr=00:10:ec:00:5c:5b, ipaddr=10.162.103.194, mask=255.255.0.0, gw=10.162.0.1
     host=10.162.103.194, domain=mvista.com, nis-domain=(none)
     bootserver=0.0.0.0, rootserver=10.162.103.226, rootpath=
     nameserver0=10.162.0.5, nameserver1=10.0.0.5
VFS: Mounted root (nfs filesystem) on device 0:10.
devtmpfs: mounted
Freeing unused kernel memory: 156K (c03f2000 - c0419000)
nfs: server 10.162.103.226 not responding, still trying
nfs: server 10.162.103.226 not responding, still trying

"LXT971A Single-Port 10/100 Mbps PHY Transceiver " -- PHY Controller Name

It is hang here.

Please support me and thanks in advance

Regards
Satish.G

0 Kudos
5 Replies

766 Views
Pavel
NXP Employee
NXP Employee

Is there u-boot on your board?

Could you test your board using a standalone project?

Attached file contains simple standalone project for FCC1 and FCC2. It is CodeWarrior project for the MPC8272.


Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

766 Views
gsatish10
Contributor I

Hi Pavel,

Thank you for the reply.

I did not see attachment here, please send me the same.

Thanks & Regards
Satish.G

0 Kudos

766 Views
gsatish10
Contributor I

Hi Pavel,

Once I get into Shell Propmt  through Intial Ram disk Image.I can mount the file system through ETH0 ,

But when I am trying NFS mount, It is getting the Issue  as

NFS server xxxxxxx not responding, still trying 

NFS server xxxxxxx not responding, still trying

I saw issue is becuse of Port Mismatch and nolock option added to Mount command.  

 "mount -o port=2049,nolock  <host ip>:/<mnt file path form host>   /<mnt path in target> " 

using the above cmd, Mounting is done successfully with slight delay to mount, using ETH0.

But when I try yo add the same arguments  to kernel command line , it is showing same error.

I think this is related  to Rx Packet loss Issue too.

Once entered through Intial RAM DISK , assigned the IPs to two ETH ports  and getting the problem as RX Packet Loss with ETH0,

Added log below.

 

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:EC:00:5C:5B 
          inet addr:10.162.103.254  Bcast:10.162.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:461 errors:46 dropped:0 overruns:0 frame:46
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:59708 (58.3 KiB)  TX bytes:468 (468.0 B)

eth1      Link encap:Ethernet  HWaddr 00:10:EC:80:5C:5B 
          inet addr:10.162.103.253  Bcast:10.162.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:486 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:67854 (66.2 KiB)  TX bytes:468 (468.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:EC:00:5C:5B 
          inet addr:10.162.103.254  Bcast:10.162.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:468 errors:46 dropped:0 overruns:0 frame:46
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:60397 (58.9 KiB)  TX bytes:468 (468.0 B)

eth1      Link encap:Ethernet  HWaddr 00:10:EC:80:5C:5B 
          inet addr:10.162.103.253  Bcast:10.162.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:494 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:68607 (66.9 KiB)  TX bytes:468 (468.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

~ # ### Application running ...

The possible reason for packet failures are "Failure NIC Card, Failure Cables, Changing to Different Switch/router or Port Speed Mismatch from Host to Target"

I checked with different switch Box,Lan cables and used mii-tool to change the speed of the Host PC to match with the ETH0 speed with the following cmd sudo ethtool -s eth0 speed 10 duplex full,
getting same issue with ETH0.
Please provide me the suggestion, I am excepting Issue is with PHY Port  because same functionlity working fine with ETH1 Port  with same setup, same kernel.
Please provide your suggestion
Thanks & Regards
Satish.G
0 Kudos

766 Views
Pavel
NXP Employee
NXP Employee

Can you ping your nfs server (10.162.103.226) from your board.

Test your board if your board and your NFS server are located in the same NET. For example test your board using ipaddr=10.162.0.194, mask=255.255.255.0, gw=10.162.0.1 and rootserver=10.162.102.226.

 

Check setting for NFS on your host PC.


Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

766 Views
gsatish10
Contributor I

Hi Pavel,

Thank you for quick reply.

1) When I am booting into the Bash shell using ETH1 , I can ping NFS server and log is as below

root@freescale-82xx:~# ping 10.162.103.226
PING 10.162.103.226 (10.162.103.226) 56(84) bytes of data.
64 bytes from 10.162.103.226: icmp_req=1 ttl=64 time=1.04 ms
64 bytes from 10.162.103.226: icmp_req=2 ttl=64 time=0.467 ms
64 bytes from 10.162.103.226: icmp_req=3 ttl=64 time=0.491 ms
64 bytes from 10.162.103.226: icmp_req=4 ttl=64 time=0.509 ms
^V
64 bytes from 10.162.103.226: icmp_req=5 ttl=64 time=0.512 ms
64 bytes from 10.162.103.226: icmp_req=6 ttl=64 time=0.501 ms
64 bytes from 10.162.103.226: icmp_req=7 ttl=64 time=0.511 ms
^C
--- 10.162.103.226 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6006ms
rtt min/avg/max/mdev = 0.467/0.576/1.046/0.194 ms
root@freescale-82xx:~#

2)  Target Board and Host PC are in the same sub net because when I am checking the

ifconfig of Target Board , it is showing Ip address of ETH1 in the same sub net.

Log is as follows:

root@freescale-82xx:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:ec:00:5c:5b  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth1      Link encap:Ethernet  HWaddr 00:10:ec:80:5c:5b  
          inet addr:10.162.103.176  Bcast:10.162.255.255  Mask:255.255.0.0
          inet6 addr: fe80::210:ecff:fe80:5c5b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:112594 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40259 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:157060886 (149.7 MiB)  TX bytes:6576714 (6.2 MiB)

With same configuration from Host PC and Board , ETH0 is showing as not responding

I changed in //etc/network/interfaces as "inet eth0 manual"  but no use.

I had suspected the issue is with Network Congestion problem, so I had used local network from Host PC to

Target Board using Router , and I got the same Issue with ETH0.

Had Used the Static IP as "root=/dev/nfs ip=10.162.103.42:::255.255.0.0:::10.162.0.1::eth0 nfsroot=<rootpath> rw"

No luck.

Here are configs mentioned in menuconfig

CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFS_USE_LEGACY_DNS=y
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_FAULT_INJECTION=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y

Please suugest me the way that which way I should go ahead

Thanks & regards

Satish,.G

0 Kudos