Hi Eyle, Thanks for the core, I think I identified the issue. Can you check if https://gerrit.fd.io/r/c/vpp/+/30346 fix the issue? It should apply to 20.05 without conflicts.
Best ben > -----Original Message----- > From: Eyle Brinkhuis <eyle.brinkh...@surf.nl> > Sent: mercredi 2 décembre 2020 17:13 > To: Benoit Ganne (bganne) <bga...@cisco.com> > Cc: vpp-dev@lists.fd.io > Subject: Re: Vpp crashes with core dump vhost-user interface > > Hi Ben, all, > > I’m sorry, I forgot about adding a backtrace. I have now posted it here: > https://surfdrive.surf.nl/files/index.php/s/0SUKUNivkpg9Dnb > > > I am not too familiar with the openstack integration, but now that > 20.09 is out, can't you move to 20.09? At least in your lab to check > whether you still see this issue. > > The last “guaranteed to work” version is 20.05.1 against networking-vpp. I > can still try though, in my testbed, but I’d like to keep to the known > working combinations as much as possible. Ill let you know if anything > comes up! > > Thanks for the quick replies, both you and Steven. > > Regards, > > Eyle > > > On 2 Dec 2020, at 16:35, Benoit Ganne (bganne) <bga...@cisco.com > <mailto:bga...@cisco.com> > wrote: > > Hi Eyle, > > I am not too familiar with the openstack integration, but now that > 20.09 is out, can't you move to 20.09? At least in your lab to check > whether you still see this issue. > Apart from that, we'd need to decipher the backtrace to be able to > help. The best should be to share a coredump as explained here: > https://fd.io/docs/vpp/master/troubleshooting/reportingissues/reportingiss > ues.html#core-files > <https://fd.io/docs/vpp/master/troubleshooting/reportingissues/reportingis > sues.html#core-files> > > Best > ben > > > > -----Original Message----- > From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp- > d...@lists.fd.io <mailto:vpp-dev@lists.fd.io> > On Behalf Of Eyle > Brinkhuis > Sent: mercredi 2 décembre 2020 14:59 > To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > Subject: [vpp-dev] Vpp crashes with core dump vhost-user > interface > > Hi all, > > In our environment (vpp 20.05.1, ubuntu 18.04.5, networking- > vpp 20.05.1, > Openstack train) we are running into an issue. When we spawn a > VM (regular > ubuntu 1804.4) with 16 CPU cores and 8G memory and a VPP > backed interface, > our VPP instance dies: > > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: > linux_epoll_file_update:120: epoll_ctl: Operation not > permitted (errno 1) > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: > linux_epoll_file_update:120: epoll_ctl: Operation not > permitted (errno 1) > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: > received signal SIGSEGV, PC 0x7fdf80653188, faulting address > 0x7ffe414b8680 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: > received signal > SIGSEGV, PC 0x7fdf80653188, faulting address 0x7ffe414b8680 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #0 > 0x00007fdf806556d5 0x7fdf806556d5 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #0 > 0x00007fdf806556d5 0x7fdf806556d5 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #1 > 0x00007fdf7feab8a0 0x7fdf7feab8a0 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #1 > 0x00007fdf7feab8a0 0x7fdf7feab8a0 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #2 > 0x00007fdf80653188 0x7fdf80653188 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #2 > 0x00007fdf80653188 0x7fdf80653188 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #3 > 0x00007fdf81f29e52 0x7fdf81f29e52 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #3 > 0x00007fdf81f29e52 0x7fdf81f29e52 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #4 > 0x00007fdf80653b79 0x7fdf80653b79 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #4 > 0x00007fdf80653b79 0x7fdf80653b79 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #5 > 0x00007fdf805f1bdb 0x7fdf805f1bdb > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #5 > 0x00007fdf805f1bdb 0x7fdf805f1bdb > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #6 > 0x00007fdf805f18c0 0x7fdf805f18c0 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #7 > 0x00007fdf80655076 0x7fdf80655076 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #6 > 0x00007fdf805f18c0 0x7fdf805f18c0 > Dec 02 13:39:39 compute03-asd002a vpp[1788161]: > /usr/bin/vpp[1788161]: #8 > 0x00007fdf7fa3b3f4 0x7fdf7fa3b3f4 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #7 > 0x00007fdf80655076 0x7fdf80655076 > Dec 02 13:39:39 compute03-asd002a /usr/bin/vpp[1788161]: #8 > 0x00007fdf7fa3b3f4 0x7fdf7fa3b3f4 > Dec 02 13:39:39 compute03-asd002a systemd[1]: vpp.service: > Main process > exited, code=dumped, status=6/ABRT > Dec 02 13:39:39 compute03-asd002a systemd[1]: vpp.service: > Failed with > result 'core-dump'. > > > While we are able to run 8 core VMs, we’d like to be able to > create > beefier. VPP restarts, but never makes it to create the vhost- > user > interface.. Anyone ran into the same issue? > > Regards, > > Eyle > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18289): https://lists.fd.io/g/vpp-dev/message/18289 Mute This Topic: https://lists.fd.io/mt/78659780/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
