On 3/18/20 10:35 AM, Kees Meijs wrote: > > On 17-03-2020 14:37, Thomas Goirand wrote: >> You may have notice my last upload of OVS in buster-proposed-updates. >> This upload fixes at least one of the crashes which leads to vswitchd >> taking 100% of one core. >> >> However, there's still some other issues we've experienced in >> production. Soon, we'll test the latest version of OVS 2.10, and I'll be >> able to tell if this fixes the other crash I've seen. In the mean time, >> you can try 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12+deb10u2 from >> buster-proposed-updates. > > Good morning Thomas, > > The past few weeks have been intense at least so I did not. Same for > comparing 2.10 with 2.11 code. Much appreciated you point out the > upload. > > To save valuable time our cluster is running 2.11 where possible but > it would be best to go back to the stock Debian packages. > > What other issues do you refer to? I would love to make time and test > your new build (thank you, taking a deep bow) but are curious about > other potential issues before I do. > > Best regards, > Kees
Hi, I've fixed *one* type of crash, but we saw others, with a different backtrace (which I could see using gdb). We're now upgrading to the version see here: http://shade.infomaniak.ch/buster-pu/openvswitch/ This is the top of the 2.10 branch, version is: 2.10.4+2020.01.14.b2ccc307f1+dfsg1-1+deb10u3 I don't know yet if it fixes the problem we have ... I can try to convince the release team to update to that version in Buster, but chances they accept is kind of low. Cheers, Thomas Goirand (zigo)