On Tue, 19 Mar 2019 11:45:44 -0700 Gregory Rose <[email protected]> wrote:
> On 3/14/2019 6:59 PM, Ben Pfaff wrote: > > On Thu, Mar 14, 2019 at 03:53:12PM -0700, Gregory Rose wrote: > >> A further update on this bug. > >> > >> A reliable indicator that the bug is going to occur imminently is when this > >> junk appears in the ovs-vswitchd log file: > >> 2019-03-14T22:26:54.862Z|00006|bridge|INFO|ovs-vswitchd (Open vSwitch) > >> 2.11.90 > >> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > >> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@2019-03-14T22:37:41.219Z|00001|vlog|INFO|opened > >> log file /usr/local/var/log/openvswitch/ovs-vswitchd.log > >> > >> Removing the test of whether the eventmask is available in function > >> check-ct_eventmask() in ../ofproto/ofproto-dpif.c makes this log file > >> corruption go away and also, of course, the panic. > >> > >> I'm trying to figure out where the memory corruption in > >> check_ct_eventmask() > >> is occurring. > > Have you already tried valgrind? > > Hi Ben, I apologize for the late reply - I've been out and am just > catching up. > > Yes I have, and when I do the bug goes away. I've also run a lockdep > enabled kernel - didn't see anything there. I've enabled some further > kernel debug options and will get back to working on this now that I'm > back to work. For me, this commit [1] seems to fix the issue. ...Juerg [1] https://lore.kernel.org/lkml/20190328063600.GC16096@xps-13 > Thanks, > > - Greg >
_______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
