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.

AM3352: LAN Smartbit issue

Part Number: AM3352

Hi 

Now we want to upgrade the system to SDK 05.03.00.07.

When we tested Lan Smartbit, the first data loss occurs probabilistically when the packet size is switched.

But the same board, using SDK 03.01.00.06 is normal.

  • Hi 

    The PHY chip we use is RTL8211F.

    The configuration of PHY chip in two versions of SDK is the same. So we wonder if the issue of the network driver causes this problem.

    Do you have any suggestions?

  • Hi,

    Based on your question please provide more detail on the following:

    - Which port is being tested? I am assuming the CPSW port since the screen shot shows GIG FULL but I want to confirm that.

    - What is meant by packet size switch? What are the sizes that the stream is changing from?

    - Could a description be provided of the columns in the screen capture? 

    - The type of network traffic being simulated with the tester?

    - Please attach the results of  ifconfig -a 

    - Please attach the results of ethtool -S <port in use, ex. eth0>

    Best Regards,

    Schuyler

  • Hi Schuyler:

    - Which port is being tested? I am assuming the CPSW port since the screen shot shows GIG FULL but I want to confirm that.

    The configuration of network and EVMSK is consistent. We also use two ports. The test results of the two ports are the same.

    - What is meant by packet size switch? What are the sizes that the stream is changing from?

    The network interface is connected with the test instrument. Then test instrument will automatically switch the size of the sending data packet.

    - Could a description be provided of the columns in the screen capture? 

    ETH0_RTL8211_1.0_RJ451000M_3m_EmbeddedLinux64bit_2B2_F_Packetloss.csvETH0_RTL8211_1.0_RJ451000M_3m_EmbeddedLinux64bit_2B2_P_Packetloss.csv

    - The type of network traffic being simulated with the tester?

    Yes

    - Please attach the results of  ifconfig -a 

    dummy0 Link encap:Ethernet HWaddr 62:F5:C3:1B:8D:85
    BROADCAST NOARP 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)

    eth0 Link encap:Ethernet HWaddr C4:00:AD:38:3E:BF
    inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::c600:adff:fe38:3ebf%775872/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:25377737 errors:0 dropped:0 overruns:0 frame:0
    TX packets:23475862 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1730137230 (1.6 GiB) TX bytes:134262976 (128.0 MiB)
    Interrupt:47

    eth1 Link encap:Ethernet HWaddr C4:00:AD:38:3E:C0
    inet addr:192.168.2.200 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::c600:adff:fe38:3ec0%775872/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2808 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:185137 (180.7 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1%775872/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:3286 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3286 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:667552 (651.9 KiB) TX bytes:667552 (651.9 KiB)

    mlan0 Link encap:Ethernet HWaddr A8:1D:16:3C:3B:4B
    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)

    sit0 Link encap:IPv6-in-IPv4
    NOARP MTU:1480 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)

    uap0 Link encap:Ethernet HWaddr A8:1D:16:3C:3C:4B
    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)

    wfd0 Link encap:Ethernet HWaddr AA:1D:16:3C:3B:4B
    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)

    - Please attach the results of ethtool -S <port in use, ex. eth0>

    # ethtool -S eth0
    NIC statistics:
    Good Rx Frames: 196764852
    Broadcast Rx Frames: 2
    Multicast Rx Frames: 0
    Pause Rx Frames: 0
    Rx CRC Errors: 41
    Rx Align/Code Errors: 0
    Oversize Rx Frames: 30
    Rx Jabbers: 0
    Undersize (Short) Rx Frames: 750
    Rx Fragments: 260687
    Rx Octets: 3636958610
    Good Tx Frames: 23478174
    Broadcast Tx Frames: 2953
    Multicast Tx Frames: 471
    Pause Tx Frames: 0
    Deferred Tx Frames: 206773
    Collisions: 265290
    Single Collision Tx Frames: 99640
    Multiple Collision Tx Frames: 69090
    Excessive Collisions: 487
    Late Collisions: 0
    Tx Underrun: 0
    Carrier Sense Errors: 2
    Tx Octets: 227622891
    Rx + Tx 64 Octet Frames: 81893348
    Rx + Tx 65-127 Octet Frames: 3081217
    Rx + Tx 128-255 Octet Frames: 49278823
    Rx + Tx 256-511 Octet Frames: 27931206
    Rx + Tx 512-1023 Octet Frames: 26755616
    Rx + Tx 1024-Up Octet Frames: 31302857
    Net Octets: 3872916906
    Rx Start of Frame Overruns: 171387115
    Rx Middle of Frame Overruns: 0
    Rx DMA Overruns: 171387115
    Rx DMA chan 0: head_enqueue: 1
    Rx DMA chan 0: tail_enqueue: 25377864
    Rx DMA chan 0: pad_enqueue: 0
    Rx DMA chan 0: misqueued: 16048444
    Rx DMA chan 0: desc_alloc_fail: 0
    Rx DMA chan 0: pad_alloc_fail: 0
    Rx DMA chan 0: runt_receive_buf: 0
    Rx DMA chan 0: runt_transmit_bu: 0
    Rx DMA chan 0: empty_dequeue: 0
    Rx DMA chan 0: busy_dequeue: 2155088
    Rx DMA chan 0: good_dequeue: 25377737
    Rx DMA chan 0: requeue: 23083
    Rx DMA chan 0: teardown_dequeue: 0
    Tx DMA chan 0: head_enqueue: 1714455
    Tx DMA chan 0: tail_enqueue: 21764208
    Tx DMA chan 0: pad_enqueue: 0
    Tx DMA chan 0: misqueued: 21667771
    Tx DMA chan 0: desc_alloc_fail: 0
    Tx DMA chan 0: pad_alloc_fail: 0
    Tx DMA chan 0: runt_receive_buf: 0
    Tx DMA chan 0: runt_transmit_bu: 3080042
    Tx DMA chan 0: empty_dequeue: 1671870
    Tx DMA chan 0: busy_dequeue: 80335
    Tx DMA chan 0: good_dequeue: 23478663
    Tx DMA chan 0: requeue: 39
    Tx DMA chan 0: teardown_dequeue: 0


    # ethtool -S eth0 1
    NIC statistics:
    Good Rx Frames: 196764852
    Broadcast Rx Frames: 2
    Multicast Rx Frames: 0
    Pause Rx Frames: 0
    Rx CRC Errors: 41
    Rx Align/Code Errors: 0
    Oversize Rx Frames: 30
    Rx Jabbers: 0
    Undersize (Short) Rx Frames: 750
    Rx Fragments: 260687
    Rx Octets: 3636958610
    Good Tx Frames: 23478178
    Broadcast Tx Frames: 2957
    Multicast Tx Frames: 471
    Pause Tx Frames: 0
    Deferred Tx Frames: 206773
    Collisions: 265290
    Single Collision Tx Frames: 99640
    Multiple Collision Tx Frames: 69090
    Excessive Collisions: 487
    Late Collisions: 0
    Tx Underrun: 0
    Carrier Sense Errors: 2
    Tx Octets: 227623163
    Rx + Tx 64 Octet Frames: 81893348
    Rx + Tx 65-127 Octet Frames: 3081221
    Rx + Tx 128-255 Octet Frames: 49278823
    Rx + Tx 256-511 Octet Frames: 27931206
    Rx + Tx 512-1023 Octet Frames: 26755616
    Rx + Tx 1024-Up Octet Frames: 31302857
    Net Octets: 3872917178
    Rx Start of Frame Overruns: 171387115
    Rx Middle of Frame Overruns: 0
    Rx DMA Overruns: 171387115
    Rx DMA chan 0: head_enqueue: 1
    Rx DMA chan 0: tail_enqueue: 25377864
    Rx DMA chan 0: pad_enqueue: 0
    Rx DMA chan 0: misqueued: 16048444
    Rx DMA chan 0: desc_alloc_fail: 0
    Rx DMA chan 0: pad_alloc_fail: 0
    Rx DMA chan 0: runt_receive_buf: 0
    Rx DMA chan 0: runt_transmit_bu: 0
    Rx DMA chan 0: empty_dequeue: 0
    Rx DMA chan 0: busy_dequeue: 2155088
    Rx DMA chan 0: good_dequeue: 25377737
    Rx DMA chan 0: requeue: 23083
    Rx DMA chan 0: teardown_dequeue: 0
    Tx DMA chan 0: head_enqueue: 1714459
    Tx DMA chan 0: tail_enqueue: 21764208
    Tx DMA chan 0: pad_enqueue: 0
    Tx DMA chan 0: misqueued: 21667771
    Tx DMA chan 0: desc_alloc_fail: 0
    Tx DMA chan 0: pad_alloc_fail: 0
    Tx DMA chan 0: runt_receive_buf: 0
    Tx DMA chan 0: runt_transmit_bu: 3080046
    Tx DMA chan 0: empty_dequeue: 1671874
    Tx DMA chan 0: busy_dequeue: 80335
    Tx DMA chan 0: good_dequeue: 23478667
    Tx DMA chan 0: requeue: 39
    Tx DMA chan 0: teardown_dequeue: 0

  • Hi,

    You are getting a very significant number of errors CRC, collisions, DMA overflow, these entries below from the ethtool will cause a packet to drop. 

    Rx CRC Errors: 41  <-- Something in the RX path between the MAC and the PHY may have an issue.
    Oversize Rx Frames: 30 <-- What is the MTU size the test is sending?

    Rx Start of Frame Overruns: 171387115  <--- Sending packets faster than can be transferred to DDR, what is the bit rate packets are being sent?

    Rx DMA Overruns: 171387115 <-- Same issue as previous line.

    Best Regards,

    Schuyler

  • Hi Schuyler:

    The MTU of our board is 1500, MTU will not be modified during testing.

    Column C/D in the table is the rate of the test

  • Hi Schuyler

    When we used SDK 05.03.00.07 to test on EVMSK, the result also failed.

  • Hi,

    I apologize as I am still not understanding how the test is taking place. The packets are being sent by the Smart Bits machine, but how is the Smart Bits counting the received packets? Could you please describe the path the packets are taking? I agree it is does appear to be odd that the lowest bandwidth is a fairly consistent in not receiving packets. 

    Also could you please attach the results of this command:

    cat  /proc/net/snmp

    Best Regards,

    Schuyler

  • Hi,

    Since I have not heard back I am assuming that you were able to move past this issue and will close the thread for now. You can re-open it later or post a new thread if you choose.

    Best Regards,

    Schuyler