igsilya
commented
3 years ago It looks like you have a coredump. Could you, please, provide a stack trace? It's hard to guess what happened otherwise.
Closed rllf closed 2 years ago
igsilya
commented
3 years ago It looks like you have a coredump. Could you, please, provide a stack trace? It's hard to guess what happened otherwise.
rllf
commented
3 years ago does this help ?
igsilya
commented
3 years ago Not really, too many things are compiled out, unfortunately. Another thing is that your info locals suggests that dp_packet structure has fields that it should not have if OVS built with DPDK. Fields like base_ and allocated_ should not be there, mbuf should be there instead. But you said that the problem is with DPDK. Something is not right here. Either OVS built without DPDK or the debuginfo is from a completely different build and all the information printed by gdb makes no sense.
rllf
commented
3 years ago thx! in a reference system (ovs & DPDK) I don't see this issue and my GDB looks like this - your hint refers to "packet = { mbuf"
rllf
commented
3 years ago additional, the ovs is build from https://salsa.debian.org/openstack-team/third-party/openvswitch/-/tree/debian/2.15.0+ds1-3 and the debug package should fit but I will double check that.
fmoessbauer
commented
3 years ago Hi @igsilya, thanks for the hint regarding the ABI.
This is actually a packaging issue of debian (mixing ovs internal libraries from different builds via update-alternatives). I just created a bugreport at the project and provided a fix here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992406
IMO this issue can be closed here as this is not an OVS issue.
Best regards, Felix
Dear all, I have a ovs problem in context with LLDP and DPDK. ovs crashes when I receive a LLDP message. I think it is related to the "source" value visible in the second picture which is set to source=DPBUF_MALLOC. I have a different setup without problems and in this setup the value is set to source=DPBUF_STUB. Any idea?