[ovs-dev] Segfaults when loading openvswitch.ko

Lynch, Daniel C-Daniel.Lynch1 at charter.com
Tue Mar 30 21:11:49 UTC 2021


This is a long shot, but I'm hoping that someone will have some insight for an issue that we are encountering. We are using an older version of Open vSwitch (2.7.1) with LEDE 17.01 on the Atom processor of a Puma7 SoC (MaxLinear SDK R7.2.1), and are using Open vSwitch 2.7.1. Yocto build environment.

Unfortunately, we don’t have the control to upgrade to the latest version of OpenWrt, and with the kernel we have, we can only get Open vSwitch 2.7.1 or 2.7.3 to compile. Attempts to compile with version 2.15 fails with error: 'struct inet_frags' has no member named 'rnd'.
We need to use the openvswitch.ko and vport*.ko kernel modules to bring up ovs bridges, so we have enabled the lines
   EXTRA_OECONF = "--with-linux=${STAGING_KERNEL_DIR} KARCH=${TARGET_ARCH}"
in openvswitch_git.bb and openvswitch.inc.

We have ovs bridges br-wan and br-home set up, and they get IP addresses assigned during bootup. But when the Intel Logger starts up, it reports several segfaults, and we lose connectivity with the backhaul. After that, we periodically get reports of segfaults in liblogger.so (the Intel logger library).

We found that the default gateway gets cleared whenever this segfault in the logger occurs. If we set it back up, we have WAN connectivity again, but only until the next time the logger segfaults.

I’m asking about this here because the segfaults occur only when openvswitch.ko is loaded. If we unload it, the segfaults stop.

Does anyone have any suggestions as to how we can resolve this?

Dan Lynch
E-MAIL CONFIDENTIALITY NOTICE: 
The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.


More information about the dev mailing list