Package: openvswitch-switch Version: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
Hi there, We extensively use Open vSwitch in our OpenStack and Ceph environments and noticed version 2.10 "eats up" a CPU core with 100% utilisation on buster. For example: > 2020-01-19T23:00:06.362Z|148220|poll_loop(handler130)|INFO|Dropped > 734849 log messages in last 6 seconds (most recently, 0 seconds ago) > due to excessive rate > 2020-01-19T23:00:06.362Z|148221|poll_loop(handler130)|INFO|wakeup due > to [POLLIN] on fd 23 (unknown anon_inode:[eventpoll]) at > lib/dpif-netlink.c:2786 (99% CPU usage) Other users experience a similar problem on other distributions as well. As it seems this is a bug resolved in version 2.11. Recently I manually built the 2.11 package from bullseye and installed that. Although the build is not perfect (needed to add some files to debian/not-installed from bugtool) the resulting packages install well and the CPU usage is back to normal values. For reference, I added the following files: > usr/share/openvswitch/bugtool-plugins/system-configuration.xml > usr/share/openvswitch/bugtool-plugins/system-configuration/openvswitch.xml > usr/share/openvswitch/bugtool-plugins/system-logs/openvswitch.xml > usr/share/openvswitch/bugtool-plugins/kernel-info/openvswitch.xml > usr/share/openvswitch/bugtool-plugins/network-status/openvswitch.xml > usr/share/openvswitch/bugtool-plugins/network-status/ovn.xml Other than that, backporting seems trivial. Is upgrading to 2.11 in stable a viable option? (The backports team felt this bug is severe enough and the upgrade is only very minor.) Thanks in advance! Best regards, Kees
