The 10G network can send data but cannot receive data

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

The 10G network can send data but cannot receive data

Jump to solution
1,394 Views
muaxi8
Contributor V

The network can send data but cannot receive data.

we used the marvell 88x3310 phy device. I have checked the PHY checklist and there is no problem. The PHY drivers have been loaded successfully.

Usxgmii is used for THE PHY and DPMAC14, and 10GBase-T mode is used for the outside of the PHY.Currently, ping the target device under the kernel, the target device can receive data, and also responded, but our LX2160 can not receive data

Can you give me some debugging advice?

root@localhost:~# ls-listni
dprc.1/dpni.2 (interface: eth0, end point: dpmac.17)
dprc.1/dpni.1 (interface: eth1, end point: dpmac.14)
dprc.1/dpni.0 (interface: eth2, end point: dpmac.13)

root@localhost:~# ifconfig eth1
eth1: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500
inet 10.0.1.111 netmask 255.0.0.0 broadcast 10.255.255.255
inet6 fe80::94ae:91ff:fea5:9ce prefixlen 64 scopeid 0x20<link>
ether 96:ae:91:a5:09:ce txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21 bytes 1314 (1.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@localhost:~#
root@localhost:~# ethtool eth1
Settings for eth1:
Supported ports: [ ]
Supported link modes: 10baseT/Full
100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Full
100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Link detected: no

root@localhost:~#

 

0 Kudos
1 Solution
1,348 Views
muaxi8
Contributor V

the problem is resolved.it is a hardware problem

View solution in original post

0 Kudos
5 Replies
1,373 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please run icmp ping for a while and then stop it.

Then share us the output of following commands -

 

restool dpmac info dpmac.14

 

restool dpni info dpni.1

 

Also give us the full boot logs, right from u-boot to linux shell

0 Kudos
1,371 Views
muaxi8
Contributor V

thanks ur reply.

The log file is attached 。i can not see any problem form follow information.

root@localhost:~# ls-listni
dprc.1/dpni.2 (interface: eth0, end point: dpmac.17)
dprc.1/dpni.1 (interface: eth1, end point: dpmac.14)
dprc.1/dpni.0 (interface: eth2, end point: dpmac.13)
root@localhost:~#
root@localhost:~# ifconfig eth1 10.0.1.111
root@localhost:~#
root@localhost:~# ping 10.0.1.222
PING 10.0.1.222 (10.0.1.222) 56(84) bytes of data.
From 10.0.1.111 icmp_seq=1 Destination Host Unreachable
From 10.0.1.111 icmp_seq=2 Destination Host Unreachable
From 10.0.1.111 icmp_seq=3 Destination Host Unreachable
From 10.0.1.111 icmp_seq=4 Destination Host Unreachable
From 10.0.1.111 icmp_seq=5 Destination Host Unreachable
From 10.0.1.111 icmp_seq=6 Destination Host Unreachable
From 10.0.1.111 icmp_seq=7 Destination Host Unreachable
From 10.0.1.111 icmp_seq=8 Destination Host Unreachable
From 10.0.1.111 icmp_seq=9 Destination Host Unreachable
^C
--- 10.0.1.222 ping statistics ---
10 packets transmitted, 0 received, +9 errors, 100% packet loss, time 9204ms
pipe 4
root@localhost:~#
root@localhost:~#
root@localhost:~#
root@localhost:~# restool dpmac info dpmac.14
dpmac version: 4.7
dpmac object id/portal id: 14
plugged state: plugged
endpoint state: 1
endpoint: dpni.1, link is up
DPMAC link type: DPMAC_LINK_TYPE_PHY
DPMAC ethernet interface: DPMAC_ETH_IF_USXGMII
MAC address: 36:ab:e6:e4:da:4d
maximum supported rate 10000 Mbps
Counters:
rx all frames: 0
rx frames ok: 0
rx frame errors: 0
rx frame discards: 0
rx u-cast: 0
rx b-cast: 0
rx m-cast: 0
rx 64 bytes: 0
rx 65-127 bytes: 0
rx 128-255 bytes: 0
rx 256-511 bytes: 0
rx 512-1023 bytes: 0
rx 1024-1518 bytes: 0
rx 1519-max bytes: 0
rx frags: 0
rx jabber: 0
rx align errors: 0
rx oversized: 0
rx pause: 0
rx bytes: 0
tx frames ok: 22
tx u-cast: 0
tx m-cast: 10
tx b-cast: 12
tx frame errors: 0
tx undersized: 0
tx b-pause: 0
tx bytes: 1604
root@localhost:~#
root@localhost:~#
root@localhost:~# restool dpni info dpni.1
dpni version: 7.16
dpni id: 1
plugged state: plugged
endpoint state: 1
endpoint: dpmac.14, link is up
link status: 1 - up
mac address: 36:ab:e6:e4:da:4d
dpni_attr.options value is: 0
num_queues: 16
num_cgs: 1
num_rx_tcs: 1
num_tx_tcs: 1
mac_entries: 16
vlan_entries: 0
qos_entries: 0
fs_entries: 64
qos_key_size: 0
fs_key_size: 56
ingress_all_frames: 0
ingress_all_bytes: 0
ingress_multicast_frames: 0
ingress_multicast_bytes: 0
ingress_broadcast_frames: 0
ingress_broadcast_bytes: 0
egress_all_frames: 22
egress_all_bytes: 1300
egress_multicast_frames: 10
egress_multicast_bytes: 796
egress_broadcast_frames: 12
egress_broadcast_bytes: 504
ingress_filtered_frames: 0
ingress_discarded_frames: 0
ingress_nobuffer_discards: 0
egress_discarded_frames: 0
egress_confirmed_frames: 22
root@localhost:~#

0 Kudos
1,354 Views
yipingwang
NXP TechSupport
NXP TechSupport

Are you using generic PHY driver or specific PHY driver say - drivers/net/phy/marvell10g.c ?

In case you are using specific PHY driver, then Can you use generic driver once and see if your problem still persists.

0 Kudos
1,349 Views
muaxi8
Contributor V

the problem is resolved.it is a hardware problem

0 Kudos
1,350 Views
muaxi8
Contributor V

generic PHY driver and specific PHY driver ---- drivers/net/phy/marvell10g.c 

I've tested them all, are the same prolem. 

0 Kudos