Open GrzegorzKania-lime opened 1 year ago
Hi, do you have a coredump or a stack trace for the crash? Otherwise it's hard to tell what went wrong.
If you suspect a driver bug, it's better to open a bug for DPDK instead.
Hello, I have encountered a similar issue on the E810 network card, which was discovered upon opening the new version. It appears to be caused by the newly introduced checksum offload.
2024-03-04T10:10:45.687Z|00274|dpdk|WARN|ice_interrupt_handler(): OICR: MDD event 2024-03-04T10:16:05.137Z|00275|dpdk|WARN|ice_interrupt_handler(): OICR: MDD event 2024-03-04T10:16:06.199Z|00276|dpdk|WARN|ice_interrupt_handler(): OICR: MDD event 2024-03-04T10:16:08.247Z|00277|dpdk|WARN|ice_interrupt_handler(): OICR: MDD event 2024-03-04T10:16:12.279Z|00278|dpdk|WARN|ice_interrupt_handler(): OICR: MDD event 2024-03-04T10:16:16.024Z|00483|netdev_linux|WARN|error receiving Ethernet packet on br-int: Invalid argument 2024-03-04T10:16:16.024Z|00484|dpif_netdev|ERR|error receiving data from br-int: Invalid argument
On Mellanox network cards, everything is normal, but there are issues with the E810. I'm using DPDK version 22.11, and it seems to be a problem on the DPDK side. @igsilya
Hey, during performance testing of mine OvS deployment, I've stumbled across the problem. The type of test that I am doing is RFC2544 for small packet sizes, but for many L3 flows (i.e. 16k).
Here is my general OvS configuration:
Bridge config:
All dpdkvhostuser interfaces are connected to l3fwd application, that is responsible for looping back traffic to the OvS and further to traffic generators. Nothing happens if OvS set:
ovs-vsctl set Open_vSwitch . other_config:hw-offload=false
but, switching to:ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
crashes the OvS, along with removing all dpdkvhostuser interfaces from the bridge.While doing the tests, the first two iterations of binary search seems to work with no problem, but in the third, OvS crashes with the following dump:
It looks like the card cannot delete flows from the inner offload table. The issue is not reproducible without dpdkvhostuser interfaces (simple phy0 <-> phy1 traffic loopback will not show the issue).