AM5716: [NIC issue] The NIC's driver occur error if we down/up the network card for 2 days.

Hi,

How are you sending ethernet data. Which application are you using for that?

Regards,
Tanmay

Dear Tanmay,

I didn't run any applications, just connected the network port to the switch, which may have had low-frequency network communication with AM5716. On the contrary, after unplugging the network cable, there will be no errors when I keep up/down the network port

Hi,

zhicheng zhang said:

ps. The network card is transmitting network data during down/up

So, in your statement above, its just the background data and not any data you are specifically sending?

Also, in your application, you are scheduling interface down every 100ms and then once every 500ms, you are bringing the interface up. When you have the cable connected, I am guessing the interface won't be able to come up in 100ms when the next link down command is scheduled. So, the links would be always down when this script is executed.

Is this analysis correct?

Can you please help me the understand the need for such a test.

Meanwhile I am trying this out and i will let you if I am able to reproduce this on my end.

Regards,
Tanmay

Dear Tanmay,

Yes, its just the background data and not any data you are specifically.

After completing the experiment at hand, we can conduct another experiment to expand the 100ms like 1s.

Hi,

Have you also tried this experiment by just bringing the interface down when it is up and bringing the interface up only when it is down?

Regards,
Tanmay

Dear Tanmay,

Yes, we did. We run the following script and it got bad result like before.

Dear Tanmay,

I would like to share with you the results of my analysis over the past few days, I have two questions that I would like to ask you：

1) The kernel error mentioned in the main text of my case is due to an exception that occurred during a network storm, and this error code is the driver of the pruss network card. After both the cpsw network card and the pruss network card suffer from a network storm for a period of time, the pruss network card will report this kernel error. In addition, when the network storm stops, the cpsw network card can still work normally, but the pruss network card cannot work properly. I want to know why? is it because the cpsw network card cannot withstand network storms?

2) When encountering a network storm, if i execute ifconfig eth1 down, it will block in emac_pru_stop()->disable_irq(emac->rx_irq) function. If I replaced the disable_irq(emac->rx_irq) function with disable_irq_nosync(emac->rx_irq), then it will no longer block, and the network card can be down. So I would like to ask if I can replaced the disable_irq(emac->rx_irq) function with disable_irq_nosync(emac->rx_irq)?

Hi,

The ports which you are toggling (eth1 and eth2), are they cpsw ports or pru ports. I was assuming them to be cpsw ports. But from the source code you are updating, they seem to be pru ports. Can you confirm.

Can you please also explain to exactly what are you trying to test with these experiments here? I might be able to make some easier to replicate setup which would help me with debug. Here is what I understood so far:

• After toggling the interfaces for a long time, you are observing a kernel panic.
• There is some data being transmitted in the background
  • I am not sure if this data is being actually sent or not.
  • As you are toggling the link state pretty fast (~100ms), are you sure the link is coming up and you are able to send/receive data on the link?

I didn't understand, why are you doing this experiment and also what is the network storm which you are talking about.

Regards,
Tanmay

Dear Tanmay,

Because we haven't communicated for many days, there are some issues that I need to raise with you again. There are also some things that you don't need to pay attention to, such as 100ms.Let me tell you again about the new problems we have encountered. We only need to discuss the following two issues:

1)When the pruss network card and the cpsw network card receive a large number of network packets in an instant. For example, within 10 minutes, both types of network ports receive 1 million packets. When the network packets stop filling these two types of network ports, the pruss network card cannot be used normally, while the cpsw network card can be used normally. So I want to know if the stability of the pruss network card is not as good as the cpsw network card?

2)If I replace the disable_irq(emac->rx_irq) function with disable_irq_nosync(emac->rx_irq) in pruss driver code, Will this change affect the performance of the pruss network card?

Hello Tanmay

Are there any new updates

My guess is, will this high traffic cause too much load on the CPU, causing a kernel panic? However, it is not clear that the network interface using CPSW will not have this problem, is it the operation mechanism of the PRU network interface? Or the driver issue?

Since the customer is currently using SDK6.03, are there any changes we have made to the PRU driver in subsequent SDK releases that address this issue?

Looking forward to your reply.

Hi Tanmay

Any update? This issue is very urgent, please give some comments as soon as possible. Thanks

Hi Ethan,

Sorry for the delay.

Is still issue still reproduced?

Regards,
Tanmay